c0nnex

If you only serve the images that's no problem, but if you also serve the LED-lights (as SPAD.neXt does) , the driver will fail randomly. I noticed that using the proxy-API coming with SaiFlightSimX is very instable. Using the Driver-API directly is a lot better. And since i throttled them to 10 fps no freezing FIP were observed any more ( tested with up to 16 FIP connected, all updating at a rate of 10 fps (which is enough imho)). A pitty the DO-Driver does not allow more than one thread to connect :( It's tied to the process id.

Make sure your are not overstressing the DO-Interface. Throttle the update to 10 fps/sec. If you send updates too frequently the DO-Interface will respond with an exception and the affected FIP will freeze. DO-Interface is very picky about timing issues. FIP draw a LOT of USB power. Best practice: Run FIP on a separate HUB , do not connect more than 3 FIP to one HUB Also do not use the Yoke-Built-In HUB. You a separate HUB to chain devices. Turn on DO Debugging to see what is going on. Create a registry key [HKEY_LOCAL_MACHINE\SOFTWARE\Saitek\DirectOutput] "DebugLogFile"="c:\\temp\\saidebug2.log" I could have a look, but a lot of files missing in the repository...