Pete Dowson

The INI file you supplied shows NO calibration other than the defaults, though the rudder is unusable with what you've got set there! Throttle=-16380,16380 Rudder=0,0,0,0 Aileron=-16380,-512,512,16380 Elevator=-16380,-512,512,16380 But you definitely have assigned a few buttons: 1=P0,0,C65588,0 -{BRAKES}- 2=P0,3,C65601,0 -{FLAPS_3}- 3=P0,4,C65597,0 -{FLAPS_1}- 4=P0,2,C65599,0 -{FLAPS_2}- I suggest that you first check your controls with a default aircraft, as if what you say is true your elevator axis simply is not working. You still need to read the chapter in the User Guide on calibration and follow the steps there. They are numbered to make them easy to follow. Please do that before posting again, because you don't seem to be following anything we are advising. Also, you may want to try assigning NOT "Direct to FSUIPC" but to the FS controls "Axis Elevator Set" and the others in that vein. Some add-on aircraft do not respond to the direct controls. Unfortunately the Log file you provided shows nothing useful. BTW you said Quite honestly, if you don't know the difference between the elevator (operated on your joke or joystick forward and aft movement) and elevator trim (operated by a trim wheel or buttons on the arms or a yoke) then why are you trying flying such an advanced aircraft? Pete

Strange that the aircraft would detect the newly saved files without you explicitly loading that flight. Are they not saved with "Previous Flight" as the name? If so, then the programmers of that aircraft must have know that those would be only associated with a flight of that name. From what you say, it sounds like you can never save a flight to start the sim from somewhere different because the aircraft would then always be loaded with settings you don't necessarily want. That seems crazy to me. And if the "Previous flight" saved files were really the problem then either the PMDG 777 sold so few copies that you are the only one to decide to post here, or it is something else entirely you are suffering from. I know what I'd bet on. Anyway, you can try adding SavePreviousFlight=No to the [General] section in the FSUIPC INI file. I think that option is still there. Pete

A saved flight cannot possibly affect anything if it's not loaded, so why re-load it? It sounds like you have "Previous flight" set as your default flight in P3D. So, just select a different flight as default. The reason FSUIPC saves this is for compatibility with FSX and previous versions of FS which did save such a flight automatically on close down. Many folks relied on that for resuming from where they left off in the next session. I used to use it to resume at the gate of the airport I last flew to, but i'm always careful to park and switch off (to "cold & dark" state) because my setup relies on ProSim avionics, and active flights cannot really be resumed. Pete

Well, of course. Please just use the version of FSUIPC6 supplied above and let me know if it does the job. I see i omitted to describe the range of the timing allowed so I'll do it now: TimeToDelayTexts=100 is the default TimeToDelayTexts=0 turns it off, making FSUIPC act exactly as before Otherwise the range allowed is 20 - 1000 (mSecs). I'd like to know if the default value is a good choice, or whether it needs increasing or can be safely reduced. I know this will depend on what software is reading it. I mainly tested with P3D displays and menus generated by Lua plug-ins, because I've never had any problem with GSX or the like and my WideClient displays. I don't really have anything else that uses both the text lines and the menus. It should be noted that this is just the maximum amount of time which a message, display window, or menu will be held back when they occur sooner than that after a different type of display (message, display window, or menu). Pete

Please install the attached version (6.0.13a) in your FSUIPC6 installation folder, overwriting the version already there. Let me know the results, please. If still not good, I'll need the same information as before. Here I've tested as well as I can without actually having the same problems as yourself -- I've had to try to simulate them. There's a new parameter in the [General] section of the FSUIPC6.INI file: TimeToDelayTexts=100 This simply says to delay the posting of changes to either the offsets or to event.textmenu for 100 mSecs after a posting of a different type of message (i.e menu vs message vs display window text). For posts of the same type they are allowed to overwrite as they would do on screen. 100 mSecs seems reasonable to me, but you can try increasing or decreasing it to see what happens. I'd like to know about this before deciding on the final default value (assuming, of course, that the logic actually works for you with some value). Pete FSUIPC6.dll

