Jump to content
The simFlight Network Forums
Sign in to follow this  
Shepred

Sim Crashes, after running for a short time

Recommended Posts

What I have connected is:

Logitech G15 Keyboard, Razer Nostromo Keypad, Logitech 3D Extreme Pro Joystick, Razer Naga Mouse and the Saitek Pro Flight Yoke, with the throttle connected to that. Only reason I have the Yoke & Joystick, is that I can't connect the Saitek throttle's to my computer, without them going through the Yoke.

I think one of those is causing the hang when interrogated. Do that logging as in my last post, please, and then perhaps try disconnecting all those and see if that allows FSX to run okay. If so, connect them back one at a time, each time going into fSUIPC options to see if that works or hangs.

Pete

Share this post


Link to post
Share on other sites

The FSUIPC4.LOG file is here:

...And stops with this line:


38048 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0000&PID_0111\Calibration\2137185"
[/CODE]

Phew! With 2,137,185 lines like that altogether?

What device isthe one with Vendoe ID = 0 and Product ID = 111 I wonder. I don't thing a PID or 0 is valid, so it's probably a maker not registered with Microsoft.

There's a program called HidScanner is the Download Links thread about Lua. Could you get that, run it, and show me the log that produces. It should list all the devices and their full names.

Are there any game controllers you can calibrate or test in the Windows control panel and which you haven't done so yet?

Meanwhile I'll look here and see why the search for device calibration data doesn't stop (or at least doesn't stop successfully).

Pete

Share this post


Link to post
Share on other sites

Hi Pete,

I just tried removing the Razer Nostromo Keypad. And woila, FSX and FSUIPC opens and works like a treat.

Here's the log:


********* FSUIPC4, Version 4.90 by Pete Dowson *********
Running inside FSX on Windows 7
Module base=5AEC0000
User Name="Jakob Marker"
User Addr="jakob_marker@live.dk"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
421 System time = 17/05/2013 17:52:03
421 FLT path = "C:\Users\Jakob\Documents\Flight Simulator X Files\"
452 Trying to connect to SimConnect Acc/SP2 Oct07 ...
468 FS path = "D:\FSX\"
733 #### Initialising Dlrectinput Axis Scanning ...
733 joyGetDevCaps for device 0 returned error 165 [000000A5]
733 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C215\Calibration\0"
733 Found correct joystick Id 1
733 ... and a "GUID" value
749 ... okay, Acquired device!
749 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0BAC\Calibration\0"
749 Found correct joystick Id 2
749 ... and a "GUID" value
749 ... okay, Acquired device!
749 joyGetDevCaps for device 3 returned error 165 [000000A5]
749 joyGetDevCaps for device 4 returned error 165 [000000A5]
749 joyGetDevCaps for device 5 returned error 165 [000000A5]
749 joyGetDevCaps for device 6 returned error 165 [000000A5]
749 joyGetDevCaps for device 7 returned error 165 [000000A5]
749 joyGetDevCaps for device 8 returned error 165 [000000A5]
749 joyGetDevCaps for device 9 returned error 165 [000000A5]
749 joyGetDevCaps for device 10 returned error 165 [000000A5]
749 joyGetDevCaps for device 11 returned error 165 [000000A5]
749 joyGetDevCaps for device 12 returned error 165 [000000A5]
749 joyGetDevCaps for device 13 returned error 165 [000000A5]
749 joyGetDevCaps for device 14 returned error 165 [000000A5]
749 joyGetDevCaps for device 15 returned error 165 [000000A5]
749 #### Completed Dlrectinput Axis Scanning
749 LogOptions=00000000 02000011
749 SIM1 Frictions access gained
749 Wind smoothing fix is fully installed
749 G3D.DLL fix attempt installed ok
749 SimConnect_Open succeeded: waiting to check version okay
749 Trying to use SimConnect Acc/SP2 Oct07
1825 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)
1825 Initialising SimConnect data requests now
1825 FSUIPC Menu entry added
1856 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
1856 D:\FSX\FLIGHTS\OTHER\FLTSIM.FLT
1856 D:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR
16848 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
17862 Starting everything now ...
17909 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
17909 System time = 17/05/2013 17:52:20, Simulator time = 17:52:05 (00:52Z)
17909 Aircraft="Aircreation582SL red"
19063 Advanced Weather Interface Enabled
20265 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y
20280 #### Initialising Dlrectinput Axis Scanning ...
20280 joyGetDevCaps for device 0 returned error 165 [000000A5]
20280 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_046D&PID_C215\Calibration\0"
20280 Found correct joystick Id 1
20280 ... and a "GUID" value
20280 ... okay, Acquired device!
20280 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0BAC\Calibration\0"
20280 Found correct joystick Id 2
20280 ... and a "GUID" value
20280 ... okay, Acquired device!
20280 joyGetDevCaps for device 3 returned error 165 [000000A5]
20280 joyGetDevCaps for device 4 returned error 165 [000000A5]
20280 joyGetDevCaps for device 5 returned error 165 [000000A5]
20280 joyGetDevCaps for device 6 returned error 165 [000000A5]
20280 joyGetDevCaps for device 7 returned error 165 [000000A5]
20280 joyGetDevCaps for device 8 returned error 165 [000000A5]
20280 joyGetDevCaps for device 9 returned error 165 [000000A5]
20280 joyGetDevCaps for device 10 returned error 165 [000000A5]
20280 joyGetDevCaps for device 11 returned error 165 [000000A5]
20280 joyGetDevCaps for device 12 returned error 165 [000000A5]
20280 joyGetDevCaps for device 13 returned error 165 [000000A5]
20280 joyGetDevCaps for device 14 returned error 165 [000000A5]
20280 joyGetDevCaps for device 15 returned error 165 [000000A5]
20280 #### Completed Dlrectinput Axis Scanning
32136 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
33603 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y
38829 System time = 17/05/2013 17:52:41, Simulator time = 17:52:08 (00:52Z)
38829 *** FSUIPC log file being closed
Average frame rate for running time of 5 secs = 19.9 fps
G3D fix: Passes 10392, Null pointers 0, Bad pointers 0, Separate instances 0
Memory managed: 6 Allocs, 6 Freed
********* FSUIPC Log file closed ***********
[/CODE]

