Redfall Xbox Series X/S - DF Tech Review - Big Issues And Unfulfilled Potential
- Thread starter Satoru
- Start date
Article.
www.eurogamer.net
Redfall on Xbox tested: a sad tale of unfulfilled potential and profound technical issues
Redfall is an open world first-person shooter that combines mechanics-driven, immersive sim-style design with optional …
www.eurogamer.net
I'm starting to fell DX12 is the biggest issue.
With DX11 you could max out the GPU pretty easy... now with DX12 you basically have several issues and the GPU is threre basically doing nothing.
There are something weird with DX12 that related to these PC ports and Series S/X performance.
Was DX12 new features just marketing?
With DX11 you could max out the GPU pretty easy... now with DX12 you basically have several issues and the GPU is threre basically doing nothing.
There are something weird with DX12 that related to these PC ports and Series S/X performance.
Was DX12 new features just marketing?
DX12 is pure trash, yes. It's the windows vista of the gaming APIs.
I've been suspecting this for a long time. The whole shader compilation stuttering thing came out of nowhere, this was not a common issue on PC.
It's either DX, Unreal or most likely both.
Last edited:
Very generic summary. Be creativeAllow me to summarize:
Remember "oh man Xbox will be so much better than PS5 due to dx12" 
when we knew Sony has some of the best apis tht they use.
when we knew Sony has some of the best apis tht they use.
Phil told us that DX12 would bring 1080p gaming on the xbone and unparalled performance on PC.
Does Vulcan have similar shaders build issues?
Yes.
Somebody shared on Beyond3D the common topics of issues from this year Vulkan conference.
Digital Foundry Article Technical Discussion [2023]
This is very simplistic and naive interpretation on where the actual problem lies. If we say that DX12 is bad than all PCs low level APIs are bad. The subject was already discussed here few times. Its not that the DX12 or Vulkan or whatever API problem. Is the complexity of new low level APIs...
forum.beyond3d.com
The true story is imo.
- Top PC developers asked low-level API and so Vulkan and DX12 was created.
- Low level APIs require that the developer controls everything and that means more work.
- It is fine on console where you have a single hardware to work on.
- It doesn't fit the PC dynamic range of hardware where that "control" means a lot more of work for multiple hardware specific issues.
- Top PC developers basically don't delivery games anymore (do research and others things) and these are very niche.
- Indie, AA and most AAA developers doesn't have all that time and/or skills to work with low level APIs for multiple hardware configurations.
- Low level APIs like Vulkan and DX12 are trying to implememt less control (like come automatic memory management like in DX11/OpenGL) due the state of Vulkan/DX12 nowdays.
Now they are facing the issue that maybe the Low level API is not good for PC variable hardware config.
That brings us back to MS decision to unify SDKs with GDK... it doesn't work... fixed hardware like consoles can use dedicated SDKs with very low level APIs while PC SDK should cover different sets de hardwares.
Last edited:
Sony’s APIs are also a lot closer to the metal than XBox, and that makes a huge difference.Remember "oh man Xbox will be so much better than PS5 due to dx12"
They didn't realize that Playstation already had an api with all the features it needed. Sony just didn't feel the need to beat their chests over it.Remember "oh man Xbox will be so much better than PS5 due to dx12"