John Dowson

March 1

This issue is continually getting reported, and my answer is always the same. Please see one of the other many posts on exactly the same issue:

...etc

Basically read the documentation and follow the advise there, and also check out the many posts on exactly the same issue.

March 1

6 hours ago, Braudoux said:

While checking the FSUIPC6.ini file, I noticed that there are twice the same reference and I suspect that it is the origin of the problem. Could you confirm?

[JoyNames]
AutoAssignLetters=Yes
A=Saitek Pro Flight X-55 Rhino Throttle
A.GUID={E94396F0-E721-11EB-8004-444553540000}
E=Saitek Pro Flight X-55 Rhino Stick
E.GUID={E942D3A0-E721-11EB-8002-444553540000}
B=MIAP STD
B.GUID={4981D2D0-E40F-11EC-8001-444553540000}
C=MIAP STD
C.GUID={E942D3A0-E721-11EB-8002-444553540000}
D=Saitek Pro Flight X-55 Rhino Stick
D.GUID={E9436FE0-E721-11EB-8003-444553540000}

So it looks like the GUIDs have changed, not only for that device but also for your Saitek Pro Flight X-55 Rhino Stick, which now has two device letters D and E.

If the GUID if your MIAP STD is now that in the C entry, but your assignments are referencing B, then switch the GUIDs and remove the C entry, ie.

Quote

JoyNames]
AutoAssignLetters=Yes
A=Saitek Pro Flight X-55 Rhino Throttle
A.GUID={E94396F0-E721-11EB-8004-444553540000}
E=Saitek Pro Flight X-55 Rhino Stick
E.GUID={E942D3A0-E721-11EB-8002-444553540000}
B=MIAP STD
B.GUID={E942D3A0-E721-11EB-8002-444553540000}
D=Saitek Pro Flight X-55 Rhino Stick
D.GUID={E9436FE0-E721-11EB-8003-444553540000}

You should also do similar for your Saitek Pro Flight X-55 Rhino Stick.

Also, please attach the full ini file next time rather than posting extracts, and also attach your FSUIPC7.log file for any further issues.

John

February 28

1 hour ago, Alhard Horstmann said:

Q: what is Offset $5428 ??

From the FSUIPC7 Offset status document - 3584 bytes starting at offset 0x5200:

Quote

Reserved:
  5200-527F = Ferry van Aesch (Asst CEO British Airways Virtual)
  5280- 52FF: Andrew McLean: Aerosoft Hardware
  5300-53FF: Mark Hastings B777 Systems Simulator
  5400-5FFF: Enrico's Project Magenta

i.e. Offset 0x5428 is in an offset area that has been allocated to Project Magenta, and you need to look at the PM documentation or ask them what that offset is used for.

John

February 28

1 hour ago, eziocin said:

I run Widefs Client on the networked laptop, but it hangs with the message "Waiting for a connection".

It is not actually hanging is it, its just waiting for a connection, no? Does it connect automatically when you restart FSUIPC, or do you have to also restart the WideClient?

Can you please show me / attach your FSUIPC7.log and WideServer.log files, both from when it initially fails to connect (and after you have exited FSUIPC7) and also from after when you restart it and it connects.

February 28

You should sort out the disconnection issues shown on your log.

On 2/27/2025 at 9:37 PM, intper said:

all i want is a previous version if its possible, i just want to compare it with new version

There are no changes from any version that cause performance issues - your problem lies elsewhere.
You can try an older version if you like (not that this will help!) - current/latest version is:
https://fsuipc.com/download/Install_FSUIPC7.5.2.zip
previous version:
https://fsuipc.com/download/Install_FSUIPC7.5.1.zip

older versions:
  https://fsuipc.com/download/Install_FSUIPC7.5.0.zip
  https://fsuipc.com/download/Install_FSUIPC7.4.17.zip
  https://fsuipc.com/download/Install_FSUIPC7.4.15.zip

etc.

February 28

It doesn't make sense to allow this in FSUIPC due to the way calibration works in FSUIPC. FSUIPC calibrates to an FS control, and as there is no specific control/event when assigning to a preset, it does not know the range to calibrate to. Max/min/scaling etc can easily be handled, either in the RPN itself. or you can just write the axis value to an offset and do whatever you want with it before using it in a preset.

February 27

20 hours ago, intper said:

