mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-19 06:29:58 -04:00
Merge the fixes line: the stutter, memory, flicker and crash fixes, co-op, the mesh shader fallback and the launcher fixes.
Brought onto the line with FSR 4, its frame generation and the debug menu. Where both sides had added to the same place, both stay: the patch table keeps the pickup count and the free camera, the settings list keeps both sides' names, the menu includes the co-op page and the debug menu, and the launcher builder takes the pipeline list and the FSR 4 folder. Both sides had added the menu's typed-character event; one definition stays, with the window code that passes characters outside the basic plane. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
@@ -79,3 +79,33 @@ Draft notes for the release after 0.7.1. The version number is not decided yet.
|
||||
shader compiler"); with it each NaN test is now made on the bits of the number instead, which no compiler can drop.
|
||||
It is on by default only with that driver (`vk_nan_bits`); the first start after the update compiles the pipelines
|
||||
again. Untested on those cards before this release: please report whether the blocks are gone.
|
||||
- AMD RX 6000 and older cards: the game should no longer end (code 71) when an enemy is killed. A player with an
|
||||
RX 6700 XT had it at every kill since 0.5 and found that `gpl = 0` (no graphics pipeline libraries) stops it; a
|
||||
player with an RX 5700 XT reported the same ending. That is now the default with AMD's Windows driver for these
|
||||
cards (the log reads "gpl no ... off by default on AMD's driver for RDNA 2 and older"). The price: a pipeline the
|
||||
game needs for the first time is built whole while its draw is left out, so new things can appear some frames
|
||||
late, and the start waits until every pipeline of earlier sessions is built instead of 20 seconds at most.
|
||||
`gpl = 1` in `nx2navi.ini` turns the libraries back on. One player's finding on one card; none of us has such a
|
||||
card, so please report whether the game stays up.
|
||||
- The older installer's last step no longer writes `nx2navi.ini` again as a whole to set the language: it changes the
|
||||
`lang` line and keeps every other byte (it turned Windows line ends into Unix ones and dropped a byte order mark).
|
||||
|
||||
## Changed
|
||||
|
||||
- **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
|
||||
`nx2navi.ini`, and the menu keeps such lines when it saves, so nothing has to be added again after an update.
|
||||
- When the game ends with a fatal error or a crash, the end of the log names the video card, its driver, the memory
|
||||
mode, whether the lazy write-back was on (with its armed ranges, its fetches so far and one in progress) and the
|
||||
texture detail, so a report that holds only the last lines of a log still says them.
|
||||
|
||||
Reference in New Issue
Block a user