Why, has it affected your applications too? I've had no feedback from your good self on this. Pete

Why do you say that? You can set null zones for the centres or the extremes -- more than what P3D can do. Just follow the step-by-step instructions in the User guide chapter on Calibration. Similarly for "sensitivity". You can choose a response slope in the calibration tab too -- less or more sensitive in the centre to suit the aircraft. Judging by your INI file settings you've not actually done any calibration whatsoever in FSUIPC, you've just enabled it. These are the default values: Throttle=-16380,16380 Rudder=-16380,-512,512,16380 Aileron=-16380,-512,512,16380 Elevator=-16380,-512,512,16380 Pete

Tested and all working. I just noticed your FSUIPC4 version is well out of date and is not supported. You need to download the current one, 4.976. My results were good, tested with this Lua plug-in: function Sound_Warning () ipc.log("Sound Warning called") sound.path("C:\\Steam\\steamapps\\common\\FSX\\sound\\") sound.play("xeng_fire_2") end event.offset(0x73AE, "UB", "Sound_Warning") With the logging enabled I get this in the log: 78078 LUA.0: Sound Warning called 78125 Sound: Id 1, PlayNow("C:\Steam\steamapps\common\FSX\sound\xeng_fire_2") 78125 Sound: Id 1, PlayTheSound("C:\Steam\steamapps\common\FSX\sound\xeng_fire_2.wav") 83812 Sound: Id 1 DeActivate: sound not playing now ... 83812 Sound: Id 1 EndPlay: releasing buffer 83812 Sound: Id 0 EndPlay: all done! This of course is using the default sound device, since I gave no device number in the sound.play function. I suggest that, after you update your FSUIPC4 installation, you test with something simpler and using one o the sounds installed with FSX. You could also try selection the sound device explicitly. The numbers to use are listed in the [Sounds] section of the FSUIPC4.INI file. Note that, unless you are changing the sound folder for different sounds, there's no point in having the sound.path in your function, being set every time. Just set it the once, at the start of the Lua code. Pete

Phew! I was expecting a tiny program which just played the sound on a change in an offset. I could then have tested it here. I'll just make something simple like your function Sound_Warning () sound.path("D:\\Airbus_FWC\\") sound.play("airbus_warning") end event.offset(0x73AE, "UB", "Sound_Warning") But with a different path and wave file (as I don't have yours. I'll also need to change the offset via FSInterrogate as I don't have anything using that one. Pete

Not that I know of. You ought to show us the Lua file itself, please. Is the WAV file is a format recognised by Windows? Pete

It's rather poor if an avionics software suite like SimAvionics doesn't properly support radios. Or is is just your particularly make of hardware it doesn't support? Perhaps the makers of the radios supply drivers for different avionics software? Have you checked? I use ProSim for my cockpit. I don't know if it supports your radio hardware. Sorry, but FSUIPC does not itself directly support add-on hardware (excepting switch & button input from many Goflight devices), but FSUIPC is probably used by any software which does support your radios. You'll need to find it, or write your own? Pete

As john says, it looks like a corrupt weather file. Please also see this thread in the FAQ subforum: Pete

