John Dowson

July 7

5 minutes ago, DaveSCUSA said:

Your control list (and it also showes in SPAD.neXt) for this includes "glider?". These events are to control the aircraft tractor.

From the controls list document:

66498 KEY_TUG_HEADING
66499 KEY_TUG_SPEED
66533 TUG_DISABLE

?

Report · July 7

👍😎

Report · July 7

1 minute ago, Arty77 said:

Sorry; last question: where i find Rotor Brake control for use this parameters?

What do you mean? The Rotor Brake control is a standard FS control/event. You would assign it as any other FS control, i.e. from the control drop-down box (when Select for FS Control is checked).

Report · July 7

2 minutes ago, Arty77 said:

But from the list that scrolls at lightning speed

Those are events that are continually sent. You should ignore those by setting the DontLogThese ini parameter so that such events are not logged.

5 minutes ago, Arty77 said:

If I click the APU Master button with the mouse, it records: Control 66587-0x0001041b Param 72516 - 0x00011b44 (if I turn on, 66587 - 0x0001041b - 72518 -0x00011b46) ROTOR BRAKE. That's all.

The n try those, i.e assign to the Rotor Brake control using those parameters (72516 & 72518). Presume one of those is for turning the APU master on, and the other off, no?
As I said, I thought that the FSLabs used custom controls via the Rotor Brake control form many buttons/switches and so that would appear to verify that...

Did you check the lights presets in the latest events.txt file that I attached above? Use that to replace the one in your FSUIPC7 installation folder then load them using File-> Reload Presets.

Report · July 7

There are also some presets available (78) for the FSLabs A321 Neo, and many of these are for the overhead/lights. However, these are all pretty new (from late June) and won't be available in the preset list (events.txt) file with the latest version of FSUIPC7. Try the one attached below.

Note that I provide the latest preset list (events.txt) from MobiFlight at the time of release. For newer presets, you should check the HubHop site (https://hubhop.mobiflight.com/presets/) and download the latest events.txt file yourself if there are newer ones that you would like to use.

John

events.txt

Report · July 7

7 minutes ago, Arty77 said:

I tried to create some Custom ones using variables found in the Behavior list of Tools (APU MASTER 72516).

What variables? What do you mean by "APU MASTER 72516"?

Unfortunately I had to re-install windows due to a failed update last week, and am slowly rebuilding my system I haven't re-installed the FSLabs yet, but when I do I can take a look.

In the mean-time, please try using FSUIPC's logging facilities: set logging for Events (Log->Events), open the console window (Log->Open Console) and see if anything is logged when you operate the function in the VC with the mouse. You can also try logging Input Events (Log->Input Events) to also see if anything is logged, and also list the lvars (Add-ons->WASM->List Lvars) to see if any of them look appropriate.

I think that the FSLabs uses custom controls (via the Rotor Brake control) for some switches (such as lights), but I may be mistaken....logging should help.

Also, if you can show me some of the code, maybe for a light switch to start with, I can take a look at that. Otherwise, I will get back to you in a few days once I have re-installed the FSLabs aircraft.

John

July 6

1 hour ago, Blade954 said:

I know that with a 7 segment display this is impossible but have read that some attempt this by creating the letter 'U' as a compromise. I guess that this isn't the case with the PMDG and/or offset?

Can you not just replace the letter W with U before sending the string to the display? I would have thought that this would be possible using MobiFlight, bit I do not use MobiFlight and so do not know how this is done - ask on MobiFlight support (Discord). There is also a discussion on this issue here: https://www.mobiflight.com/forum/topic/5175.html

1 hour ago, Blade954 said:

In relation to the offset '643D (IRS_DisplayShowsDots), I'm not sure as to how to implement this?

All PMDG offsets are read-only. What does this offset hold? Presumably 0 (false) if the decimal point is not shown, no?
I do not know what controls this or how you would change this to 1 (true), Maybe another question for MobiFlight.

There was a similar question but for the PMDG version, reported here: https://www.mobiflight.com/forum/topic/3948.html. There is a link to another page but in German - maybe try translating that.

As you are using MobiFlight to drive the displays, you should maybe ask there. I don't use MobiFlight, but maybe some other MobiFlight/FSUIPC users can help....

John

July 6

17 hours ago, gerod said:

the runways.xml file being not created

Are you sure about this? You have windows explorer set to 'Hide extensions of known file types' - it may be just that you cannot see it. Try turning that view option off. I can't see how this file cannot be created if the other files are created.

17 hours ago, gerod said:

and also what about MSFS24 ?

I don't think it will be possible with MSFS2024 as most files are streamed and so not available, and file encryption may also be an issue.

John

July 5

43 minutes ago, nicky9499 said:

There are multiple mentions of FSUIPC in there.

Are these before or after the events from MSFS? It is usual/normal/expected for such events AFTER MSFS has crashed. It would be helpful if you showed the events - both for MSFS and FSUIPC.

45 minutes ago, nicky9499 said:

the file properties states v7.5.0.3 even though website lists v7.5.3.

Thats ok, and just the way I version. 7.5.03 is 7.5.3, 7.5.13 would be 7.5.13.

49 minutes ago, nicky9499 said:

https://drive.google.com/file/d/1WsmgPBcEu-VAB-m8mhSUqPfkmX20YELj/view?usp=sharing

The first event there is for MSFS, not FSUIPC. Are there any events prior to that?

As I keep telling everyone who reports MSFS crashes, this is not related to FSUIPC and I cannot do anything about this - investigate or provide any assistance, FSUIPC7 is a separate/distinct application, and can in no way cause a CTD in MSFS. Well, it can occasionally, but only due to issues with SimConnect (also an issue for Asobo) and usually only in MSFS betas and these are generally fixed before release.

As with all MSFS CTDs, you need to check the Asobo forums and report there.

Sorry I can't be of more assistance, but I can guarantee you that this is not an issue with FSUIPC7.

Regards,

John

July 5

5 minutes ago, gerod said:

the runways.xml file being not created

Not sure why that would be - check the log (Runways.txt).

5 minutes ago, gerod said:

and also what about MSFS24 ?)

