John Dowson

Well, no issues installing them and running them individually. However, if P3D is running with FSUIPC6, you cannot then run FSUIPC7 for MSFS, i.e. only one copy of FSUIPC can be active/running at any given point. WideFS7 works with all versions of FSUIPC from 4 onwards. That is old and needs updating. Yes, but WideFS talks to FSUIPC, not the FS. WideFS7 works with FSUIPC6 for P3D versions 4,5 & 6, FSUIPC4 for FSX, and FSUIPC7 for MSFS2020 and MSFS2024. Only one license is required. You can have a single installation to support both FSUIPC6/P3D and FSUIPC7/MSFS2020/2024, or you can have separate installations. It is up to you. You can try the trial license for FSUIPC7, available in a post at the top of this forum. This also contains a trial license for WideFS7. Regards, John

According to the MSFS documentation: But I have tried this here and also don't seen any bmp file. As this is a control provided by the SDK, there is not much I can do about this except report to Asobo. John

This is nothing to do with FSUIPC7 - please use the Asobo forums for all issues with MSFS, including CTDs. Your log file shows that FSUIPC7 was functiong normally and exited as MSFS was no longer available (as it had crashed). Please also use the FSUIPC7 sub-forum for any questions/issues with FSUIPC7 / MSFS, not the main support forum. I will move your post. John.

Ok, that is interesting. You can remove that option from the MSFS24.bat file. Thanks for the update. John

The log file you attached shows that it was attached while FSUIPC7 was still running (always exit FSUIPC before attaching files), and shows that FSUIPC could not connect the the FS, and ends after 104 seconds. It also shows that auto-tuning was active, but I don't know if this completed as you need to keep FSUIPC running until MSFS arrives at the main menu, and FSUIPC7 must obtain a connection to the FS to be able to tune. You should try manually tuning the start-up parameters - see the Advanced User guide, or the following FAQ entry: You need to increase the DetectToConnectDelayAuto ini parameter, and maybe the InitialStallTime ini parameter. Also, try exiting FSUIPC7 once it is auto-started, and then start in manually once MSFS arrives at the main menu. does it then connect or do you still have issues?

You can also ask the developer of this plugin for help here: https://flightsim.to/file/39243/pmco-fnx32x-pilot-monitoring-callouts-for-the-fenix-a320-add-on John

What version of FSUIPC7 were you using before the update? If it was before 7.5.0, it may be due to the FS version number held in offset 0x3308, which is now only populated once FSUIPC7 is connected to the FS. To pre-populate this, you can add init3308=13 to the [General] section of your FSUIPC7.ini file. Note 13 is for MSFS2020 - use 14 for MSFS2024. Otherwise, please attach your FSUIPC7.log file so I can check for any errors / start-up issues. John

I've now switched to the beta and it works ok here, but I have the Steam version. The desktop icon that FSUIPC installs links to the MSFS24.bat file in your FSUIPC7 installation, and simply starts MSFS2024 with the following command: cmd.exe /C start shell:AppsFolder\Microsoft.Limitless_8wekyb3d8bbwe!App -FastLaunch Maybe that is not valid for the beta, and it is trying to start the released version which is no longer available? or maybe it doesn't like the -FastLaunch argument - you could try removing that. I can't really look into this as I do not have access to an MS Store version. Can you check to see how the default MS 2024 shortcut starts MSFS? You could update the MSFS24.bat file with the appropriate command to start the beta if you so wish. Or just use the default icon and remove/delete the one installed by the FSUIPC7 installer. John

Sorry, but your issue isn't clear... in the first case you say you use 'default 2024 icon' and in the second case you use 'the default icon', and then 'if I only use the default icon it starts correctly'. The images seem to show that there was an exception in MSFS2024 and the game crashed, and the second image is just telling you that the game crashed the previous time it was started. So I am confused as to what is actually happening. The icon(s) installed by FSUIPC only starts the FS and this should be the same as when started by other means, so I'm not sure what is going on. I am not registered for the MSFS2024 beta (yet), so cannot check this here. Are you using a Steam or MS Store version of MSFS2024? If Steam, are you using the beta switcher app? Did you install FSUIPC7 when using the released version or the beta? Maybe the FSUIPC-installed icon is trying to start the released version?

