yuzu/yuzu-emu.github.io
1
0
Fork 0
mirror of https://github.com/yuzu-emu/yuzu-emu.github.io.git synced 2026-08-09 11:15:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update index.md

Browse source
This commit is contained in:
Matías Locatti 2023-10-20 16:02:31 -03:00 committed by GitHub
parent 5fa29f2462
commit 7d3053502a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
site/content/entry/yuzu-progress-report-sep-2023/index.md
View file

@ -300,12 +300,15 @@ Keep in mind that this doesn't solve the vertex explosions affecting the Pentela
Another good bit is that recent drivers also seem to have introduced DXGI swapchain support, allowing AMD cards to work with AutoHDR out of the box. Another good bit is that recent drivers also seem to have introduced DXGI swapchain support, allowing AMD cards to work with AutoHDR out of the box.
There doesn't seem to be a driver toggle for this though. There doesn't seem to be a driver toggle for this though.
Users interested in enabling AutoHDR for yuzu can use [this piece of software](https://github.com/ledoge/autohdr_force) to do the registry work for them.
Now for a bit of bad news. Now for a bit of bad news.
Windows driver version `23.9.3` and newer cause the VSync options to be ignored, resulting in tearing during gameplay. Windows driver version `23.9.3` and newer cause the VSync options to be ignored, resulting in tearing during gameplay.
If you’re affected by this, revert back to driver `23.9.2` for now. If you’re affected by this, revert back to driver `23.9.2` for now.
The standard procedure was followed: we've opened a ticket with AMD regarding this issue and provided a generic test case. The standard procedure was followed: we've opened a ticket with AMD regarding this issue and provided a generic test case.
ED: Driver `23.10.2` seems to have solved this issue entirely, we recommend updating to it.
Switching to something more interesting, we heard you! Despite our previous rants about frame generation, we think Switching to something more interesting, we heard you! Despite our previous rants about frame generation, we think
vendor-agnostic frame generation like FSR3 would be cool to make Pokémon games playable, but the same requisites which prevent us from using vendor-agnostic frame generation like FSR3 would be cool to make Pokémon games playable, but the same requisites which prevent us from using
FSR2, or even DLSS/XeSS for that matter, apply here. FSR2, or even DLSS/XeSS for that matter, apply here.