John Dowson

What does this mean? It would be helpful if you could attach the pause.lua that you are using... The FS's pause function dies not affect WideFS7 directly. However, pausing the FS will restrict the data updates going to FSUIPC and so many offsets are not updated when the sim is paused, and so WideFS will also not see the offset changes. If you run the lua script on the server (PC running FSX and FSUIPC4) do you see the same behavior? I would expect so,,, Is the offset actually changing? If you log the offset value in FSUIPC4, can you see the change there?

That is just an informational message indicating that FSUIPC has detected that the PMDG 737 is loaded and the thread that handles the PMDG data offset population is started. It will have nothing to do with your sim freeze issue. FSUIPC will/should have nothing to do with this issue at all - you can try without FSUIPC7 running and you should get the same problem. John

Yes, you have to create this file yourself. Most are grouped together, and comments are also included. You just have to search for them - if you filter first on the hubhop site, you will see the prefix used for that aircraft, then you can search for that in the events.txt file in a text editor. Yes - it always exports the entire list. It is not possible to just export your filtered selection - you could raise a feature request for this with MobiFlight.

Event files are those files with the extension .evt - some are provided in the EventFiles folder under your FSUIPC7 installation folder. You will need the MF WASM module installed if using MF event files, other event files (such as the one for the FBW A32X are handled by the aircraft itself. So, when using event files, you need to have whatever handles those events installed in your Community folder. However, there is not much need to use actual event files these days - this functionality is better accessed via presets. The events.txt file is not an event file! It is the MF preset file, and contains the preset names together with the calculator code that is executed when you call the preset. These are the presets that you see in the FSUIPC7 assignment drop-down when you check 'Select for presets'. The FSUIPC WASM must be installed to use these presets (not the MobiFlight WASM). You can have both. The events.txt file are the presets provided by MobiFlight and is the same file you can download from the MF HubHop site. I only update this file (included in the FSUIPC7 installer) on new releases, but you can always download this file from the MF HubHop site and use it to replace the one in your FSUIPC7 installation folder if you want to use some newer presets that are not available in the one provided by the installer. It is recommended not to edit this file, as it will get overwritten/replaced the next time you update/re-install FSUIPC7. This is why the myevents.txt file is provided, so that you can define your own presets. Some folks even just copy the presets for the aircraft they use from the events.txt file to the myevents.txt file, and then remove or rename the events.txt file, to restrict the drop-down menu options to contain only the presets they may use, reducing the drop-down menu size considerably and making presets easier to find. Please refer to the section on presets in the Advanced User manual, in the WASM section. John

You need to determine what NMEA sentences are supported by Foreflight - the website mentions GDL90 Extension protocol which I know nothing about... I would try with RMC and GGA - also remember you need to set SimModeIndicator=Yes in the [GPSout] section of the FSUIPC4.INI file if using an IOS device. John

How do you know this? Well, as you have no general button assignments (i.e. for all aircraft), nothing will show in the button assignment window unless you have the Fenix loaded AND you check the Profile specific? checkbox. Button assignments (as well as key assignments) are inherited (unless overwritten) and you always have the possibility of adding a button or key assignments to the general section or the profile specific section. You need to manually check/uncheck that checkbox to switch between the two. Axes assignments work differently - if the aircraft is in a profile, the profile specific will be checked and inoperative (i.e. you cannot uncheck it), If you still think you have a problem, show me the files as advised. John

I have released 7.3.15 now, with the following additional controls available, mostly for helicopters it seems: ROTOR_LONGITUDINAL_TRIM_SET ROTOR_LONGITUDINAL_TRIM_INC ROTOR_LONGITUDINAL_TRIM_DEC ROTOR_TRIM_RESET AXIS_ROTOR_BRAKE_SET ROTOR_BRAKE_ON ROTOR_BRAKE_OFF ROTOR_BRAKE_TOGGLE MAC_CREADY_SETTING_DEC MAC_CREADY_SETTING_INC MAC_CREADY_SETTING_SET PROP_LOCK_ON PROP_LOCK_OFF PROP_LOCK_SET PROP_LOCK_TOGGLE AXIS_COLLECTIVE_SET COLLECTIVE_INCR COLLECTIVE_DECR TAIL_ROTOR_INCR TAIL_ROTOR_DECR ROTOR_GOV_SWITCH_OFF ROTOR_GOV_SWITCH_ON AUTO_HOVER_TOGGLE AUTO_HOVER_OFF AUTO_HOVER_SET AUTO_HOVER_ON PLASMA_ON PLASMA_OFF PLASMA_SET PLASMA_TOGGLE SPOILERS_INC SPOILERS_DEC RADIO_VOR3_IDENT_TOGGLE RADIO_VOR3_IDENT_SET RADIO_VOR3_IDENT_ENABLE RADIO_VOR3_IDENT_DISABLE RADIO_VOR4_IDENT_TOGGLE RADIO_VOR4_IDENT_SET RADIO_VOR4_IDENT_ENABLE RADIO_VOR4_IDENT_DISABLE ADF2_SET ADF2_EXTENDED_SET ADF2_LOWRANGE_SET ADF2_HIGHRANGE_SET ADF2_OUTSIDE_SOURCE ADF2_NEEDLE_SET ADF2_VOLUME_SET ADF2_VOLUME_INC ADF2_VOLUME_DEC HELICOPTER_THROTTLE_INC HELICOPTER_THROTTLE_DEC AXIS_HELICOPTER_THROTTLE_SET HELICOPTER_THROTTLE_SET HELICOPTER_THROTTLE_CUT HELICOPTER_THROTTLE_FULL HELICOPTER_THROTTLE1_INC HELICOPTER_THROTTLE1_DEC AXIS_HELICOPTER_THROTTLE1_SET HELICOPTER_THROTTLE1_SET HELICOPTER_THROTTLE1_CUT HELICOPTER_THROTTLE1_FULL HELICOPTER_THROTTLE2_INC HELICOPTER_THROTTLE2_DEC AXIS_HELICOPTER_THROTTLE2_SET HELICOPTER_THROTTLE2_SET HELICOPTER_THROTTLE2_CUT HELICOPTER_THROTTLE2_FULL AXIS_CYCLIC_LATERAL_SET AXIS_CYCLIC_LONGITUDINAL_SET CYCLIC_LATERAL_LEFT CYCLIC_LATERAL_RIGHT CYCLIC_LONGITUDINAL_DOWN CYCLIC_LONGITUDINAL_UP Note that the new axis AXIS_TAIL_ROTOR_SET is currently not recognised and so has not been added. This seems to be the only one. John

Yes of course you can...and that is what I thought you have already done. You said that you have done this but your settings no longer work. The GUIDs in the log you attached match those in your ini, so really everything should be working ok. I do not understand what your problem actually is... The log file shows one issue: This is from this assignment: 6=PB,135,CPFNX320_LIGHT_DOME_OFF,0 -{Preset Control}- That failed as you tried to send this (i.e. pressed button 135 on your X-56 Rhino Throttle) before everything (e.g. WASM/WAPI) was ready. You need to wait for a few seconds after the aircraft is loaded and ready-to-fly before trying to control. I am getting confused, as well as wasting time, on this thread/issue. Do you actually have any problems, and if so can you please explain clearly what they are. Also, attach a log file with appropriate logging activated for your issue. So, if you have a button assignment that is not working, activate logging for Buttons & Keys and Events, generate a log file showing the problem (i.e. button pressed, no event sent) and show me that, together with your FSUIPC7.ini file. If the issue is with an axis assignment, activate logging for Axis Controls (as well as Events) and generate a log file showing that issue. Always attach both your FSUIPC7.ini and FSUIPC7.log files from the same session.

Strange....

What happens with the Maddog X? Have you tried logging what the lua is doing to see what the issue is with this aircraft? I don't have the Maddog X so cannot really help you, but logging the offsets suggested in the initial post, as well as using lua debug logging, should show you what is happening - especially if you compare the log output to that produced with an aircraft where the script is working as expected. John

The sentences output are controlled by the check boxes in the GPSout panel: The geographic position (latitude, longitude) will be emitted if the GLL box is checked. See the following for the sentences emitted with each check-box: https://www.rfwireless-world.com/Terminology/GPS-sentences-or-NMEA-sentences.html Or am I misunderstanding your question? John

I am not sure there us a suitable example for this... You can take a look at the lua examples provided (there will be a zip file of examples in your FSUIPC Documents folder). If you could explain further how the differential braking works using this brake lever and rudder, I could help you with this. However, I am quite busy at the moment (need to get an update out for SU11....), so this would be at the weekend or maybe next week. But if you can provide more details (or a reference), I can provide you with a lua script that you could then tune to your needs. I do have the Flying Iron Spitfire (although I haven't had much time to fly this yet....) so I can do some testing here... John

You cannot see the log file as you have windows explorer set to hide the extension of known file types. Change your Windows Explorer options to see the extensions correctly - see the Addendum Identifying Files in Windows Explorer in the Installing and Registering FSUIPC document if you require further details. Note also that you only have assignments in FSUIPC for one aircraft - the Fenix A320, so you will have no assignments with any other aircraft. Also, the name/title of the aircraft loaded must contain the string FenixA320 for your assignments to be loaded. Your controllers are recognised ok, so looks like the GUIDs haven't changed, and so I suspect your issue is that you just don't have any asignments defined for the aircraft that you are using. Again, the FSUIPC7.log file would tell us this... John

Could you please read the section on using presets in the Advanced User manual, under the WASM section. This should tell you everything you need to know about using presets. Yes they do! You need to scroll down further, and note that they start with PMDG B737-7 and not PMDG B737. Also, make sure that you are using the latest version of FSUIPC, 7.3.14. All MF presets are stored in a file called events.txt, and this is only updated when I release a new version of FSUIPC7. For new presets (added after an FSUIPC release), you can either download the latest events.txt file from the MF Hub-Hob site (you will need to register and sign-in to do this), or add them yourself. John

That is strange - I thought those functions were working ok in P3Dv4 and P3Dv5 - it is MSFS that is having issues with message displays. I'm a bit busy at the moment (new version to prepare for the MSFS SU11 release), but I will take a look at this when time permits (hopefully next week). John

It' me now, John Dowson - Pete retired several years ago, although he does help out occasionally (but more for MakeRunways or FSUIPC4 rather than later versions). There are quite a few new rotor related controls, all though I am not sure which ones are actually recognised yet, I will release an update in the next few days and any new events/controls will be added then (check the history document or changes file when released for a summary of the new ones added). John

The log file is just for confirmation of joystick ids acquired, and there corresponding GUIDs. However, any new devices/GUIDs should also be in the updated FSUIPC7.ini. The ini you posted only shows the original GUIDs - so either they haven't changed or that ini has not been re-written by the new PC. As it is from a backup, I suspect the latter... Anyway, show me both files from the new PC, and after you have updated FSUIPC to the latest (and only supported) version, and ran FSUIPC7 once and then exit - no need to run MSFS. John

And for the cut-off, there are also these: PMDG_B737_ENGINE_START_LEFT_LEVER_CUTOFF#68802 (>K:ROTOR_BRAKE) PMDG_B737_ENGINE_START_LEFT_LEVER_IDLE#68801 (>K:ROTOR_BRAKE) PMDG_B737_ENGINE_START_RIGHT_LEVER_CUTOFF#68902 (>K:ROTOR_BRAKE) PMDG_B737_ENGINE_START_RIGHT_LEVER_IDLE#68901 (>K:ROTOR_BRAKE) as well as PMDG_B737-7_FUEL_CUT_OFF_LEVER1_DN#(L:switch_688_73X) 0 == if{ 68801 (>K:ROTOR_BRAKE) } PMDG_B737-7_FUEL_CUT_OFF_LEVER1_UP#(L:switch_688_73X) 100 == if{ 68801 (>K:ROTOR_BRAKE) } PMDG_B737-7_FUEL_CUT_OFF_LEVER2_DN#(L:switch_689_73X) 0 == if{ 68901 (>K:ROTOR_BRAKE) } PMDG_B737-7_FUEL_CUT_OFF_LEVER2_UP#(L:switch_689_73X) 100 == if{ 68901 (>K:ROTOR_BRAKE) } Not sure why there are duplicates or why they are slightly different...suggest you try both/all to see which work, John

Then how did you provide the FSUIPC7.ini file? I need to see that from your new PC, not the old one. The old one will just have the GUIDs from your old PC. I need to see both of these files from your new PC, and once updated by running FSUIPC7 on the new PC. Ince you have those it is a simple change - you just need to replace/update the GUIDs for the letter assignments in the [JoyNames] section, so, for example: you would replace that GUID (which is from your old PC) with the new/updated one from your new PC. This will be listed (in the same section) with a joyId or number - just use the number where the name matches and update the letter GUID to match the one listed with the number, so this one: Of course, the GUID there is the same (as from the same PC), but it will be different on your new one. John

Yes, it seems that even though that preset is listed (https://hubhop.mobiflight.com/presets/) it is not exported to the events.txt file...strange, but this is a question for MobiFlight... However, you can see the controls for the left knob in that screenshot: PMDG_B737-7_ENGINE_START_LEFT_ROTARY_SWITCH_CONT_POS PMDG_B737-7_ENGINE_START_LEFT_ROTARY_SWITCH_FLT_POS PMDG_B737-7_ENGINE_START_LEFT_ROTARY_SWITCH_GRD_POS PMDG_B737-7_ENGINE_START_LEFT_ROTARY_SWITCH_OFF_POS and there are matching presets for the right knob: PMDG_B737-7_ENGINE_START_RIGHT_ROTARY_SWITCH_CONT_POS PMDG_B737-7_ENGINE_START_RIGHT_ROTARY_SWITCH_FLT_POS PMDG_B737-7_ENGINE_START_RIGHT_ROTARY_SWITCH_GRD_POS PMDG_B737-7_ENGINE_START_RIGHT_ROTARY_SWITCH_OFF_POS John

I need to see an FSUIPC7.log file as well, as I said... However, looking at your ini, there are no missing devices. Did you also copy across your FSUIPC7.key file or re-register? If you are using an unregistered version, your controllers (i.e. the [JoyNames] section of your ini) will not be re-written and no assignments will be available. So, first check that you are actually using a registered version, and then show me both your FSUIPC7.ini file and a FSUIPC7.log files. Note that you are also using an old and unsupported version of FSUIPC7 - 7.3.12. The latest and only supported version is 7.3.14 - please update. John

When using/reading lvars in lua, you can check that they exist before trying to read them as follows: id = ipc.getLvarId("L:myLvarName") while id == nil do ipc.reloadWASM() ipc.sleep(100) id = ipc.getLvarId("L:myLvarName") end -- Lvar now available! Of course, the while loop would never end if the lvar doesn't become available, so you may also want to add a counter and exit the script (or do something else) if the lvar doesn't become available after a fixed number of attempts. John

Sorry, I don't know that lua...can't you also pull that from your backup? John

If you have changed your PC, the GUIDs of your controllers will have changed (assuming that you are using the same controllers) and your FSUIPC7.ini file will need updating to use the new GUIDs otherwise your controllers will be recognised as new devices (as they have new GUIDs). If you can attach your FSUIPC7.ini and an FSUIPC7.log file I can take a look and do this for you. John

Keys? What keys? What 737 are you using? PMDG? The name/function associated to a switch/button/control is usually shown in a pop-up when you position the mouse over it in the VC (depending on your settings)..the first is ENGINE START LEFT and the second ENG 1 START and ENG 2 START. If using the PMDG 737, the left start knob can either be controlled with the lvar L:switch_119_73X with GND=0, OFF=10, CONT=20, FLT=30, or using the preset PMDG_B737_ENGINE_START_LEFT_KNOB. For the cut-off levers, you can use presets PMDG_B737-7_FUEL_CUT_OFF_LEVER1_UP, PMDG_B737-7_FUEL_CUT_OFF_LEVER1_DN, PMDG_B737-7_FUEL_CUT_OFF_LEVER2_UP and PMDG_B737-7_FUEL_CUT_OFF_LEVER1_DN. John