Nvapi implements reflex on proton not vkd3d. dxvk-nvapi would be the place. If reflex isnt functioning as it should make sure its not a driver behavior and head over to dxvk-nvapi and search for reflex discussion before posting an issue.
Also rtss implements reflex injection it doesnt break reflex it takes over handling it. Arguably RTSS handles reflex better than any game does.
This is outside the scope of vkd3d-proton. Policy decision like these belong in dxvk-nvapi or something like that, or maybe even the NV driver implementation.
Nothing extracted yet.
In windows, when reflex and gsync are enabled, nvidia driver automatically limits the FPS to just below the maximum refresh rate to prevent vsync latency. Shouldn't this behaviour be replicated at vkd3d-proton layer in linux as it implements reflex?
Currently there is no good solution to this in linux, as external FPS limiters unfortunately break reflex immediately upon enabling the limit (ie mangohud in linux and rtss in windows). And without a reliable FPS limit that is compatible with reflex, one has to choose between mailbox judder, vsync latency, or tearing when FPS exceeds the upper limit of VRR.
Sorry if this is not the correct place for this issue.