Léo Lam

Was the trace useful? https://github.com/libusb/libusb/files/672199/UsbDkTrace.zip The crash reported in #232 can be reproduced very simply, by using the [usbdk build of Dolphin](http://dl.dolphin-emu.org/prs/pr-4465-dolphin-latest-dbg-x64.7z) (here's the [source PR](https://dolp.in/pr4465) if needed), plugging in...

Thanks for looking into it! A small question though: is it allowed to use several libusb contexts and enumerate devices from several (pretty much independant) threads? That currently fails with...

I see, thanks for the advice! This should work good enough for our purposes. Since this is not a libusb issue, but a limitation in UsbDk, I'm closing this.

There are still some failures even when using a single libusb context, mostly when enumerating devices from two separate threads, which is why I reopened the issue, but it's not...

Just ended up calling it several times until it works.

Closing this again because it appears the thread safety issue with device enumeration is not related to the usbdk code, but rather to libusb (possibly only the Windows specific parts?)...

Alright, I'll reopen this issue then. FWIW, we ended up dropping support for usbdk and using several contexts with WinUSB after we identified and fixed bugs that prevented the WinUSB...

We are still using libusb as it lets us avoid having to write platform specific code. libusb works well enough on Linux and Windows as far as Dolphin is concerned.

Sounds like a good idea to me. Months ago I considered making the game nicer to play on large screens by doing the FOV edit you suggested and editing a...

No, it's entirely unrelated. This issue is about the camera, #44 is about the player controls (if I've understood it correctly).