PC to MAC/MAC to PC

I have what I feel is a complicated question. I did search but found no answers but I am sure someone will reply with a link… But anyway, I am working on a project with a few people I met online. I am doing this mostly to learn so I purchased that indie version of Unity. I am on PC and they are on Mac OSX and plan to release the game on Mac. I will not corrupt anything by doing this correct?

Also they are using PRO and I am not. Will that effect me if the files originate in pro?

In theory, everything should just work.

The question is: how are you going to be sharing files? You can only use Asset Server with a Pro w/ Asset Server license.

Read the EULA, you can’t work on the same project with a team and mix between PRO and Indy, so you can’t code for the same game they are working on to help them and only use Indy. Now, if you are only using Indy and not ‘helping’ them out but writing your own stuff for you, then that is ok, but Higgy has mentioned elsewhere that licenses can not be mixed which is what you are doing.

Well we are not using the asset server we are just using a subversion server to share the files. That had been suggested and then I told them I do not have pro.

But I noticed pro file assets including reflective water and security cameras and indie is not supposed to support that…

This is not for a production game and I interpret the EULA to be protecting that part of the production. You require PRO to make a fully produced game that is licensed to be sold.

I am helping on a project that is for education purposes.

It is a matter of sharing resources in the same project or working collaboritively on the same project with mixed environments. Indy has about 90% of what Pro has if truth be told, and you could write script files and test them in Indy and pass them to a person working on the Pro. The license is their to keep a team of people from buying 10 indy licenses and 1 pro license then using the 1 pro licnese later to only add in what is needed from pro and build / deploy on pro.

You can easily make unity assets in Indy and give them to a person with pro and they can use them, they can make assets and give them to you and you can use them, you just can’t use any advanced features. The pro and indy are the same binary code base, only the keys split features out.

And you can sell anything you make with Indy just like a person can do with Pro, you just have the Unity logo / watermark thing in Indy produced for sale.

I recommend you get with Higgy before you get to involved.

The actual license agreement says that:

I’m not a lawyer, but it sounds to me like they can work together as long as they aren’t a company or an incorporated entity.

Yes, you can import Pro assets into an Indie project with no problems, it’s just that they won’t do anything.

–Eric

“A company, incorporated entity, or individual may not license both Unity Pro and Unity Indie at the same time.” and per this quote he is technically being added to the “team” and as a “team” member, he is part of the “company” like I said, get with Higgy, area is to grey.

Let’s be clear in reading the above (note the parts in bold). If you are working as a group of individuals then you are neither a company, nor an incorporated entity nor a single “individual”. So if you meet folks online, and you all want to work together, and you have a mix of licenses (Indie/Pro) then that’s fine, go for it. Another example would be you as a contractor with Indie, you can do work for a company that owns Pro as the mix of licenses is again not owned by one company, nor are they owned by one incorporated entity nor are they owned by one individual.

So foundre, there is nothing about our licensing that would prevent you from working with those folks despite your owning Indie and them owning Pro. You will however have to think about the handling of feature usage, notably if they use Pro features as those won’t work for you.

FWIW, whether you’re doing a commercial game, an educational game or whatever, none of that impacts our license restrictions. We will not sell schools one copy of Pro and four Indie, they gotta buy all of one or all of the other. You can work for a non-profit doing internal projects only, we still will hold that entity to the license requirements: no mixing. So the nature of your work (commercial production, educational title, whatever) isn’t relevant at all with respect to the “no mixing” part of the EULA.