Unity's new price structure and how it affects Godot

It could, but I'm not that optimistic about it, if Adobe is anything to go by. When Adobe announced their CC only offering, there were plenty of mad people on their forums and elsewhere, who were skeptical that paying forever just to use a software tool was a good idea (and because of things like price hikes, and no incentive to offer useful features because they're going to get paid anyways). Some of those fears were not completely unfounded, but in the end, the skeptical people didn't exactly make that much of a dent in Adobe's pockets--sure they're probably still not using Photoshop, and I don't doubt a few of them managed to find other programs like Krita, except that Krita has more specialization than Photoshop, so that leaves a few other PS users looking for something else (eg, if you're not using PS for digital painting). The other problem is that this generally only affects freelancers and hobbyists--companies who have more money and need to rely on something dependable rather than affordable won't see the point in using free software, especially if they think it's anything at all like GIMP (and some hobbyists don't even bother to give other free software tools a chance because they think it will be like GIMP as well). And people looking to get hired by these companies won't be putting free software tools on their resume either.Don't get me wrong; I'd love it if people woke up and realized the implications of renting software tools rather than having the choice to own your tools forever or choose when or if you want to upgrade them, but there's just too many people and groups at this point who think they either don't need the switch or don't consider the free software alternatives to be adequate for their needs, and won't even try it. We do still need to convince them that it's worth it; not rely on the fact that some other big software company has decided to do a rental only model. It can help start people looking elsewhere, but it's not going to have as large an impact as it sounds like it could.

This will be a great thing, if/when Godot supports C#. If I was one of the Godot devs i'd make that a priority right now, to make the most of the exodus that will certainly come from Unity Bay.I'm not a C# fan, i think .net support will bloat the engine, and i really like GDscript, but the reality of the world is a lot of devs out there know and love c#...And it will bring the world of static typing to us, which will make a lot of users happy.Also, C# is in the middle between GD and C++ in a lot of ways, so maybe it's worth it regardless of whatever.Right now it's a wait and see. Frankly, the moment it supports C# i think the internet will take care of spreading the news. Microsoft for one is always keen on the latest tech that supports their turf.

