mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-18 00:29:58 -04:00
Turn the lazy write-back off by default on every card of AMD's own Windows driver, and let the device probe print the fatal summary line.
The default was off only on AMD's driver branch for RDNA 1 and 2, on the grounds that builds with the default on had been measured on an RX 7900 XT. Those measurements were standing in Hyrule Field and walking through a village; the report this is about is of a game that ended in fights, on an AMD card the player did not name, and fights are where the lazy path is busiest. Nobody has played one on an AMD card under our eyes on either branch, so the exception is now AMD's own driver as a whole (wb_lazy_choice.h, by VkDriverId), until a card of each branch has played fights with wb_lazy = 1 and a log to show. The cost is the open-area frame rate of 0.7.0 on every AMD card under Windows; the RX 7900 XT figures in the draft notes come from builds that had it on by default, which the notes now say. wb_lazy = 1 still turns it on. --probe-vkdevice prints the line a fatal error or a crash adds to the log, so its wording can be read without a failing run. On an RTX 5090: "fatal: gpu NVIDIA GeForce RTX 5090, driver NVIDIA "621.01" version 621.1.0.0; memory mode mirror, lazy write-back on (the default on Windows (wb_lazy = 0 turns it off)); texture detail not chosen yet (no texture made)", and with the reporting player's nx2navi.ini beside the exe "lazy write-back off (wb_lazy = 0 is set)", after a start whose log names async_compute, vram_safe_mode and exception_handler as no settings of this version. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
@@ -38,14 +38,16 @@ Draft notes for the release after 0.7.1. The version number is not decided yet.
|
||||
|
||||
## Changed
|
||||
|
||||
- **AMD RX 5000 and RX 6000 cards: the faster copy-back of 0.7.1 is off by default again.** 0.7.1 turned it on for
|
||||
every card on Windows (what the game's shaders write is copied back from the video card once, and then only when
|
||||
the game's CPU code touches it). None of us has one of these cards, their Windows driver is a branch of its own,
|
||||
and one report from an RX 6600 lost its video device a few minutes into play with it on. We found no fault in the
|
||||
code and cannot say it was the cause, so until someone has run it there the old copy-back at the end of every GPU
|
||||
submission is the default with that driver; open areas run slower for it, as they did in 0.7.0. `wb_lazy = 1` in
|
||||
`nx2navi.ini` turns it on: if you try it, tell us whether the game stays up, with the log. NVIDIA cards and AMD's
|
||||
RX 7000 and RX 9000 cards keep it on. The log says which is in effect and why ("mem: lazy write-back ...").
|
||||
- **AMD cards: the faster copy-back of 0.7.1 is off by default again.** 0.7.1 turned it on for every card on Windows
|
||||
(what the game's shaders write is copied back from the video card once, and then only when the game's CPU code
|
||||
touches it). Since then two reports from AMD cards had the game end in play: an RX 6600 lost its video device a
|
||||
few minutes in with it on, and a player whose game ended in fights played for hours with it off. We found no fault
|
||||
in the code and cannot say it was the cause, and none of us has played a fight on an AMD card with it on. Until
|
||||
someone has, the old copy-back at the end of every GPU submission is the default with AMD's Windows driver; open
|
||||
areas run slower for it, as they did in 0.7.0. The RX 7900 XT figures under *Faster* come from builds that had it
|
||||
on by default. `wb_lazy = 1` in `nx2navi.ini` turns it on: if you try it, play a few fights and tell us whether the
|
||||
game stays up, with the log. NVIDIA cards keep it on. The log says which is in effect and why ("mem: lazy
|
||||
write-back ...").
|
||||
- **A line in `nx2navi.ini` that is no setting of this version is pointed out.** Such a line does nothing; the game
|
||||
only wrote "unknown key" into its log. The log now lists them in one line at the start, beside a line with every
|
||||
setting the file does set, and the settings menu shows them in its bottom row. An update or a rebuild never rewrites
|
||||
|
||||
Reference in New Issue
Block a user