If it works, it works, if not, you are welcome to take a look and update it! From the MakeRwys download page:

Quote

Note that MakeRunways is now closed for further development, as Peter Dowson, the original author of this product, has now retired. However, you can download the source and update for your own needs. The source code for this utility is available on GitHub at the following location: https://github.com/jldowson/MakeRunways/. If you would like to take over development and support of this product, please PM me via the support forum (SimMarket)(John Dowson).

I don't really support MakeRwys, and only help out with basic issues, sorry.

John

July 5

19 minutes ago, mattsfalck said:

I am a real novice with SIOC (and programming).

I have never used SIOC and cannot help with this - maybe @Linguini or @jonas_llubi can assist. Otherwise, try SIOC support.

John

July 5

You are running MakeRwys from a sub-folder of the P3Fv5 folder (MakeRwys-P3Dv5). It therefore cannot find the Prepar3d.exe, and so is generating for MSFS.
You must place both the MakeRwys.exe and the LorbySceneryExport.exe in the Prepar3D v5 folder, the same folder that contains the Prepar3d.exe.

John

July 5

Can you zip up the log (Runways.txt) and attach it please.

John

July 5

On 7/5/2025 at 3:48 AM, Omega38K said:

I tried changing the offset to 0x0BCC in the Log, but the box only allows me to type "0BCC,"

Yes, you omit the preceding 0x. However, when I talk about offsets I always specify this so you know its a hex value. That is just the convention.

On 7/5/2025 at 3:48 AM, Omega38K said:

and the value did not change after changing the offset

You mean the value (as logged in the log file) did not change when arming the spoilers?

On 7/5/2025 at 3:48 AM, Omega38K said:

I also checked the lvars list, but I couldn't find anything related to the spoiler arm/disarm value.

Then why did you post the list of lvars? Please dom't post such long lists. If you need to show me such information, export it to a file and attach that - or in this case you can just list the lvars and then show me / attach the FSUIPC7.log file, as the lvars are also logged there.

Maybe try asking TFDI where or how to access this value. I do not have this aircraft and cannot help you with this.

John

July 5

Did you install the LorbySceneryExport program from the ZIP into the Prepar3D folder, to sit beside MakeRwys.exe, as described in the documentation?

