John Dowson

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

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

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

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

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): or maybe this one: The current position of this switch is also held in offset 0x64FC: John

You dont have to buy again - all upgrades are free. You just need to download and install the latest version. John

Not sure. There have been previous reports of loss of power in PMDG aircraft, but I think these were during climb (and I think for the 737). This issue was identified as being caused by either flaps or spoilers configuration/calibration in FSUIPC, which sometimes doesn't pay well with FSUIPC unless configured correctly. See But as this only occurs with one variant, I doubt this is the issue. Not sure what to advise. You could maybe try logging the throttle lever position offset, the auto-throttle arm offset and maybe the engine N1/N2 values to see if that reveals anything. You can also attach your FSUIPC7.ini file here and I will check it to see if anything stands out, but I can't think of anything in FSUIPC which would cause such issues. John

You files still show you are using an old unsupported version of FSUIPC7. please download and install the latest and only supported version. Your log file also shows that FSUIPC7 connected to MSFS. Sowhat exactly is your issue? If FSUIPC7 is not auto-starting, please see John

No problem - permission granted (well, not even needed really!). You could also add it to the User Contribution section if you like, and/or I could include it in the FSUIPC SDK download. Let me know. Regards, John

Please use the FSUIPC7 support sub-forum for all issues/questions on FSUIPC7 with MSFS2020 and MSFS2024. I have moved your post. Why are you attaching an installation log from win10 if your issue is with win11? That log file also shows you installed version 7.3.6. That is quite out of date - the latest version is 7.5.3. Please download and install that if you have not already. Only the latest vertsion is supported. What exactly is your issue? The title says that FSUIPC is not connecting - if that is the case, then FSUIPC will do nothing. I do not know what a MiniPanel or a MSFSPopup panel is, or what they have to do with FSUIPC. First, install the latest version of FSUIPC7. Run MSFS and let FSUIPC7 auto-start, and wait for MSFS to arrive at the main menu. Does FSUIPC7 connect? If not, you probably need to manually tune the auto-start parameters - this is described in the Advanced User guide, and also in the following FAQ entry: You can also try exiting FSUIPC7 and then starting it manually - does it then connect? Do you have assignments in FSUIPC? If so, your device GUIDs may have changed with the upgrade from windows 10 to 11, and your assignments may no longer be valid. If this is the case, please attach your FSUIPC7.log and FSUIPC7.ini files and I will take a look. John.