John Dowson

A new trial license is now available (from first post in this topic), valid until 1st December 2025. Note that this is the last time I will provide a trial license in this topic/via these forums. These forums will be closing at the end of the year and all support will be moving to the FSUIPC7 home website (fsuipc.com) and Discord. I will post more information about this in the coming days once the update/new website has been released.. John

Not sure why that would be - is the value of the lvar decreasing when you do this? You can verify by re-enabling that log line and check the log file (or open the logging console so you can see the messages in real time when you move your assigned axis. Also set logging for Events/Controls, and maybe also axes controls, yo see if any other event is registered that could be preventing this. If it is decreasing, then it could be due to assignments in FSX - check you have disabled controllers in FSX if assigning everything in FSUIPC. John

You will only have profile sections in your ini file if you are actually using profiles. Also, if you are using profiles-in-separate files, the profile-specific sections will be in a separate file (named after the profile) and will not contain the profile-name extension. So it really depends on how you are using FSUIPC. If you fly multiple aircraft, you should be using profiles. The only reason to not use profiles is if you only fly a specific aircraft. See the section on profiles is the User guide for details. John

The additional '.FENIX A320' indicates that this is a profile-specific calibration section - FENIX A320 is the name of the profile. If you are not using a profile for the Fenix, then you would use the general calibration section [JoystickCalibration], which will apply to all aircraft that don't have a profile specific calibration section, even when the aircraft is in a profile and has its own profile specific [Axes.xxx] section. John

Note the license is still valid today - it expires at the end of the day. I will update later today (if I get time) or tomorrow.... John

You can attach your FSUIPC7.log file, or copy the relevant text from there. But why are you using an 8-byte floating point number? Even though input events (and lvars) are always stored internally as 8-byte floats, they are often used as just integers, Booleans, etc. As this one has a fixed set of discrete values within the rang 0-255, you should add it as an unsigned byte (UB) and use the Offset UByte Increment/Decrement controls (or Offset Byte Cyclic Increment/Decrement). Always use the the type relating to how input events/lvars are used when adding to offsets, which is rarely a 64-bit float. Note also you have an extra 0 - its A000 and not A0000. Any further issues, please attach your log and ini files. John

You can do this easily in two ways: 1. use a preset to increment using '++'. Also use min/max so it stays within range 2. Add the lvar to an FSUIPC offset, then use the FSUIPC-added controls to inc/dec/cycle the offset. Changing the offset value in this way, when the offste holds an lvar, will send the new value to the FS. Well, many standard events don't work for many add-on aircraft in MSFS, both MSFS2020 and MSFS2024. That is why you need to look into lvars, hvars, bvars, etc Usually you can use FSUIPC logging - either events or input events. For lvars its more complicated - you have to find the lvars you want to monitor first (list them in FSUIPC), and then you can log the lvar changes to the lvars by adding a section to the FSUIPC7.ini file. This is documented in the WASM section of the Advanced User guide. B-events are Input Events, just via a different root - in FSUIPC, you can use input events directly via the Simconnect interface. B-events are only for use in gauge code, i.e. via valculator code or a preset. There is a mapping from B-events to input events, but not 1-1. For ecample, there may be just one input event which has a value (which you can change/set), but there may be several b-events associated to this input event, such as *_set, *_inc, *_dec. You won;t see these in the input event interface, just a variable with a value that you can control. No problem! Cheers, John

Did you try the MAGNETO_INCR k-event instead of the MAGNETO1 one? But I don't think that will work either... If the BS Bonanza G36 uses an lvar, I would have thought the Pro would use something similar. Have you tried listing the lvars to see if anything looks appropriate? Also maybe try looking at the Input Events - you can list these, and also log any changes. Set logging for Input Events, (Log->Input Events) open the logging console (Log->Open Console) and turn the magneto in the virtual cockpit (VC) to see if anything is logged. You can also examine the behavior of the switch using the MSFS dev tools to see how it is controlled - see this MF documentation: https://docs.mobiflight.com/guides/input-events-2024/ You can assign to input events in FSUIPC in two ways: 1. Using Input Event assignments directly 2. via calculator code and using them as B events (MSFS2024 only - doesn't work in MSFS2020) John

Some standard controls don't work when assigned externally, and this is aircraft-dependent and I assume an issue with the event implementation in the aircraft. I cannot do anything about this in FSUIPC. There are no MF presets for this yet. The presets for the magneto in the BS Bonanza G36 use the lvar L:BKSQ_IgnitionPosition_1 with a parameter of 0, 1 or 3 (for off/right/left), so maybe try them - check to see if those lvars exist or if there are similar ones for this aircraft. See the MSFS documentation: https://docs.flightsimulator.com/msfs2024/html/6_Programming_APIs/Reverse_Polish_Notation.htm John

I have PM'ed you a key file. Please save this to your FSUIPC7 installation folder, then run the installer again. The registration fields should be pre-populated with the details from the file - try validating them and let me know the result. Even if it doesn't validate in the installer (which would indicate that there are still issues with your VC++ redistributables), please try starting FSUIPC7 and see of that runs as a licensed copy (i.e. can you see the Assignments menu?).

Just change the calibration - change to You can also comment out that log line (as shown) if its working as you don't want to flood you log with messages. John

No, you don't. It is me that sorsts out such issues, not SimMarket. Did you read the documentation, as advised? What exactly have you trued? Have you installed/re-installed the latest combined redistibutables (from Microsoft) for both x86 and x64? Have you checked your anti-virus for any warnings? If all else fails, please let me know your order number and I will check them here. Do NOT post your key details. Please note that EVERY order I have checked when people post this issue has been successful here, and the error is always a user error, mostly by not copying/pasting the details (name, address/email and key - all 3 parts must match EXACTLY) or by not having the correct VC++ redistributables installed. John

I don't think a 90 degree turn should be possible!! The max steering angle is defined by the NOSEWHEEL MAX STEERING ANGLE simvar, which I guess is taken from the aircraft.cfg file or some other aircraft-specific configuration file. I am pretty sure this will be less than 90 degrees, although this is updatable. I would have thought this would be obeyed regardless of how the steering tiller is assigned. Okay, so you are just using MSFS assignments for the tiller. Thats fine if you want to do this, but @Alhard Horstmann wants to assign in FSUIPC and not MSFS, hence his post. Note that the OP of this topic (firs post) also recommended removing the SteeringTiller calibration entries to get this to work. I am not sure what the issues are with the SteeringTiller assignments in the Fenix as I do not have this aircraft and so cannot look into this in detail. John

There was also a minor error in that lua script (an additional space before the lvar name), so please use the attached instead. John BellUH1Throttle.lua

Your ini file shows that the lua script I provided is not in your installation folder, as it does not appear in your [LuaFiles] section (do NOT add this manually!). Can you please make sure that the lua file is in your installation folder. Also, as you are using profiles, you should use the auto section for your profile. i.e. change [Auto] to [Auto..Bell UH1c]. You should also use substrings for your aircraft profile names, i.e. change to and to and to This will then load the profile when you are using different variants/liveries of the same aircraft. You also have quite a few invalid assignments that you should remove, especially in your [Buttons.Dodsim 206] section, e.g. these So please correct those issues, and make sure the lua file I provided is in your FSUIPC4 installation folder, and any issues please also attach your FSUIPC4.log file as well as the FSUIPC4.ini file. John