John Dowson

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

Ok, thanks for the update. Its a pity that you did not find the cause before the re-install though! Regards, John

Many people use VoiceAttack with FSUIPC / MSFS. However, VoiceAttack works by sending key presses/releases from voice commands. These should be directed at MSFS (not FSUIPC), and MSFS will send them to FSUIPC for processing. Thee are several support requests on using VoiceAttack with FSUIPC - with MSFS and other flight simulators. Maybe check out those if you have any issues. John

Yes (the FSUIPC6.log file) You don't install it. All lua facilities are always available. Here (in key assignments): Sometimes aircraft developers re-purpose controls that are not used for other purposes (usually the ROTOR_BRAKE control as this is never used in airplanes). You can try assigning to that to see if it works, but that may be just a coincidence or a side-effect. Mouse macros are only available where provided by the aircraft developer. If you are trying to create a mouse macro in an area that is not supported, then that is because the developers have not allowed this and FSUIPC cannot create a mouse macro where no support for this is provided. John

I don't know why you would think that. FSUIPC only detects lua files that are in the FSUIPC installation folder, unless the LuaPath ini parameter is specified which changes the location. See the Advanced User guide for details of this ini parameter. What do you mean - the Add-ons menu? Why would you think that lua files would appear there? Known lua files can be used for assignments (Key, button or axis) or they can be auto-started (via the [Auto] and profile-specific [Auto.xxx] sections), or they can be started by other lua files (usually via the predefined lua files ipcinit.lua and ipcready.lua). John

Ah, sorry...you can still list available lvars in FSX though. Which is what I think you get when the Lvar does not exist. No - there is a syntax error in your lua script. You need to use standard double-quotes, i.e. ipc.writeLvar("L:Electrical master battery", 0) Word changes these to opening and closing quotes (in the documentation) which is a bit of a pain, but you always need to use standard double quotes, not the opening/closing quotes, You won't get any error if the lvar doesn't exist - nothing will happen. In that xml file, the standard event Toggle Master Battery is used (>K:TOGGLE_MASTER_BATTERY) as well as other code, but I am not familiar with gauge programming. It does seem to also set the lvar L:Electrical master battery to 0 (for off) and 25 (for on), so you probably need to se the lvar AND send the event (using ipc.control)

Please use the FSUIPC7 sub-forum for all issues / questions on FSUIPC7 with MMSFS2020 and MSFS2024. I have moved your post. Why not? Please give me more information on what your issue actually is. Are presets working for other aircraft? Is the WASM installed and active? Do you see any lvars for this aircraft - the number of lvars will be displayed in the FSUIPC main window - if you have any lvars, then the WASM will be installed and working. I do not provide videos - only documentation. Please see the User manual on key/button assignments. PMDG aircraft mainly use custom controls. Presets are one way to assign to these, but you can also assign to the custom controls directly. See the following FAQ entries on how to use PMDG custom controls: If you can give me one or two buttons/switches/knobs that you would like to control, and also let me know if you want this assigned to a button or key, then I can give you details on how to assign for this to get you started. John

No problem - thanks for the update. For future reference, any issues with the auto-start not working, see John

No - those log lines indicate keypresses from the keyboard (KEYDOWN). See the section Gauge local variable access (L:vars), by macro in the FSUIPC6 Advanced User guide, page 39. No. That is for FSUIPC7 and MSFS2020 / MSFS2024 only. What is logged when you press that button in the VC? It is not the KEYDOWN. Your log seems to contain many PANEL_ID_OPEN and PANEL_ID_CLOSE events logged with different parameters - maybe these have been repurposed. But I cannot tell from just looking at the log file. You need to do this with the logging console window open so that you can see what is logged when you press the switches in the VC in real time. No point posting the log file - look yourself! Or look into lvars to see if any are available. I know what the master warning and caution switches and lights are - its just helpful to me if you tell me in detail what you want to do - sometimes the warning/caution lights are independent from the switches, and I am not familiar with the aircraft you are using. John

Then that must be an older version that is linked to the windows start menu. Start it again that way, check the version number, then use File->Open Installation folder to see where it is installed. Then exit and delete/remove it.

Why not? Have you tried? It is incredibly easy and explained well: So, just create a myevents.txt file (in your FSUIPC7 installation folder), if you do not already have one, and paste those entries into it, reload the presets if FSUIPC7 is running (using File->Reload Presets) and then assign your axis to those presets in the normal way, by selecting Send Preset to FS, click the Find Preset.. button and navigate to those presets (under Personal -> Blacksquare Duke Mixture) and select the the preset (or presets) to use.

That may also work for the ini A350, but you might need to update the throttle positions and maybe the controls used.... John

If mouse-macros work for other switches, it seems strange that there is not one for this. But what exactly is "Warning"? If you log Events, do you not see anything when you click this in the VC? If anything is logged, then you can use that. I don't have this aircraft so I cannot look into this, sorry. You can check to see if there are any lvars available for this - try listing the available lvars and see if any look applicable (there is an FSUIPC-added control to log available lvars). Otherwise, ask on the aircraft support forums to see if / how this can be controlled. Well, that last message was good - no scroll bars! John

I cannot see any issues with FSUIPC7, and your access violations are in the LINDA.exe. Sorry, but I cannot help with this - I have never used and know very little about LINDA. Traffic scanning is being re-started a few times but this is almost certainly due to your system being under a heavy load and is nothing to worry about. John

@one2tw Please try the attached lua script. Save it to your FSUIPC7 installation folder and have this auto-started by adding it to the [Auto] or (better) [Auto.xxx] section (where xxx is your profile name) of your FSUIPC7.ini file, e.g. Clear the assignments to the F4 and F1 keys in MSFS2020 (as these will move to full throttle and cut-off by default). I am not sure this goes into TOGA, but please test and if not, let me know how you go into TOGA and I can update. Please take a look at the script and maybe adjust if needed. The throttle positions are defined here: local throttleStates = {"Idle", "Climb", "FLX", "TOGA"} local throttlePositions = {-3225, 8131, 12131, 16384} You can try adjusting those positions as needed (and restart the script afterwards!). Note that the strings in throttleStates are just used for logging purposes. Let me know how it goes. John A380Throttle.lua

First, when pasting text, please paste as plain text so that I don't see those annoying scroll bars... A macro is a macro.... If you have instructed FSUIPC to start the macro making process and the multiline simconnect message window does not appear when you click in the area that you want to create the macro for, then either the aircraft does not support macros (not all aircraft do) or there is no macro (i.e. mouse rectangle) available in the area that you clicked. John

Your installation log shows that you installed the latest version - I am not sure why your ini file does not show that old version. Have you ran it yet? And why are you posting in this topic anyway - do you actually have any connection issues? If so, read the documentation and follow the advice. Then only post if you still have issues, and attach both your .ini and .log files. John

@Eduardo P You are using an old an unsupported version of FSUIPC7 (7.5_ - please update. Do not set those parameters unless you really need to (and those are for the OPs system and may not be valid/work for your system). Better to read the documentation and follow the advice there - see the section Auto-tuning of initial start-up ini parameters on page 11 of the Advanced User guide. John

Sorry for the delay - you posted in the wrong forum and I did not see your message until now. Please check the SDK folder (after installing FSUIPC) - there is a Python SDK there. John

The trial license is now available from the first post in this topic. John

If it is detecting a steam version and you have an MS Store version, this is because you have a UserCfg.opt file in the following location: <user>\AppData\Roaming\Microsoft Flight Simulator 2024\UserCfg.opt Delete or rename that file and re-install.

It isn't - add an exception or disable while you download...