Yes it is. One game on the Switch is hardly anything significant.
Several. Silent Hill 2, Until Dawn, Gears E-Day, Black Myth: Wukong, Legend of Ymir, ..etc.
You took his statement out of context, he only made it in the context of his engine embracing path tracing instead of virtual geometry.
I disagree with that. His main opening statement is "[in response to virtual geometry being added to FOSS] I don't think this is that useful compared to traditional LOD."
For all of Sony's talk about "believing in generations", there's seemingly a severe lack of exclusive current generation defining AAA games by the other major publishers with dismal results so far ...
Bold of you to list games that don't even have release dates yet, no gameplay footage, or don't even specify 'hardware' RT ...
Respectfully, I did not as he exactly implicates the mutual exclusion between the choice of virtual geometry and ray tracing ...
Then he goes on to express his views that realistic lighting + RT are enough.
He is.
Only Gears has no gameplay footage or a release date, the rest have release dates, gameplay footage and confirmed RT. Gears also specify "hardware" RT.
That discussion is a theoretical. He states the engine has been modernised which is a prerequisite for attempting a cinematic renderer. He then goes into the hypothetical, "okay, let's say everything ready to do a cinematic renderer". "We should, we need to plan, we could..." Not, "we are, we chose, we will be..." He then reiterates that AAA-quality cinematic renderers and assets isn't Godot's audience, it isn't a priority, they aren't catering to AAA devs, and any Godot design choices will be around what their indie dev users need. Godot is not trying to compete with Epic and will not be chasing solutions to match Epic's but instead doing their own thing with their own priorities.
That doesn't mean we're not seeing some pushback against it and do you think it won't see more resistance w/ competing technologies over time in the future ?
The same process applies for extensions or feature enhancements too and it's not invariably any easier either!
Great to see AMD responding to a number of the problem cases for current hardware and APIs.
Hmm, the DGF (hardware compression support for meshlets w/RT support) thing looks like a proposal for something that could show up in RDNA5/Xbox whatthefuckever. Still doesn't allow skinned geometry, but still kinda neat.
Yikes! Their software implementation (intersection shaders) of this feature is slower (check table 5) than ray tracing against uncompressed geometry by a factor of up to ~2.4x and this doesn't really help address the acceleration structure update cost either. It's going to be a shaky proposition to persuade the hardware team to implement support if it doesn't really improve performance ...
That's got to be the most lame plan ever, AMD doesn't have the marketshare or market leverage to do this, WorkGraph is properly supported only on their latest poor sales arch (RX 7000), and their next arch (RX 8000) has no high end GPUs, besides WorkGraph doesn't have an immediate visual flair like ray tracing or path tracing. and PC gamers expect their games to look no less than next gen now. Not to mention it would take WorkGraphs years to take off at it's current trajectory.
I don't know either, WorkGraphs is in the conception stage right now, fearure tiers are still being added in, drivers are in beta stage, enigne integrations is years off, it's a 3 years project at best right now.
According to him, AMD is going into that direction (citation needed), he thinks GPU driven rendering is an antagonist to ray tracing (it isn't).
They had enough political power to convince Epic Games and Microsoft to unilaterally standardize the feature despite the protests from the leading graphics hardware vendor ...
They're likely to still go through with their initial aim to sabotage real-time RT HW regardless of yours or anyone else's preferences. It's just basic prisoner's dilemma that their dominant strategy always involves underselling RT since they get absolutely nothing out of cooperating with their competitor to promote RT ...
Which doesn't mean much in the grand scheme of things, we shall see if the feature gets adopted once it finishes it's lengthy beta stage.
A failed and naive strategy, it's a losing one at best and a catastrophic one at worst.
Those research papers often get from to theory to real applications real fast, we have stuff like path tracing, RTXGI, RTXDI, neural denoisers, etc that got applied pretty quickly into actual games, while WorkGraphs are still being worked on for a year and a half with nothing to show for it (with maybe 2 more years until it becomes mature enough).
