News for hackers. Stuff that matters.
Re:Raytracing won't simplify AAA real-time rendering by lmm on Monday December 28, 2020 @04:37AM (#25557916)
> In fact, it's easier for AAA to become relatively irrelevant (compared to the overall market size - that expands faster in other directions than in the established AAA one) - than for it to radically embrace change.

This has already happened. AAA is now a small and ever-shrinking fraction of the overall games market.

Will raytracing the best engine that a 30-person team can build in 2 years any simpler? No, because "the best engine that a 30-person team can build in 2 years" is at a particular level of complexity by definition. Will it make the gap between the best engine that a 30-person team can build in 2 years and the best engine that one guy in his bedroom can build much smaller? Yes, yes it will.

Custom game engines are already dinosaurs; most of the money in games is elsewhere. I'm sure they'll continue to be produced, just like you can still pay a lot of money for a mainframe today. Mainframes were never defeated, not exactly - they can still do things that commodity hardware can't do. But they just became irrelevant.

Re:Raytracing won't simplify AAA real-time rendering by smt88 on Monday December 28, 2020 @06:08AM (#25558292)
> AAA is now a small and ever-shrinking fraction of the overall games market.

I don't know how you can know this. No one has:

- a widely agreed-upon definition of AAA (budget? team size? total work-hours that went into it?)

- an estimate of how much revenue AAA games generate from subscriptions, DLC, and any other add-ons

Without both of those, how can you even guess at AAA games' collective market share? Citation definitely needed.

> Custom game engines are already dinosaurs; most of the money in games is elsewhere. I'm sure they'll continue to be produced, just like you can still pay a lot of money for a mainframe today.

What does raytracing have to do with the popularity of custom engines?

Whether I'm planning to build a custom engine or license an existing engine, aren't we discussing whether my job is easier with raytracing than without it?

Put another way: it seems like the article is comparing reusable engines without raytracing to reusable engines without raytracing, as well as comparing one-off engines without raytracting to one-off engines with raytracing.

I don't think being able to use raytracing is going to move any dev team from one option to the other. If they had the desire and resources to build a custom engine, they'll probably still do that (against all logic).

> Mainframes were never defeated, not exactly - they can still do things that commodity hardware can't do. But they just became irrelevant.

Off topic, but this is not a good analogy. The "cloud" is just a network of mainframes, which means mainframes are arguably the dominant form of computing (and will become more dominant as thin clients, like Stadia, rise in popularity).

Mainframes were not necessarily purpose-built, unique machines. They were instead defined by their sharing model, which is where the term "personal computing" comes from -- as a contrast to the mainframe/server model.

Re:Raytracing won't simplify AAA real-time rendering by lmm on Monday December 28, 2020 @08:46PM (#25565726)
> What does raytracing have to do with the popularity of custom engines?

Raytracing is being used as a synecdoche for technological advances in rendering. The point is that as off-the-shelf rendering improves, the advantages of a vertically integrated engine diminish.

> Off topic, but this is not a good analogy. The "cloud" is just a network of mainframes, which means mainframes are arguably the dominant form of computing (and will become more dominant as thin clients, like Stadia, rise in popularity).

> Mainframes were not necessarily purpose-built, unique machines. They were instead defined by their sharing model, which is where the term "personal computing" comes from -- as a contrast to the mainframe/server model.

That's a very essentialist perspective; there are a lot of ways mainframe computing differs from typical personal computing and no single one of them is definitive. As a programmer, a mainframe offered you a reliable computing environment, because they're built to be highly available from the hardware up. That's very much not the case with the cloud, which follows a worse-is-better approach where your jobs can be terminated whenever and you're expected to handle it. While shared computing resources may be making a comeback, I don't think that kind of ground-up high availability will, so while the cloud has some aspects in common with mainframes, it's very much not the same thing.

Re:Raytracing won't simplify AAA real-time rendering by asdfasgasdgasdg on Monday December 28, 2020 @12:10PM (#25560888)
> Custom game engines are already dinosaurs; most of the money in games is elsewhere.

It's interesting you say that because a lot of the biggest games that get released are on custom engines. I'm most familiar with FPSes, but as I understand it, the cod games, the battlefield games, destiny, the halo games, cs-go, valorant, cyberpunk etc. are all on "custom" engines -- i.e. engines that are not provided commercially by third parties. I'm actually having trouble thinking of a big name fps that is on unreal or unity.

