John Dowson

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

Yes - read the Installing and Registering FSUIPC7 manual provided, and try the solutions outlined there. 99% of all registration issues are either due to user error (not inputting the details EXACTLY as provided in your purchase email) or to the required VC++ redistributables not being installed. If you still have issues after reading and trying the solutions outlined there, let me know your order number and I will check them here. Please do not do this unless you have already updated your VC++ redistributables. John

No, sorry, I will not be increasing this number for the time being (for various technical reasons. This is really an MSFS issue - it should only provide lvars that are in use with the current aircraft. Try raising a bug report to Asobo...hopefully they will fix this at some point, and the more people that complain the better the chance of this getting fixed. Note that you can still set/change lvars that are not known to FSUIPC by using calculator code, but you will not be able to read the value. John

I am slightly confused you first say that you want the trim tab positions, but then say: i.e. actual positions in degrees. For Aileron position, you can use offsets 0x03B0 for left aileron deflection (in radians - easy to convert to degrees) and 0x03B8 for the tight aileron deflection, or 0x2EA8 for average of left/right deflection. For the aileron trim deflection, you can use offset 0x2EB0 (also in radians). If you search the offset status document, you will also find the offsets for rudder and elevator deflection, as well as the corresponding trim deflection. For displaying the values in a pop-up window, maybe take a look at the script provided in this user contribution which you can adapt: John

What do you actually mean by this? Does the spitfire actually have/support differential braking? For differential braking, you would usually just assign one axis to the left brake control , and the other to the right brake control. For anything more complicated, you can assign the axis to a free FSUIPC offset and pick up the offset values/changes in a lua script (using event.offset) and process the values there and sent on whatever you want to achieve to the FS. John

3066 is the maximum number of lvars supported by FSUIPC. However, any single aircraft should not have that many lvars - many are probably either from the previous aircraft loaded, or aircraft sitting in your Community folder. You can try restarting - using the same aircraft as the previous aircraft used after a restart may reduce this number of phantom lvars (i,e, from other aircraft), Otherwise, the usual procedure is to clear out ither aircraft that you are not using from your Community folder before starting MSFS, Many people use the MSFS Add-in Manager (freeware) to do this. John

No, sorry - that is a question for Fenix support. John

No. Yes. All your SimMarket purchases will be listed in your SimMarket account, so check there. The FSUIPC7.key file is located in your FSUIPC7 installation folder. It is not removed when you uninstall FSUIPC7, so it should still be there. Note that you do not need to manually uninstall FSUIPC7 when updating - just run the new installer and that will prompt you to uninstall the previous version if installed, and yout chosen installation location will be preserved. If you have not purchased FSUIPC7, you can try with the trial license available in a sticky post at the top of this sub-forum. John

@Cuantreau Key assignments seem to be working as normal in SU11. If you are still having issues, please show me your files as described in my previous comment. John

This is working ok here... Could you show me your FSUIPC7.ini and a log file produced with WAPI debug level logging enabled. Thanks, John

The calibration facilities in FSUIPC7 are the same as in other versions of FSUIPC. There is a trial license available in a sticky post at the top of this sub-forum you can download to try the registered facilities. To reduce the sensitivity of an axis, you can also edit the FSUIPC ini file to manually increase the axis range (by editing the calibration entry). This can dramatically change the sensitivity, but you will use the full range of the axis, For example, this is my Aileron calibration entry: Aileron=-16384,-600,600,16383 If I change this to: Aileron=-22384,-600,600,22383 That would make the aileron less sensitive, but you would lose the ability to set 100% deflection - max would be 16384/22384, so about 73%. Combining this with a suitable calibration slope can be used to get better sensitivity, although you may also want to do this individually for each aircraft (i.e. in a profile). John

I am updating now and will check this later, but as @ark1320has reported that this is working for him, can you check again. If you get the same issue, please attach your FSUIPC7.ini and FSUIPC7.log files, the latter generated with logging for Buttons & Keys and Events activated, and showing some assigned key presses that are no longer working. John

This seems strange...are lvars available? Luas are auto-started once the lvars have been received, so if luas aren't started then lvars will also not be available... I am updating now and will take a look later... John

Yes - all MSFS clients, as well as FSUIPC clients, need to be ran at the same level. Glad you sorted it out, Regards, John

Also note that there is a trial license available for FSUIPC7 in a sticky post at the top of this forum. Please download and use this to try FSUIPC7 before purchasing. John