👍

Pete retired over 5 years ago, but I will pass on your message. There is nothing wrong with the installer. This error has been previously reported here: This looks to be due to the fact that the installer cannot acquire full admin rights. Make sure that you are using an account that has full admin rights for the installation. Note that you do not have to run the installer as admin - it will automatically request these. This is probably due to the previous error, so lease correct that first and try again. If you still get this error, then check that you have the APPDATA environment variable defined - this should be defined for all windows user accounts. The installer looks for the UserCfg.opt file under: %APPDATA%\Microsoft Flight Simulator\UserCfg.opt for a steam install - do you have this file? Note also that FSUIPC7 is for MSFS2020 and MSFS2024 only, not FSX. If you are using FSX, you need FSUIPC4. So, when you say FSX, do you mean MSFS2020? John

You cannot change the email address in your registration details, but this is not necessary as it is never actually used to send emails. It is only used to generate the key. However, you should update your email address in your SimMarket account. John

Any issue with button assignments, I need to see both your FSUIPC7.ini and FSUIPC7.log files, the latter with logging for Buttons & Keys activated, and if assigned to presets also WAPI->Debug level logging. Note that it could be that you are using an aircraft with a different name that is not covered by your profile. You should shorten your aircraft names in your profile sections and use substring matching. i.e. change: to You should do the same for all the aircraft names in your profiles. i.e. use the shortest substring)s) of the name that matches all the aircraft you want to capture in that profile and no others. You should get into the habit of editing the aircraft name in a profile whenever you add an aircraft to a profile or create a new profile. John

For the tail number, you can try offset 0x313C, which is the ATC ID which should correspond to the tail number as specified in the aircrraft.cfg file. I am not sure what an IF formula is, but can't you either 1. do a substring comparison, i.e. check that the title starts with the string you are comparing it to, not a full match, or 2. Truncate or only read the number of characters from the title offset that you want to compare.

Please use the specific sub-forum for FSUIPC7 support - I have moved your post. Please see the provided documentation - the Installing and Registering FSUIPC7 document, section Invalid Key Problems. 99.9% of all problems with registration are due to either not entering the details exactly as given, not having the correct VC++ redistributables installed, or anti-virus blocking the registration validation. John

If by '3d cockpit view' you mean the standard virtual cockpit view, then yes. Otherwise, switch to the standard virtual cockpit view to create them. If you mean that you don't see the initial 'Mouse action Macro making' panel, where you enter the macro file name, then the only way this is not displayed is if you have not updated your FSX to at least SP!. If you mean that you do not see the multi-line message when clicking or using the mouse wheel in the desired area, then the aircraft probably does not support mouse-macros (or none available in that area). Very few aircraft in FSX actually support mouse-macros, and if not you should try lvars - as it says in the documentation: John

There are various WASM ini parameters that control scanning for new lvars, but this should only be done in the fist few minutes after aircraft load, as that is generally when all useful lvars will be created. If any lvars are created after this period, then you will need to request a WASM reload (via lua, the provided control or the Add-ons->WASM menu->Reload WASM item) for them to be known by FSUIPC. However if the lvars are specifically created by FSUIPC, either via using lua ipc.createLvar or via offset 0x0D70), then the new lvars will automatically be pushed out to all WASM clients (including FSUIPC) and so no reload is necessary, although a short delay will still be needed before the lvar becomes available. This does not apply if the lvar is created in an ad-hoc manner via executing calculator code as you are doing (although there is nothing wrong doing it this way). Just FYI. Cheers, John

Although the lvar will be crested in the sim, it won't yet be known to FSUIPC. After the execCalcCode call, you need to add a csll to ipc.reloadWASM(), then wait/sleep for 100ms or so for the updated lvar list to be received.

No, not at the moment. There are plenty of discussions on this (and a weather API in general) over on the Asobo developer forums, but there is still no API for weather provided by the SDK. That offset holds the Ambient Wind Velocity, as documented, and always has.... John

