On Fri Nov 29 22:30:56 2024 +0000, Rémi Bernon wrote:
If we want to test what happens with multiple joysticks with the same VID/PID the test driver would need to be fixed first, I believe it uses VID/PID to uniquely identify devices and I've had VM crashes when trying duplicate devices.
Oh, interesting, somehow I missed Joistick Id here while found those DirectInput properties keys.
But in a practical sense in terms of implementation, it looks like the case with artificially cleaned up registry is least interesting, in practice that works without cleaning registry keys before any controller replug? We could probably persist that in registry as well, although I am not sure whether it worth the complication, I still suggest to track it locally / in memory. Yes, device path may be not the best choice, I could do it using vid / pid and sequential index accounting for multiple controllers with duplicated vid / pid (and in that case it doesn't matter which index each of those identical controllers get on replug I guess).