Pete Dowson

No. not necessary. That's ONLY if you intend to assign joysticks and buttons in FSUIPC instead of P3D. You can't do it in both, there will be conflicts! Where did you get FSUIPC5 from? If you downloaded the official ZIP then it contains an Installation document which tells you clearly where everything is, especially documentation - i.e. in the FSUIPC Documents folder, in the Sim's Modules folder. Ouch! Best never to buy anything without knowing why! Quite honestly, if you don't know what you want to use it for it is a waste of your good money! I don't knwo why do you thought FSUIPC would help. Did you ask the suppot for that aircraft for help first? Sorry, i've no idea what this is about. If you mean you disabled controllers, then unless you've already assigned your controls in FSUIPC then of course they are now disabled! Please just don't do it until you know what you are doing. There is actually rarely any need at all to assign controls in FSUIPC. It is for folks who want different assignments for different aircraft types. Is that you? Good luck, and hope yuou find the real answers to you aircraft problems. Maybe describing those here, or better, in the relevant AVSIM Forum, might elicit specific help for it? Pete

No. That's a bit odd. P3D should re-create it there. Not sure that it does any harm. It probably doesn't do it until you close the session though. Maybe you should just correct that by doing it yourself -- copy the wxstationlist.bin file from the Weather subfolder in the main P3D4 folder into the AppData\Roaming P3D4 folder. I think that's basically all the Sim does in any case. Pete

Thanks for the file. It seems to be a station list, but it is woefully short. Very few WXstation names. I am not sure how it causes P3D to have the strange symptoms you suffered. Here itjust makes P3D crash -- invisibly. It just disappears when FSUIPC asks SimConnect for weather. No trace, no error message, no entry in the Windows Event Viewer. But at least the FSUIPC5 log shows the exact point this happens, and points clearly to weather reading starting. But with your symptoms it was far from obvious. This is the trouble with corrupted files, The results can be very different on different systems. I am sending the file to L-M for their attention. It is only one example, but hopefully it will get something done. Pete

If you are assigning an axis, you can see the numbers actually arriving from your device. If they don't run smoothly from somethig like -16380 to +16380, or less, but jump from one to the other, then it is a typical Saitek installation bug. From Windows Control Panel, Device Manager uninstall the device completely including driver. Then re-boot and let Windows sort it out. Pete

Go to the SimMarket purchase page for it, of course. See the “How do I pay” section near the beginning of the User Guide, which of course you’ve looked in the FSUIPC Documents folder (in the P3D4 Modules folder)? Pete

You really need to go to an X-Plane forum for possible answers to such a question. Pete

Aha! That’s a completely different state of affairs than was implied in all your previous messages! Look back and read what I said about the missing Dialog state response, and the error logged in FSUIPC’s log. If there wasn’t code in FSUIPC which handled that, FSUIPC wouldn’t respond either! I think you have a corrupt file in your P3D — probably wxstationlist.bin. Usually this would cause P3D to crash as soon as SimConnect is asked to read the weather — as it is when FSUIPC runs! In your case it is evidently just corrupting something else. The file is in your user Appdata\roaming P3D4 folder, where your PREPAR3D.cfg file is. I’ve asked L-M to check this file when it is read — it is a binary file with no checks at all! Please ZIP it up and let me have it, so I can look at it. Then DELETE it. P3D will make another. If this doesn’t help, please make a safe copy of the .wx files in your P3D files folder, in Documents, then delete one at a time, testing after each. If that fixes it ZIP up the bad one and let me have it please. You don’t need the WX files as you use ASP4 for weather. And they are unchecked binary files too! This will help L-M fix this very annoying and oft occurring problem. Pete

The GUID is generated by Windows. If the new one looks absolutely identical to the old one, and you don't update Windows in the meanwhile, I think it may well be the same. But don't "uninstall£ the old one from Windows. No. Don'tdelete anything. Best to make sure you are using JoyLetters NOW, before unplugging it,. Then when the new one comes even if Windows treats it as a different device it will simply be a matter of editing a couple of lines in the FSUIPC INI file "JoyNames" section. Pete

