Mono for Unreal Engine • Hacker News Board

Re: Mono for Unreal Engine

#91

Post by gillianseed » Sat, Oct 25, 2014, 11:03 AM UTC

mnglkhn2 wrote: post #88

gillianseed wrote: post #82

Earlier quoted context omitted.

>We only require licensing for uses of Mono and Moonlight on embedded systems, or systems where you are unable to fulfill the obligations of the GNU LGPL. In other words, you have to pay a license fee for shipping the Mono runtime in a proprietary game, which is what Unity does. So Unity has negotiated a license deal with Xamarin for the Mono runtime version they use, and if they want to use a newer version they will…

Unity has negotiated a license with Novell. Now they would have to do it again with Xamarin for the newer version of Mono. But we don't know if Unity was really nice to the Mono guys when Novell pushed out what would quickly become Xamarin. As always, if it were only money things would be simpler. But if there is some beef things will drag. Plus, Unity has forked Mono and they contribute to their own internal version…

>Unity has negotiated a license with Novell. Now they would have to do it again with Xamarin for the newer version of Mono.

Ah, so the deal was before Xamarin bought the rights to Mono from Attachmate/Novell, I didn't know that.

>At the same time they are working hard on their own proprietary il2cpp (to export to C++). The writing is clear: they will drag things as long as possible with using their old version of Mono until they are able to switch to il2cpp.

From what I understood they would still ship Mono as part of Unity (as in development framework), however what they want to avoid is the license costs that comes with shipping the Mono runtime with each Unity game, hence il2cpp, but perhaps I'm mistaken here ?

Re: Mono for Unreal Engine

#92

Post by gillianseed » Sat, Oct 25, 2014, 11:09 AM UTC

the_why_of_y wrote: post #87

gillianseed wrote: post #82

Earlier quoted context omitted.

>We only require licensing for uses of Mono and Moonlight on embedded systems, or systems where you are unable to fulfill the obligations of the GNU LGPL. In other words, you have to pay a license fee for shipping the Mono runtime in a proprietary game, which is what Unity does. So Unity has negotiated a license deal with Xamarin for the Mono runtime version they use, and if they want to use a newer version they will…

You can bundle LGPL libraries with proprietary applications quite easily; it just has to be possible for the user to replace it, which is rarely a problem because the usual situation is that your proprietary code sits "above" the LGPL library. But reportedly Apple does not allow LGPL in its app store for some reason.

Well there are likely lots of potential markets where a prerequisite of allowing the end user to swap out LGPL libraries won't be accepted (sadly), not only Apple but the consoles as well, so from that perspective Unity needs to buy a license which allows them to forego the LGPL requirements.

Re: Mono for Unreal Engine

#93

Post by mnglkhn2 » Sat, Oct 25, 2014, 1:22 PM UTC

gillianseed wrote: post #91

mnglkhn2 wrote: post #88

Earlier quoted context omitted.

Unity has negotiated a license with Novell. Now they would have to do it again with Xamarin for the newer version of Mono. But we don't know if Unity was really nice to the Mono guys when Novell pushed out what would quickly become Xamarin. As always, if it were only money things would be simpler. But if there is some beef things will drag. Plus, Unity has forked Mono and they contribute to their own internal version…

>Unity has negotiated a license with Novell. Now they would have to do it again with Xamarin for the newer version of Mono. Ah, so the deal was before Xamarin bought the rights to Mono from Attachmate/Novell, I didn't know that. >At the same time they are working hard on their own proprietary il2cpp (to export to C++). The writing is clear: they will drag things as long as possible with using their old version of Mon…

For them to invest serious resources into a Mono fork and also in a proprietary solution (il2cpp) shows that they do not believe in a deal for a license of their liking, whatever the reasons: interpersonal or purely monetary.

Re: Mono for Unreal Engine

#94

Post by coldtea » Sun, Oct 26, 2014, 10:27 AM UTC

davidjade wrote: post #52

yulaow wrote: post #49

Earlier quoted context omitted.

They just need to make two different price plans: you are a corporation? Here the corporation pack. You are a alone dev? Here a very lowered-price alone dev pack. It is not that hard, just put a clause in the license that oblige the corporations to buy their related pack

Or maybe just charge more for the 2nd and later license seats. That may make it even easier to get business to go all-in. There really should be a one-man shop deep price break. I've used the iOS Pro edition for years since I got grandfathered in for my small iOS app but I don't come anywhere near to breaking even with that so I can't consider adding on Android at full price. I've love to but since I have Pro iOS I c…

On the other hand, if you aren't earning at least 10 * $1800/yr, are you really a professional games programmer?