Thanks. Very interesting. The previous menu: was dispatched immediately (the "broadcast" message is when the offsets are updated), but the problem one: appears to have been delayed by 15 mSec -- enough for the following text message to overwrite it: I think the arrival of the new message so quickly after the menu somehow interrupts the flow of the menu processing in FSUIPC. I think the only answer is to artificially delay the "broadcast" of any message X millisecs after one of a different type is broadcast. (It doesn't matter if the types are the same, because the latter should overwrite the former as it would on screen). The question then is how long to keep them pending (X=?). I could make it adjustable but I need a default. Maybe start with 100 mSecs and experiment with lower? If I send you a test version you could run your tests again and let me know the minimum delay which works for you, then for the default I'd just add a bit in case of PC and user application variation. Okay? By the way, if you de-select the Logging option to log lua plug-ins separately, the log entries for the plug-in would appear in their proper position in the main log, instead of trying to match them up afterwards. With P3D message displays can only be suppressed on the P3D screen by using the Text display option in the P3D UI. The FSUIPC filtering just operates on the feeding of the text to the Lua plug-ins and offsets. The messages are checked and discarded -- instead of being buffered and delayed as proposed above. I'm moving this thread now ... Pete

So those two are appearing faster than the results can be processed correctly. I don't think there's much we can do about that as the interception is a blanket facility -- you get them all or none. It would be possible is to separate the types into different offsets, but that would have ramifications for existing applications, including the WideClient access from client PCs (which is where the facilities were first implemented, and the main reason for them -- to get the messages and menus onto a separate screen, probably inside a cockpit. Just to check the timings so I can fully understand this, could you run the test again, but first add Debug=Please TestOptions=x8000 to the [General] section of the INI file. This will log the reception of the text as soon as it is signalled to FSUIPC, and I can see then the milliseconds difference. Maybe a workable solution would be to buffer the arrival of text arriving in less than so many mSecs after a previous one, keeping it separate for a defined period (adjustable or fixed? Don't know) before placing it into the same offsets. That period would need to be enough for other processes, including WideFS, to extract the data from the offsets. It is a little strange that I've used GSX2 with WideClient doing the displays for me (suppressed on the P3D screen) and not noticed such a problem before, but I must admit I've not tried it for quite a while now. Too much other stuff to attend to. BTW this thread definitely should be in the main FSUIPC Support Forum. I'll move it after your next reply. Pete P.S. If you didn't need to process the text message which is overwriting the menu, then you could try using a Message Filter as an interim solution. Assuming, that is, the message is always the same and that there are no others you actually want also starting with the same first 16 characters. (See the section "Message Filters" near the back of the FSUIPC Advanced Guide).

I've investigated this, and have found that the base scenery version of KATL, the one in the fs-base\scenery folder "APX25200.bgl" still has the taxiway names, but that is overridden by the one in the file "microsoft-airport-katl-atlanta\scenery\Microsoft\Atlanta\KATL-Airport.bgl" -- which includes no taxiway names at all! I think you will be able to see that for yourself if you (temporarily) rename the .bgl to .bgloff. I don't see a way of getting around this in MakeRwys. It needs to be fixed at source, by Asobo. Or maybe some scenery add-on maker will produce a better KATL? ... Just found one: https://forums.flightsimulator.com/t/katl-atlanta-airport-released-in-the-marketplace/316646 Pete

Can you please try it with a Lua plug-in, so I can see what is going on sequentially. It is not easy to understand when I don't know your program. The facility was designed for use in Lua plug-ins, via the event.textmenu function. The dumping into the offsets for program use instead was an after thought, but for clarity here I'd like you to check results with a plug-in, please. I'm not sure you are in the right place, by the way. If this is really a question of some special textmenu support in Paul's DLL (this is his forum) then I think he will need to intervene. But let us check that the original method works. Pete

Looking at the data: 3461531 READ0[33552] B000, 2048 bytes: FA B7 37 00 01 01 00 00 00 00 C0 40 00 00 00 00 ..7........@.... 3461531 28 00 00 00 5B 47 53 58 5D 20 48 61 6E 64 6C 69 (...[GSX] Handli 3461531 6E 67 20 62 79 20 4C 4F 53 43 48 20 41 69 72 70 ng by LOSCH Airp 3461531 6F 72 74 20 53 65 72 76 69 63 65 00 00 the length of the supplied data stated is 0028 (40 bytes). This is not a menu -- it is type 0x0101 which is a non-scrolling text line, and it terminates with the 00 00. Pete

Yes, it seems that Asobo/Microsoft have made some change in the KATL taxiways details in the recent World Update 3. We are finding that with each MSFS update you get as many steps backwards as you do forwards. It really does make add-on development very difficult. In this case, the data seems to be there okay (according to the Log ("Runways.txt"), but for some reason it is not being used in the T5 file. I'll take a look, find out what is going on ... Pete

Not sure why you'd do that. You haven't enabled the button or event logging for P3D4, only P3D5, so the P3d4 log is not useful. Test your assignments with default aircraft. Not sure why you'd only have Parking Brakes assigned for a single profile in any case, as it will be a very generally used control. Maybe your P3D4 aircraft (which isn't the same one you are assigning with in P3D5) handles its Parking brake differently. BTW there's a problem in the Registry indicated by this: 156 WARNING: Joystick ID 1 is duplicated in Registry 156 WARNING: Joystick ID 0 is duplicated in Registry That's not good, but it doesn't seem to affect FSUIPC as the correct ones seem to be selected. However, rather than uninstall FSUIPC and re-install it might have been better to unplug then uninstall your control devices (via Windows Device Manager), power off the PC, plug them back in and power on again so the Registry entries get re-written. But I don't think this is anything to do with your Parking brakes problem. Check with default aircraft, and check that the normal default key assignment in P3d is working. Pete

Neither, assuming you are using the default KATL. The T5.CSV file shows many of the taxiways with names, varying from simple letters to longer ones like SG12, SG14, SG16. See small extract below (lines 113516 to 11352 in my T5.csv. Mind you, this is with the previous version of MSFS. I'll run MakeRwys again with the latest, to see if Asobo have messed it up. Pete -------------------------------------- KATL,R10,25.00,33.629646,-84.426544,1,25.00,33.629662,-84.426483,1,25.00,33.629692,-84.426422,1,25.00,33.629883,-84.426193,1,25.00,33.630054,-84.425987,1,25.00,33.630211,-84.425804,1,25.00,33.630638,-84.425285,1,25.00,33.630695,-84.425179,1,25.00,33.630726,-84.425041,1,0.00 KATL,R10,25.00,33.630730,-84.426338,1,25.00,33.630661,-84.426102,1,25.00,33.630558,-84.425964,1,25.00,33.630413,-84.425888,1,25.00,33.630226,-84.425888,1,25.00,33.630054,-84.425987,1,0.00 KATL,R10,25.00,33.630730,-84.425705,1,25.00,33.630417,-84.425705,1,25.00,33.630325,-84.425728,1,25.00,33.630211,-84.425804,1,0.00 KATL,R11,25.00,33.630730,-84.426155,1,25.00,33.630741,-84.426064,1,25.00,33.630821,-84.425880,1,25.00,33.630920,-84.425774,1,25.00,33.631027,-84.425720,7,25.00,33.631084,-84.425705,1,25.00,33.631027,-84.425705,7,25.00,33.630741,-84.425705,1,25.00,33.630730,-84.425705,1,0.00 KATL,R11,25.00,33.630726,-84.425232,1,25.00,33.630745,-84.425346,1,25.00,33.630810,-84.425514,1,25.00,33.630920,-84.425629,1,25.00,33.631027,-84.425690,7,25.00,33.631084,-84.425705,1,25.00,33.631344,-84.425705,1,25.00,33.631828,-84.425705,1,0.00 KATL,R11,25.00,33.631828,-84.426270,1,25.00,33.631725,-84.425995,1,25.00,33.631611,-84.425842,1,25.00,33.631344,-84.425705,1,0.00 KATL,R12,25.00,33.630726,-84.424812,1,25.00,33.630638,-84.424568,1,25.00,33.630493,-84.424431,1,25.00,33.630329,-84.424385,1,25.00,33.630493,-84.424339,1,25.00,33.630642,-84.424202,1,25.00,33.630726,-84.423950,1,0.00 KATL,R12,25.00,33.629623,-84.424385,1,25.00,33.630329,-84.424385,1,0.00 KATL,R3,25.00,33.630722,-84.441994,1,25.00,33.630745,-84.441895,1,25.00,33.630775,-84.441811,1,25.00,33.630833,-84.441719,1,25.00,33.630909,-84.441643,1,25.00,33.631031,-84.441574,7,25.00,33.631073,-84.441566,1,25.00,33.631031,-84.441559,7,25.00,33.630909,-84.441498,1,25.00,33.630833,-84.441422,1,25.00,33.630779,-84.441322,1,25.00,33.630741,-84.441223,1,25.00,33.630726,-84.441132,1,0.00 KATL,R3,25.00,33.631821,-84.441566,1,25.00,33.631294,-84.441566,1,25.00,33.631073,-84.441566,1,0.00 KATL,R3,25.00,33.631821,-84.440994,1,25.00,33.631729,-84.441223,1,25.00,33.631630,-84.441383,1,25.00,33.631485,-84.441505,1,25.00,33.631294,-84.441566,1,0.00 KATL,R6,25.00,33.630730,-84.428795,1,25.00,33.630657,-84.429024,1,25.00,33.630524,-84.429169,1,25.00,33.630360,-84.429230,1,25.00,33.630520,-84.429291,1,25.00,33.630657,-84.429436,1,25.00,33.630730,-84.429665,1,0.00 KATL,R6,25.00,33.628513,-84.428528,1,25.00,33.629234,-84.428528,1,25.00,33.629276,-84.428528,1,25.00,33.629425,-84.428558,1,25.00,33.629528,-84.428635,1,25.00,33.629620,-84.428764,1,25.00,33.629665,-84.428871,1,25.00,33.629711,-84.429001,1,25.00,33.629803,-84.429123,1,25.00,33.629917,-84.429199,1,25.00,33.630070,-84.429230,1,25.00,33.630142,-84.429230,1,25.00,33.630360,-84.429230,1,0.00 KATL,R6,25.00,33.629646,-84.428116,1,25.00,33.629620,-84.428223,1,25.00,33.629547,-84.428368,1,25.00,33.629425,-84.428474,1,25.00,33.629276,-84.428528,1,0.00 KATL,R6,25.00,33.629646,-84.428116,1,25.00,33.629654,-84.428757,1,25.00,33.629665,-84.428871,1,0.00 KATL,R7,25.00,33.630730,-84.432289,1,25.00,33.630745,-84.432213,1,25.00,33.630814,-84.432045,1,25.00,33.630913,-84.431938,1,25.00,33.631035,-84.431877,7,25.00,33.631115,-84.431862,1,25.00,33.631035,-84.431839,7,25.00,33.630913,-84.431778,1,25.00,33.630814,-84.431679,1,25.00,33.630749,-84.431526,1,25.00,33.630726,-84.431419,1,0.00 KATL,R7,25.00,33.631824,-84.431862,1,25.00,33.631115,-84.431862,1,0.00 KATL,S,25.00,33.633610,-84.428955,1,25.00,33.633648,-84.428879,1,25.00,33.633614,-84.429077,1,0.00 KATL,S,25.00,33.633610,-84.427887,1,25.00,33.633636,-84.428009,1,25.00,33.633717,-84.428207,1,25.00,33.633801,-84.428322,1,25.00,33.633892,-84.428398,7,25.00,33.634083,-84.428474,1,25.00,33.634716,-84.428474,1,25.00,33.634731,-84.428474,1,25.00,33.635292,-84.428467,1,25.00,33.635502,-84.428535,7,25.00,33.635639,-84.428650,1,25.00,33.635719,-84.428764,1,25.00,33.635784,-84.428902,1,25.00,33.635811,-84.429039,1,0.00 KATL,S,25.00,33.635811,-84.427856,1,25.00,33.635777,-84.428032,1,25.00,33.635715,-84.428185,1,25.00,33.635628,-84.428299,1,25.00,33.635506,-84.428398,7,25.00,33.635292,-84.428467,1,0.00 KATL,S,25.00,33.635815,-84.428001,1,25.00,33.635777,-84.428032,1,0.00 KATL,S,25.00,33.633804,-84.428627,1,25.00,33.633892,-84.428551,7,25.00,33.634083,-84.428474,1,0.00 KATL,S,25.00,33.633804,-84.428627,1,25.00,33.633728,-84.428719,1,25.00,33.633648,-84.428879,1,0.00 KATL,SC,25.00,33.622116,-84.434654,1,25.00,33.622192,-84.434296,1,25.00,33.622368,-84.434082,1,25.00,33.622631,-84.433975,1,25.00,33.624611,-84.433983,1,25.00,33.625263,-84.433968,1,25.00,33.627476,-84.433983,1,0.00 KATL,SC,25.00,33.628109,-84.433983,1,25.00,33.629910,-84.433983,1,25.00,33.630150,-84.433983,1,25.00,33.630207,-84.433983,1,25.00,33.630455,-84.433983,1,25.00,33.630634,-84.434044,1,25.00,33.630726,-84.434113,1,25.00,33.630756,-84.434135,1,25.00,33.630909,-84.434219,1,25.00,33.631035,-84.434250,7,25.00,33.631130,-84.434250,1,25.00,33.631824,-84.434250,1,25.00,33.632599,-84.434250,7,25.00,33.632973,-84.434250,1,25.00,33.633038,-84.434250,1,25.00,33.633228,-84.434250,1,25.00,33.633400,-84.434311,1,25.00,33.633541,-84.434471,1,25.00,33.633606,-84.434692,1,0.00 KATL,SC,25.00,33.622120,-84.433357,1,25.00,33.622147,-84.433540,1,25.00,33.622234,-84.433731,1,25.00,33.622375,-84.433876,1,25.00,33.622631,-84.433975,1,0.00 KATL,SC,25.00,33.630726,-84.433388,1,25.00,33.630699,-84.433540,1,25.00,33.630630,-84.433693,1,25.00,33.630550,-84.433807,1,25.00,33.630478,-84.433876,1,25.00,33.630367,-84.433945,1,25.00,33.630207,-84.433983,1,25.00,33.630367,-84.434021,1,25.00,33.630474,-84.434090,1,25.00,33.630558,-84.434166,1,25.00,33.630630,-84.434273,1,25.00,33.630684,-84.434387,1,25.00,33.630711,-84.434486,1,25.00,33.630722,-84.434593,1,25.00,33.630726,-84.434715,1,25.00,33.630745,-84.434601,1,25.00,33.630787,-84.434486,1,25.00,33.630852,-84.434387,1,25.00,33.630936,-84.434311,1,25.00,33.631035,-84.434265,7,25.00,33.631130,-84.434250,1,0.00 KATL,SC,25.00,33.633610,-84.433815,1,25.00,33.633541,-84.434029,1,25.00,33.633400,-84.434189,1,25.00,33.633228,-84.434250,1,0.00 KATL,SG,25.00,33.620296,-84.419075,1,25.00,33.620358,-84.418800,1,25.00,33.620491,-84.418610,1,25.00,33.620647,-84.418488,1,25.00,33.620811,-84.418449,1,25.00,33.621094,-84.418449,7,25.00,33.621765,-84.418449,1,25.00,33.621822,-84.418465,6,25.00,33.621922,-84.418510,1,25.00,33.622025,-84.418617,1,25.00,33.622093,-84.418747,1,25.00,33.622124,-84.418900,1,25.00,33.622120,-84.420036,1,25.00,33.622124,-84.422462,1,25.00,33.622124,-84.423050,1,25.00,33.622120,-84.424210,1,25.00,33.622116,-84.424370,1,25.00,33.622086,-84.424515,1,25.00,33.622028,-84.424652,1,25.00,33.621944,-84.424812,1,25.00,33.621834,-84.425095,1,25.00,33.621735,-84.425453,1,25.00,33.621677,-84.425858,1,25.00,33.621681,-84.426361,1,25.00,33.621887,-84.427834,1,25.00,33.622108,-84.429359,1,25.00,33.622120,-84.429596,1,25.00,33.622120,-84.430237,1,25.00,33.622120,-84.431435,1,25.00,33.622120,-84.432510,1,25.00,33.622120,-84.433357,1,25.00,33.622116,-84.433731,1,25.00,33.622116,-84.434654,1,25.00,33.622116,-84.437721,1,25.00,33.622116,-84.438942,1,25.00,33.622112,-84.440903,1,25.00,33.622112,-84.442017,1,25.00,33.622093,-84.442200,1,25.00,33.622036,-84.442429,1,25.00,33.621956,-84.442619,1,25.00,33.621536,-84.443474,1,25.00,33.621479,-84.443611,1,25.00,33.621433,-84.443756,1,25.00,33.621399,-84.443901,1,25.00,33.621380,-84.444069,1,25.00,33.621380,-84.446144,1,25.00,33.621376,-84.447319,1,25.00,33.621361,-84.447411,1,25.00,33.621304,-84.447556,1,25.00,33.621204,-84.447670,1,25.00,33.621067,-84.447746,7,25.00,33.621002,-84.447762,1,25.00,33.620785,-84.447754,1,25.00,33.620628,-84.447708,1,25.00,33.620483,-84.447601,1,25.00,33.620350,-84.447411,1,25.00,33.620274,-84.447182,1,0.00 KATL,SG12,25.00,33.622120,-84.430237,1,25.00,33.622078,-84.430420,1,25.00,33.621990,-84.430588,1,25.00,33.621883,-84.430710,1,25.00,33.621777,-84.430779,1,25.00,33.621616,-84.430824,1,25.00,33.621395,-84.430855,1,25.00,33.621292,-84.430908,1,25.00,33.621166,-84.431030,1,25.00,33.621078,-84.431190,7,25.00,33.620926,-84.431496,1,25.00,33.620792,-84.431793,1,25.00,33.620659,-84.432152,1,25.00,33.620548,-84.432526,1,25.00,33.620445,-84.432953,1,25.00,33.620361,-84.433479,1,25.00,33.620304,-84.434135,1,25.00,33.620285,-84.434578,1,0.00 KATL,SG12,25.00,33.622120,-84.431435,1,25.00,33.622066,-84.431198,1,25.00,33.621960,-84.431015,1,25.00,33.621811,-84.430885,1,25.00,33.621616,-84.430824,1,0.00 KATL,SG14,25.00,33.622124,-84.423050,1,25.00,33.622059,-84.423271,1,25.00,33.621948,-84.423454,1,25.00,33.621811,-84.423561,1,25.00,33.621639,-84.423622,1,25.00,33.621487,-84.423637,1,25.00,33.621376,-84.423668,1,25.00,33.621265,-84.423737,1,25.00,33.621155,-84.423851,1,25.00,33.621082,-84.423988,7,25.00,33.620899,-84.424370,1,25.00,33.620728,-84.424782,1,25.00,33.620556,-84.425316,1,25.00,33.620430,-84.425858,1,25.00,33.620335,-84.426476,1,25.00,33.620289,-84.427094,1,0.00 KATL,SG14,25.00,33.622120,-84.424210,1,25.00,33.622070,-84.423996,1,25.00,33.621986,-84.423851,1,25.00,33.621891,-84.423752,1,25.00,33.621780,-84.423676,1,25.00,33.621639,-84.423622,1,0.00 KATL,SG16,25.00,33.622120,-84.420036,1,25.00,33.622078,-84.419861,1,25.00,33.621994,-84.419731,1,25.00,33.621902,-84.419647,1,25.00,33.621826,-84.419617,6,25.00,33.621769,-84.419601,1,25.00,33.621090,-84.419601,7,25.00,33.620808,-84.419601,1,25.00,33.620598,-84.419670,1,25.00,33.620438,-84.419815,1,25.00,33.620335,-84.420044,1,25.00,33.620308,-84.420181,1,25.00,33.620304,-84.420853,1,25.00,33.620293,-84.420944,1,0.00 KATL,SG2,25.00,33.620281,-84.445198,1,25.00,33.620296,-84.445290,1,25.00,33.620296,-84.445961,1,25.00,33.620342,-84.446213,1,25.00,33.620480,-84.446442,1,25.00,33.620644,-84.446564,1,25.00,33.620834,-84.446609,1,25.00,33.621002,-84.446609,1,25.00,33.621071,-84.446602,7,25.00,33.621178,-84.446541,1,25.00,33.621269,-84.446449,1,25.00,33.621353,-84.446297,1,25.00,33.621380,-84.446144,1,0.00 KATL,SG4,25.00,33.622112,-84.442017,1,25.00,33.622063,-84.442215,1,25.00,33.621964,-84.442375,1,25.00,33.621822,-84.442505,1,25.00,33.621666,-84.442566,1,25.00,33.621513,-84.442574,1,25.00,33.621391,-84.442551,1,25.00,33.621227,-84.442444,1,25.00,33.621136,-84.442345,1,25.00,33.621250,-84.442680,1,25.00,33.621334,-84.443016,1,25.00,33.621368,-84.443314,1,25.00,33.621376,-84.443550,1,25.00,33.621376,-84.443802,1,25.00,33.621380,-84.444069,1,0.00 KATL,SG4,25.00,33.620281,-84.438972,1,25.00,33.620354,-84.439941,1,25.00,33.620483,-84.440643,1,25.00,33.620708,-84.441391,1,25.00,33.620857,-84.441772,1,25.00,33.621075,-84.442215,7,25.00,33.621136,-84.442345,1,0.00

Yes. it is, and it even includes the Com/Hid facilities. But Eric should know that FSUIPC3 is no longer supported, so whilst we can answer some questions, ones like this, mostly we would not be able to help. Pete

The parking brake control is just a simple toggle, "Parking brakes". It is identical on P3D4 and 5, and, indeed, has been the exact same since FS98 days. Are you using a separate FSUIPC6 installation for the two sims, or a common one, with one lot of settings? We need to see your FSUIPC6.INI file so we can see your settings. If you have separate installations for the two sims, show us both, appropriately labelled. Pete

Your scenery.cfg file is corrupt. The [General] section is missing at the start. It is normally: [General] Title=Prepar3D Scenery Description=Prepar3D Scenery Areas Data Clean_on_Exit=TRUE I think that, without that, the Lorby program treats it as invalid and so you get no entries at all in the one generated by it for MakeRwys. Pete

John will answer more definitely than I, but I think the Add-Ons menu is only updated by PFC when everything is running -- i.e with MSFS ready to fly. Your FSUIPC log doesn't show these steps (edited for brevity): 3437 Simulator detected ... 32015 SimConnect_Open succeeded 32015 Running in "KittyHawk", ... 32015 MSFS version = ... 32015 Initialising SimConnect data requests now ... 129797 11592 -------------------- Starting everything now ---------------------- The PFC driver needs details from MSFS it only receives when things are fully connected. Pete

We updated FSUIPC so that the values in common between the NGX and NGXu were in the very same offsets, with the new ones added at the end. Your reference is NOT the PMDG SDK but the FSUIPC PMDG offsets documentation: Offset Mapping for PMDG 737NGX and 737NGXu.pdf Dated December 2019. Pete