John Dowson

Profile matching can either be done on Title (simvar) or the folder name of the aircraft directory (aircraft.cfg location), the latter by using/setting the UseAirLocForProfiles ini parameter, but not both. It doesn't make sense using both for profile matching, as the name (aircraft title or folder name) is automatically saved and will only match one. However, yes, I can check both to determine if the loaded aircraft is a PMDG aircraft to start the PMDG-specific threads to load/update the PMDG offset area - thats a good idea. Yes, sorry - I should have known that from what you have already said! Could you please try the attached version with MSFS2024 and show me the log file afterwards so I can check to see if the PMDG threads have been started? This version also checks for the string 'pmdg' in the aircraft folder name to determine if the PMDG threads should be started. John FSUIPC7.exe

I have moved your post to the FSUIPC7 support sub-forum, Please use this forum for all questions/issues with FSUIPC7 and MSFS2020/MSFS2024. For newer PFC HID devices, you do not need any additional software. You should be able to assign directly using FSUIPC's assignment panels. However, I think the PFC Cirrus II Pro is a non-Joystick type of HID device. If so you'd need to install the PFChid64.dll. You will not see the PFC menu in the Add-ons menu until FSUIPC7 is connected to MSFS and you may even need an aircraft loaded and ready-to-fly. The log file you attached shows that MSFS wasn't even running. See this thread/comment and later:

Ok, that makes sense. However, this still presents a problem... As the title of the aircraft doesn't contain 'PMDG', the additional offsets available for PMDG aircraft (provided by the PMDG SDK) will not be populated/available. I will need to update FSUIPC to handle this. Do you also use MSFS2020? If so, is the title in MSFS2020 the same?

I currently only have the 777-300er, which is only compatible with MSFS2020 at the moment. I will see if I can get hold of the 777-200er. John

Ah, its the 777-200er...I do have this for MSFS2020. Saw this was now missing for OC2 and so have installed OC3, but I can't see how to install the 777 in MSFS2024.., I will try and get this installed and take a look...

Why is this an issue? Surly the PMDG B772er has a title - and will contain 772 and not 777. Did you add the title of the aircraft to your profile? i.e. when the aircraft is loaded, go into one of the assignment panels and click the 'profile specific' checkbox and then select your PMDG profile. You should then look at the name/title added and shorten that to a substring. However, as the livery name is separate from the title, this may not now be necessary. FSUIPC does not read the aircraft.cfg file for the title, or livery name - it uses the simvars, which were populated from the aircraft.cfg file. If this information is no longer available in the aircraft.cfg file, it must be available somewhere and it will be MSFS that gets this information to make available in the simvars. Are you saying that there is no title now for this aircraft? Could you please show me / attach your FSUIPC7.log and FSUIPC7.ini files, generated after a flight using the PMDG in MSFS2024 and I will take a look. John P.S. Is the SDK (header file) for the PMDG B772er for MSFS2024 the same as the one for the PMDG 737 for MSFS2020? Do you use the specific PMDG offsets? Maybe you could attach the header file for me and I will take a look, Not needed

You have NO aircraft name strings in your profile: How do you expect that to work? I suggested to use this: I also explained how this works: And explained what to check if a profile isn't loaded: Why is this not clear? Sorry but I don't know how else to explain this.... John

No problem.

@GiankMustang Please DO NOT ask for support via DM/PM or email. Always use the support forum. I will ignore any future messages sent via DM/PM. This was your message: First this: No!. "List local panel vars" shows local panel variables, or lvars, NOT lua scripts. This cannot be correct. Lvars are NOT listed under [LuaFiles]. That section only shows lua scripts in your installation folder. Again, they are not 'lua macros'. Lua scripts (NOT macros) are files ending in .lua, macros are files ending in .mcro, and lvars are internal variables (local) to the aircraft. the easiest way to use lvars is to write a macro - see the section 'Gauge local variable access (L:vars)' on page 39 of the Advanced User guide on how to use lvars in macro files. Once you have created a macro to control the lvar, you can then assign to a button or key press. John

That should be the default. i.e. no need to set this. You are not using substrings...change that section to: Then any aircraft whose title matches the substring 'PMDG 737-800' will use that profile. That is how substring matching works. Any time you add an aircraft to a profile, or create a new profile for an aircraft, you should edit the aircraft name in the [Profile.xxx] section to be the shortest substring that matches all aircraft you want to capture/use in that profile. If a profile isn't loaded for a particular aircraft and you think it should, check the title of the aircraft (as logged in the FSUIPC7.log file) and make sure it is captured by an entry/substring match to the names used in the profile section. No idea what this means. SLC should not prevent FSUIPC from working, although SLC itself may not work if not configured correctly. John

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