(I don't know how big these games are compared to mobile games, but I can say for sure that they are big enough that studios seem to be investing more and more on them, rather than less as you would expect if they were economically insignificant.)

Re:Raytracing won't simplify AAA real-time rendering by EugeneOZ on Monday December 28, 2020 @12:49PM (#25561286)
I can give one hint: Epic :)

p.s.: I share your opinion

Re:Raytracing won't simplify AAA real-time rendering by mockery on Monday December 28, 2020 @02:02PM (#25562078)
Using GP's definition: "custom" engines -- i.e. engines that are not provided commercially by third parties it's pretty easy to argue Fortnite also uses a "custom" engine. (And that's not pedantry - they obviously have knowledge and access that no licensee could dream of.)

That said, tere are a decent set of AAA games that license Unreal (PUBG, State of Decay, Borderlands series, Arkham series, XCom series) but it's rare among the absolute biggest titles ("AAAA" if you will.)

Re:Raytracing won't simplify AAA real-time rendering by asdfasgasdgasdg on Monday December 28, 2020 @01:51PM (#25561956)
I guess I think of Fortnite as a "custom" game engine since Epic owns both the game and the Unreal engine. So it matches the pattern, "FPSes are built on engines owned by the same entity that owns the game." But you could argue that since Unreal is commercially available Fortnite runs on a non-"custom" game engine. Depends on your definition.
Re:Raytracing won't simplify AAA real-time rendering by ekianjo on Monday December 28, 2020 @05:06AM (#25558035)
> AAA is now a small and ever-shrinking fraction of the overall games market.

This entirely depends on how you define AAA.

Re:Raytracing won't simplify AAA real-time rendering by Rapzid on Monday December 28, 2020 @05:06PM (#25563793)
Here is a list of the top 10 selling games from 2018. Nearly all of them used in-house engines:

* Red Dead Redemption 2

* Call of Duty: Black Ops 4

* NBA 2K19

* Madden NFL 19

* Super Smash Bros. Ultimate*

* Marvel’s Spider-Man

* Far Cry 5

* God of War 2018

* Monster Hunter: World

* Assassin’s Creed: Odyssey

Further, what I would call the poster triplets for ray tracing Control, Metro Exodus, and CP 2077 all use in-house engines.

Re:Raytracing won't simplify AAA real-time rendering by lmm on Monday December 28, 2020 @09:29PM (#25566049)
> Here is a list of the top 10 selling games from 2018. Nearly all of them used in-house engines:

Sure - those are the AAA games we're talking about (and even then, a lot of those are long-running franchises that reuse a significant chunk of engine code between multiple installments). The biggest sales numbers will keep coming from that segment for a long time. But it's a shrinking segment in terms of overall revenue (much of which is no longer up-front sales), and even more so if you look at profit; each year the line where it makes sense to use a custom engine gets higher, and a bigger share of money coming in is from games built on commodity engines.

Re:Raytracing won't simplify AAA real-time rendering by EugeneOZ on Monday December 28, 2020 @09:50AM (#25559572)
> Custom game engines are already dinosaurs; most of the money in games is elsewhere

Not sure if it's true. Look at the profits of GTA, Cyberpunk, Witcher.

Re:Raytracing won't simplify AAA real-time rendering by charrondev on Monday December 28, 2020 @05:10PM (#25563829)
Profits of cyberpunk? They’ve been delisted from one platform and an open refund policy on 2 platforms because of how buggy it is.

If anything that tells me they may have been better off investing that developer time into the game instead of a custom engine.

Re:Raytracing won't simplify AAA real-time rendering by vvillena on Monday December 28, 2020 @06:10PM (#25564409)
The game sold about 5 million units in the first week. IIRC the game's budget was about 130 million, so yeah, there are lots of profits, with more to come next year when the next gen versions are released. And there will be single-player expansions and a multiplayer mode. Profits indeed.
Re:Raytracing won't simplify AAA real-time rendering by Dirlewanger on Monday December 28, 2020 @01:46PM (#25561902)
They may be ever-shrinking, but their share of the revenue pie is growing.