Lach

Can you provide EDID for yours mode 1? It looks to me like SteamVR sees frame rate as 90Hz in EDID for you. It should be possible to explicitly override...

You can try using this branch, here I added ability to explicitly provide frame rate. https://github.com/CertainLach/VivePro2-Linux-Driver/pull/31

There is two ways to obtain vsync_to_photon, one using valve config: https://github.com/CertainLach/VivePro2-Linux-Driver/blob/master/crates/vive-hid/src/lib.rs#L75-L76 And one using vive config: https://github.com/CertainLach/VivePro2-Linux-Driver/blob/master/crates/vive-hid/src/lib.rs#L144-L145 Valve config is used by SteamVR by default, as it is also...

Also, do you use CoreCtrl for your GPU? On windows, SteamVR automatically updates GPU profile to VR for better performance and latency, but on Linux gpu always uses default profile,...

For testing, you can try providing your own values, like I do provide framerate here: https://github.com/CertainLach/VivePro2-Linux-Driver/pull/31 I haven't implemented reading this value from config on this branch, because I don't...

Go to crates/vive-hid/src/lib.rs Add this to the end of file: ```rust #[test] fn test() -> Result { let dev = ViveDevice::open_first()?; dbg!(dev.read_config()?); let dev = SteamDevice::open_first()?; dbg!(dev.read_config()?); Ok(()) } ```...

Yep, that's not right. Values written on my device are much higher, and I don't observe this problem Well, seems like they needs to be provided from somewhere else

I have updated my PR. I'm not sure how vive devices are being provisioned, so I think I need to also port some of the other values which vive driver...

In PR, I have implemented logic from the original driver,  (mode here = vive-hid mode id - 1)  So the values will be exactly as you have.

`vsync_to_photon` is only read on device activation, and updates are ignored later, this delay is constant. Is everything ok with frame times? Do you have vulkanAsync enabled? It might be...