John Dowson

2025-11-08T12:20:05Z

These forums will soon be closing, and are already closed for new topics. Please see the following announcement:

John / FSUIPC

2025-11-08T12:18:37Z

These forums will soon be closing, and are already closed for new topics. Please see the following announcement:

John / FSUIPC

Thursday at 03:35 PM

1 hour ago, Shand359 said:

i was copying the key from the Simmarket app which as it turns out misses the last 4 characters of the Key....

This depends on how you select the key to copy it. If you just double-click it, it may not select the entire key due to the mix of letters and numbers. It is up to you to make sure that you are copying the entire key string - I am not going to provide details on how to copy and paste correctly...! However, I will add a comment to make sure that the entire 12 characters of the key are copied/pasted.

Anyway, glad its working and thanks for responding with what your issue actually was.

Regards,

John

Tuesday at 05:59 PM

Just now, Tim7378 said:

is there any way to see my password and key for FSUIPC?

There is no 'password' - your FSUIPC7 license contains 3 parts: name, email/address & key.
If you have already registered your license, the details will be in your FSUIPC7.key file.

Otherwise, the license details can be retrieved from:
1. the purchase email you received from SimMarket
2. Your SimMarket account

If you have issues accessing your SimMarket account, you need to resolve this with SimMarket, not here. I am just a vendor on SimMarket and cannot assist with SimMarket issues.

John

Tuesday at 12:22 PM

13 hours ago, Realpilotnow said:

As long as FSUIPC is launched in the EXE.xml file, I get NO cyclic regardless of what I do. Remove FSUIPC from EXE.xml, and my cyclic works fine.

I don't think this can be due to the fact that FSUIPC7 is auto-started via the EXE.xml. Don't you get the same issue when FSUIPC7 is started manually?

What I suspect is happening is that FSUIPC (post) calibration is affecting the controls. If you have a general calibration section, this will apply by default even when the axis is assigned in MSFS or elsewhere.

You can do one of two things:

1. Create a profile-specific calibration section for the CowanSim and remove/reset all calibration controls - you should do this even if you are not currently using a profile for this aircraft.
To do this, just click the 'Profile Specific' checkbox in the calibration tab of the axis assignment panel. Then on each calibration page where the button says 'Reset' (as opposed to 'Set'), click that.

2. You can disable all post-calibration (i.e. to not calibrate at all unless an axis is assigned in FSUIPC using 'send direct to FSUIPC calibration') by setting
AllowSendToFSCalibration=No
in the [General] section of your FSUIPC7.ini file.
Note that setting this will affect all axes assignments not assigned in FSUIPC with 'send direct to FSUIPC calibration'.

13 hours ago, Realpilotnow said:

IF a solution is found, I'll try to remember to post here.

Please do!

John

Monday at 03:45 PM

1 minute ago, Ferran-Gonzalez said:

this is the log file

You did not activate the requested logging option for IPC Reads.

However, your log file does show some connection issues:

Quote

719 Auto-started via EXE.xml with DetectToConnectDelayAuto=50, InitialStallTime=15
3656 Simulator detected
53656 Trying to connect...
68656 **** SimConnect open event not received in required time limit: Re-connecting now...
68875 Trying to connect...
83875 **** SimConnect open event not received in required time limit: Re-connecting now...
84078 Trying to connect...
407125 === AI slots deleted!
410500 Trying to connect...

It also looks like you disconnected and reconnect before FSUIPC had established a connection with MSFS2020...I didn't think this was even possible! And I do not understand why the connection attempt at 84078 didn't time out after 15 seconds.

For this connection issue, you need to increase the DetectToConnectDelayAuto ini parameter (in your FSUIPC7.ini file). I am not sure wht value you should use - you need to time the period between when you see the FSUIPC7 splash screen to when MSFS2020 arrives at the main menu, and then set the value for that ini parameter to this. Please see the following FAQ entry on this connection issue:

Note that this parameter will also be used when running MSFS2024 if you are using the same FSUIPC7 installation for both simulators.

Once you have configured this parameter correctly (and for use with both MSFS2020 and MSFS2024 if using the same FSUIPC7 installation for both), you should set the ini parameter StartUpTuningDoneVersion to -1, which will disable the auto-tuning of this parameter by FSUIPC7 itself.

John

Monday at 12:50 PM

18 hours ago, jwilson0514 said:

Latest windows updates with redistributable installed.

But which redistributables? As it says in the documentation, you need to install the latest combined (i.e. for 2015-2022) redistibutables for both x86 and x64. Did you install these? If so, please let me know your order number and I will check your details here. Do not post your key details.

Please note that EVERY report I get on this is down to user error, usually either by not entering the correct details (all 3 parts, name, email/address, key) must match exactly, or due to not having the required redistribtable packages installed.

