Pete Dowson

Is there any more information? Check the FSX Modules folder for an FSUIPC4.LOG file -- this will at least show (a) if FSUIPC4 got to run at all, and if so (b) how far it got. And use the Windows "Event viewer" to look for the windows-detected crash which must have led to this report in the first place. One of the more usual reasons for this sort of error to occur is a corrupted WX (weather) file, or a corrupted "weatherstationlist.bin" file. The problem with those is that, being binary, they aren't properly checked and when FSUIPC asks SimConnect to supply the weather, bang. Pete

The only way that can happen is when SimConnect stops responding. The problem will be an overloaded or failed SimConnect interface, probably caused by other add-ons. The details of what is going on will be shown in the FSUIPC4.LOG file. Please find that file in the FSX Modules folder, and paste its contents here -- use the <> button above the Edit area to enclose it. Pete

You cannot have assignments in FSUIPC and leave controllers enabled in FS or P3D because it will still auto-assign things now and then. Do one or the other. You can still calibrate etc in FSUIPC even if you assign in FS/P3D. There are various Mouse facilities in FSUIPC. which include panning, zooming and moving your eyepoint. Why not use those? Have you not read the documentation or browsed the options on screen? Check the options on the Miscellaneous tab. The Mouselook and Mousemove facilities were added over two years ago, in version 4.84 (July 2012)! If you must enable controllers in P3D, you must use P3D for assignments rather than FSUIPC if you don't want periodic trouble with double assignments when P3D does its automatic thing. Pete

Apologies. I'm afraid that FSUIPC is now so complex, and old (FSUIPC4, the 4th incarnation) has now been continuously developed now for 9 years -- and every update with no extra charge, mind -- that an old man like myself (well over 71 now), who should have stopped years ago, doesn't remember everything all the time and sometimes makes mistakes. But I do try and make up for it. Believe me, there are plenty of bug reports here which the reporter "definitely shows is caused by FSUIPC" which are nothing of the kind and in fact are mostly shown not to be later on. Problems which come and go with FSUIPC's presence are often much more complex than you'd think, what with the resulting different memory arrangements plus so many applications, be they inside and outside FS, using it when it is detected. Apologies again, and do have a very Happy Christmas! Pete

That just means you have them assigned to more than one thing, in different places. Most likely is that you are trying to assign in FSUIPC without disabling controllers in FS. Either do all assignments in FS, or all in FSUIPC. It doesn't matter where you do them, just only in one place! You can calibrate in FSUIPC, if you wish, no matter where you assign them. If you assign in FS you simply select the reverse option there to reverse the direction. If you calibrate in FSUIPC the reverse is the REV option. But don't reverse in both places or they will cancel out. And calibrate AFTER selecting reverse, not before! There is a User Guide supplied with FSUIPC, in the FSUIPC documents folder. Take a look sometime, it will help. Pete

The Forum is accessible through the same Steam app you used to download / install / start FSX-SE. Check the right-hand side. For registry editing, use Windows Start - Run. Type Regedit <ENTER> and you'll get an Explorer-type window where you can open up HKEY_LOCAL_MACHINE, then SOFTWARE ... and so on. When you find the entry above, just make sure it is highlighted and hit Delete. Pete

Yes, something evidently weird happened during your FSX S-E install? Best report this on the Steam FSX forum. Or are you using some sort of migration program which messes with paths and doesn't understand FSX-SE? Even the utilities designed to "fix" FSX registry pointers might do this, until they are fixed to recognise FSX-SE. Meanwhile you'll need to delete the whole registry entry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 SetupPath=D:\Microsoft Flight Simulator X\ or maybe correct it. But since it isn't normally there it would be better to delete it. (I checked on my PC, and it is correct in HKEY_CURRENT_USER, AppPath, as you found). Pete

Well, the actual statement of the error would have been a good start. Why photograph text? Makes no sense. If there was a Windows detected crash then there will be an entry in the windows Event Viewer. If FSUIPC actually ran at all, which isn't usual in these circumstances, there will be an FSUIPC4.LOG file in the FSX Modules folder. Have you checked the FAQ subforum thread "FSX fails to run after FSUIPC4 first installed"? That's where the most common loading problem, caused by SimConnect trust issues, is discussed at length. Pete

I don't want photos. Please just describe the problem. Try using words. I can usually understand them. Thanks, Pete

Hmm. Very confusing. I've modified the Installer slightly to log the path at the point where it finds it. It's in the Installer for 4.938a, which I'm just uploading now. If you could run that and show me the log, please, I might be able to understand what is happening. Pete

FSUIPC has nothing to do with "Steam/steamapps/common/FSX/SDK/Core Utilities Kit/SimConnectSDK/legacyinterfaces.". What are you messing there for? FSUIPC can and does use the FSX-SE version of Simconnect which should have been correctly installed by Steam. I can't guess what the error is, and you've told me nothing about it. What are these mytsterious "issues" you seem reluctant to even describe? I suspect you have something else going on there, but you aren't telling me anything. Pete

What error did you get? No one else has reported any loading error before. What files are you removing? Pete

Hmm. Very strange. The installer is getting the path from HKEY_LOCAL_MACHINE, parameter "SetupPath". What does that say in your Registry? The Installer checks there first, only going to HKEY_CURRENT_USER etc if it can't find it there. I don't want ot have to try both and make some random decision between them. They should either point to the same path, or one of them be omitted. Else it makes no sense. I shall have to log a bit more information to see what is going on in these cases. Pete

Fixed it -- Mouse Macro creation now works and the hooks don't mess up mouse operations. 4.938a is now available, manual install only. Pete