[quote author=Kiori link=topic=15572.msg16527#msg16527 date=1464813525]This will be a great thing, if/when Godot supports C#. If I was one of the Godot devs i'd make that a priority right now, to make the most of the exodus that will certainly come from Unity Bay.I'm not a C# fan, i think .net support will bloat the engine, and i really like GDscript, but the reality of the world is a lot of devs out there know and love c#...And it will bring the world of static typing to us, which will make a lot of users happy.Also, C# is in the middle between GD and C++ in a lot of ways, so maybe it's worth it regardless of whatever.Right now it's a wait and see. Frankly, the moment it supports C# i think the internet will take care of spreading the news. Microsoft for one is always keen on the latest tech that supports their turf.[/quote]How difficult is it to implement another programming language into a game engine? I like C# also, but I wouldn't think the developers would really consider adding this to the engine. If they would, then that'd be pretty amazing on top of the other things they're doing. I'd use the language too over GDscript.

[quote author=Kris link=topic=15572.msg16531#msg16531 date=1464814618] but I wouldn't think the developers would really consider adding this to the engine.[/quote]They said they would on the facebook group, or github, somewhere. I believe it's in the to-do list.

[quote author=Kiori link=topic=15572.msg16532#msg16532 date=1464815169][quote author=Kris link=topic=15572.msg16531#msg16531 date=1464814618] but I wouldn't think the developers would really consider adding this to the engine.[/quote]They said they would on the facebook group, or github, somewhere. I believe it's in the to-do list.[/quote]Color me impressed! I would totally follow that development.

About .net plans:[img width=417 height=57]http://s33.postimg.org/tc6erh90v/screenshot_www_facebook_com_2016_06_01_19_47_02.png[/img]

In a more recent statement he also explicitly mentioned c#.And I believe he said it would come sooner than GDScript static typing, but don't quote me on that. :)

Reading about .NET support makes me kinda worried.. Isn't it Windows only?

[quote author=danjo link=topic=15572.msg16536#msg16536 date=1464824111]Reading about .NET support makes me kinda worried.. Isn't it Windows only?[/quote]No, not necessarily. There's plenty of open-source alternatives that basically allow you to use C# and .NET on Linux and OS X as well, but they're kind of iffy and tend to lag behind all of the updates. At least, that's what I think MonoDevelop is doing, but I could be wrong. I think Unity has indeed probably forced a good amount of users away. Those prices are steep, especially when there's so much competition right now. UE4 is still, for the foreseeable future, completely free (except for the 5% royalties you have to pay to Epic Games), and Godot is becoming significantly more popular this year as well. We'll see what happens with Unity. As others have said, when Adobe originally announced Creative Cloud, many people were upset. However, it let me use Adobe Premiere Pro for a small project for one month (I paid $20 to essentially "rent" the program), and I really liked it. If I were an independent filmmaker I would probably use it extensively, as $50/month is quite easy to fit in a budget, as long as you plan accordingly. I don't think the same model works with game development software though. Time to wait and see!

Yeah, I am not too thrilled about c# in Godot at this stage, but definitely keen on static typing of gdscript if it yields good performance gains. I feel that it is too early in the life of Godot to get competing languages and it may split the community at a crucial stage.Don't get me wrong, I like c#, but the implications for multi language support on documentation, tutorials and the higher level of bug reports is worrying. Think of the early days of Unity with the 3 potential languages...of course almost everyone uses c# now, but it can muddy the waters.Anyway, I am a fan of Python and gdscript, so I hope it remains the dominant Godot language.

I'm agree with zendorf I'd rather improvements on GDScript performance and features.People who are comfortable with C# will have no difficulties to learn static GDScript.We should not worry about people who want to be game developpers without making some learning efforts.

I'm happy to see more ppl being supportive of GdScript.+1 for continuing improvements on the GD front, be it static typing or whatnot.

Considering that GDscript and its built-in editor formed a key reason for me to come to Godot from the BGE, I too think the priorities in terms of programming performance and features should be centered on it.Having GDscript remain the centerpiece would also ensure that Godot remains a very lightweight engine (even as it becomes far more powerful in the 3D front with the future 3.0 release).

Unity tried to "fix" their problems with the new pricing structure, but in my opinion they're still taking a giant leap of faith. Basically, all they did was increase the revenue cap for the plus plan from $100k to $200k. That's it. A lot of people are still very angry, and honestly, so am I, as now I have no incentive to stay with Unity in the long run. I was working on a project in there but I guess I will just have to work on porting it to Godot. The only reason I hadn't yet was because I was quite far along in coding, but it's definitely worth it to change it over to Godot.

I thought with the changes to "plus" removing the splash screen and revenue increase to 200k, now it's pretty good. You're talking $420 a year to do whatever you want in any platform in the engine, with all the features.If you're making real money off of games that's not too bad frankly. Until then you can use personal.I would choose Godot for other reasons, not financial.Reasons like engineering(I mentioned before), OSS, and frankly the fact that I have a bigger trust in the Godot devs, than in the Unity devs.Unity goes around i circles when adding new features...

All good points. I'm just upset because I had invested tons of money into Unity via assets, and now they have changed their pricing structures (again). $420 a year really isn't so bad, but when you consider that the Unreal Engine (currently leading in features and graphics) and Godot are both free, it's really surprising to me that Unity would pick now to change their pricing strategies so much.

The change in strategy for pricing is good news for their current users, but they still have the monumental task of how to keep parts of Unity's architecture from breaking down whenever they make a change.Reading their forums, it looks like Unity's developing the infamous reputation of seeing new regressions pop up whenever a bug is fixed (even in their bugfix releases). The roundabout bugfixing/regression cycle may also be what's preventing them from getting to the point where they can confidently release version 5.4 so as to not see a lot of people complaining about how broken their projects are now.It seems to me that the biggest challenge for now is getting Unity's architecture to a more stable state (and what's not helping is the bureaucracy that plagues their bugfixing process, noting just how long it can take for a fix to wind its way through the system and the large amounts of information they expect from users before it's even considered).I know with Blender at least they have a high priority on fixes all through the release Cycle. The Godot devs. meanwhile have a different approach (they don't do it as much in the heavier stages, but boy does the bug/issue count fall like a stone once the major targets are in). Another good thing shared by the Blender and Godot projects is that the developers actually recognize just what systems could use a full rewrite (though it can take a while due to resource availability and the size of certain systems).

Hmm, I didn't notice that the revamp of the revamp clarified that you can still use the Personal Edition until you hit 100k of revenue. So it looks like I can finish my current project in Unity after all. This is good, but I still will eventually port it to Godot, once I learn how to use Godot's file system. It's a bit more complicated than in C#.  :P EDIT: Well, actually, it doesn't look like the file system in Godot is really that much more complicated, it's just different. I have been going over the example in the documentation again and again, and it seems fairly straightforward. I think I will work on porting my game to Godot now, as I don't really feel comfortable in Unity anymore. I want to give Godot as much of a boost as I can. So that's what I will do!

@BOYou will have to adjust to some concepts and ideas, but all in all it's a worth while task. I mean think about it, you'll be using a free open source engine, which is effectively yours and limit-free. So specially considering the long term, it's really worth it.