this one with fsuipc connected to sim; https://paste.pics/SVWS1
and this one without fsuipc connection to sim; https://paste.pics/SVWSA

All I can see in those images is that one has an FPS of 127 and the other of 110. Isn't an FPS of 110 enough?

The log file you attached is very strange, as it just shows FSUIPC connecting and disconnecting, It makes no sense to me, and you have not provided any context.
What actually happened? What/why is FSUIPC closing shortly after being started:

Quote

...
266469 -------------------- Starting everything now ----------------------
316391 === Calling SimConnect_Close ...
...
393782 -------------------- Starting everything now ----------------------
393782 Additional 361 InputEvents received - now have 900
443891 === Calling SimConnect_Close ...
...
478766 -------------------- Starting everything now ----------------------
478782 Additional 361 InputEvents received - now have 900
489360 === Calling SimConnect_Close ...
...
498766 Requesting Input Events....
498766 -------------------- Starting everything now ----------------------
498782 Additional 361 InputEvents received - now have 900
504875 === Calling SimConnect_Close ...
...

?

February 27

The log file you attached was attached when FSUIPC was still running and also stops after 30 seconds.

You are also using an old an unsupported version of FSUIPC. Only the latest version is supported - please update.

And your ini file shows that you are not actually using FSUIPC for anything. You only have one (strange) button assignment, you have profiles but they are empty, and you [MacroFiles] section is very weird...

Are you assigning in MobiFlight? i cannot support mobiflight - please use their support channels (discord) for issues with MF.

February 27

On 2/27/2025 at 8:40 AM, Christikitty said:

The issue I'm having is when I select VHF1-3 the led annunciator turns off, instead of on. Is there anyway to reverse the output action or flip the action of the LED to reflect what the sim is doing?

How have you assigned?
There can be toggle controls, set controls that take a parameter (on/off) and separate on/off controls. So it depends on how you have assigned. You can also use offset conditions to check the state of a button before changing it, if require.

Please show me / attach your ini file so that I can see your assignments.

February 27

20 hours ago, pilotjohn said:

It would be great if I could send FSUIPC calibrated values somehow. What would be the best way to do that?

You cannot calibrate when assigning to presets - this just doesn't make sense to allow this.

20 hours ago, pilotjohn said:

Is there someway to assign an axes to calibration, then use those values to send to a preset?

No - it doesn't make any sense to allow this. There is no way that FSUIPC can calibrate values needed for a preset.

20 hours ago, pilotjohn said:

Any chance of adding "extra"/arbitrary joystick calibration sections that could be then sent to a preset?

No. Just use scaling.

February 26

Is there a simvar or lvar that holds the current state of this button? If so, log that...
And also please at least activate logging for Events, and attach your log file here (as well as your ini) and I can take a look.

Just defining a macro cannot affect the aircraft state on start-up. Something must be triggering this.

February 26

25 minutes ago, pilotjohn said:
AILERON_TRIM_PCT and RUDDER_TRIM_PCT are listed as Lvars, and the calculator above works on them. ELEVATOR_TRIM_PCT is not listed as an Lvar which is why obviously it's not doing anything.
2067531   [INFO]:     ID=1165 RUDDER_TRIM_PCT = 50.000000
2067531   [INFO]:     ID=1169 AILERON_TRIM_PCT = 0.000000
  

So its NOT an lvar. And it is not 'doing anything' as it doesn't exist. Juat because an lvar exists for the rudder trim and aileron trim, doesn't necessarily mean that one will exist for elevator trim. And if you list the lvars and its not there, it doesn't exist.

If you are thinking that it should exists as there are similar ones for rudder and aileron trim, then you are mistaken and are wasting both your and my time on this.
Use the facilities provided to determine what is available, don't guess.

February 26

Please:
- turn off WAPI trace logging. Debug level logging is sufficient
- also activate logging for Axes Controls and Extras
- please also attach both your FSUIPC7.ini and myevents.txt files as well as a new FSUIPC7.log
- please don't attach images unless requested. It is the files I need to see.

February 26

1 hour ago, pilotjohn said:

I mean that the aircraft defined it,

Almost all lvars are defined by the aircraft...

1 hour ago, pilotjohn said:

it's not the one listed int the SDK or offsets.

