dom1984 Posted January 5, 2014 Report Share Posted January 5, 2014 Hi, I run FSX in a networked configuration with FSX SP2 + latest version of FSUIPC on one PC and WideClient on another. Both PCs run Windows 8.1. I can get WideClient to connect but after a while it crashes. For example today I first started running it at 1745. It crashed at 1805, again at 1811 and then again at 1853. The error is always the same (see attached file). The faulting module seems to be DINPUT.DLL The FSUIPC and FSX machine works with no problems. Do let me know if you need any more information. Thanks in advance. Dominic wideclienterror.txt Link to comment Share on other sites More sharing options...
Thomas Richter Posted January 5, 2014 Report Share Posted January 5, 2014 Hi, what application is running on the WideClient PC? Link to comment Share on other sites More sharing options...
dom1984 Posted January 5, 2014 Author Report Share Posted January 5, 2014 Hi, I'm trying to run it with SimPhysics. Best, Dominic Link to comment Share on other sites More sharing options...
Thomas Richter Posted January 5, 2014 Report Share Posted January 5, 2014 Hi, just let WideClient run on its own or with something else if possible to see who forces the crash. Link to comment Share on other sites More sharing options...
alaxus Posted January 6, 2014 Report Share Posted January 6, 2014 DINPUT.DLL is the direct input module of DirectX. Maybe Direct X has an issue. Run dxdiag and see if you have any problems in the log file. cheers Link to comment Share on other sites More sharing options...
dom1984 Posted January 6, 2014 Author Report Share Posted January 6, 2014 Hi, I tried dxdiag - no errors were found in the logs. I also tried running WideFS on its own and still saw the same crash. Dominic Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 10, 2014 Report Share Posted January 10, 2014 Hi, I tried dxdiag - no errors were found in the logs. I also tried running WideFS on its own and still saw the same crash. Dominic I've seen this before. One of the joystick type devices installed on that PC has a bad driver. If you are not using any such devices, check the device manager for drivers installed, nevertheless, and uninstall them or update them. Failing that just stop Wideclient scanning joystick devices by setting ButtonScanInterval=0 in the [Config] section of the INI file. Pete Link to comment Share on other sites More sharing options...
dom1984 Posted January 30, 2014 Author Report Share Posted January 30, 2014 Thanks Pete. I have no controllers installed on the client PC so I will try setting ButtonScanInterval=0 and see how I get on. Thanks again. Dominic Link to comment Share on other sites More sharing options...
dom1984 Posted February 2, 2014 Author Report Share Posted February 2, 2014 Pete, you're a genius. Not had a single crash since I changed the button scan interval. Thanks, Dominic Link to comment Share on other sites More sharing options...
Pete Dowson Posted February 3, 2014 Report Share Posted February 3, 2014 Pete, you're a genius. Not had a single crash since I changed the button scan interval. Okay. But that does probably mean there's some rogue device or device driver registered in Windows. You might want to review the device list in Windows device manager. Regards Pete Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now