Pete Dowson

The INI files are more important than the logs. The odd thing is that the NEW INI file shows no assignments at all. Didn't you use you old INI file? This NEW one is just a default one, generated because there was't one there! So, it is really not surprising you "lost" all your assignments! --------------------------------------- Looking only at the [JoyNames] section, the joystick numbers HAVE changed between the two but at first glance the GUIDs seem to have been retained. So if you had been using Joy Letters as always advised, the IDs would have been adjusted automatically. As it is your best bet is to edit the OLD INI by replacing just the [JoyNames] section with this: [JoyNames] AutoAssignLetters=Yes 0=F16 MFD 2 0.GUID={4902D9B0-8D38-11EA-8001-444553540000} 1=F16 MFD 1 1.GUID={4902D9B0-8D38-11EA-8002-444553540000} 2=Joystick - HOTAS Warthog 2.GUID={E07DC270-8D36-11EA-8009-444553540000} 3=Throttle - HOTAS Warthog 3.GUID={E07DC270-8D36-11EA-800A-444553540000} 4=Mad Catz Pro Flight Combat Rudder Pedals 4.GUID={DCB664C0-8D37-11EA-8002-444553540000} 5=BU0836A Interface 5.GUID={EE9B7700-8DE3-11EA-8003-444553540000} Those then equate to what you had before, and I've enabled the joystick lettering for you so this mess won't happen again (unless of course you don't use the settings again). Replace your "NEW" INI file with the corrected OLD one, and run the Sim. Pete

This is because you calibrated with a Reverse Zone! Please see that checkbox (which you forgot to check) labelled "No reverse zone". It is in your picture, top left. Check that, then recalibrate. This is covered in the Calibration explanations in the User Guide. Pete

It is, as clearly shown in your logs (didn't you look?). You are starting the Lua plug-in by pressing a button allocated to run it: 715172 [Buttons] now profile-specific: 715172 2=P0,10,CL3:S,3 715172 3=P0,11,CL3:S,4 715172 4=P0,8,CL3:R,1 715172 5=P0,9,CL3:S,2 716922 Button changed: bRef=0, Joy=0, Btn=8, Pressed 716922 [Buttons.Airbus A319 Avianca HK-4553] 4=P0,8,CL3:R,1 716969 LUA.0: beginning "C:\Steam\steamapps\common\FSX\Modules\AS_A320.lua" Notice the button assignments you are using: they are specific to Airbus A319 Avianca HK-4553. 3 of them are for flags 2, 3 and 4, but you have no assignment for flag 1. You just kept restating the plug-in using button 8. The button you assigned to Set flag 1 is here: [Buttons.AS_Airbus] 2=P0,10,CL3:S,3 -{LuaSet AS_A320 (Flag 3)}- 3=P0,11,CL3:S,4 -{LuaSet AS_A320 (Flag 4)}- 4=P0,8,CL3:S,1 -{LuaSet AS_A320 (Flag 1)}- 5=P0,9,CL3:S,2 -{LuaSet AS_A320 (Flag 2)}- Those only operate for the AS_Airbus profile, which you weren't using according to the logs. It appears you also tried to make the plug-in start automatically for that AS_Airbus profile: [Auto.AS_Airbus] 1=AS_A320 but that won't work because the entries for Auto are full control names, not simply filenames. You need 1=Lua AS_A320 just as you would select in the assignments. The Auto sections are to enavle ANY cotrols to be automatically executed, it isn't only for loading plug-ins. Pete

Check the entries for LEMD in the Runways.txt file, which is the log of the processing MakeRunways performed. The last such entry in the file will tell you why. Pete

FSUIPC User Guide, Page 20, 3rd paragraph. Setting "Yes" enables you to use profiles, but "Files" tells it to use separate files. Pete

FSUIPC runs internal to P3D, so doesn't use the same interface. LINDA uses FSUIPC. ActiveSky has an internal component too, but also uses the natural P3D SimConnect interface. I don't know your two applications which i assume from your heading run on an iPhone or iPad? If so they presumably have a component you install on the P3D PC. Is that an internal DLL or an extermal EXE program? If the latter, and it was not specifically written for P3D, it will need additional SimConnect "Legacy" installs. Either way, it will need a properly configured Simconnect.xml and Simconnect.cfg. Please see P3D documentation about these. Since I don't know the programs I cannot comment. The only thing FSUIPC provides for moving maps is the GPSout facilitiy, which can send NMEA standard sentences which are read by some moving map programs over a serial link. Pete

Have you tried using any of the FSUIPC logging facilities to check? You can get a trace on what the Lua is doing and what button actions are occurring. There's a bug we've only just found whereby LuaKill, LuaSet/Toggle/Clear, and LuaValue don't work if yo are using a separate path for your Lua files. Could that be the case? A fix has been implemented and in included in FSUIPC6.0.6, now available. The fix for FSUIPC5 will be later. But I'm afraid one isn't currently planned for FSUIPC4. Otherwise a sight of your FSUIPC4.INI file, and such a log, would be useful if you can't figure it out from that. As already noted by others, unless you clear the flag using LuaSet on it again won't change it and so won't trigger an event. I also think you need to use LuaToggle, so it changes each time. Pete

Oh, I don't know. They're about as wide as some cockpits. you'd just have to mount the screens on the outside! 😉 We've enjoyed a few trips on Narrowboats. Pete

1990's? Hmm, flight sim software or my previous company, wordcraft software. That's a long time ago for an old geyser like me (77 this year), so, sorry, I don't recall. Maybe 1999 or later regarding WideFS networks? I preferred the original and more efficiant Novell protocols in those days before Microsoft eventually ousted it from its systems. Tell me about it! And I started with a ready built one (PFC 737NG), but with much rather old technology which I gradually replaced, or got PFC to update. Like you, though, most all of the recent work, though, has been on software. I use Prosim. For a 737NG i think now there's a choice -- SimAvionics or ProSim. My original, Project Magenta, doesn't seem to be in it now. You still list it along with ProSim. i assume you are talking historically? You are welcome. glad you find it worthwhile! :-) Pete

Can you describe what you mean by the nuclear option please? I assume you mean the unnstalling? Do you have any CH software installed? If so you also needed to uninstall that. If nothing else works I'm afraid the Registry is really in too much of a mess. Then it comes down to a choice: 1. A Windows re-install, to start with a freh registry, or 2. Some serious registry editing, manually removing all of the entries detailing the devices. If you opt for (2), I can help, but it might take a while. I could tell you how to get a log listing for me of all the relevant Registry keys, and then I could make a REG file which you can execute to remove the erroneous entries. You'd need to make a safety backup of the Registry first 9a standard Windows function). Pete

Well, duplicate Windows-assigned Device IDs are a simple registration problem, but identical GUIDs should be impossible according to Microsoft. Rearranging the joysticks "acquired" for use by FSUIPC, you see there are 4 (!!) with ID = 0, and 2 with ID = 3; ID = 0 702 Device acquired for use: 702 Joystick ID = 0 (Registry okay) 702 0=CH Pro Throttle USB 702 0.GUID={E4320650-7036-11EA-8005-444553540000} 702 Device acquired for use: 702 Joystick ID = 0 (Registry okay) 702 0=CH Throttle Quadrant USB 702 0.GUID={E4320650-7036-11EA-8005-444553540000} 702 Device acquired for use: 702 Joystick ID = 0 (Registry okay) 702 0=CH Throttle Quadrant USB 702 0.GUID={E4320650-7036-11EA-8005-444553540000} 702 Device acquired for use: 702 Joystick ID = 0 (Registry fixed) 702 0=CH Flight Sim Yoke USB 702 0.GUID={E80A3770-7036-11EA-8006-444553540000} ID = 2 702 Device acquired for use: 702 Joystick ID = 2 (Registry okay) 702 2=CH Pro Pedals USB 702 2.GUID={DC90E650-7036-11EA-8001-444553540000} ID = 3 686 Device acquired for use: 686 Joystick ID = 3 (Registry okay) 686 3=Logitech Extreme 3D 686 3.GUID={9F156DC0-B2D7-11E1-8001-444553540000} 702 Device acquired for use: 702 Joystick ID = 3 (Registry okay) 702 3=CH Throttle Quadrant USB 702 3.GUID={9F156DC0-B2D7-11E1-8001-444553540000} FSUIPC doesn't assign these IDs, Windows does. As it does with the GUIDs. I don't understand how it manages to get duplicate GUIDs at all -- I've never seen that! I note that there are three CH Quadrannts listed. Is that right? In later versions of FSUIPC we added extra code to try to deal with incorrect IDs, cirrecting the errors in the Registry, but not with the version you are using. There is a way of doing it yourself using a program called JoyIDs. Please refer to this thread in the FAQ subforum (which I'm sureprised you missed if you've been looking for answers already): However, I'm not sure that would fix it completely because of the multiple identical GUIDs. I really think you need to do some more drastic things first: 1. Go into Windows Device Manager, find all those devices and uninstall them. If the option is offered, uninstall the drivers too. (This is to try to remove the bad registry entries). 2. Unplug the devices, all of them. 3, Re-boot. 4. Plug the devices back in and re-check. 5. If necessary, then do the manual reassignment of the JoyIDs. Pete

Hmm. I'm using ViewGroups and VSync and TB, so I wonder if that's why I don't see that flicker? Interesting though. Thanks for the feedback. Pete

Good, glad it was easily sorted! Pete

I've cross-checked 31C8, and see it is one of three values, the X Y and Z accelerations. These offsets are in fact populated directly as read from SimConnect, with no manipulation or changes being made to the value. If you use the FSUIPC Monitor facility on the Logging tab you will see the actual Variable name alongside the value provided. The actual Simulation Variable populating this offset is as below (from the P3D SDK). If you think it is wrong (and I cannot tell one way or the other) I think you need to report it as a bug to Lockheed Martin. Pete ACCELERATION WORLD Y Acceleration relative to Earth, in vertical direction Feet per second squared

In earlier versions of 32 bit FSUIPC this was done by hacking into the weather code in the Sim. In later versions it was superseded by better ways in programs like Active Sky. FSUIPC has not really been involved for a while. And, sorry, but we are not going to start hacking into P3D 64bit code. Pete

Have you added your report of that odd menu problem to the L-M forum? Best to add weight to it. I must admit I'm pleased with HF1, though I did have to switch that new texture opton of to fix terrible white flashing. Pete

Well the files are being produced okay then, and if you double-click the bitmap you could see if it looked correct. BUT I never heard of a version of Project Magenta using these files. Is that a new development? ProSim definitely works with the BIN file. The BMP can be viewed in any viewer, and a facility in WideClient displays it too. If you think PM should be using it I think you need to ask PM support. Pete

No, but each simulator has its own default positions for the SimConnect windows. The windows are also suppressed (or possibly just hidden) by the "Message Text" option being unticked in the P3D Options -- Information section, bottom right. This is the option used 'unticked' when you are re-directing such displays to a different external display, usually via WideFS on another PC. I've just tried the Log Lvars lua provided with the FSUIPC6 Install, and the SimConnect window it uses comes up, by default, at the top left, but not right up to the border. Pete

Could you ask on the Lorby-Si support site, please? MakeRunways simply asks that Export program to make the file, but I've no idea how it works it all out. Oliver, the author, will know the right things to ask you to check. http://www.avsim.com/forum/788-lorby-si-support-forum/ Pete

Buttons & Switches tab. Where else? There is a range of offset controls listed in the drop-down assignments list in addition to the normal FS controls. Pete

You have Registry problem, with your Virtual Joysticks usurping the Windows-assigned ID numbers. In later developments in FSUIPC and later, this could be corrected automatically by FSUIPC changing the Registered IDs, but not in FSUIPC3 as it was no longer maintained (nor really supported fully). You can do the correction yourself using the JoyIDs program. Please see this thread in the FAQ subforum: Pete

Well, something's obviously happened on your PC, because FSUIPC 4.974 certainly hasn't changed. One of the possibilities is that either some previous crash you had corrupted a weather file, or an add-on has done so. Please see this thread in the FAQ subforum: If that doesn't help you need to show the FSUIPC4.LOG, up to the posint of the crash (if one is generated), and the Windows Event Viewer details showing the details of the crash (Event Viewer -- Windows Logs - Application. Pete

Ah, okay. But it is the pressing of the button which you wanted stopping the engine? Not just the move back to the button? Is that section of movement not recognised as part of the axis range? Pete

Ok. Sorry, I thought you just wanted a way to stop the engine. Good that you found what you wanted, though I thought you were pulling back the throttle manually! Pete

Thanks. Will try it this afternoon. Pete