emoose

Changing `VibrationMode` to 0 in INI might help, seems it might be the XInputSetState call which sets vibration, guess it waits for a reply from controller or something

Ah increasing the camera near-Z value actually helps with this, apparently low near-Z values (like the 0.1 value game uses) can reduce precision of depth buffer for distant objects, hm......

Maybe some issue with x1nput, had a lot of crashes with the different versions on there, only 1.3 really seemed to work with C2C, maybe that ver has some issue...

Ah darn, probably is related to the impulse stuff then, just to make sure does setting `ImpulseVibrationMode = 0` in the INI stop the disconnects? The impulse code from X1nput...

Hm, wonder if it's the `ControllerHotPlug` setting, that tries scanning for any newly connected devices, maybe has some issue with bluetooth? Could be worth seeing if `VibrationMode = 0` helps...

The build at https://github.com/Aleksoid1978/VideoRenderer/issues/116#issuecomment-1911214362 appears to support it, not sure if it's working as well as in chrome/edge though.

@Naboum could you see if this build works any better? Added a check so RTX HDR is only enabled if source video isn't HDR: [MpcVideoRenderer64-rtxhdr1.1.zip](https://github.com/emoose/VideoRenderer/files/14066799/MpcVideoRenderer64-rtxhdr1.1.zip)

Glad to hear, pushed 1.1 release at https://github.com/emoose/VideoRenderer/releases/tag/rtx-hdr-1.1 which includes the change along with a fix to let VSR work up to 1440p

Hmm, guess maybe we should only try enabling superres for non-native-HDR content seeing as NV mention that VSR doesn't support HDR, and should also only enable RTX HDR when it's...

Oh might have an idea what it is, for RTX HDR to work this removed a check for it being HDR source so it'd use right color space, with SDR...