koobas.hobune.stream
Another Basic and Pro License Question
I am working on some game projects with some friends of mine. We are using the Basic Unity license. That is all we need and will work fine.
Now I have the great privilege of being able to start using Unity Pro at work.
The problem is that I have heard that once you open a project using the Pro version you can't share it with someone who is using the basic license.
So how do I install and use the Pro version on the same computer that I am working on my Basic license projects with?
Sorry I didn't specify. I am using a $$anonymous$$acbook Pro and OSX 10.8. I wish I could afford to buy a second $$anonymous$$ac, but can't.
There is no actual Pro version...there is only one Unity app, so there's nothing separate to install. Pro is a license. There are no technical issues opening a project made with Pro in Basic, since again there is not any such thing as a "Pro project". Any Pro features used are simply not available if opened on a machine with a Basic license.
The issue is one of licensing, since it's against the agreement to mix Pro and Basic licenses on the same team. I think it's a bit of a grey area as to whether what you have is an actual "team" or not, but if you refrain from using any Pro features on the project that you're sharing with your friends, I imagine that might satisfy the conditions of the license.
The 2 "$$anonymous$$ms" of people and their projects will NEVER meet or be working on the same projects. They are 2 totally separate groups of projects.
The problem is if I open a Basic project with the Pro version I am told that my other $$anonymous$$m members will not be able to open them using the Basic version any more. $$anonymous$$y friends and I who are using the Basic license share the project files using SVN.
So the question is how can I open and work on the Basic projects and share with my friends working on the Basic projects and also work on and share the projects with my co-workers who are using the Pro version all on the same computer?
The problem is if I open a Basic project with the Pro version I am told that my other $$anonymous$$m members will not be able to open them using the Basic version any more.
As I mentioned, that's not the case. A project doesn't store license information and doesn't know if it someone who had a Pro license worked on it or not.
Oh, that is news to me. I was told that was the case. I will have to install the pro license I have and see if one of my friends can open it with the basic license installed.
Thank you.
I installed my Pro license, opened my project and made a change to one of the scripts.
I didn't notice any changes to any other files when I looked in SVN, so I believe I am good to go.
This is by no means a definitive test, but unless I have trouble down the road I think I am good to go.
Thanks for the help!
Sorry to bump a 4-year old thread, but this answer is high up on Google search and I would like to clarify..
Your projects does, in fact, store your license information. Every asset has a corresponding meta file, and in each of those meta files is an entry called licenseType followed by your subscription. I don't believe it causes any actual damage to mix these, but it should be avoided if possible.
