krfilby Posted April 14, 2009 Report Posted April 14, 2009 Hi Peter, Since reinstalling FSX I have a problem with FSUIPC 4.5, when I open the tab to assign an axis I am not able to, as the rescan button is greyed out and no movement of any axis is recognised. Not only the rescan button but the clear, ignore axis, clear axis, delete this and delete all buttons also. All works well on the Buttons and Switches tab and I have no problem assigning Key presses. Am running FSX under Vista 64. Any help and guidance would be greatly appreciated. Regards Keith
Pete Dowson Posted April 14, 2009 Report Posted April 14, 2009 Since reinstalling FSX I have a problem with FSUIPC 4.5, when I open the tab to assign an axis I am not able to, as the rescan button is greyed out and no movement of any axis is recognised. Not only the rescan button but the clear, ignore axis, clear axis, delete this and delete all buttons also. It isn't detecting any DirectInput joysticks, then, or it cannot find a valid joystick number assignment to go with them. Please try using the attached utilities to see what can be detected. The JoyView one uses the Windows "joy" API (same as FSUIPC4 does for buttons) whilst DIView uses DirectInput (used by FSX for everything, but by FSUIPC4 only for axis assignment).. All works well on the Buttons and Switches tab and I have no problem assigning Key presses. Am running FSX under Vista 64. Does FSX see the axes? If not then it could be that your joystick drivers aren't 64-bit compatible. If FSX has no problems then I can only think that the Registry entries, the ones which relate the DirectInput identity of a joystick to its "joystick ID" number, are corrupted. Why did you re-install FSX by the way? It isn't normally advisable -- seems to create more problems than it solves. Or was this a Windows upgrade? If so, then maybe something went wrong with the joystick installs? BTW I'm away from tomorrow (Wednesday 15th) until Friday 24th, so apologies if I disappear before this is resolved. Regards Pete DIView.zip joyview.zip
krfilby Posted April 15, 2009 Author Report Posted April 15, 2009 Peter, Many thanks for your prompt reply. Using Diview all axis movements on all controllers are detected, so assume from your reply that my registry entries are corrupt? As far as FSUIPC was concerned all was running well untill I reinstalled FSX on another directory so drivers should be OK. Regards
Pete Dowson Posted April 15, 2009 Report Posted April 15, 2009 I only just have time for this one reply before leavingI'm away now till the 24th. Many thanks for your prompt reply. Using Diview all axis movements on all controllers are detected, so assume from your reply that my registry entries are corrupt? What about Joyview? Does that also show the axes? -- That's also important, because Joyview relies on the Joystick ID being intact. As far as FSUIPC was concerned all was running well untill I reinstalled FSX on another directory so drivers should be OK.Regards Re-installing FSX is well known by now to be rather fraught. It seems to cause more problems than it solves. Are you sure that SimConnect is all working okay? Check the FSUIPC4.LOG file, and its Install Log, see if there are any problems reported. Though I cannot think of anything that SimConnect could do to interfere with FSUIPC's DirectInput access. [EDIT] Final ideas before I disappear: 1) The DirectInput scanning in FSUIPC4 is repeated every time you re-enter the FSUIPC4 options, so try exiting and re-entering a few times, see if it can "re-discover" them. 2) There's some DirectX debugging options still in FSUIPC4. You can enable these as follows: Before running FSX, edit the FSUIPC4.INI file. Add these two lines to the [General] section (or replace them if there already): Debug=Please LogExtras=x200000 Run FSX, try the Axis assignments again, then look at the FSUIPC4.LOG file. Sorry, but I won't be around to help further till Friday 24th. Regards Pete
krfilby Posted April 23, 2009 Author Report Posted April 23, 2009 Pete, Joyview status is OK for Joysticks 1,2,5, & 6 all others status is error. After edit of ini file for debug and logextras as per you e-mail the logfile is as below ********* FSUIPC4, Version 4.50 by Pete Dowson ********* Reading options from "C:\FSX\Modules\FSUIPC4.ini" User Name="Keith Filby" User Addr="krfilby@gmail.com" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired Running inside FSX (using SimConnect Acc/SP2 Oct07) Module base=61000000 Wind smoothing fix is fully installed DebugStatus=15 140 System time = 15:32:07 140 FLT UNC path = "C:\Users\Keith\Documents\Flight Simulator X Files\" 140 FS UNC path = "C:\FSX\" 1201 LogOptions=00000000 02000011 1201 SimConnect_Open succeeded: waiting to check version okay 37362 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 37362 Initialising SimConnect data requests now 37362 FSUIPC Menu entry added 37456 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 37456 c:\users\keith\documents\flight simulator x files\At Stansted.FLT 37456 C:\FSX\SimObjects\Airplanes\LVLD_B763\B767-300.AIR 309069 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N 309989 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 309989 System time = 15:37:17, Simulator time = 15:32:46 (14:32Z) 310426 Aircraft="Level D Simulations B767-300ER" 311081 Advanced Weather Interface Enabled 341408 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 341408 Sim stopped: average frame rate for last 32 secs = 14.4 fps 341424 #### Initialising Dlrectinput Axis Scanning ... 341424 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FA\Calibration\0" 341424 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00F2\Calibration\0" 341424 joyGetDevCaps for device 2 returned error 165 [000000A5] 341424 joyGetDevCaps for device 3 returned error 165 [000000A5] 341424 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FF\Calibration\0" 341424 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_8000\Calibration\0" 341424 joyGetDevCaps for device 6 returned error 165 [000000A5] 341424 joyGetDevCaps for device 7 returned error 165 [000000A5] 341424 joyGetDevCaps for device 8 returned error 165 [000000A5] 341424 joyGetDevCaps for device 9 returned error 165 [000000A5] 341424 joyGetDevCaps for device 10 returned error 165 [000000A5] 341424 joyGetDevCaps for device 11 returned error 165 [000000A5] 341424 joyGetDevCaps for device 12 returned error 165 [000000A5] 341424 joyGetDevCaps for device 13 returned error 165 [000000A5] 341424 joyGetDevCaps for device 14 returned error 165 [000000A5] 341424 joyGetDevCaps for device 15 returned error 165 [000000A5] 341424 #### Completed Dlrectinput Axis Scanning 349286 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 354013 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 359426 System time = 15:38:07, Simulator time = 15:33:22 (14:33Z) 359426 *** FSUIPC log file being closed Average frame rate for running time of 36 secs = 14.2 fps Memory managed: 78 Allocs, 78 Freed ********* FSUIPC Log file closed *********** Regards Keith
Pete Dowson Posted April 24, 2009 Report Posted April 24, 2009 Joyview status is OK for Joysticks 1,2,5, & 6 all others status is error. After edit of ini file for debug and logextras as per you e-mail the logfile is as below ... 341424 #### Initialising Dlrectinput Axis Scanning ... 341424 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FA\Calibration\0" 341424 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00F2\Calibration\0" 341424 joyGetDevCaps for device 2 returned error 165 [000000A5] 341424 joyGetDevCaps for device 3 returned error 165 [000000A5] 341424 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FF\Calibration\0" 341424 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_8000\Calibration\0" 341424 joyGetDevCaps for device 6 returned error 165 [000000A5] 341424 joyGetDevCaps for device 7 returned error 165 [000000A5] 341424 joyGetDevCaps for device 8 returned error 165 [000000A5] 341424 joyGetDevCaps for device 9 returned error 165 [000000A5] 341424 joyGetDevCaps for device 10 returned error 165 [000000A5] 341424 joyGetDevCaps for device 11 returned error 165 [000000A5] 341424 joyGetDevCaps for device 12 returned error 165 [000000A5] 341424 joyGetDevCaps for device 13 returned error 165 [000000A5] 341424 joyGetDevCaps for device 14 returned error 165 [000000A5] 341424 joyGetDevCaps for device 15 returned error 165 [000000A5] 341424 #### Completed Dlrectinput Axis Scanning Well, FSUIPC4 agrees with Joyview (but FSUIPC numbering starts from 0 instead of 1) -- the 4 devices it found where 0,1,4,5. All the others errored, same as in Joyview. So, the mystery deepens. FSUIPC4 sees the devices but NEVER (?) sees any axis values change? You ARE waggling the levers aren't you? FSUIPC ignores the first 10 or 20 readings to avoid bad "wake-up" values.. Then it only sees changes. Maybe you could post your FSUIPC4.INI file here, please. I may need to add some more logging, to see what happens after those " Trying: "HKLM\..." lines. Regards Pete
Pete Dowson Posted April 24, 2009 Report Posted April 24, 2009 So, the mystery deepens. .... I may need to add some more logging, to see what happens after those " Trying: "HKLM\..." lines. I've looked at the code again. After those "Trying ..." lines, FSUIPC4 tries to do the following: 1. Open the Registry key you see logged. If this fails then it simply aborts that joystick and moves on. 2. If it opens okay, it reads the key called "Joystick Id". This is crucial. If it succeeds you get "Found correct Joystick ID" logged. Otherwise you'd get "No joystick ID there" logged. Since neither of the messages for (2) appear, it looks like there are no Registry entries formed like this: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FA\Calibration\0" where the VID and PID numbers (here 068E and 00FA) vary according to joystick maker and model. My code does search for Keys with 0 then 1 then 2etc in the last position (where you see \0 above). However, I've no way of determining where that sequence ends except by there being, apparently, no more. I now think that it is possible for there to be MISSING entries (though this has never happened before in the three+ years of FSUIPC4). I am altering my code to continue to search after a missing entry up to at least \9. I hope that will fix it. Meanwhile, do you think you might be able to use "Regedit" (Start - Run - Regedit) to look for me, find the keys like those above, let me know? I'll post a link to a test version of FSUIPC4 later. Regards Pete
Pete Dowson Posted April 24, 2009 Report Posted April 24, 2009 I'll post a link to a test version of FSUIPC4 later. Okay. Try this please: http://fsuipc.simflight.com/beta/FSUIPC4512.zip Keep the extra logging I asked for in for the first test, and show me the Log whether it works or not. Thanks, Pete
krfilby Posted April 24, 2009 Author Report Posted April 24, 2009 Peter, Have followed the registration entries down and what I have is.......CurrentControlSet/Control/MediaProperties/PrivateProperties/DirectInput/VID_068E&PID_00FA/Calibration/0/Type/Axes/0,1,2,3,4,5(These last numbers are empty folders). I did run FSUIPC4.512 and resultand logfile as below. ********* FSUIPC4, Version 4.512 by Pete Dowson ********* Reading options from "C:\FSX\Modules\FSUIPC4.ini" User Name="Keith Filby" User Addr="krfilby@gmail.com" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired Running inside FSX (using SimConnect Acc/SP2 Oct07) Module base=61000000 Wind smoothing fix is fully installed DebugStatus=15 94 System time = 17:06:57 94 FLT UNC path = "C:\Users\Keith\Documents\Flight Simulator X Files\" 94 FS UNC path = "C:\FSX\" 1232 LogOptions=00000000 02000011 1232 SimConnect_Open succeeded: waiting to check version okay 62837 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 62837 Initialising SimConnect data requests now 62837 FSUIPC Menu entry added 62853 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 62853 c:\users\keith\documents\flight simulator x files\At Stansted.FLT 62853 C:\FSX\SimObjects\Airplanes\LVLD_B763\B767-300.AIR 414994 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N 415228 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 415743 System time = 17:13:53, Simulator time = 17:08:01 (16:08Z) 416039 Aircraft="Level D Simulations B767-300ER" 416257 Advanced Weather Interface Enabled 425992 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 426023 #### Initialising Dlrectinput Axis Scanning ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FA\Calibration\0" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FA\Calibration\1" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FA\Calibration\2" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FA\Calibration\3" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FA\Calibration\4" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FA\Calibration\5" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FA\Calibration\6" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FA\Calibration\7" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FA\Calibration\8" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FA\Calibration\9" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00F2\Calibration\0" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00F2\Calibration\1" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00F2\Calibration\2" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00F2\Calibration\3" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00F2\Calibration\4" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00F2\Calibration\5" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00F2\Calibration\6" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00F2\Calibration\7" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00F2\Calibration\8" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00F2\Calibration\9" 426023 Missing key? Trying a later one ... 426023 joyGetDevCaps for device 2 returned error 165 [000000A5] 426023 joyGetDevCaps for device 3 returned error 165 [000000A5] 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FF\Calibration\0" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FF\Calibration\1" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FF\Calibration\2" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FF\Calibration\3" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FF\Calibration\4" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FF\Calibration\5" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FF\Calibration\6" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FF\Calibration\7" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FF\Calibration\8" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FF\Calibration\9" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_8000\Calibration\0" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_8000\Calibration\1" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_8000\Calibration\2" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_8000\Calibration\3" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_8000\Calibration\4" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_8000\Calibration\5" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_8000\Calibration\6" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_8000\Calibration\7" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_8000\Calibration\8" 426023 Missing key? Trying a later one ... 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_8000\Calibration\9" 426023 Missing key? Trying a later one ... 426023 joyGetDevCaps for device 6 returned error 165 [000000A5] 426023 joyGetDevCaps for device 7 returned error 165 [000000A5] 426023 joyGetDevCaps for device 8 returned error 165 [000000A5] 426023 joyGetDevCaps for device 9 returned error 165 [000000A5] 426023 joyGetDevCaps for device 10 returned error 165 [000000A5] 426023 joyGetDevCaps for device 11 returned error 165 [000000A5] 426023 joyGetDevCaps for device 12 returned error 165 [000000A5] 426023 joyGetDevCaps for device 13 returned error 165 [000000A5] 426023 joyGetDevCaps for device 14 returned error 165 [000000A5] 426023 joyGetDevCaps for device 15 returned error 165 [000000A5] 426023 #### Completed Dlrectinput Axis Scanning 459532 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 466771 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 471934 System time = 17:14:49, Simulator time = 17:08:18 (16:08Z) 471934 *** FSUIPC log file being closed Average frame rate for running time of 18 secs = 15.7 fps Memory managed: 70 Allocs, 70 Freed ********* FSUIPC Log file closed *********** needless to say I did waggle the stick and hit rescan often but the greyouts remain. Regards Keith
Pete Dowson Posted April 24, 2009 Report Posted April 24, 2009 Have followed the registration entries down and what I have is.......CurrentControlSet/Control/MediaProperties/PrivateProperties/DirectInput/VID_068E&PID_00FA/Calibration/0/Type/Axes/0,1,2,3,4,5(These last numbers are empty folders). Erthe Type/Axes levels aren't relevant. Stop after Calibration/0 and see if there are keys there -- there should be at least GUID and Joystick Id. They are the entries I need. I did run FSUIPC4.512 and resultand logfile as below. Which only proves that my original code was correct and there's no point in going past a missing entry. :-( What I don't understand is that apparently you found: HKLM/SYSTEM/CurrentControlSet/Control/MediaProperties/PrivateProperties/DirectInput/VID_068E&PID_00FA/Calibration/0 yet FSUIPC4 failed to find that, or at least was refused: 426023 Trying: "HKLM\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FA\Calibration\0" 426023 Missing key? Trying a later one ... I'm removing the changes I made to FSUIPC4. At present there's nothing I can really add -- though I may try asking for an Error number for the failure on the key opening. Two things now: 1. Can you please go back to RegEdit, get to the HKLM/SYSTEM/CurrentControlSet/Control/MediaProperties/PrivateProperties/DirectInput level, with the "DirectInput" label highlit, right-click and select "export". Export as "DirectInput.reg" (it will add the .reg), ,then ZIP the file and send it to me at petedowson@btconnect.com. 2. My only other guess at present is that you somehow have the system so protected that it is stopping FSUIPC even reading registry entries. I cannot understand how that can be unless it is a third-party add-on which is over-enthusiastic. But try running FSX "as administrator" (that is , right-click it, and select "run as administrator"). Regards Pete
Pete Dowson Posted April 25, 2009 Report Posted April 25, 2009 Peter,Have followed the registration entries down and what I have is.......CurrentControlSet/Control/MediaProperties/PrivateProperties/DirectInput/VID_068E&PID_00FA/Calibration/0/Type ... Thanks for the Registry export file. Did you not notice that you have been looking in a different place to that I requested? Here's a line from it: [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput You are looking in HKCU (HKEY_CURRENT_USER) not HKLM (HKEY_LOCAL_MACHINE) as I am logging and as I requested. Now, this is actually a big clue, and one I should have noticed straight away! Mea culpa. Windows XP stores the entries I need in HKLM whilst, at least on all the Vista systems I've seen, Vista stores them in HKCU. You are using Vista, and certainly the correct entries ARE in HKCU, yet FSUIPC is looking in HKLM. This means that FSUIPC (and therefore FSX) thinks you are running on XP, not Vista. So, tell me, have you, for any strange reason, told Windows to run FSX in some sort of XP compatibility mode (via right-click properties)? If so, why? Try letting it run knowing it is running in Vista, please -- when running in XP a lot of the registry and disk paths are different. Otherwise, somehow, FSUIPC is not getting the correct Windows version number from your system. [LATER] Before "correcting" the settings for FSX (which is, after all, fully Vista-aware), please try FSUIPC 4.514, in which I've tried HKCU when getting nothing from HKLM. If it succeeds it subsequently assumes it is running on Vista so that other differences won't mess it up! ;-) http://fsuipc.simflight.com/beta/FSUIPC4514.zip Regards Pete
krfilby Posted April 25, 2009 Author Report Posted April 25, 2009 Pete, Running FSUIPC4.514 worked and all buttons lit up except "Clr Ignor". You are correct I am running FSX in compatabilty mode for Windows XP service pack 2. Something I read on the Level D forum in fact It is posted as a sticky by the administrator, part as below. With Vista, you can reconfigure your system so that it works similar to the way XP worked and this may take care of many issues. However, there still could be issues. Some products and applications (of all types) will run just perfect, and some may not run at all. Some may run with updates, and it is even possible some may work on some Vista installations and not work on other Vista installations. So please be aware that Vista is a major change! So you should be prepared for both the good and bad. In less common cases, some software may never be Vista compatible. So do check to see if and when upgrading to Vista is right for you by seeing if your most important software is Vista compatible before upgrading or switching to Vista. Guess I should've paid more attention to the reservations. I have just rebooted FSX using FSUIPC 4.514 with the compatability mode unchecked and everything \OK except the axis tab "Clr Ignor" which remains greyed out. Regards Keith
Pete Dowson Posted April 25, 2009 Report Posted April 25, 2009 Running FSUIPC4.514 worked and all buttons lit up except "Clr Ignor". "Clr Ignor" is only usable if you've already told the assignment tab to ignore any axes, else there's nothing to clear! You are correct I am running FSX in compatabilty mode for Windows XP service pack 2. Something I read on the Level D forum in fact It is posted as a sticky by the administrator, part as below. I don't think that is at all relevant to FSX, which was designed with Vista in mind and works better if it knows it is running under Vista. The problem with setting compatibility mode is that Windows then lies to the program about what version it is, so any version-specific code does the wrong thing. You might need to use compatibility mode for some older add-ons which aren't Vista-aware, but otherwise I'd recommend you leave things be, as the designers intended. :-) Regards Pete
krfilby Posted April 26, 2009 Author Report Posted April 26, 2009 Pete, All running AOK thank you so much for you help and for a great application. Regards Keith
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