Commit Graph

4 Commits

Author SHA1 Message Date
chrg6
cb234fade1 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>
2026-11-09 12:18:17 -05:00
chrg6
5fb384b906 Add DLSS multi frame generation, the Intel pipeline cache crash and the pinned Streamline runtime to the 0.6.1 notes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-09 12:18:17 -05:00
chrg6
78ee0ddb1e Say in the 0.6.1 notes that an update from 0.5.0 keeps its compiled game too, and that the device-lost fix covers low memory.
Checked with the 0.6.0 launcher's own update path against a local copy of the 0.6.1 release: 552 of the game's 562 objects
were taken over, 10 compiled, the prepared shaders kept with the translator that made them named, done 0.2 minutes after
the download.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-09 11:44:39 -05:00
chrg6
8a4cb72b61 Set the version to 0.6.1 and write its release notes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-09 11:28:41 -05:00