John Dowson

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

Of course not - FSUIPC7 is a different product and requires its own unique key/license, available from SimMarket. John

I've tested that here now and that works - sending lalt+1 on button press (& release) of B.18 and lalt+2 on B.19, using the facilities provided at offset 0x3110. John

What is this? If you want to test by using buttons to write to offsets, you need to use the Offset DWord Set control, and if you set the parameter offset on press, and set the control number 1070 on release, it should look like this: 5=RB,18,Cx03003114,x00001031 -{offset dword set, offset 3114}- 6=UB,18,Cx03003110,x0000042E -{offset dword set, offset 3110}- 7=RB,19,Cx03003114,x00001032 -{offset dword set, offset 3114}- 8=UB,19,Cx03003110,x0000042E -{offset dword set, offset 3110}- John

No you haven't. I want to know what you have tried and what happened - I said please, do as advised and report back what you have done, and what the result was To be clear, did you check the box marked Check if using a different name or address for WideFS, and enter the name and email address for your WideFS7 purchase and then click on Register? You should then see 2 pop-up boxes approving or denying validation - what did they say? If you did that and the licenses didn't valid, it can ONLY be that your VC++ redistibutables are out of date. Please download and install the latest combined redistributable package from Microsoft. Details and a link are provided in the README.txt and in the installation manual. These both validate just fine. I will PM you. John

They are not the correct parameters - as it says in the documentation, the message (0x3200 4 bytes) is WM_KEYDOWN or WM_KEYUP which are 256 and 257 respectfully. You can see the parameter to use in the log message. Using this offset you would have to send both a WM_KEYDOWN and WM_KEYUP message to get a key press and release, as well as sending the Alt key separately (i.e. 4 messages in total), so maybe better/easier to use offset 0x3110. As specified in the documentation: Unfortunately it seems I removed the text that shows you how to calculate the actual parameter if using offsets. The parameter is keycode+256*shift code, So for lalt +1 (49 + 24), it would be 49 +256*24 = 6193. Alternatively, also 49+256*16 = 4145 (as 8 is the shift code for a normal key and can be ignored). Note that lalt and tab shift codes are switched for key press assignments, and I am not sure which mapping the 1070 control uses. If it uses the key assignments shift codes, it would be 49+256*4 = 1073. So, first try with parameters 4145 and 4146 (or 6193 and 6194), and if those don't work try 1073 and 1074. Remember to write the parameter to offset 0x3114 before writing 1070 to 0x3110. John

The LINDA support forum still seems to be active: https://www.avsim.com/forums/forum/429-linda-support/ However, most folks have moved on now from FSX, especially since the release of MSFS2020. There should be a text document in your FSUIPC4 installation folder called The 2016 List of FSX and P3D Controls.pdf - yjis contains a list of available events and their ids, in both numerical and alphabetical order. For a description of whatthe events do, you need to consult the SimConnect SDK documentation. You can use FSUIPC's logging facilities - activate logging for Events (non-axis controls) and Send to console window (both from logging tab) and you can see any event + parameter used when a button/switch is used in the VC. John