John Dowson

But an axis and an lvar are two completely different things. If you are assigning an axis to a preset, it is the axis value that is sent to the preset as the parameter. It is then up to you to calibrate/adjust that value in the preset RPN to whatever is needed. An lvar can accept a range of values, and every lvar is different. Some lvars only hold a 1 or 0, others can hold a range, and that may be from 0-100, -100 to +100, 0 to 1, etc. It is up to you to determine the range and scale the axis range accordingly. The range of values an axis sends depends on the axis. Standard joystick axis usually send values in the range -16384 - +16383, but some (especially those using potentiometers) can have a range of 0-1024 or -1024 to +1024. Calibration is used to calibrate the axis range to the range expected by the control being used. There are quite a few MF presets that calibrate to that range, and some for other ranges (0-1024 being another common range). You need to look at the preset code and description for such 'potentiometer' presets and update or change to your axes range. Because different hardware/drivers use different ranges for axes.

What do you mean by this? If an lvar isn't listed, it doesn't exist (or hasn't been 'discovered' yet in a scan).

Can you please show me / attach both your macro file and your FSUIPC6.ini file.

When FSUIPC7 is auto-started, 'Exit with FS' is always set and the options menu entry for this is removed.

Well then that needs to be looked into and fixed. Is the 'Exit with FS' active/checked? If so, and FSUIPC7 is not exiting cleanly when MSFS exits, can you please show the FSUIPC7.log file.

If you need to know/read the value of anything (lvar, input event, simvar) then add it to an FSUIPC offset, You can then use FSUIPCs offset controls to set the value, including increment and decrement controls. Are you sure thats an lvar? There is a simvar called ELEVATOR TRIM PCT, held in offset 0x0BC0. You can try assigning to the offset word inc/dec controls on that offset to control the trim. That is the normal method of getting a more responsive trim as you can specify the delta amount to your needs, or have a fast and slow assignments (i.e. different deltas) on different buttons (or virtual buttons). There are also other solutions for trim - e,g, see

FSUIPC knows nothing about MSFS assignments or settings, and I do not know if they apply when assigned using FSUIPC - you will just need to try it. You can/should first calibrate in FSUIPC if assigned there, and you can also apply sensitivity "slopes" there.

Having never tried MSFS (or even used) an xbox, I cannot really advise. These forums are for FSUIPC support, which only works with the PC version, so I doubt you will find many xbox users here either. I would presume all flight simmers, as opposed to gamers, would be using PCs. John

Yes - if assigning an axis or button/switch/key in fsuipc, you should remove any assignment to the same axis/button/switch/key in MSFS, otherwise both assignments will apply and cause issues/conflicts. If using fsuipc for all assignments, you can create a new/empty profile for your controller in msfs. Otherwise, you csn just remive any assignment in msfs once assigned in fsuipc.

Sorry but I cannot help you with issues with FSX - try avsim. John

This is already implemented and will be in the next release. This only affects the auto-start of the websocketserver, as it doesn't make sense starting it before FSUIPC has a connection, That would also be a good idea. Latest beta attached below - you shouldn't need the Init3308 init parameter with this. John FSUIPC7.exe

The FS version is not available until FSUIPC is connected to the FS. You can set the FSUIPC7 ini parameter init3308 to 13 (for MSFS2020) or 14 (MSFS2024) to prevent this. In the next FSUIPC7 release, I will also delay the starting of the websocketserver until FSUIPC7 is connected to the FS and the version known - see John

I gave details on how to add input events to offsets in a post earlier in this thread, with a link to an example... The "input events' you see in the MSFS behavior windows are B-vars, and are only accessible via calculator code, and only in MSFS2024 (i.e. you cannot use these in MSFS2020). As I said before, you should look at the Input Events available via FSUIPC, and use the input event logging facilities in FSUIPC to determine what input event controls a particular function. The B-vars and input events are basically the same, but you will find there are usually several b-vars associated to a given function (*_set, *_inc, *_dec, etc) but only one input event. So, for the taxi lights 3, there is the input event LIGHTING_TAXI_3 which you can either: - assign to directly to change the value and thus turn the lights on/off - add the input event to an FSUIPC offset, where you can read it, write write to it (to also trigger the input event value change), wait for an event, etc So, to read the value in lua or get an event when it changes, add it to a free/spare FSUIPC offset. And if it is in an offset, you can then set the offset to 1/0 to turn the lights on/off, using FSUIPC's offset controls, rather than using calculator code. Please re-read my earlier posts and take a look at the example i gave (to increment/decrement the value of an input event, which is slightly more complicated than just setting it). There are many FSUIPC offset areas designated as free for general use, see the Offset Status document and search for 'free' or 'general'. John

Sorry but no. If I did that, then I would get many support issues saying that they couldn't start FSUIPC as they double-click it and nothing happens, when it is already running and sitting in the system tray. There just has to be some feedback if/when you start something and nothing happens - surly you understand that? You should really look into the issue causing this - why is FSUIPC being started multiple times? John

That is normally the case, but as I had to fire-up the license generation machine I have also generated one for FSUIPC6, valid until 15th March. Just save the attached file to your FSUIPC6 installation folder. John FSUIPC6.key

No need to shout... Once a macro is created, you would assign to the macro as you would any FS control, as stated in the User guide (relevant part in bold): Is that not clear enough? Regards, John

Do you mean logging simconnect? What is confusing about those instructions? Please let me know and I will update... But you probably don't need to do this - it is a last resort. It can help with diagnosing simconnect connection issues as it shows all simconnect clients and how many connections they are using (as well as all SimConnect activity). And the log files can grow large very quickly. Ok, not problem - thanks for the update. If these issues return, check the FSUIPC log file and see if there are any connection issues and if so take appropriate action (whatever that may be!). Regards, John

As I said in the DM you sent me: This is all in the documentation. It will log ALL events that have been applied in the FS, but note that Axes controls/events are logged on a separate check-box for (hopefully) obvious reasons. Yes, of course, but you need the registered version to use the assignment functionality. The free version is mainly used for two purposes: - supporting 3rd party add-ons that use FSUIPC - its logging facilities For StreamDeck, did you read that link? In it it says: So why don't you try that first, with the unregistered version of FSUIPC, and see if that is enough for your needs. You can then decide if you need the full/licensed version. Well, FSUIPC has been around for 20 odd years and the current documentation and available resources seems to be good enough for almost all other users. As I said, try these forums (there is a wealth of information here) and there are also other resources (videos, etc) - just google. I know the documentation is not ideal but it is what it is - I have far too much to do and have no time at all to even consider re-writing the documentation. And it really isn't difficult if you just play around with it - many people get by and don't even realise that there is ample documentation installed in their Documents folder.... I only provide a trial license for FSUIPC7 / MSFS. I suggested that, if you are looking for something to help you with StreamDeck, you try that plugin with an unregistered FSUIPC, and then you can decide if you want to purchase a license. Please also note that you posted in a topic that is 15 years old and not related to your post. Any further questions, please find an appropriate topic or create a new one. John

Yes - please see the Installing vJoyOffsets section of the documentation: You should download and install the latest version of vJoy (from https://sourceforge.net/projects/vjoystick/) and then follow the installation instructions. John

I have no idea what those variables are so do not know if they can be "accessed". You should maybe clarify what these variables actually are - either on the Asobo forums or maybe on the MobiFlight discord channel. Also, I do not see anything under Local here with the TBM loaded - is that the aircraft you are using? They are certainly not standard lvars or input events, and so cannot be used directly in FSUIPC. It may be possible to access them using calculator code, but I don't know how to do this (as I don't know what they are!). Again, a question for Asobo or MobiFlight. What are you actually trying to achieve? Maybe it is not necessary to use those.. John

I have moved your post to the FSUIPC7 support sub-forum. That is a very long start-up time...how long from when FSUIPC7 is started by MSFS until you get to the main menu in MSFS? With such a long start-up time, I think it is probably better if you disable auto-start of FSUIPC7 and always start it manually once MSFS is ready. You can (manually) create a link on your desktop to start FSUIPC7 only. This is not related to any changes in FSUIPC7. Just use the latest release. Ok. If you get issues, check the to see if FSUIPC is connected. To determine if there are any simconnect issues, you can enable simconnect logging - see Also you should increase the maxClients parameter in your SimConnect.xml file from the default of 64 to 128, if you have not done that already. John

This may help - a lua function to convert a decimal frequency, in MHz not Hz) to BCD16: -- Convert frequency to BCD (e.g., "113.45" → 0x1345) function convertToBCD(freq) local cleanFreq = freq:gsub("%.", "") -- Remove decimal (e.g., "109.2" → "0920") local decimalNumber = tonumber(cleanFreq) -- Convert to number if not decimalNumber then return 0 end -- Return 0 if conversion fails local bcd = 0 local shift = 0 -- Convert each decimal digit to BCD format while decimalNumber > 0 do local digit = decimalNumber % 10 bcd = bcd + (digit * (16 ^ shift)) -- Use base 16 shift instead of bitwise left shift decimalNumber = math.floor(decimalNumber / 10) shift = shift + 1 end return bcd end John

You should look into them, its not difficult. MSFS is a very different beast that FSX/P3D, and there are various different options for assignment (not just FS controls and the occasional lvar). FSUIPC's logging helps you determine what to use, and is a lot easier and quicker (in most cases, IMHO) than using the MSFS debugging tools, which I only use rarely as a last resort.

Sorry, didn't realise (or forgot) that you were using FSX/FSUIPC4, No, it is not available - you should use NAV1_RADIO_SET (65708) instead. That takes the frequency in BCD format. Sets the chosen NAV frequency (BCD16 encoded Hz). But you cannot just change 67251 to 65708 and expect the script to work. You need to change the parameter to BCD format, or to an integer than when converted to hex shows the frequency in BCD format (with leading 1 dropped). Try and do that yourself - use logging to check that you are sending the correct parameter. If you have difficulties I can look at it for you, but you should at least try. I do not have much free time for these type of things at the moment.... John

For all auto-start issues, see For connection issues, see the section Auto-tuning of initial start-up ini parameters in the Advanced User guide, or the following FAQ entry: If you still have issues after reading and following the advice there, please show me/attach your FSUIPC7.log file and explain what the issue is. John