DukenukemX
Supreme [H]ardness
- Joined
- Jan 30, 2005
- Messages
- 8,076
Yep, this is what was said by one of the members of the Yuzu team.The emulator can't provide the information DLSS or Xess needs in a generic way. The emulator has no idea what's being drawn and it can't make assumptions because any and every game is free to do whatever it wants.
https://github.com/yuzu-emu/yuzu/issues/12525#issuecomment-1872470058
"DLSS conflicts licence-wise, and the experimental build required using video encoding as motion vectors data.
FSR3 has the same limitation, without motion vectors data, it's useless, and Switch games don't export that information.
Frame generation on TVs has a little cost called input lag, good luck getting a game with a base framerate of 30 FPS into something playable if you delay for 66ms to get input data. And that's not even counting the ghosting.
It's not impossible to implement FSR3, but unless you find a way to extract motion vectors data in a sensible way, that works for any game, it will remain as not viable."
So far games that have FSR2 can have FSR3.FSR3 and temporal friends cannot be implemented by the compositor in the Steam Deck either. Has nothing to do with source code, the information they need to function needs to come from the game - which is why Steam Deck can only ever spatially upscale for you.
View: https://youtu.be/jst_zjiDCLw?si=MIC_418bnv4An39v