Lach

Huh, so it's broken on proton 9 for you? It works for me

I need to redo it properly (In current form, it is somewhat ad-hoc and too specific, I.e those timings should only be applied to IV timings, but not others, and...

For cosmos support, you should at least 1. Set your modes here: https://github.com/CertainLach/VivePro2-Linux-Driver/blob/master/crates/vive-hid/src/lib.rs#L169 (Only one mode is available on cosmos) 2. Disable every writing method in vive-hid crate (Because cosmos...

Set of changes, that was applied on v0.3.1-cosmos tag: https://gist.github.com/CertainLach/888c4958678bee5f1736bc2ac3a5095d It also disables lens distortion functionality, as I'm not sure of its protocol on cosmos either.

You should remove writings, as cosmos has slightly different protocol, which also lacks some of the vive pro 2 features (I.e mode switching)

chmod a+rw /dev/hidraw* for a quick test There is no udev rules for vive cosmos installed

To make stations sleep, you should enable power management for them, driver tells its going to put only managed ones to sleep.

For Vive Pro 2 nothing is required, the display just starts working as soon as it receives the DisplayPort signal. There are commands for led control, but they are not...

I have looked in EyesReader.dll, and seems like there is some function for managing HMD panel. Is I can see, report should have 0x782938 as its 1-3 bytes (counting from...

I think you should be able to easly recover all of the protocol messages by using api monitor (http://www.rohitab.com/apimonitor), and capturing HidD_SetFeature calls from the `EyesReader.dll` library, every function there...