Well, there are no lvars added to offsets by default. And as I have said many times now, listing the lvars in FSUIPC will list ALL lvars available fromthe last scan. You can even reload and list lvars, which will list ALL lvars defined and available. If that lvar isn't there' it is NOT an lvar, 'custom' (which means nothing) or otherwise.

I don't understand why you think that is an lvar - why do you think that? How can you see it? How can you read/set/change it then?

February 26

1 minute ago, GiankMustang said:

So I deduce that it is the FSUIPC-MobiFlight Macro that forces them On, and not a Default setting of the Plane.

But the macro does nothing unless you run it. So, if something is running the macro when you start FSUIPC or MobiFlight, then stop/disable that.
A macro file does nothing by itself - something needs to trigger it to be ran. You can use FSUIPC's logging facilities to determine what,

February 26

12 hours ago, pilotjohn said:

Maybe L:AILERON_TRIM_PCT is custom (defined by) the aircraft in questions,

Almost all lvars are defined by the aircraf...
I still have no idea what you mean when you say 'custom'.

As I said, if FSUIPC does not list it, it is NOT an lvar

February 26

12 hours ago, pilotjohn said:

5. However, for one preset, I'm receiving a range of -1024 to 1024 (even though FSUIPC is showing -16384 to 16384) and so I have to scale accordingly

I don't see how this can be the case.

12 hours ago, pilotjohn said:

So where is the scaling from -16k..16k -> -1k..1k happening? Is there a setting somewhere I'm missing?

There is no such scaling. If assigning an axis to a preset, the axis value Out value should be used as the parameter, which should also match the In value.
WAPI Debug level logging should show the values being used.

February 26

13 hours ago, FPVSteve said:

In that case it appears to not be working (for me) as when I close MSFS 2020/2024, FSUIPC continues to run in the system tray.

We seem to be going in circles here....I know that it isn't closing, and I need to see your file if you want my help looking into why...

John

February 25

25 minutes ago, Scotfleiger said:

This has an adverse effect on SpadNext forcing it to lose connection with a Stream Deck XR device.

I am sorry but I don't understand this - how can running FSUIPC7 force spad.next to lose a connection?

27 minutes ago, Scotfleiger said:

is there a sure way of making sure FSUIPC7 is not interacting with MSFS2020

Yes - by not connecting FSUIPC7 to MSFS. Once it is connected, it is interacting...

28 minutes ago, Scotfleiger said:

making sure FSUIPC7 is not interacting with MSFS2020 or any devices

FSUIPC does not do anything with any devices/controllers unless you tell it to. Unregistered versions do not even scan for devices.

February 25

3 hours ago, GiankMustang said:

when I start the Sim I find the STBY INSTRs always On, whether the Switch is Off or On.

Then that must be the default value that it has when started. All aircraft switched/buttons/knobs will be in a pre-defined state on start-up, and this may not match the state/positions of your buttons/switches. The state of your physical buttons/switches are not read at start-up and the aircraft but in the same state - you have to start the aircraft with your buttons/switches in the correct position to match the state of the aircraft when started.

You may be able to change the default state somehow but I don't know about this - you would have to ask on the aircraft support forums. Otherwise, you could just send the command to turn standby off when you start, for example by just running that macro, e.g.

[Auto]
1=1SK CLOCHE:StbyInstrum

February 25

37 minutes ago, pilotjohn said:

For these, I generally (now) declare a preset in my events.txt and do the needful scaling to make it work.

However, I'm confused as to what ranges are to be expected from FSUIPC, despite the ranges shown in FSUIPC axes window as -16384 to 16384.

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.

49 minutes ago, pilotjohn said:

However, the FFX HA420 throttle range the RPN preset receives from FSUIPC appears to be -1024 to 1024 (or 1023, whatever).

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.

1 hour ago, pilotjohn said:

Given that FSUIPC has now idea whether I'll be doing throttle, rudder or what the axis is used for, why are these ranges different?

Because different hardware/drivers use different ranges for axes.

February 25

41 minutes ago, pilotjohn said:

So maybe it's custom.

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

February 25

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

February 25

8 minutes ago, FPVSteve said:

I don't seem to have an "Exit with FS" option (or at least I can't find one):

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

February 25

12 hours ago, FPVSteve said:

Well I presume it isn't closing when the simulator closes - perhaps it's not detecting that the simulator is no longer running?

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.

Profiles

Forums

Events

Gallery

Downloads

Posts posted by John Dowson

Important Information