Earlier quoted context omitted.
Or move to Godot/C#.
Doesn't do game consoles.
GODOT developers are trying to do it via https://w4games.com/. But not sure if it's ready
So You've Decided to Move from Unity to Unreal Engine
101–110 of 152 posts
Re: So You've Decided to Move from Unity to Unreal Engine
#102Earlier quoted context omitted.
Earlier this year we completed a huge refactor that involved, among other things, getting us almost 100% off blueprints (now we use them just for little bits of presentation logic in UIs). BPs are amazing for discovering how to use the engine - they provide a sort of guided exploration of things, especially when you don't know what you don't know. For us they really, really, really broke down when it came to version…
It's nice to hear from someone with real experience. Blueprints clearly delivered negative ROI. In general they probably do. This is the worst time to be advocating for visual programming, considering the first truly groundbreaking application of AI is going to be in writing code. The real question is, did C++ give you any real ROI either? Probably not, it probably only got in the way compared to the way Unity is arc…
Blueprints are extremely useful in prototyping at the very least, not just in the initial stages of development but for adding new systems. There is nothing wrong with them and the idea that LLM’s are going to replace blueprints is ridiculous. Sure, you will be able to have them write a block of collision code, but gamedev is one of the most complicated fields in terms of having an understanding of what your state is and what references what.
LLM’s can spit out code without understanding the problem, but understanding the problem is 99% of gamedev
Re: So You've Decided to Move from Unity to Unreal Engine
#103Unity offices are closing due to death threats. Things going smoothly after their pricing change. https://www.bloomberg.com/news/articles/2023-09-14/video-gam...
What up with the gaming community? I get the the players being carried away or be from a special demographics but aren't the game professionals aware that they are doing business? Underpaid developers, death treats after some pricing changes. Wow.
"The gaming community" consists of an insanely large number of people. Some percentage of people on Earth are willing/crazy enough to use death threats to get their way. The gaming community is large enough that that percentage manifests itself in the form of death threats being used. The question isn't so much "what's up with the gaming community" as it is "what's up with this small percentage of humanity."
Re: So You've Decided to Move from Unity to Unreal Engine
#104Re: So You've Decided to Move from Unity to Unreal Engine
#105Earlier quoted context omitted.
I'm surprised they can sustain such low pricing
The side benefits are enormous. Its not like Unity where Unity fees are the bread and butter for the company.
And with respect for indie games the vast majority of them barely make money.
Unity was trying to squeeze water from a rock.
Re: So You've Decided to Move from Unity to Unreal Engine
#106Earlier quoted context omitted.
What up with the gaming community? I get the the players being carried away or be from a special demographics but aren't the game professionals aware that they are doing business? Underpaid developers, death treats after some pricing changes. Wow.
The developers are revolting.
Rent goes up 200%: [we sleep]
Unity changes pricing: [ we riot ]
Re: So You've Decided to Move from Unity to Unreal Engine
#107For any Unreal experts:
I'm an aspiring graphics/engine programmer. I don't really care about making games, I'm more excited about improving the tools available. My feet are wet enough with C++ that I think it would be good to start digging around in/ modifying/ contributing (likely merely attempting 'small' stuff like bugfixes) to the Unreal codebase. I've been doing so lately with Blender's codebase lately with some success, so large software isn't totally new to me. Blender is mostly C though, hence my interest in seeing how things are done in Unreal.
Any tips/ resources/ advice/ quirks I should know that you can share would be greatly appreciated!
Re: So You've Decided to Move from Unity to Unreal Engine
#108Unity offices are closing due to death threats. Things going smoothly after their pricing change. https://www.bloomberg.com/news/articles/2023-09-14/video-gam...
What up with the gaming community? I get the the players being carried away or be from a special demographics but aren't the game professionals aware that they are doing business? Underpaid developers, death treats after some pricing changes. Wow.
This is not necessarily the gaming community. If anything, the devs who are currently revolting are usually pretty critical of said community
Re: So You've Decided to Move from Unity to Unreal Engine
#109> It's free until you make a million bucks USD, and only after that is it 5% gross, and only in quarters where you made more than $10,000 USD. So most folks never end up paying anything. There are no subscription fees or anything. To clarify, if you make a million bucks, and then one dollar, you only owe them five cents. It sounds very fair to me, what are the general thoughts here?
What happens when your business has a portfolio of products/services over multiple departments, spanning various platforms, and only one consumer mobile app uses Unity for an augmented reality component that's not a core offering (premium feature)?
Should Unity still be entitled to the same cut?
Re: So You've Decided to Move from Unity to Unreal Engine
#110> I heard Blueprint sucks! > Blueprint actually rules. Look, I get it - why would a visual scripting thing be good? They're all shit! I agree. > Blueprint is the only one that's any good. It's amazing. It will also help you learn the engine. Everything you do there will be applicable to C++. No matter who you are, you should start in Blueprint. It's 100% true that you can build an entire game in Blueprint. Yeah, with…
Blueprints have terrible performance. They just do. Even trying to compile them into c++ doesn't work well. Blueprints run at least 100x-1000x slower than equivalent c++. This isn't even discussing working with multiple coders and version control, which is also a disaster. If you are making a simple game then they can work. If you aren't then they are not great.
>Blueprints run at least 100x-1000x slower than equivalent c++.
they are slower but unless you are doing literal math in the blueprints this is a huge exaggeration... which is exactly what one AAA game I worked on did. sigh. And they wondered why we couldn't hit 60fps (tho, that wasn't even the biggest detractor to performance).
Now, BP's in general usage when you're not doing literally everything in them is about 10x slower. But when you properly use blueprints, you can mitigate this a lot. BP's in a large project work best when you expose existing c++ code to BP and make sure any designer code is piped through c++ first. The main exception tends to be UI code, but UI is rarely a performance bottleneck in large 3D games to begin with.
>This isn't even discussing working with multiple coders and version control, which is also a disaster.
yup, that's my 2nd biggest gripe. Nothing worse than trying to submit code and the BP you changed one node in is locked, with the owner of the lock being out for the day.