mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-21 12:19:58 -04:00
Enable the drivers' low-latency extensions only in a run that starts with the setting on.
With the setting off the device is made exactly as before the mode existed, so the mode cannot change anything for a player who never turns it on. Turning it on in the menu then takes a restart, and the row says so; in a run that started with it on, changes still apply at once. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
@@ -1,4 +1,6 @@
|
||||
// Low latency without frame generation (NX2NAVI_LOW_LATENCY: 0 off, 1 on, 2 on with boost; default 0; live).
|
||||
// Low latency without frame generation (NX2NAVI_LOW_LATENCY: 0 off, 1 on, 2 on with boost; default 0). In a run that
|
||||
// starts with it on, a change takes effect at once; a run that starts with it off makes its device without the
|
||||
// drivers' extensions (vk_device.c create_device), so turning it on then takes a restart.
|
||||
//
|
||||
// A frame's delay from the pad to the screen has two parts the runtime can shorten. The first is the time the frame
|
||||
// waits after it is drawn: the frame limit used to hold a finished picture back until its slot (vk_backend.c
|
||||
@@ -504,6 +506,12 @@ void vk_lowlat_init(VkCtx *c) {
|
||||
}
|
||||
rt_log("lowlat: VK_AMD_anti_lag is enabled but its entry point is missing");
|
||||
}
|
||||
if (c->lists_low_latency) {
|
||||
L.why = VK_LOWLAT_RESTART;
|
||||
rt_log("lowlat: the driver has a low-latency mode; this run started with NX2NAVI_LOW_LATENCY off and made its "
|
||||
"device without it, so the setting takes effect at the next start");
|
||||
return;
|
||||
}
|
||||
rt_log("lowlat: this driver has neither VK_NV_low_latency2 nor VK_AMD_anti_lag: no low-latency mode%s",
|
||||
level ? " (NX2NAVI_LOW_LATENCY does nothing here)" : "");
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user