You can also try manually creating your key file (as shown in the Installing and Registering FSUIPC document) and then running FSUIPC7 to see if the license is recognised. If it is recognised by FSUIPC7 but not validated by the installer, it will be due to either your VC++ redistributables or anti-virus software.

John

Monday at 08:54 AM

13 hours ago, Ferran-Gonzalez said:

In my case, even though FSUIPC is open and connected to the simulator, addons such as Talking Flight Monitor or Flight Simulator First Officer do not detect it.

Can you activate logging for IPC Reads and show me a log file for this. Start everything as normal, and when the client programs cannot connect, disconnect and re-connect so that they connect, then exit FSUIPC7 and show me / attach your FSUIPC7.log file.

John

November 2

On 11/1/2025 at 9:23 AM, Ripperman said:

I am deeply interested in FSUIPC, would it be possible to update the trial key as we allready have Nov 1st. please? 😉

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

November 2

15 hours ago, Reco said:

That's helped but the collective in the cockpit is increasing but not decreasing when rolling back collective.

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

November 1

10 minutes ago, Aq86 said:

I must’ve missed it in my .ini file.

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

November 1

1 hour ago, Aq86 said:

I couldn’t find a [JoystickCalibration.FENIX A320] specifically in my FSUIPC.ini, instead I only found a [JoystickCalibration] section, t

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

November 1

1 hour ago, Ripperman said:

would it be possible to update the trial key as we allready have Nov 1st. please? 😉

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

November 1

6 hours ago, jsmarko3 said:

Here is a screenshot of the console since it won't let me copy the text:

You can attach your FSUIPC7.log file, or copy the relevant text from there.

6 hours ago, jsmarko3 said:

[InputEventOffsets]
0=BKSQ_MAGNETOCONTROLLER=F0xA0000

And here is the resulting button binding after trying to use the Float64 Offset Inc/1000

2=PA,7,Cx7C00A000,x00000001 -{offset float64 inc/1000, offset A000 (0.001000)}-

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

October 31

1 hour ago, jsmarko3 said:

I could write something right now to set it to a specific value, and I may do that myself in a few days when my button box and key switch arrive, but for an increase/decrease function I would need to get smart on scripting to check what it is set to and where it should go.

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.

1 hour ago, jsmarko3 said:

I have asked Nick on the Just Flight forums if he has any insight as to why the magneto K event would not work

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

1 hour ago, jsmarko3 said:

I will likely put some thought and man-hours into trying to log it as you suggest; someone in a different topic on the JF forums mentioned he used some in-game developer tools to see what variables are changing, so I have a few options to go down that rabbit hole.

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.

1 hour ago, jsmarko3 said:

B events are something I never touched, but I see there are few listed in various Black Square manuals as variables you can manipulate, so I may end up needing or wanting to learn them down the road.

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.

1 hour ago, jsmarko3 said:

EDIT: and as always, thanks for the help.

No problem!

Cheers,

John

October 31

4 minutes ago, jsmarko3 said:

For the Black Square Bonanza Pro specifically, no, but in the events.txt file I did find one for just MagnetoIncrease#(>K:MAGNETO1_INCR) or named similarly,

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

October 31

13 minutes ago, jsmarko3 said:

Since it works via the Asobo bindings I'm very surprised it doesn't work via the FS Controls (I remove any conflicting bindings between tests).

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.

17 minutes ago, jsmarko3 said:

I cannot get Magneto1_Incr or Magneto1_Decr to work, at least in the new Black Square Bonanza Pro

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.

20 minutes ago, jsmarko3 said:

Semi-related: what language or formatting are events written in? I am familiar with the RPN portion for at least math, but my eyes very quickly glaze over when I get to some of the examples with various if statements or even simple things like one that had "near" before the min and max. I assume that's some sort of rounding function, but any pointers to what language or style, or some documentation there of would be appreciated.

See the MSFS documentation: https://docs.flightsimulator.com/msfs2024/html/6_Programming_APIs/Reverse_Polish_Notation.htm

John

October 31

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?).

October 31

4 hours ago, Reco said:

How do I reverse the axis, the throttle in the cockpit is opposite to my hardware throttle

Just change the calibration - change

Quote

-- Calibrate value from range -16384 - +16384 to 0-100
-- NB if the lvar range is fifferent, change this, e.g. if the range is 0-1, use
-- newValue = (value + 16384) / 32768
newValue = (value + 16384) / 327.68
ipc.log("Throttle axis value is " .. value .. " resulting in lvar value " .. newValue)

to

Quote

-- Calibrate value from range -16384 - +16384 to 0-100
-- NB if the lvar range is fifferent, change this, e.g. if the range is 0-1, use
-- newValue = (value + 16384) / 32768
newValue = (16384 - value) / 327.68
-- ipc.log("Throttle axis value is " .. value .. " resulting in lvar value " .. newValue)

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

