rlw9sr Posted September 1 Report Posted September 1 I have read the documentation for the creation of Profiles (files) and I have continue to have problems with the correct .ini file being read. I have attached the fsuipc.ini and log file. I also appended the Profile file (PMDG772LR.ini). Please note "config" in the fsuipc7.ini file for the PMDG772LR aircraft. Apparently,the needed data are never read from the profile file. I'd appreciate any help--Thanks-- Robert FSUIPC7.log FSUIPC7.ini PMDG772LR.ini
John Dowson Posted Tuesday at 07:30 AM Report Posted Tuesday at 07:30 AM 11 hours ago, rlw9sr said: Apparently,the needed data are never read from the profile file. Why do you think this? If you open the axes assignment dialog, do you see the profile name in the window title? If you think a profile isn't being loaded, I need to see the log file with logging for Buttons & Keys activated and a button press for a profile-specific assignment, as well as the FSUIPC7.ini and profile-specific ini file. 11 hours ago, rlw9sr said: Please note "config" in the fsuipc7.ini file for the PMDG772LR aircraft. Yes, I can see this is an issue. This is because you are using UseAirLocForProfiles=Yes and as aircraft in MSFS2024 are streamed, the folder containing the aircraft.cfg file is not actually available. I will look into this to see if anything can be done (but I doubt this for streamed aircraft), but for now you should not use this option if using MSFS2024. So please either remove this or set it to No. I will clarify this in the documentation. After changing/removing that setting, you will also need to update the profile aircraft names (or add each aircraft back into the profile), e.g for the PMDG772LR profile use: [Profile.PMDG772LR] 1=777-200LR However, I would have expected the profile to still have been loaded, as your log indicates that the 'config' folder is being used, and that should match. However, I suspect that the same folder may be used for other aircraft, so that the same profile is being used for all/most aircraft. Anyway, try removing that option, update your profile aircraft names and let me know if you still have issues. Note that in the next release, the profile that is being used will be logged in the FSUIPC7 main window. John
rlw9sr Posted Wednesday at 12:45 AM Author Report Posted Wednesday at 12:45 AM Thanks for your comments. I will try your suggestions when I return tomorrow. I do have a question regarding the profile name. I had used the name "Boeing 777-2000LR." which I identified from the aircraft.cfg file; the PMDG aircraft are not streamed. Why is referred to as "777-200LR?" Thanks, I appreciate your time Robert
John Dowson Posted Wednesday at 09:04 AM Report Posted Wednesday at 09:04 AM 7 hours ago, rlw9sr said: I do have a question regarding the profile name. I had used the name "Boeing 777-2000LR." which I identified from the aircraft.cfg file; the PMDG aircraft are not streamed. Why is referred to as "777-200LR?" Profile names can be anything - they are just used to connect to the files or the various sections in the ini - they don't have to be related to the aircraft name at all (e.g. you can use 'Jet' or 'MyProfile'). What is important, and is used to match the aircraft to the profile, are the names of the aircraft under the [Profile.xxx] sections. When matching on aircraft names (the default, when UseAirLocForProfiles is No or not set), then the aircraft name added to the profile (and used for matching when loaded) is the aircraft Title (simvar), which in both MSF2020 and MSFS2024 is defined as 'Title from the aircraft.cfg file'. In MSFS2020, for the PMDG 777 its this: Quote [fltsim.0] title="PMDG 777-300ER PMDG House" However, in MSFS2024, its commented out for some reason: Quote [FLTSIM.0] ;title="Boeing 777-300ER" So the title seems to be coming from the icao_model entry instead. But in both cases. FSUIPC takes this from the value of the Title simvar provided by MSFS - it does not read the aircraft.cfg file directly. It uses what MSFS provides. When using UseAirLocForProfile=Yes, the folder name containing the aircraft.cfg file is used. In MSFS2020, this is: Community\pmdg-aircraft-77w\SimObjects\Airplanes\PMDG 777-300ER whereas in MSFS2024 it is: Community\pmdg-aircraft-77w\SimObjects\Airplanes\PMDG 777-300ER\common\config which is where that config entry is coming from. And this location is different for different add-ons in MSFS2024. For example, for the JustFlight Piper Arrow, its: Community\justflight-aircraft-pa28-arrow-bundle\SimObjects\Airplanes\JF_PA28_Arrow i.e. the same location as used in MSFS2020. So even though the PMDG aircraft isn't streamed, it is probably not a good idea to use the aircraft.cfg file folder name for matching in MSFS2024- and certainly not when using streamed aircraft. John
rlw9sr Posted Friday at 08:07 PM Author Report Posted Friday at 08:07 PM Thank your all you help in this. I successfully created the profiles for the aircraft--I appreciate your insights-- Robert 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now