1) Using an existing product like Unity or Unreal Engine or GameMaker. 2) Using their own engine but with very basic graphics.
"Ghost of a Tale" uses Unity. "The Forest" uses Unity.
So yeah, it's not "that hard" if you use a product which has already had millions of developer hours put into it like Unity or UnrealEngine.
Take away any prepackaged game engine and see if either of those two developer teams would have been able to make those games. :)
"When you're an adult you won't always have a calculator with you !"
Do you make the same comment about someone using standard libraries or frameworks? How productive would you be without system libraries or even an OS?
I was more making the point that starting by building an engine is a huge commitment and you need the skills and times (and the reason) to do that.
> So yeah, it's not "that hard" if you use a product which has already had millions of developer hours put into it like Unity or UnrealEngine.
What point are you making? The GGP correctly claimed it's "not hard" for small teams to make games. The games they referenced were made by small teams. The fact those games used an off the shelf game engine is immaterial. There's no "point" to make about it.
Your "point" comes off as a qualitative judgement about those developers using an off the shelf engine. If you've got no problem with someone using Unity what point are you really making?
Using someone else's hard work doesn't mean that its easy, just that you don't have to do that work yourself because others have done it for you.
> Your "point" comes off as a qualitative judgement about those developers using an off the shelf engine.
I didn't read it like that at all. In most cases, for most teams (certainly small ones), using an off the shelf engine is absolutely the right call, exactly because it means you don't have to solve the hard graphics problems yourself. But using an off the shelf engine does not mean that those hard problems don't exist or aren't hard, just that you can outsource them to the engine vendor.
From the point of view of a game developer, having good graphics is "easy" because Unity and Unreal exist. The fact Unreal and Unity exist enables thousands of developers to make games that couldn't otherwise. Making a "point" that a small game developer didn't write their entire stack is just shitty gatekeeping.
But this is not what the article, and this comment section, is about.
Unity is popular with the indies, but Unreal and Frostbite have powered games with collective sales of several hundreds of billions of dollars.
There are engines that will allow you to do a 3d FPS and make it look very good without ever having to worry about any low level barycentric coordinate issues.
Isn't that a good thing?
But I disagree with the higher level idea - that this means that things become simple. It's the other way around - they became so complex that a few person studio cannot write a new, general engine (see how many people programmed Doom or Quake which were state of the art back then!). At Unity there are a few thousands of just programmers working on the engine (yes!). This is not FAANG size, but I don't know if there is a team at FAANG that has a few thousands of engineers working on a single product. You need a team of this size to make a multi-platform, universal engine that is still not good enough to make AAA or open-world games.
Also my personal experience at my last games job (I left games) was the complete opposite of what you suggest as "engines being commodities" (at least this is at odds with you writing that they are working on AAA engines- sounds like they might be "using" engines and not writing in-house ones?). At Sony Santa Monica we had a team of ~30 programmers, out of which ~8 graphics people (just for a single platform and a single game) and I was constantly frustrated with how impossible it was just to catch up on all necessary state of the art techniques with a team of that size.
There are people much smarter than me who spend for example a half of a year on something as obscure as "multiscattering rough diffuse BRDF" - and a larger engine has hundreds of "features" like this.
My teenager doesn't need to know about cylinders and pistons and fuel injection and air-fuel ratios and timing and radio reception and electronic motors and A/C compressors and alternators and power brakes and traction control and ...
Just needs to know the interfaces to control and maintain the car.
We've made driving so simple that even a 16-year-old can do it.
For a truly small games developer leveraging modern technology, look at Wube, the studio behind Factorio. Or Intoversion, the creators of Prison Architect. I think they each still have less than 20 people. Those games are not graphics beasts but they do rely heavily on modern CPU/memory speeds.
More telling, could they have sold better with a massive marketing campaign?
I don't think a lot of the complexity that goes into graphics is essential, though.
I do think top end will remain top end. However, I also think many games can be done without putting graphics rendering at the top of the budget. Axiom Verge is a recent find of mine that I feel hits this well. Thimbleweed Park is another good one here.
Which is not to say that either of those were easy. I doubt they were.
Two examples.
https://store.steampowered.com/app/417290/Ghost_of_a_Tale/
Made almost entirely by one person
https://store.steampowered.com/app/242760/The_Forest/
Small team
There are tons of others. Sure, someone had to solve those issues but they mostly packaged the solutions into Unreal, Unity, etc.
It's like concentrating on making cameras instead of making movies. Sure there are new techniques that might give your movie some special edge (like when they invented bullet time for The Matrix) but a good story (or a well designed game) doesn't really need the technical tricks. In fact some of the most famous games are designed around the limits of the tech (either the limits of the hardware or the limits of their particular engine).
Note I've written several AAA game engines and have friends that work on AAA engines for others. They are all admitting / lamenting now that engines are basically a commodity and their skills are not needed. They're turning into scripters for the artist and designers and management is pushing to just license the engines.