John Dowson

May 28

1 hour ago, GiankMustang said:

Now almost all Mustang.LUA commands work. Except AVIONICS and ENGINE-SYNC which I make work via Macro, and except the two STARTs which do not backlight when activated.

Did you follow the instructions in the la script when assigning to these?

1 hour ago, GiankMustang said:

I would like to be able to communicate directly with the programmer of Mustang.LUA, Mr. GC McMillen. Do you think you can give me his Email?

Maybe it is @Glen McMillen? Last time he posted was in 2007 so I don't know if he is still monitoring these forums - he should receive a message now I have tagged him and he may respond here. I cannot give out emails, sorry, but you could also try sending him a (personal/direct) message via these forums.

John

May 28

Clear your browser cache or try a different browser. There is nothing wring with the website as far as I can tell - looks fine in both Chrome and Edge.

May 27

33 minutes ago, bernard LORIDAN said:

I cannot connect to my account on the Flight Sim website to purchase an airport scene.

What has this got to do with FSUIPC?

This is the forums for the support of FSUIPC and related products ONLY. For any issues with the flight sim (simmarket?), you need to raise a ticket with them (https://secure.simmarket.com/customerservice.php).

John

May 27

14 hours ago, didja said:

I installed all of the most revent VC++ distributable files

You need to install the latest combined distributables, i.e. for 2015, 2017, 2019, and 2022, not necessarily the most recent. And please install both x86 and x64 versions.

14 hours ago, didja said:

When I start the installer and give permission for it to install, I get the Invalid OPCODE error. I am the only user on this computer and have full admin rights. I still cannot get the installer to work. I am hoping that you have another option/correction.

The only reason I know of for this error is due to the account being used being unable to be elevated to full admin rights, so please double check this.
Also make sure that
- you are not running the installer from within the zip file - it needs to be extracted first
- your windows environment variables are set-up correctly, especially APPDIR and TMPDIR
- you are not trying to install into a protected folder

John

May 26

On 5/24/2025 at 6:54 PM, GiankMustang said:

1- THROTTLE CUTOFF. To turn off an engine, I set the Throttle to CUTOFF, but the engine does NOT turn off, the rpm go to minimum in IDLE but do not go to zero, in fact FUELBOOST does not turn off on the CAS-MSG. To turn off the engine I should act on DISENGAGE, but it is a subterfuge because this only cuts the electrical power, while CUTOFF cuts the fuel.

You could try sending a THROTLLE_DECR once in Idle.

On 5/24/2025 at 6:54 PM, GiankMustang said:

2- STBY-AVIONICS and ENGINE-SYNC. I could not make them work in any way, so I programmed them with Mouse Macros.

Did you follow the instructions, e.g. you have to assign to the press AND release.

Quote

-- Emulate the Standby Avionics switch upper mouse area.
-- Using a SPDT Center off switch, Assign parameter = 0
-- to the upper switch position "pressed" and "released"

On 5/24/2025 at 6:54 PM, GiankMustang said:

Do you have a solution to these Problems again?

No - I do not have this aircraft and cannot look onto this.

John

May 26

I am not sure how to embed a pause/wait in a calculator code string and that sleep syntax is not familiar to me.
There are a couple of other ways you could do this:

1. Use lua instead, e.g.

ipc.execCalcCode("23 (>L:VC_Miscellaneous_trigger_VAL, number)")
ipc.sleep(100)
ipc.execCalcCode("25 (>L:VC_Miscellaneous_trigger_VAL, number)")

2.Define two separate presets:
IFLY_RWY_ONa#23 (>L:VC_Miscellaneous_trigger_VAL, number)
IFLY_RWY_ONb#25 (>L:VC_Miscellaneous_trigger_VAL, number)
and then create a macro to call the first one, then pause (using the FSUIPC-added pause control), then call the second preset.
You can also overload the assignments instead of using a macro if you prefer.

May 26

8 hours ago, mekong said:

As title suggest every time i try to log in it comes up with website blocked

login where? You can download FSUIPC from https://fsuipc.com/ - no login required.
If your antivirus software is blocking FSUIPCfrom being installed or ran, it will be a false-positive. You should add an exception to allow the installer (and FSUIPC) to run.

May 24

Pete retired over 6 years ago now.
And FSUIPC4 (for FSX, FSX-SE and P3Dv3) was closed for further development around 8-10 years ago. I am not prepared to do any further development on this version of FSUIPC, sorry.

I really cannot remember if or how FSX (or FSX aircraft) supports the 8.55KHz frequency spacing. But if it is supported, you just need to use the Hz offsets to read/write//update the frequency, and not the BCD-encoded ones. e.g. for active COM1, use 0x05C4 instead of 0x034E. But as far as I can remember, FSX only supports 25KHz spacing.

Maybe see:

and maybe:

On 5/23/2025 at 1:08 PM, NicHer said:

Is this something you would be interested in supporting ?

Basically no, as FSUIPC4 is no longer in development.

John

May 23

51 minutes ago, Airbuspilot said:

Thanks for the Answer. But this Post seems to be Hardware related.

No, its not hardware related. The problem is the same - the PMDG-specific offsets are not populated in MSFS2024 for the B77F as the string 'PMDG' does not appear in the aircraft title. The beta version in that post fixes this.
And you don't need to use profiles.

May 23

All the helicopter throttle axes are already available in FSUIPC. "Set Helicopter Throttle Axis" would be Axis Helicopter Throttle Set.
But I don't think this works in the Cowansim MD500 (but try it anyway).
This has been reported before for this aircraft - see

May 22

This could be due to the aircraft title received does not contain the string 'pmdg' and so the additional threads to populate the PMDG-specific offsets are not started.
This has been reported before and I have provided a beta version that also checks the folder name for the 'pmdg' string which should solve this issue. So first try the beta version posted here:

And if that is not working, show me / attach your FSUIPC7.log file generated when using the B77F.

John

May 22

If you have issues with presets not loading, please show me both your FSUIPC7.ini and FSUIPC7.log files, the latter with logging for Buttons & Keys activated and showing a button press assignment that is in the profile that should be loaded but is not working.

May 22

Just checked and there is an SU3 beta release available, but your log shows that you are using the latest official release which is SU2 - unless they have forgotten to update the version number in the SU3 beta release.

May 22

4 hours ago, Metall4You said:

I loaded msfs2024 su3

There is no SUU3, as far as I know, and your log file shows that you are using the latest release of MSFS2024, which is SU2:

Quote

119672 MSFS version = 12.2.282174.999

4 hours ago, Metall4You said:

my LUA scripts are no longer working.

But your log shows that the lua scripts were started:

Quote

307234 Lvars/Hvars received - checking aircraft autos....
307297 LUA.1: beginning "I:\FSUIPC7\ipcReady.lua"
307313 LUA.1: Lvar now available0
308531 Lvar not logged: 0
372281 **** Restarting traffic scanning due to non-reception ****

and also terminated:

Quote

734625 Lua threads being terminated:
734625 1 = "I:\FSUIPC7\ipcReady.lua"
734828 LUA: "I:\FSUIPC7\ipcReady.lua": killed
734828 2 = "I:\FSUIPC7\announcement.lua"
735016 LUA: "I:\FSUIPC7\announcement.lua": killed

I do not know if any other lua scriptys should have been started as you did not attach your FSUIPC7.ini file. Please show me that, together with your log file, if you think they are not being started.

4 hours ago, Metall4You said:

I suspect the WASM module is no longer loading.

But your log file shows the WASM module is working just fine - you even listed the available lvars.

So I do not undertand what your issue is. Why do you think the lua scripts are not being started?

John

May 21

First, to understand profiles you should read the section User profiles for all control settings, on page 22 of the FSUIPC7 User manual/guide. Profiles are enabled automatically.
Having profiles in separate files is generally only used if you have many profiles and these are quite large, as it separates them into different files. You do not have to use this feature when using profiles if you don't want to, but if you have already switched to profiles-in-separate files then thats ok.

8 minutes ago, niki21 said:

I opened the folder and there is no file in it. The folder is empty even when I started the simulator and closed it. I made several changes to the profile. I set up various switches on the throttle that work fine in Flight Simulator, but I don't know how the profile is saved. In the FSUIPC software itself, there is no place related to profiles or how to save or how to upload a saved profile.

The changes you made will only be saved in the profile (and in the profile-specific file) if you clicked the profile-specific checkbox (in the assignments panel) when adding the assignment, and when you have added the currently loaded aircraft to a profile (or have created a new profile for the aircraft). Check your FSUIPC7.ini - they will have been added there to the general sections if you did not specify profile-specific.

Note that when you create a new profile for an aircraft, or add an aircraft to an existing profile, it is a good idea to shorten the aircraft name (listed under the [Profile.xxx] section of your FSUIPC7.ini file) to a substring that matches all variants of that aircraft. This will prevent issues with the profile not being loaded when you use a new variant. Alternatively, you can set the UseAirLocForProfiles in parameter to Yes to perform matching on the aircraft folder name instead, but if you want to use this then do it now before adding the aircraft name/title to the profile. Again, see that section in the User manual for more details.

John

May 21

@Claude Decarie I have just seen this post in Paul's .Net dll support forum and have moved it to the main support forum (for FSUIPC4/5/6).

Did you manage to successfully create a profile for the C172? It should be straightforward - you just need to create a specific profile for the C172, allow the current axes assignments to be imported and then modify these axis assignments in the profile for throttle, brakes and rudder to use the controls used by the C172. You can then also re-map any buttons/switches you need by making these profile-specific. Please see the section on using profiles in the FSUIPC User guide.

If you have any issues or problems, please show me / attach your current FSUIPC6.ini and FSUIPC6.log file (generated when using the C172) and I can take a look.

John

May 21

On 5/16/2025 at 9:12 PM, jdriskell said:

So I fell back to the 2020 keyboard layout in the controls section.

Ah yes, thats a good idea - I hadn't notice that you could do this. I have now also changed this, for both the general controls (to 'Keyboard 2020 Transversal' and the Airplanes controls (to 'Keyboard 2020 Planes') and this works well for my assignments.

On 5/16/2025 at 9:12 PM, jdriskell said:

Everything works the way I had set it up in MSFS2020 except for various instrument views where I'm using ctl+shift+ what ever number I need.

Once changing to use the 2020 keyboard assignments, the ctl+shift+n combination should again be mapped to switch to the fixed camera views. In MSFS2020, these fixed camera views seem to be the same as the instrument views, via the ctrl+n keyboard assignment. And these seem to be the same in MSFS2024 (when using the MSFS2020 keyboard mapping), so I don't understand why these are not working for you in MSFS2024.

May 20

Did you manage to find anything for this?

Just noticed this post on the MF discord server:

Quote

I can't find how to control Black Square Duke's variables for the following:

Fuel pumps (L and R)

Starters / Gen L and R

Igniotion Auto / On L and R

Condition levers - somehow normal usage mapping joystick axes doesn't work for me...

with response:

Quote

Fuel Pumps - L:var_FuelPumpSwitchL / L:var_FuelPumpSwitchR / Values 0/1/2

Starters - L:var_StarterGenSwitchL / L:var_StarterGenSwitchR / Values 0/1/2

Ignition - L:var_IgnitionSwitchL / L:var_IgnitionSwitchR / Values 0/1/2

Condition Lever - L:BKSQ_ConditionLever_1 / L:BKSQ_ConditionLever_1 / Values 0/1

But that is for the MSFS2020 version. If those lvars exist in MSFS2024, you could try them.
Also, check the aircrafts documentation - look at the section Primary Control Variables which seems to list all the lvars available, e.g.:

Quote

Left Ignition Switch L:var_IgnitionSwitch_L 0 = ON, 2 = AUTO

Right Ignition Switch L:var_IgnitionSwitch_R 0 = ON, 2 = AUTO

Left Starter-Generator Switch L:var_StarterGenSwitch_L 0 = GEN, 2 = START

Right Starter-Generator Switch L:var_StarterGenSwitch_R 0 = GEN, 2 = START

Left Fuel Pump Switch L:var_FuelPumpSwitch_L 0 = WING, 2= AUX

Right Fuel Pump Switch L:var_FuelPumpSwitch_R 0 = WING,

John

May 20

45 minutes ago, didi1 said:

Good news first, Today it seems to work, I mean the GPSout with MSFS2024.

Ok, but what changed?

45 minutes ago, didi1 said:

Sorry but it is not possible to load only 20 Kb screenshots.

Your upload limit will increase as you post more - it is set very low for new users. However, be aware that there is no check-box next to the AutoSave and GPSOut options - these menu entries should open a separate panel (indicated by the ellipsis (three dots/full-stops, - ...) after the menu item name. Do you not see those panels that configure GPSOut and AutoSave?
See the User guide for a full description.

May 20

On 5/18/2025 at 6:12 AM, mac8892fs said:

Thank you. Yes, as you said, it is automatically assigned to the 6th position. Therefore, it is assigned to the axis and is working correctly.
I also reset this 6th value to the standard value.

Ok, so you can see the values change in the elevator trim calibration panel? That is interesting, but I wonder what, if any, macro it is using. I would expect it to use PitchTrim, but I can only see PitchTrimMust logged, and only once. I am not sure what that macro should be doing (if provided), so I don't really understand how itis controlling the pitch/elevator trim.
Maybe setting LogIPCwrites to Yes in the PFC ini would help.

On 5/18/2025 at 6:12 AM, mac8892fs said:

The value fluctuates by 128.
This is logged by 128, so the operation seems to be correct.
However, the speed is fast. I felt that it was beyond the range of FSUIPC adjustment.

128 would be the delta adjustment, i.e. it won't move for smaller adjustments. Changing this won't affect the speed of the trim adjustments, just the steps/deltas (i.e. the size of the increment/decrement.

On 5/18/2025 at 6:12 AM, mac8892fs said:

Below are the values.

AXIS: Cntrl= 65706 (0x000100aa), Param= 5819 (0x000016bb) ELEVATOR_TRIM_SET

Throttle1=-16380,-256,256,16380/32

But that is the throttle calibration. not the elevator trim calibration.

If the elevator trim is being calibrated, one way of slowing down the trim movement is to extend the upper range. So, if this is my elevator trim calibration:
ElevatorTrim=-16383,0,0,16254/16
I would extend the upper range by increasing the upper threshold, e.g
ElevatorTrim=-16383,0,0,20254/16

(or extend in both directions, and maybe add a null-zone for zero trim, i.e.
ElevatorTrim=-20383,-512,512,20254/16

)
However, the problem with doing this is that you would lose the full range, and it won't be possible to get to full trim (as you axis would need to send a value of 20254 to do this in the example above).

Does the TrimRange setting have much affect? I see this is now set very high (1023), whereas before you had it set very low (16).

May 20

I cannot see how this can happen as its the same version of FSUIPC for both MSFS2020 and MSFS2024.
Are you using the same installation for MSFS2020 and MSFS2024, or separate installations?
If you are using the same installation, then the same GPSOut settings will be used for each version. i.e. it it is enabled for MSFS2020, it will be enabled in MSFS2024.
The autosave sections are distinct for MSFS2020 and MSFS2024, so you can have different settings in each simulator, with the MSFS2020 settings saved under [AutoSave], and the MSFS2024 settings saved under [AutoSave24]. Do you have an [AutoSave24] section the FSUIPC7.ini file used for MSFS2024?
Note that FSUIPC7 must be connected to MSFS so that it knows the version being used before the AutoSave settings can be adjusted.

I do not understand why you cannot tick the options though. What do you mean by " no hock shown in front of these Options"? Do you mean no check-box? Could you show me a screenshot of this please, and also include/attach your FSUIPC7.ini and FSUIPC7.log files.

May 20

On 5/18/2025 at 2:41 PM, Jock in a Frock said:

As per thread title, I had to re-install MSFS 2024 (Xbox Store version), so I uninstalled and re-installed FSUIPC 7.5.3 (licensed). However FSUIPC won't auto start.

Your installation log indicates that an steam version of MSFS2024 was detected:

Quote

MSFS2020 MS Store version detected
MSFS2024 Steam version detected

The installer would have therefore created the EXE.xml in the location used by Steam, not the MS Store version. It will probably also have installed the WASM in the wrong Community folder.

To resolve this, you should remove (or rename) the steam UserCfg.opt file (which determines a steam install) from the following location::
C:\Users\Andy\AppData\Roaming\Microsoft Flight Simulator 2024\UserCfg.opt

Then re-install and your MS Store version of MSFS2024 should be detected and the EXE.xml created in the correct place.

John

May 16

1 hour ago, kaha said:

Somehow my Community content got disabled.

I didn't know that could be disabled...! Can you re-enable it and test again then?

May 16

In steam, you can verify the integrity of the game files of the MSFS2024 installation. Can you do this with the MS Store version? If so, try that.

May 16

Sorry but I have no idea why MSFS2024 is not starting the WASM. Are all your other WASMS being loaded? Did you reboot?
Try temporarily moving everything out of your MSFS2024 Community folder except for the FSUIPC WASM module - does it then load/start?
You can try reporting this on the Asobo forums as there is nothing I can do or advise if MSFS2024 is not starting the WASM.

Left Ignition Switch	L:var_IgnitionSwitch_L	0 = ON, 2 = AUTO
Right Ignition Switch	L:var_IgnitionSwitch_R	0 = ON, 2 = AUTO

Left Starter-Generator Switch	L:var_StarterGenSwitch_L	0 = GEN, 2 = START
Right Starter-Generator Switch	L:var_StarterGenSwitch_R	0 = GEN, 2 = START
Left Fuel Pump Switch	L:var_FuelPumpSwitch_L	0 = WING, 2= AUX
Right Fuel Pump Switch	L:var_FuelPumpSwitch_R	0 = WING,

Profiles

Forums

Events

Gallery

Downloads

Posts posted by John Dowson

Important Information