Ok, it appears your registry shows FSX-SE installed in the wrong folder. can you check? Using Regedit, look at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 for the parameter "SetupPath" or "AppPath" Oh, or it could be in HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 Pete

It is only greyed out when you can't change it! You can't change it if you've made an assignment using it. You need to deselect the assignment, below, first! The User Guide is your friend! Pete

Sorry, there's not enough information there for me to understand this. Please always post the entire log file. Pete

Okay. I see there is a problem with some knobs and buttons -- for me, in Virtual Cockpit mode only. I think it must be to do with the Mouse Macro making hook. I can't see what is wrong at present, so i'll make an Interim version with Mouse Macro making eliminated, for FSX-SE only, and try to fix it properly tomorrow. Meanwhile, download FSUIPC 4.938a from the Download Links subforum -- look out for it in the next hour or so. You'll need to replace the FSUIPC4.DLL only, in the FSX Modules folder. [LATER] Fixed it! 'Twas easier than I thought. 4.938a is now available for manual install. Pete

The Schiratti page is not mine! I cannot change the words and have to wait for Mr. Schiratti to change them. But the link always points to the latest version! There are also links to ALL my programs in the Download Links subforum her. That is why is it called "Download Links". Pete

Sorry, I do not know why they say that. Best ask over in a PMDG support forum I think. Pete

As reported in another thread , the 4.938 installer was fixed for this a couple of hours after I saw it reported, i.e. about 13 hours ago. Please download again! Pete

The behaviour you reported, i.e. "When only any one of these controllers is plugged in, FSUIPC can detect it and I can make assignments which work. If I make assignments for each controller in this manner and then try to fly with both of them plugged in, there is a constant haywire control output!" is unique. I've never heard of anything like that and have absolutely no idea how it could happen. It makes no sense. Could you describe "constant haywire control output!" more precisely, as I cannot actually envisage what you mean by that? Can you also try starting with default settings. i.e. before running FS, rename your FSUIPC4.INI file so that it make a new one. Maybe there's something tangled up there. FSUIPC detects and reads these things using the same interface as FS, so it's a real puzzle. You can make FSUIPC log more information about its detection system by adding these lines to the [General] section of the INI file before running FS: Debug=Please LogExtras=x200000 All this stuff is buried in the Registry. Here's an example from mine, relating to my test Saitek Throttle Quadrant. This extract is produced by the Regedit "Export" function: [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D] [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration] [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\0] "GUID"=hex:c0,de,ab,b0,a5,6d,e0,11,80,01,44,45,53,54,00,00 "Joystick Id"=hex:00,00,00,00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\0\Type] [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\0\Type\Axes] [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\0\Type\Axes\0] "Calibration"=hex:00,00,00,00,80,00,00,00,ff,00,00,00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\0\Type\Axes\1] "Calibration"=hex:00,00,00,00,80,00,00,00,ff,00,00,00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\0\Type\Axes\2] "Calibration"=hex:00,00,00,00,80,00,00,00,ff,00,00,00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\DeviceInstances] "8&2D4EEC&0&0000"=hex:02 "9&11EBDAD6&0&0000"=hex:02 "7&3AFC8A82&0&0000"=hex:02 "7&25515117&0&0000"=hex:02 You'll see the GUID and ID in the third entry down, thus: "GUID"=hex:c0,de,ab,b0,a5,6d,e0,11,80,01,44,45,53,54,00,00 "Joystick Id"=hex:00,00,00,00 The GUID in "normal" form becomes {B0ABDEC0-6DA5-11E0-8001-444553540000}, because of the Lo-Hi reversal of byte orders in Intel format numerc representation. The ID used by FSUIPC in this case is 0, ie Joystick 0 in the assignments tab. Maybe your Registry is in a tangle? Might be worthtrying to uninstall the devices (in Windows Device Maager) and re-installing them. The debug logging for this, my only device connected on this test machine, shows simply this: 61043 #### Initialising Dlrectinput Axis Scanning ... 61043 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\0" 61043 Found correct joystick Id 0 61043 ... and a "GUID" value 61043 ... okay, Acquired device! 61059 joyGetDevCaps for device 1 returned error 165 [000000A5] 61059 joyGetDevCaps for device 2 returned error 165 [000000A5] 61059 joyGetDevCaps for device 3 returned error 165 [000000A5] 61059 joyGetDevCaps for device 4 returned error 165 [000000A5] 61059 joyGetDevCaps for device 5 returned error 165 [000000A5] 61059 joyGetDevCaps for device 6 returned error 165 [000000A5] 61059 joyGetDevCaps for device 7 returned error 165 [000000A5] 61059 joyGetDevCaps for device 8 returned error 165 [000000A5] 61059 joyGetDevCaps for device 9 returned error 165 [000000A5] 61059 joyGetDevCaps for device 10 returned error 165 [000000A5] 61059 joyGetDevCaps for device 11 returned error 165 [000000A5] 61074 joyGetDevCaps for device 12 returned error 165 [000000A5] 61074 joyGetDevCaps for device 13 returned error 165 [000000A5] 61074 joyGetDevCaps for device 14 returned error 165 [000000A5] 61074 joyGetDevCaps for device 15 returned error 165 [000000A5] 61074 #### Completed Dlrectinput Axis Scanning The 15 errors are just for non-existent devices 1 to 15 (FSUIPC only supports 0-15 hardware joystick devices). Pete

Same places as always -- Dowson page on Schiratti.com or the Download Links subforum here. Pete

Same places as always, the Dowson page at Schiratti or the Download Links subforum here. Pete

FSUIPC does nothing on its own, and even less if you've not registered. And it most certainly does not interfere with the mouse. You will need to look elsewhere. The presence or otherwise of the DLL can ony be just a coincidence. Pete