John Dowson

This should be fixed in the attached version, 7.5.4b. I will release this officially in the coming days. John FSUIPC7.exe

It would help if you could attach your FSUIPC7.ini so I can see your assignments, and also maybe a log (with appropriate logging enabled: Buttons & Keys, Events and WAPI Debug level if using presets)) so that I can see what is happening . Are you using a (combined) presets for this assignment, using a macro or overloading your assignments? What you can try is dependent on what you are currently using. If using individual presets and have overloaded your assignments, you can try combining them to use one preset. Here are some combined presets for the 777, but I am not sure if they are valid for MSFS2020, MSFS2024 or both: //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) If using a macro or overloading your assignments and sending multiple commands (one for each light), then you can also try adding a pause control (control number 1152) between sending each command (whether this is a preset, an event/control or an input event). John

What apps? The FSUIPC7 offset document does say 'for gliders I assume" in the offsets 0x31F8 (tug heading control) and 0x31FC (tug speed control). Probably a hangover from FSX - I can remove that.

Thanks for your kind words. Good luck - please report back if you find anything. You could maybe try turning off some of the on-line services, (live weather and traffic). But if its only happening at one airport, it sounds more like a scenery issue, or maybe badly cached or out-of-date cached scenery. You could try turning of your rolling cache to see if that helps John

From the controls list document: 66498 KEY_TUG_HEADING 66499 KEY_TUG_SPEED 66533 TUG_DISABLE ?

👍😎

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

Those are events that are continually sent. You should ignore those by setting the DontLogThese ini parameter so that such events are not logged. 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.

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

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

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

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

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. Thats ok, and just the way I version. 7.5.03 is 7.5.3, 7.5.13 would be 7.5.13. 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

Not sure why that would be - check the log (Runways.txt). If it works, it works, if not, you are welcome to take a look and update it! From the MakeRwys download page: I don't really support MakeRwys, and only help out with basic issues, sorry. John

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

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

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

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. You mean the value (as logged in the log file) did not change when arming the spoilers? 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

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

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

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

You need a registered version of FSUIPC7 to use lua. 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

This was released in version 7.5.2, on 14th February. From the FSUIPC7 Offset status document: Looks like I forgot to add this to the changes.txt and history document - sorry about that, I will correct this. John

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

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