It seems that was what caused the problem, do you know of any way I can still have my Nostromo plugged in, and play FSX?

Share this post


Link to post
Share on other sites

Oh, one thing you could do for me. Can you run RegEdit (from the Start button) and go to

HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0000&PID_0111\

and see if there is a "Calibration" section in there and if so what it contains in the way of keys and data fields? Or even simpler, Export that key to a file and paste its contents here. Dodn't double click the exported file, rename it as a text file first.

Thanks,

Pete

Share this post


Link to post
Share on other sites

I just tried removing the Razer Nostromo Keypad. And woila, FSX and FSUIPC opens and works like a treat.

Oh, good. Well done.

It seems that was what caused the problem, do you know of any way I can still have my Nostromo plugged in, and play FSX?

I'll need to work out why it is doing what it is doing with that device. The registry entries for it would be very handy so I can determine the best way to eliminate it without affecting other devices.

Does this keypad produce button presses or axis inputs for you, or is it really a keyboard? If the latter that it appears to be mis-classified by its IUdentifiers, as I don't scan for keyboards.

Regards

Pete

Share this post


Link to post
Share on other sites

I'll need to work out why it is doing what it is doing with that device. The registry entries for it would be very handy so I can determine the best way to eliminate it without affecting other devices.

Does this keypad produce button presses or axis inputs for you, or is it really a keyboard? If the latter that it appears to be mis-classified by its IUdentifiers, as I don't scan for keyboards.

Hi Pete,

Here's a link for the product: http://www.razerzone.com/gaming-keyboards-keypads/razer-nostromo

Share this post


Link to post
Share on other sites

Surely, I attached the files.

There was only the one line, the key I asked you to look at, in that file! There should (must as far as Iknew) be entries below it. For example, here's the RegEdit export file for just one of my devices:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_00FF&PID_7927]

[HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_00FF&PID_7927\Calibration]

[HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_00FF&PID_7927\Calibration\0]

"GUID"=hex:c0,2e,2b,b0,da,30,e2,11,80,02,44,45,53,54,00,00

[HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_00FF&PID_7927\Calibration\0\Type]

[HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_00FF&PID_7927\DeviceInstances]

"1&2D595CA7&0&0000"=hex:02

"1&2D595CA7&1&0000"=hex:02

"1&2D595CA7&2&0000"=hex:02

"1&2D595CA7&3&0000"=hex:02

"1&2D595CA7&4&0000"=hex:02

Pete

Share this post


Link to post
Share on other sites

Hi Pete,

Yes, it works like a plain keyboard, but just a different layout.

I am unsure where to find the entire Registry for it, i'd gladly send it over, if you tell me where to find it :razz:

Share this post


Link to post
Share on other sites

I am unsure where to find the entire Registry for it, i'd gladly send it over, if you tell me where to find it :razz:

Sorry, you misunderstand. There appears to be a key for it entitled:

[HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0000&PID_0111]

because that's the one you sent me. but the key is normally there for a reason -- because there's ddata or sub-keys associated with it. The file you provided ONLY contained the Key, as above, which we knew in any case as that was what you looked for. I need to know what that key contains.

If it contains nothing at all, if it is jusr a waste of Registry space, please say so. It just seems unlikely (along with that VID or 0).

Pete

Share this post


Link to post
Share on other sites

Hi Pete,

I went into the RegEdit, navigated to that file, exported it to the desktop, edited it to a .txt file, and that's what it contained. I tried uploading the .reg file as well, but seems like the forum won't let me.

Share this post


Link to post
Share on other sites

I went into the RegEdit, navigated to that file, exported it to the desktop, edited it to a .txt file, and that's what it contained. I tried uploading the .reg file as well, but seems like the forum won't let me.

Correct. Never send REG files in any case, because if double clicked they amend the Registry!!

The point I need to know is whether there is anything at all within that KEY. It sounds like there isn't, else presumably it would be in the file, but please can you actually verify that by LOOKING at it. i.e. Will it expand to anything lower? Are there any data entries on the right for that key?

If there's only the key you went to and nothing else it evidently serves no purpose whatsoever, so I don't know why it is there. However, I can take steps to deal with it. I just need to know.

Pete

Share this post


Link to post
Share on other sites

Hi Pete,

There is nothing else inside that Reg file other than this:


Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0000&PID_0111]
[/CODE]

Share this post


Link to post
Share on other sites

Just one final question, am I okay to install the rest of my addons into FSX?

I don't see any reason not to.

I'll have the update to 4.902 available in an hour or two. You'll just need to download it from Download Links and copy the DLL (only) into the Modules folder.

Regards

Pete

Share this post


Link to post
Share on other sites

Hi Pete,

I have just replaced the FSUIPC4.DLL with the new one, provided in the link. With the Razer Nostromo plugged in it works, just fine! ;-)

Share this post


Link to post
Share on other sites

I have just replaced the FSUIPC4.DLL with the new one, provided in the link. With the Razer Nostromo plugged in it works, just fine! ;-)

Thanks for te confirmation. I'll change the Download Links entry now ...

Pete

Share this post


Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.