Whenever they can get their game running acceptably under DX12. Developers should have a specific reason to use lower level APIs given the extra complexity and knowledge required. Using it just because has not been a benefit to anyone. It's made games worse.
Smart Delivery for precompiled shaders. Sign me up.
The specific reason is that it's the industry standard API that's been around for more than half a decade and is also the current standard API on another platform (Xbox). And when compared to most FromSoftware games, Elden Ring does run "acceptably". I'm pretty sure the PC port of Sekiro still has weird issues with controllers. As in, it won't detect controllers sometimes (either Xbox or Playstation controllers), and using a wired controller has a performance penalty. As in, you get lower FPS with a wired controller. The fact that Elden Ring's performance issues seam to be mostly related to shader compilation, which other games also have, is a step in the right direction compared to the more exotic issues their previous games have had or still have.
That is like always, on the one hand people (in this case many developers) want more control of that what happens, but on the other side, they don't want the responsibility to manage all themselves. IMHO this is why Vulkan & DX12 aren't used in more games. DX11 makes it quite easy to get and keep something running. On Playstation they don't have a choice, they must go through this. It is like always, if you have the choice between the easy way and the much more complicated way, you always choose the easy way, especially if all your refined tools use the easy way and you have knowledge how the easy way works. But it is also a cost decision as more time equals more costs so even if they want to implement a DX12 mode, they might be forced to just implement the old way.
some, yes, but far to many DX11 titles are still released. Even games developed years after DX12 was out. Even the unreal engine has still problems with DX12. It is really a never ending story. Just like DX9 was still used while DX11 was out.
give it time. A large portion of the PC audience did not have hardware to support DX12. With the generation now moving forward and the baseline on PC truly becoming XBO hardware, DX12 is now an API that will see widespread coverage.
LOL.
It doesn't explain the PS5 running at 60fps in backwards compatible mode though. The Xbox SX is supposed to be more powerful than the PS5.
It's not exactly as high res as Quality Mode but it certainly is sharper than FPS mode.
still running BC code, which is inefficient in comparison to a native binary. DF didn't expect the engine to ramp up settings for X1X when moved to Series X.
So, now we need to test just the xbox one version instead of the X version to try the same ^^
.I really enjoy videos like this. When DF are like WTF-this-makes-no-sense, I know it's going to be entertaining. This documents some utterly weird decisions made during the development of this game, but also the dilemma of game devs trying to produce games that select the "best" combination of settings for the average player.
lol yup.
I think that's true for the previous generation Xbox game version which was never expected to greatly exceed 30fps for the most part, so having the game adapt higher quality settings and higher resolution made sense. When run on hardware which could have hit 60fps if certain settings were weighted differently, it makes less sense. This is where a really good variety of settings helps. It feels like that From put more effort, and tuning of settings for particular console versions, than the are given credit for. It also falls apart when you want to do something unexpected, like run Elden Ring at 60fps on any Xbox.
