It’s also massive and one of those perpetual beta situations that won’t ever be finished. And it has that stupid shader language. Missed chance, the API isn’t bad.
I won’t defend the state soup, but there are upsides: the GL api has no structs which makes it easier to port the API to different languages and environments.
The state model isn’t nearly as much of an issue for the fixed function architectures it was originally developed for, you can see how adherence to the extension mechanism and the resulting design by committee left its marks. Microsoft didn’t have those constraints.
Iirc it was a stupid C-suite decision to use Frostbyte across EA studios. It never made much technical sense and DICE lacked the bandwidth and capital to support so many teams and usecases.
Yes after the success of frostbite around Bad Company 2 and Battlefield 3 or so, EA decided it should be used in everything. Not unlike the mistake Capcom is making with REngine right now, if the performance woes of Monster Hunter Wilds and Dragons Dogma 2 are anything to go by.
Pretty sure there was even a Need for Speed game on Frostbite which was... huh.
I worked on three of them! While there are some serious issues with Frostbite and everyone loves blaming it for everything, its role in sabotaging huge projects is definitely overblown.
There are some issues with workflow and it is true that the UI definitely was, as many at EA said, "by programmers for programmers". But it's a very capable engine in the right hands.
That said, I'd pick Unreal any day for a AAA project and Unity or Unreal for smaller projects.
cool, i think Frostbite is really pretty honestly. performs well in BF but ive not played other games that use it knowingly.
Why would you pick unreal? It seems a lot of games made in it suffer performance issues. In my mind its a really unwieldy engine. (ofc, because its so feature packed, and perhaps because i am no professional engine dev :-))
For a professional project with at least 30+ developers the complexity of using Unreal is necessary and on par with any competent engine. In fact, I feel it is often much easier to do things well in Unreal.
I like Unreal because it's really quite intuitive and ergonomic for larger productions, fairly well documented, and has some of the coolest tech in the industry. Their rendering pipelines are beautiful and a joy to work with and I could rant all day about my love for Nanite and Lumen. It is light years ahead of Unity and much easier to understand and modify than Frostbite.
I will say that Unity has better support out of the box for custom shaders and compute than Unreal (and Frostbite).
Now, you mentioned performance. Funny thing: performance has been my primary professional concern for the last six years of my career. Unreal itself performs very well if you use it correctly and has really good documentation for best practices as well as amazing tools for measuring performance and indicating what is wrong. The tools in Frostbite were very lackluster. Unity has some fairly good stuff. Unreal feels so far ahead.
I believe the reason there are more visible Unreal games with performance issues is because there are a lot more noteworthy ambitious productions in Unreal. That means games which push what they can deliver, and often don't quite get there. And for smaller productions it's likely just a matter of less experienced teams not following the best practices or cranking settings up to 11 without proper performance budgeting.
You mean the prices are going up, so people can afford to keep the housing empty for more time to get a better price. That's not the same if you think about it.