mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-17 09:19:58 -04:00
With frame generation and no frame limit chosen, limit to the display's refresh rate.
Since the pacer divides the limit by frame generation's factor, the default limit of 60 held the game to 30, 20 or 15 rendered frames a second at 2x, 3x or 4x on any monitor, 15 at DLSS 4x on a 165 Hz one. While AMD's or NVIDIA's frame generation swapchain is in use and neither fps_limit nor the older fps60 = 0 is set, the limit is now the monitor's rate, as with fps_limit = display: 4x on 165 Hz draws about 41 and shows 165. A limit the player set is kept, and the menu's Frame rate limit row shows the display choice while this applies. The mouse camera divided its input by the limit's frame ratio, which counts generated frames, so frame generation turned it faster by its factor; it now uses the rate the game draws at (frame_step_game_hz). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -110,7 +110,8 @@ beside the game.
|
||||
background while you play.
|
||||
- **Screen** in the menu has Upscaling (DLSS on NVIDIA RTX cards, FSR 3.1 on any card), Frame generation (NVIDIA DLSS
|
||||
on RTX 40 and 50 cards, with a DLSS multiplier of 2x, or 3x and 4x on RTX 50 cards; FSR 3.1 on any card; it needs
|
||||
DLSS or FSR 3.1 upscaling on, and the frame limit then counts the frames on screen), HDR (the game's picture tone mapped to your display, with its own grading rows, or Native, the game's own HDR; turn HDR on in Windows first) and the
|
||||
DLSS or FSR 3.1 upscaling on, and the frame limit then counts the frames on screen; with no limit chosen it is the
|
||||
display's refresh rate), HDR (the game's picture tone mapped to your display, with its own grading rows, or Native, the game's own HDR; turn HDR on in Windows first) and the
|
||||
resolution. Those marked "after restart" take effect when the game starts again.
|
||||
- **Controls** in the menu has Button prompts: the game's own, or Xbox, PlayStation or keyboard and mouse ones when
|
||||
the build drew them (a kit with `prompt-art`). It takes effect after a restart. The keyboard and mouse prompts show
|
||||
|
||||
@@ -28,8 +28,9 @@ cards).
|
||||
- *Rebuild the Game* compiles the game for your current processor.
|
||||
- DLSS Frame Generation at 2x, 3x or 4x: the *DLSS multiplier* row under Frame generation in the settings menu
|
||||
(`framegen_multiplier`). 3x and 4x need a GeForce RTX 50 GPU and are not yet tested in play. The frame limit now
|
||||
counts the frames on screen: with 2x a limit of 60 shows 60 frames a second, not 120. RivaTuner Statistics Server
|
||||
stays out of the frame limit while DLSS Frame Generation runs.
|
||||
counts the frames on screen: with 2x a limit of 60 shows 60 frames a second, not 120. With no limit chosen, frame
|
||||
generation now uses the display's refresh rate, so on a 165 Hz monitor 4x draws about 41 frames a second and shows
|
||||
165. RivaTuner Statistics Server stays out of the frame limit while DLSS Frame Generation runs.
|
||||
|
||||
## Fixed
|
||||
|
||||
@@ -46,6 +47,8 @@ cards).
|
||||
video memory.
|
||||
- Shader preparation no longer crashes the RADV driver (AMD GPUs on Linux) on a texture size query.
|
||||
- Things that moved no longer leave a trail when neither DLSS nor FSR 3.1 is on.
|
||||
- With frame generation on, the mouse turned the camera as fast as if the game drew every frame on screen: twice as
|
||||
fast with FSR 3.1 frame generation.
|
||||
- The game's own Restart no longer brings the launcher back over the game, where Play could start a second copy.
|
||||
- A cut connection while the launcher reads a small file, such as the package index of *Gather Build Tools*, is tried
|
||||
again instead of failing the install.
|
||||
|
||||
Reference in New Issue
Block a user