I KNOW! And I told you that because those programs are not mine I have no way whatsoever of diagnosing WHY they will not run! However, your statement that they do not run is not quite true. The SimConnect log clearly shows all these being successfully loaded by SimConnect:: 0.22581 Exe Launched: Path="C:\PROGRAM FILES\FLIGHT ONE SOFTWARE\ULTIMATE TRAFFIC LIVE\utl_client.exe" CommandLine="" Version="1.1.0.0" 0.32061 Exe Launched: Path="C:\Program Files (x86)\12bPilot\SODE\SimObjectDisplayEngine.exe" CommandLine="P3Dv4" Version="1.6.3.0" 2.89884 Exe Launched: Path="C:\Program Files (x86)\Addon Manager\Couatl\Couatl.exe" CommandLine="" Version="3.2.0.3995" 2.93513 Exe Launched: Path="C:\Users\djomaster\Documents\Prepar3d v4 Add-ons\FSLabs\Libraries\FSL_Configurator.exe" CommandLine="..\SimObjects\Airplanes" Version="10.0.61356.237" 2.97793 DLL Loaded: Path="C:\Users\djomaster\Documents\Prepar3D v4 Add-ons\Navigraph Simlink\NavigraphSimlink_64.dll" Version="1.0.19.1219" 2.99041 DLL Loaded: Path="C:\Users\djomaster\AppData\Local\Orbx\FTXCentral\v3.3.0.4\Orbx_ObjectFlow_x64.dll" Version="<Unknown>" 3.00567 DLL Loaded: Path="C:\Program Files (x86)\12bPilot\SODE\SimObjectAnimationModule64.dll" Version="1.6.3.0" 3.88630 DLL Loaded: Path="C:\Program Files (x86)\Addon Manager\bglmanx64.dll" Version="4.5.0.3" 3.93814 DLL Loaded: Path="C:\Users\djomaster\Documents\Prepar3d v4 Add-ons\FSLabs\Libraries\FSLSounds.dll" Version="10.0.61356.237" 3.95024 DLL Loaded: Path="C:\Users\djomaster\Documents\Prepar3d v4 Add-ons\FSLabs\Libraries\FSLEvents.dll" Version="10.0.61356.237" 3.97629 DLL Loaded: Path="C:\Users\djomaster\Documents\Prepar3d v4 Add-ons\FSLabs\Libraries\FSLOptions.dll" Version="10.0.61356.237" 9.43556 DLL Loaded: Path="C:\Users\djomaster\Documents\Prepar3d v4 Add-ons\Spotlights\DLLs\FSLSpotlights_P3D_x64.dll" Version="10.0.61356.230" 69.33414 DLL Loaded: Path="D:\P3Dv4\Modules\FSUIPC5.dll" Version="5.1.3.101" 69.34802 DLL Loaded: Path="as_srv\as_connect_64.dll" Version="17.0.0.79" which show SODE, Orbx, and FSLabs addons running as well as the ones you list. Also, attempts to load these which it can't find and which, I think, aren't even P3D4 compatible (ViMaCoreX certainly isn't -- it is a 32-bit DLL). 69.33484 File not found: Path="Captain_Sim\bin\cs.sound.dll" 69.33541 File not found: Path="VistaMare\ViMaCoreX.dll" 69.33593 File not found: Path=".\Carenavigraph.dll" Then, as the log shows, these (and others, including some EXEs not being loaded by SimConnect but still opening a SimConnect link: > 90.28389 [64, 1]Open: Version=0x00000004 Name="ChasePlane" > 90.28809 [ 1, 1]Open: Version=0x0000001A Name="NavigraphChartsSimlinkFS" > 90.29188 [23, 1]Open: Version=0x0000001A Name="REXLocation" I've omitted listing the OPEN calls for the other DLLs already listed -- AddOn Manager is one, and of course couatl and bglmanx operate the GSX facilities. So, I think you need to explain what you mean by "do not run". Also I notice that the ActiveSky module appears to be loading BEFORE FSUIPC5. That is not so good. Please re-run the FSUIPC5 Installer to make FSUIPC5 run before the ActiveSky module (though I’m sure this isn’t part of the problem you are reporting). I did ask this: but you've not answered. Anyway, in conclusion I have to repeat this. Sorry: I'm afraid it really does need one of the authors of the other programs to find out what their program isn't working. They need to delve into what they are doing which could possibly have this result. Once that is determined I'm sure it wil be resolvable, but not till then. It will likely turn out to be something wrong in P3D itself, as that is the only common part. Pete

You are using some package with plug-ins for FSUIPC which is evidently dependent upon the socket package, including "socket.dll " or "socket.lua". Unlike FSUIPC4, the 64-bit version of FSUIPC doesn't include any Socket facilities because there's no 64-bit builds available which are compatible with the rest of the built-in Lua facilities. Folks who need Lua sockets find and install the 64-bit package for this themselves. Have a search for solutions in the forum or elsewhere. What I don't understand is why on Earth the GoFlight interface tool is trying to use any Lua plug-ins in the first place! And especially not sockets, which are generally used for communicating with the Internet or with other PCs on your local network. You do really need to seek Goflight suppot on this. Pete

The LOG shows FSUIPC is running perfectly, except for one oddity: 746156 ### MENU: Error: failed to receive DLGMODE notification! Going ahead anyway ... I assume you went into the FSUIPC5 Options? I have seen this error now and then. Basically, when you click on FSUIPC's Add-Ons entry in the menus, SimConnect notifies FSUIPC, and then, in order to display its dialogue, it asks SimConnect to set "DLGMODE". When it gets a confirmation, it opens the options for you. The above message occurs if it doesn't get one of those as it should. but it is carrying on regardless. [I have just asked L-M about this, i.e. how come a proper response can go missing and what does it imply[. This might be a clue. Are the other add-ons managing to add their Menu entries, but then just not responding when selected, or are they not appearing at all? If the former, then it will probably be the same sort of problem, that SimConnect is not giving permission to enter dialogue mode. I remember I had to add the above override to stop that happening, but we could never work out WHY simconnect occasionally failed in this way. In case it is FSUIPC using a Dialogue without permission like this, please make sure to test wour other add-ons WITHOUT using the FSUIPC options. Yes, just add it. I wouldn't have expected it to change anything. The problem here is that, since FSUIPC literally has nothing whatsoever to do with GSX and your other add-ons, and most certainly doesn't deliberately do anything which could stop them operating, there's no way I can work out why those other programs are not running. In the P3D4 64-bit orld there are no "hacks" into the sim's code at all, unlike in all the 32-bit versions. Everything is done via well documentated methods through SimConnect and, yes, a little via the PDK (that was the only way to implement Mouse Macros, for instance). So, as a consequence, I'm afraid it really does need one of the authors of the other programs to find out what their program isn't working. They need to delve into what they are doing which could possibly have this result. Once that is determined I'm sure it wil be resolvable, but not till then. It will likely turn out to be something wrong in P3D itself, as that is the only common part. There is one other source of information which might help. A SimConnect log. For one of these, you need to add a file like this into your P3D4 Files folder, in Documents: [SimConnect] level=Verbose console=No OutputDebugString=0 file=<your P3D4 path>\Modules\simconnect%u.log file_max_index=9 Replace <your P3d4 path> with the main path to Prepar3D4. Or of course you can replace the entire path to one possibly more convenient to you. Run P3D only just long enough to see the other add-ons not working, then close it down. Otherwise the Log will become really huge! It will be pretty large in any case, so do NOT paste it here! ZIP it and attach it. If it is too big even for that, send it to me at petedowson@btconnect.com. I'll need a litst of the add-on programs you are actually using as well, please -- the ones you expected to load, whether they appeared not to or otherwise. Pete

Well Addon Manager is included in the GSX package. I use all of those except Chse Plane, will never ay trouble. I think one of the things you have installed is messing up the normal SimConnect interface, but only when FSUIPC is there for some reason. By all means show me a FULL FSUIPC5.LOG file (last time you on;y showed the start of a session). I'll checvk that everything there looks okay. Run some things and close the session before getting the log. A while back you said: "last week everything worked well. I went to Boston 5 days then suddently I got this issue" But FSUIPC doesn't know or care where you go away to, and it doesn't change just sitting there. It's certainly somethhing on your system. Pete

No, only the offset ones, so that the plug-in gets the initial value -- otherwise how can it determine what the difference is when a change is notified? And there are some applications for plug-ins where the initial value is essential -- things that don't change often, but are needed for display on a gauge or similar. I actually use a plug-in to drive my Flight Illusion cockpit gauges. Things like switch and axis positions have initial values, but FSUIPC doesn't detect a position till it changes and it gets notified. Pete

Assuming you downloaded a new copy of GSX then, sorry, I don't know what is wrong there. I use GSX all the time. Never any problems . There's absolutely no connection between the two programs. Have you asked FSDT / Virtuali for help? If it is their program not running then really only they can work out why, maybe with some logging information. That's what I'd do if FSUIPC wasn't running -- add more logging to find out exactly why. Pete

Yes, I know (I wrote FSUIPC). But I thought you said you were using FSX options for assignments! 😉 Pete

That's really a question about FSX, not FSUIPC. But "Select 1" is not keyboard 1, it is the control used after, for example, pressing 'E' to select Engine 1, or after shift+E for Exit 1, and so on. Keyboard 1 is just key 1. There are only Select 1 to Select 4 because only 4 are ever used (4 Engines, 4 Exits, for example). Pete

Yes. You would need to check the value supplied for the offset to see if has changed to the value you'd expect for a termination. The sleep actually suspends the Lua's thread by calling the Windows sleep function. that's more efficient than maintaining a watch on the time in a loop. Events being monitored will still be registered during the sleep, but after the sleep you will only receive the last such event. They aren't queued and fed to you one by one. Pete

Oh, sorry. I didn't know. 😉 Pete

The speed brake (= spoiler) IS an axis in P3D, as it was in FSX. Are you sure your aircraft isn't using the normal built-in axis? Try assigning in FSUIPC. For fixed positions you can use a button with the Axis spoiler set control and the relevant value (which will be 0-16384, not a percentage). Otherwise there's Spoilers arm off, on , set and toggle, and Spoilers off, on, set and toggle. I'm only familiar with airliners -- then it's normally an axis with four special positions -- down, armed, flight and spoiler, with the last being the fully up action to keep the aircraft on the ground after landing and help with braking. Do you a parachute for that in an F-16? 😉 Pete

It really cannot be down to FSUIPC, as it is completely uninvolved with graphics and gauges. And an unregistered FSUIPC is doing nothing in any case apart from asking Simconnect for data and waiting till it arrives. There was a bug in the P3D4 versions of those PMDG planes some time ago (over a year for sure) which was caused by their code using wrong code when it detected FSUIPC running. It caused similar symptoms, if not the exactly the same. That was fixed by updates. I think you have the originall PMDG aircraft not the fully updated ones. Check that and do the updating. Pete

The crash details refer to a very heavily used part of Windows -- the run time library for C/C++ programs. It could be called from anywhere (noy actually FSUIPC directly because its usage is static -- i.e ocmpiled into the FSUIPC5.DLL. The error is a stack overflow, which s unusual unless something got stuck in a recurrant action, a loop. It must be something in the DirectInput part of Windows. The extra logging in the FSUIPC5 log definitely shows a problem, a mix-up by the look of it, in the Registry for the X52: 125 #### Initialising Dlrectinput Axis Scanning ... 125 (Entry from GetRegisteredOptions) 125 ---------------------- Joystick Device Scan ----------------------- 125 Checking: \\?\hid#intc816&col02#3&36a7043c&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030} 125 Usage=12, UsagePage=1, =Flight Mode Switch 125 Checking: \\?\hid#vid_06a3&pid_0762#6&24b5a767&2&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 125 Usage=4, UsagePage=1, =Game Controller 125 Product= Saitek X52 Pro Flight Control System 125 Manufacturer= Saitek 125 Vendor=06A3, Product=0762 (Version 1.35) 156 ------------------------------------------------------------------- 156 ****** Registry scanning: VID=06A3, PID=0762 ****** 156 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0762\Calibration\0" 156 ... and a "GUID" value 156 GUID= {89E68830-6754-11E7-8002-444553540000} 156 NB: not valid for this device according to GetConfig! The HidScanner log shows that the X52 is the last USB device listed in the Registry, so it will be the only thing causing the problem as FSUIPC does the scan in Registry order. I think you should uninstall the device completely (including driver), using the Windows Device Manager, then re-boot the PC. This will get its Registry entries rebuilt. Pete

True. Maybe there's another, one with a name you didn't recognise? Have you tried using the Lua plug-in which displays the L:Vars as they change? Use that whilst operating the speedbrake with the mouse. Pete

FSUIPC will not be operating two separate controls in your aircraft unless specifically configured to in the Axis assignments tab (where you can assign to up to 4 actions). I suspect you have not disabled controllers in the Sim. You need to do that to prevent such conflicts. Using someone elses configuration won't help in such a case and probably won't work in any case because of different USB connections giving different IDs for each device. The GUIDs are generated per PC too, they are not common. Pete

Well, all that shows perfection as far as FSUIPC is concerned. There's really nothing else it can do. Can you get support from the makers or suppliers? It seems to be the only problem device. They must be doing something very non-standard. Pete

You don't need to Register FSUIPC for any application using its data interface. You can retrieve all your SimMarket purchased registrations via your SimMarket account. Pete