October 30

Just now, Shand359 said:

I will need to contact Simmarket for a resolution.

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

October 30

1 hour ago, Aq86 said:

This workaround wouldn’t have been an issue except that now it won’t allow me to make hard 90 degree turns for some strange reason.

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.

41 minutes ago, Aq86 said:

I managed to resolve the issue for me at least. This is what I did:

- Open up FSUIPC.ini

- Go to the [JoystickCalibration] section

- Delete both "Steering Tiller" sections

Now unassign your tiller axis in FSUIPC, and just have it configured in regular MSFS controls.

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

October 30

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

October 30

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

Quote

[Profile.Bell UH1c]
1=Bell UH-1C Huey N204BH

to

Quote

[Profile.Bell UH1c]
1=Bell UH-1C

and

Quote

[Profile.MD530f]
1=Milviz MD 530 N23FF
2=Milviz MD 530 NWHC

to

Quote

[Profile.MD530f]
1=Milviz MD 530

and

Quote

[Profile.Dodsim 206]
1=DodoSim 206 Utility
2=DodoSim 206 High Skid

to

Quote

[Profile.Dodsim 206]
1=DodoSim 206

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

Quote

0=P0,11,C32981,0    -{}-
1=U0,11,C32981,0    -{}-
4=P0,3,C32887,0    -{}-
5=U0,3,C32887,0    -{}-
6=P0,13,C32883,0    -{}-
7=U0,13,C32883,0    -{}-
8=P0,18,C32773,0    -{}-
9=U0,18,C32773,0    -{}-
10=P0,6,C32864,0    -{}-
11=U0,6,C32864,0    -{}-
12=P0,10,C32879,0    -{}-
13=U0,10,C32879,0    -{}-
14=P0,7,C32868,0    -{}-
15=U0,7,C32868,0    -{}-
16=P0,8,C32881,0    -{}-
17=U0,8,C32881,0    -{}-
18=P0,9,C32979,0    -{}-
19=U0,9,C32979,0    -{}-
20=R0,16,C32997,0    -{}-
21=U0,16,C32997,0    -{}-
24=P0,20,C32794,1    -{}-
26=U0,20,C32794,0    -{}-

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

October 29

9 hours ago, Reco said:

I can transfer the zip file I have for you to look at at your convenience

You can send it to me, but can you at least try and report back your issues first...

9 hours ago, Reco said:

Sorry struggling on this ,adding a Macro is about my limit of knowledge when it comes to programming.

What issues are you having?
Here are more detailed instructions - please try these and report back any issues, and include/attach your .log and .ini files:

1. Assign your axis using Send to FSUIPC Offset, using Offset Dword Set and offset x66D0

2. Save the attached lua script to your FSUIPC4 installation folder: BellUH1Throttle.lua
Take a look at that script to see how it works - you may need to change the calibration.

3. Set the script to be auto-ran. To do this, add the following [Auto] section (or update this section if you already have one) to your FSUIPC ini file - note if using profiles you should use [Auto.xxx] (where xxx is you profile name) instead:

[Auto]
1=Lua BellUH1Throttle

Do this when FSX/FSUIPC4 is nor running.

Try that and report back, attaching relevant files if you have issues.

John

October 28

Your install log looks fine - no errors or issues.

There is one thing that could be causing these issues - you are running FSUIPC7 with elevated privileges from the log file you attached earlier:

Quote

********* FSUIPC7, Version 7.5.4 (13th July 2025) by John Dowson *********
WebSocket server found: C:\FSUIPC7\\Utils\FSUIPCWebSocketServer.exe
Windows 11 detected - setting DisableMSFSMonitor to 'Enum'
Windows 10 Pro 64 Bit reported as Build 26100, Release ID: 2009 (OS 10.0)
FSUIPC is running with elevated privileges
Reading options from "C:\FSUIPC7\FSUIPC7.ini"
...

Why are you running with elevated privileges? If you run FSUIPC7 with elevated privileges, then you must also run your java program (and all FSUIPC client programs) at the same privilege level, otherwise it won't connect. Are you dong this?

And are you also running MSFS with elevated privileges, and if so, why?

If MSFS is not running with elevated privileges, then it won't be able to auto-start FSUIPC7 if that is set to run with elevated privileges.

If you have set the FSUIPC7.exe to be ran with elevated privileges, remove this.

If you ran the FSUIPC7 installer as admin (i.e. with elevated privileges), then uninstall, and then re-install as a standard user. The installer will request the privileges it needs which you need to approve, but it should not be ran as admin.

John

Profiles

Forums

Events

Gallery

Downloads

Posts posted by John Dowson

Important Information