If you also used the same parameter as logged, then this would indicate that something else is needed. Could it be that the control does actually control/start the pump, but the visuals don't update in the cockpit (i.e. the switch doesn't move)? This is an issues sometimes, but more with MSFS2020/20204 than FSX. If the aircraft supports mouse macros and there iso ne available for that switch, then yes. I don't have or know that aircraft so do not know - you just have to try. You can also try with a mouse macro, if supported. Also try listing the available lvars/local panel variables (there is a control you can assign to a button/key to list these) to see if any of these look applicable (for both the fuel pump and the annunciator), and if so you can try using those (via a macro). You can also maybe check the aircraft documentation (or support) to see if there are any custom controls provided by the aircraft (developers). John.

No, and I don't think this is even possible. Windows itself receives mouse-clicks and then 1. If the mouse-click is in the window that has the focus, then it will send the mouse-click to the application that owns the window with the focus 2. If the mouse-click is in the window without the focus, it gives the application/window the focus Therefore for the FS to receive the mouse-click, it will need the focus first. If the place you want to send a mouse-click to is always in the same position or same relative position, you could write a small lua scrip to do this for you. The lua script should: 1. First ensure that the FS has the focus by calling ext.focus() 2. Move the mouse cursor to the correct position using mouse.move(x, y, method) 3. Send the mouse-click using mouse.click(button) You can then assign a button or key to activate the lua script. See the FSUIPC Lua Library documentation for details on these functions, and the FSUIPC Lua Plug-Ins document if not familiar with lua scripts. John

Ok, thanks for the update. But note that you do not have to run everything at admin level, but at the same level. Better to run everything with standard privileges unless something must be run with admin privileges, in which case everything must then be run with admin privileges. John

@GiankMustang Posting empty posts again....I will delete those last two....

Your log file shows that FSUIPC7 was started manually and was started way before MSFS was ready to accept connections from client programs. You do have the auto-start component installed, so why not just let MSFS start FSUIPC7 when ready? If you want to start FSUIPC7 manually, then better to do this when MSFS is already running and has arrived at the main menu. If you want to start it earlier, you should adjust the DetectToConnectDelay ini parameter (only used when FSUIPC7 is manually started), which has a default value of 1. See the Advanced user guide on tuning FSUIPC start-up parameters. If 3rd party programs don't recognise FSUIPC as running, then this is either because they are being ran at the wrong privilege level (all 3rd party programs must be ran at the same privilege level as FSUIPC) or is an issue with the program, in which case contact the program developer. However, it could be that it is connecting to FSUIPC but not recognising the FS version being used. To check this, you need to set logging for IPC Reads (Log->IPC Reads) and send me /attach another log file. Many 3rd party programs use offset 0x3308 to determine the FS being used. This used to contain 13 for FSUIPC7 with MSFS2020 and was always available. However, with the release of MSFS2024, this is now only populated once connected to the FS and contains 14 for MSFS2024. Some 3rd party programs read this offset before FSUPC7 is connected to the FS and so receive a value of 0, and do not recognise the FS and so fail to connect. To prevent this, you can try adding the following to the [General] section of your FSUIPC7.ini file: Init3308=14 Otherwise, if a 3rd-party program is using offset 0x3124 to determine the FS version, this used to contain 120 for MSFS2024, but since the release of SU1 this now contains 121. If this is an issue, it needs to be corrected by the program developer. John

Did you disable firewalls on both client and server? If not, try that, This issue has been reported many times from people upgrading to Win11, and it is always either a workgroup or firewall issue (check other posts!) ServerName goes in the WideClient.ini file, not in the WideServer.ini. In fact, there is no WideServer.ini (unless you are using FSUIPC3 or earlier) - wideserver parameters go in the [WideServer] section of your FSUIPC ini file. And don't use BroadCastMode - that is for UDP. You can also try with ServerIPAddr in case its a look-up problem. But I really don't have anything more to say that is not in the WideFS documentation, so read that carefully... John