July 5

The lua is not being started as you are using an unregistered version of FSUIPC7. As I said, you need a licensed version of FSUIPC7 to run a lua script.

All FSUIPC-specific lua sciri[ts generated by chatgpt are useless and full of errors, and this one is no exception. You can use ChapGPT for non-fsuipc specific lua scripts (e.g. string manipulation, etc), but not for using the FSUIPC-specific library. There are many things wrong with that script. Just a few:

- you cannot write to pmdg-specific offsets (0x64F0 & 0x64F4). And those offsets are for the wiper states - why would you even want to set them every time you send a control?
- ipc_display does not work in FSUIPC7. You need to use the Wnd library for display in a window
- there is no such control number as 0x11223344
- all the parameter values are incorrect. I haven't checked to the control numbers, but I doubt they are correct.

Please don't use chatGPT for liua scripts. If you do, please dopn't send them to me for correction. If you want to use Lua, you should learn how to use it. There are many examples available to get you started.

John

July 4

Not doing too bad, thanks. And yes, I try to remain hopeful, but seems to get harder by the day...!

July 4

Just now, unc1rlm said:

Does the version need to be registered for this to show up

You need a registered version of FSUIPC7 to use lua.

1 minute ago, unc1rlm said:

Does it need to be in a folder in FSUIPC...Folder name "Scripts" or "Lua Files" or what do you suggest?

Lua scripts are recognized (and added to the [LuaFiles] section of the FSUIPC7.ini file) when placed in the FSUIPC7 installation folder. However, you can use/set the LuaPath ini parameter (which goes under [LuaFiles] section) if you want to use a different location (you can specify a relative or full path to a folder).

Note also that lua scripts never appear under the add-ons menu. You activate/start lua scripts in one of two ways:
1. via assignments, such as on a key or button press
2. by having them auto-started, either via the ipcReady.lua or the [Auto] (or a profile-specific [Auto.xxx] section).

Please see the provided documentation.

John

July 4

9 hours ago, PeterW said:

Is there already a planned release date for the version that includes the new livery offset?

This was released in version 7.5.2, on 14th February. From the FSUIPC7 Offset status document:

Quote

0x2480 128 LIVERY NAME Responded Only available in MSFS2024

Looks like I forgot to add this to the changes.txt and history document - sorry about that, I will correct this.

John

July 3

6 hours ago, chasbruce said:

I tried setting x0B47 and x0B48 offsets to 1

The COM SPACING MODE simvar (held in offsets x0B47 and x0B48) report the spacing mode of the COM radios of the currently loaded aircraft, are read-only and cannot be changed. If they are set to 0, then the COM radios are 25khz (or the simvar/offsets are not being used/set).

Do you get 8.33KHz spacing when tuning the radios in the VC, or only 25KHz? If the latter, the only thing you can do is to try to switch out the radios for ones that support 8.33KHz spacing. If they do support 8.33KHz spacing, then it could be that those simvars/offsets are not being used. If that is the case, how are you controlling the frequency - are you using FSUIPC for this? If so, note that offsets 0x034E and 0x3118 are in BCD format and only support 4-digits (leading 1 assumed). To set 8.33KHz spacing, use offsets 0x05C4 and 0x05C8. If using controls/events to set the frequency, you need to use the *_HZ ones.

John

July 2

I can see the issue - the parameter is converted to an integer rather than a floating point value, so 0.5 is converted to 0. I will correct this.

I could provide you with a beta version, but I have discovered a very strange issue that I need to fix before I can provide any more updates. For some (unknown) reason, all builds since sometime mid-April have an issue with showing the 'Find Preset' panel, and pressing the 'Find Preset...' button causes FSUIPC7 to CTD. Its a very puzzling issue - no code change and even re-building existing released versions, where there was no issue, now suffer from this problem. It is very puzzling - and worrying....

John

July 1

Hmm, strange....I will take a look and get back to you....

Unfortunately I had a catastrophic crash on a windows (Insider) update last week and have had to re-install Windows, as well as MSFS, P3D, etc. As well as my development environment. No recent backup unfortunately either (the last one I had was from 2023!). So it may take a few days...

John

June 30

17 hours ago, Ray Lu said:

I guess my problem is I really don't understand how they are supposed to be programmed in Mobiflight.

This is support for FSUIPC, not Mobiflight - try MobiFlight support (on Discord).

John

June 30

18 hours ago, ose159 said:

Can i assign to that button a "mouse left click" (0x20000000) ? How to do it if possible ?

You can use a lua script to operate the mouse, but I would not recommend this. You would need to move the mouse cursor to the correct position before sending the click, and the position could change depending on the view. Note that the versions of FSUIPC for P3D and FSX had a mouse macro facility, for sending mouse clicks to specific 'mouse rectangles' defined in the aircraft. However, this facility is not available in FSUPC7 as MSFS does not support this.

18 hours ago, ose159 said:

I did not find any preset to activate all of them at once but just the left, center, right but i have just a button available.

There are 3 different ways that you can achieve this:

1. Define your own preset to activate all of them (in the myevents.txt file) and use that. Just define the preset to send the calc code of each individual preset. I showed how to do this for the PMDG 777-300ER in another post:

Quote

//PMDG/B777 300ER/Lights
PMDG_B777_Landing_Light_All_Off#(L:switch_22_a) if{ 2201 (>K:ROTOR_BRAKE) } (L:switch_23_a) if{ 2301 (>K:ROTOR_BRAKE) } (L:switch_24_a) if{ 2401 (>K:ROTOR_BRAKE) }
PMDG_B777_Landing_Light_All_On#(L:switch_22_a) ! if{ 2201 (>K:ROTOR_BRAKE) } (L:switch_23_a) ! if{ 2301 (>K:ROTOR_BRAKE) } (L:switch_24_a) ! if{ 2401 (>K:ROTOR_BRAKE) }
PMDG_B777_Landing_Light_All_Toggle#2201 (>K:ROTOR_BRAKE) 2301 (>K:ROTOR_BRAKE) 2401 (>K:ROTOR_BRAKE)
PMDG_B777_Runway_Turnoff_Light_All_Off#(L:switch_119_a) if{ 11901 (>K:ROTOR_BRAKE) } (L:switch_120_a) if{ 12001 (>K:ROTOR_BRAKE) }
PMDG_B777_Runway_Turnoff_Light_All_On#(L:switch_119_a) ! if{ 11901 (>K:ROTOR_BRAKE) } (L:switch_120_a) ! if{ 12001 (>K:ROTOR_BRAKE) }
PMDG_B777_Runway_Turnoff_Light_All_Toggle#11901 (>K:ROTOR_BRAKE) 12001 (>K:ROTOR_BRAKE)

Not sure if they work in the 777-200. You can try them - or correct to use the 777-200 light presets if different.

2. Define a macro to send each light preset. Macros can be used to send multiple commands on a single button or key press - see the Advanced User guide for details un using macros.

3. Overload your assignments so that you have multiple preset assignments on the same button. To do this, assign the first preset. Then open the FSUIPC7.ini file and comment out the assignment (add a semi-colon after the '=' sign) and reload the assignments. Then assign the next preset. Then comment that one out. Repeat until you have all the assignments you require, then uncomment out the assignments previously commented out.
When doing this, make sure that you edit the FSUIPC7.ini file with the button assignments panel open, and click 'Reload all buttons' when you have saved the changes, to reload the file.

John

June 30

Take a look at the offset mapping document for the PMDG 737 (Offset Mapping for PMDG 737NGX and 737NGXu.pdf) - note that you need to enable data broadcasts in the PMDG to have these offset populated. There is this offset (1-byte each, for each engine):

Quote

65D5 2 BYTE x 2 ENG_StartValve[2] true: valve open

or maybe this one:

Quote

6463 2 BYTE x 2 FUEL_annunENG_VALVE_CLOSED[2] Boolean

12 hours ago, Geferson Alves said:

I've configured the GRD, OFF, CONT, and FLT switch positions using PMDG Event IDs.

The current position of this switch is also held in offset 0x64FC:

Quote

64FC 2 BYTE x 2 ENG_StartSelector[2] 0: GRD 1: OFF 2: CONT 3: FLT

John

Profiles

Forums

Events

Gallery

Downloads

Posts posted by John Dowson

Important Information