That's like saying "car's aren't too hard to build once you understand the four stroke cycle". Did you read the changelog? The manpower involved is immense.
(Of course you can write a much much simpler engine yourself, but we aren't talking about those.)
Note I'm only talking about the graphics aka shader side here, not the whole engine.
Of course it gets "easier" once you've done it a couple of time and understand the basics, but really doing it for the first time is a hard edge to climb.
Been writing my first 3D C++/OpenGL engine for the last 2 years, one of the most taunting tasks I've taken in my career. And just to cover a very specific use case of graphics rendering, not to do cover an overly generalized case like Unreal Engine is doing.
Unreal engine is also over at least 20 years old, so I think you're overly simplifying the task required.
Graphics engine is so much more than just figuring out the graphics pipeline, ultimately it's about flexible data management in a way that lets you achieve what you want, with performance.
These days C# + Monogame solves all my Language, API and Platform distribution problems and allows for fast iteration during development.
Implementing a cross platform modern game engine is perhaps a single step below writing an operating system from scratch.
Source- I've written 3 feature rich, but not feature complete, game engines over the last 25 years.
When new engine features come out, FXAA for example, it's mainly just a case of finding it online [1] and implementing it as needed. I've done this with many parts of my engine (model loading [2], animation [3] and physics [4] come to mind) where I don't need to re-invent the wheel, but I have full source for when I need to modify it (always the case), and it comes unrestricted by licences which is another plus.
Cross platform? Mono runtime + Monogame already has me covered, and I can use a modern language to write my games for faster iterative development.
[1] https://github.com/SeriousMaxx/FXAAMonoGame
[2] https://github.com/assimp/assimp
[3] https://xnanimation.codeplex.com
[4] http://community.monogame.net/t/which-physics-engine-is-work...
One other benefit, apart from outsourcing, is that there's now a large pool of people using the same system. So, you're not working in isolation anymore and you can ask for help when you get stuck - and stuck you will get.
Could you please elaborate on this one? Do you have first hand experience?
It's true that there has been more questions then there are answers, but I was wondering what attempts have been taken thus far to solve it.
More specifically, I was curious to hear if OP had any story to share dealing with this kind of problem.
The biggest problem with this pre-packaged software is when something ultimately goes wrong, which it always does. Then you find yourself digging round in internals (assuming you have access, looking at you Unity) to find out what when wrong and why banding is appearing only when you use stencil shadows and apply SSAO factor X.. basically, it's still complicated, and you still have to know your stuff.
Another problem with these engines is they force you into a particular way of working. Unreal blueprints for example are a nightmare once you add a decent amount of functionality as per the law that visual programming does not scale.
Finally you underestimate how much code is the actual game logic, which is also the hardest part to write. In this case the engines don't help at all, Unity even just throws you into Visual Studio and lets that deal with you. Additionally I've yet to see a good solution for figuring out why my AI are running through walls on their way to a target, without writing a ton of custom visualization stuff myself. Many algorithms take place over time (units moving, animating, etc), so you can't just step though code in a debugger as that's like looking at a landscape through a keyhole.