WideClient crashing

[dom1984]

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

[Thomas Richter]

Hi,

 

what application is running on the WideClient PC?

[dom1984]

Hi,

 

I'm trying to run it with SimPhysics.

 

Best,

 

Dominic

[Thomas Richter]

Hi,

 

just let WideClient run on its own or with something else if possible to see who forces the crash.

[alaxus]

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

[dom1984]

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

[Pete Dowson]

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

[dom1984]

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

[dom1984]

Pete, you're a genius. Not had a single crash since I changed the button scan interval.

 

Thanks,

 

Dominic

[Pete Dowson]

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