PC Windows 10
RAASPRO for MSFS
Version: 1.9.67.0

I have created a custom profile for PMDG737-800 and FBWA32NX

But it does't matter which profile is nominated as the Default Profile (ticked), it is always the PMDG737-800 profile which auto-loads after re-launching the program

I must be doing something wrong - anyone got any suggestions please?
 

 

Can you post your RAAS XML config file's content and also both custom profiles (PMDG737 and FBW) content too?...so I can take a look at them?

6 hours ago, Manuel82 said:

Can you post your RAAS XML config file's content and also both custom profiles (PMDG737 and FBW) content too?...so I can take a look at them?

Thanks @Manuel82 not at the computer right now but will do asap

15 hours ago, slicker55 said:

Thanks @Manuel82 not at the computer right now but will do asap

\AppData\Roaming\FS2Crew MSFS RAASPRO\FS2Crew RAASPRO.xml

<RAASPROConfig>
<FSExeXmlFp>C:\Users\grahj\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\EXE.XML</FSExeXmlFp>
<MasterSwitch>True</MasterSwitch>
<UIRepaintTimer>True</UIRepaintTimer>
<ToggleRAASOnOffKey> </ToggleRAASOnOffKey>
<HTTPSvrEnabled>True</HTTPSvrEnabled>
<HTTPToolTipsEnabled>True</HTTPToolTipsEnabled>
<HTTPSvrPort>4448</HTTPSvrPort>
<SimBriefPID>0</SimBriefPID>
<OnTop6HzEnabled>True</OnTop6HzEnabled>
<AptAPITimeOut>5</AptAPITimeOut>
<AptAPIEnabled>True</AptAPIEnabled>
<SVStatisticsOn>False</SVStatisticsOn>
<AutoDetectSceneryChanges>False</AutoDetectSceneryChanges>
<DefaultProfile>B737-800</DefaultProfile>
<RAASLVarEnabled>True</RAASLVarEnabled>
<SupprFlashIcon>False</SupprFlashIcon>
<MSFSAutoStart>False</MSFSAutoStart>
<LockMainPanel>False</LockMainPanel>
<UpdateDbTimeOut>15.0</UpdateDbTimeOut>
<AudioVolume>0.5</AudioVolume>
<HeadsetDeviceIdx>0</HeadsetDeviceIdx>
<AudioDeviceIdx>0</AudioDeviceIdx>
</RAASPROConfig>

---------------------------------------------------------------------------------------------------------

\AppData\Roaming\FS2Crew MSFS RAASPRO\Profiles\Default Profile.xml

<RAASProfile>
<AppRwyOnGnd>True</AppRwyOnGnd>
<AppRwyInAir>True</AppRwyInAir>
<OnRunway>True</OnRunway>
<RunwayEnd>True</RunwayEnd>
<TaxiwayTakeOff>True</TaxiwayTakeOff>
<InsufficientRwyLenOnGnd>True</InsufficientRwyLenOnGnd>
<ExtendedHoldingOnRwy>True</ExtendedHoldingOnRwy>
<AppShortRwyInAir>True</AppShortRwyInAir>
<TaxiwayLanding>True</TaxiwayLanding>
<TakeOffFlapMonitor>True</TakeOffFlapMonitor>
<LandingDistRemain>True</LandingDistRemain>
<RTODistRemain>True</RTODistRemain>
<LandingFlapMonitor>True</LandingFlapMonitor>
<ExcessiveApprSpeed>True</ExcessiveApprSpeed>
<ExcessiveApprAngle>True</ExcessiveApprAngle>
<UnstableApproach>True</UnstableApproach>
<AltSettingAbove>True</AltSettingAbove>
<AltSettingBelow>True</AltSettingBelow>
<LongLanding>True</LongLanding>
<CautionEnabled>True</CautionEnabled>
<ExcludeShortRwys>True</ExcludeShortRwys>
<AirbusSupprZone>False</AirbusSupprZone>
<AnnunciateUnits>True</AnnunciateUnits>
<ShowAltSetMsg>True</ShowAltSetMsg>
<RepAltSetCallOut>False</RepAltSetCallOut>
<UnitsOfMeasure>0</UnitsOfMeasure>
<MinTakeOffLength>1000</MinTakeOffLength>
<MinLandingLength>800</MinLandingLength>
<TouchdownZoneLen>25</TouchdownZoneLen>
<ExtHoldInitialTime>60</ExtHoldInitialTime>
<ExtHoldRepeatTime>30</ExtHoldRepeatTime>
<MinTakeOffFlaps>1</MinTakeOffFlaps>
<MinLandingFlaps>3</MinLandingFlaps>
<MaxApproachSpeed>220</MaxApproachSpeed>
<UpperFlapGateAlert>950</UpperFlapGateAlert>
<LowerFlapGateAlert>600</LowerFlapGateAlert>
<TransitionAltitude>13000</TransitionAltitude>
<ClimbDescendVSpeed>100</ClimbDescendVSpeed>
<TransitionLevel>5000</TransitionLevel>
<AltSetTolerance>0.1</AltSetTolerance>
</RAASProfile>

---------------------------------------------------------------------------------------------------------

\AppData\Roaming\FS2Crew MSFS RAASPRO\Profiles\B737-800.xml

<RAASProfile>
<AppRwyOnGnd>True</AppRwyOnGnd>
<AppRwyInAir>True</AppRwyInAir>
<OnRunway>True</OnRunway>
<RunwayEnd>True</RunwayEnd>
<TaxiwayTakeOff>True</TaxiwayTakeOff>
<InsufficientRwyLenOnGnd>True</InsufficientRwyLenOnGnd>
<ExtendedHoldingOnRwy>True</ExtendedHoldingOnRwy>
<AppShortRwyInAir>True</AppShortRwyInAir>
<TaxiwayLanding>True</TaxiwayLanding>
<TakeOffFlapMonitor>True</TakeOffFlapMonitor>
<LandingDistRemain>True</LandingDistRemain>
<RTODistRemain>True</RTODistRemain>
<LandingFlapMonitor>True</LandingFlapMonitor>
<ExcessiveApprSpeed>True</ExcessiveApprSpeed>
<ExcessiveApprAngle>True</ExcessiveApprAngle>
<UnstableApproach>True</UnstableApproach>
<AltSettingAbove>True</AltSettingAbove>
<AltSettingBelow>True</AltSettingBelow>
<LongLanding>True</LongLanding>
<CautionEnabled>True</CautionEnabled>
<ExcludeShortRwys>True</ExcludeShortRwys>
<AirbusSupprZone>False</AirbusSupprZone>
<AnnunciateUnits>True</AnnunciateUnits>
<ShowAltSetMsg>True</ShowAltSetMsg>
<RepAltSetCallOut>False</RepAltSetCallOut>
<UnitsOfMeasure>0</UnitsOfMeasure>
<MinTakeOffLength>1000</MinTakeOffLength>
<MinLandingLength>800</MinLandingLength>
<TouchdownZoneLen>25</TouchdownZoneLen>
<ExtHoldInitialTime>60</ExtHoldInitialTime>
<ExtHoldRepeatTime>30</ExtHoldRepeatTime>
<MinTakeOffFlaps>3</MinTakeOffFlaps>
<MinLandingFlaps>6</MinLandingFlaps>
<MaxApproachSpeed>220</MaxApproachSpeed>
<UpperFlapGateAlert>950</UpperFlapGateAlert>
<LowerFlapGateAlert>600</LowerFlapGateAlert>
<TransitionAltitude>10000</TransitionAltitude>
<ClimbDescendVSpeed>100</ClimbDescendVSpeed>
<TransitionLevel>13000</TransitionLevel>
<AltSetTolerance>0.1</AltSetTolerance>
</RAASProfile>

---------------------------------------------------------------------------------------------------------

\AppData\Roaming\FS2Crew MSFS RAASPRO\Profiles\A320.xml

<RAASProfile>
<AppRwyOnGnd>True</AppRwyOnGnd>
<AppRwyInAir>True</AppRwyInAir>
<OnRunway>True</OnRunway>
<RunwayEnd>True</RunwayEnd>
<TaxiwayTakeOff>True</TaxiwayTakeOff>
<InsufficientRwyLenOnGnd>True</InsufficientRwyLenOnGnd>
<ExtendedHoldingOnRwy>True</ExtendedHoldingOnRwy>
<AppShortRwyInAir>True</AppShortRwyInAir>
<TaxiwayLanding>True</TaxiwayLanding>
<TakeOffFlapMonitor>True</TakeOffFlapMonitor>
<LandingDistRemain>True</LandingDistRemain>
<RTODistRemain>True</RTODistRemain>
<LandingFlapMonitor>True</LandingFlapMonitor>
<ExcessiveApprSpeed>True</ExcessiveApprSpeed>
<ExcessiveApprAngle>True</ExcessiveApprAngle>
<UnstableApproach>True</UnstableApproach>
<AltSettingAbove>True</AltSettingAbove>
<AltSettingBelow>True</AltSettingBelow>
<LongLanding>True</LongLanding>
<CautionEnabled>True</CautionEnabled>
<ExcludeShortRwys>True</ExcludeShortRwys>
<AirbusSupprZone>True</AirbusSupprZone>
<AnnunciateUnits>True</AnnunciateUnits>
<ShowAltSetMsg>True</ShowAltSetMsg>
<RepAltSetCallOut>False</RepAltSetCallOut>
<UnitsOfMeasure>0</UnitsOfMeasure>
<MinTakeOffLength>1000</MinTakeOffLength>
<MinLandingLength>800</MinLandingLength>
<TouchdownZoneLen>25</TouchdownZoneLen>
<ExtHoldInitialTime>60</ExtHoldInitialTime>
<ExtHoldRepeatTime>30</ExtHoldRepeatTime>
<MinTakeOffFlaps>1</MinTakeOffFlaps>
<MinLandingFlaps>3</MinLandingFlaps>
<MaxApproachSpeed>220</MaxApproachSpeed>
<UpperFlapGateAlert>950</UpperFlapGateAlert>
<LowerFlapGateAlert>600</LowerFlapGateAlert>
<TransitionAltitude>5000</TransitionAltitude>
<ClimbDescendVSpeed>100</ClimbDescendVSpeed>
<TransitionLevel>6000</TransitionLevel>
<AltSetTolerance>0.1</AltSetTolerance>
</RAASProfile>

---------------------------------------------------------------------------------------------------------
 

Edited January 26, 20242 yr by slicker55

Ok, I'm not seeing anything wrong with the files, just that the RAAS xml settings file is set to be default the "b737-800.xml" profile....for example, if you would like to make the "A320.xml" custom profile as default, you would need to follow the following steps:

• Start MSFS RAAS
• RAAS will obviously load the "B737-800.xml" profile as Default
• Select the "A320.xml" profile in RAAS window from the dropdown
• Once loaded, check/tick the "Default Profile" checkbox
• Click on "Save Profile"
• Exit/close RAAS main window
• Restart RAAS, now it should be loadiung the "A320.xml" as Default profile.

Try those steps and let me know.

Manuel

@Manuel82 Thanks for taking a look ... I have been doing exactly as you said but it doesn't save the default (ticked) ... but, your answer gave me an idea ...

I have now changed the setting (directly) in \AppData\Roaming\FS2Crew MSFS RAASPRO\FS2Crew RAASPRO.xml from B737-800 to A320 which now loads the A320 as the default.

So, it issue seems the issue is related to writing the 'default' preference to the file?

Perhaps something is blocking our attempts to write to the file?

51 minutes ago, byork said:

Perhaps something is blocking our attempts to write to the file?

Yes, looks that way ... will let you know if I manage to trace the problem

 

@Manuel82  as promised, an update after some more testing ...

Confirm disabled Webroot Antivirus (to exclude that possibility)

Confirm, using Notepad++, can manually write/save to:

C:\Users\grahj\AppData\Roaming\FS2Crew MSFS RAASPRO\FS2Crew RAASPRO.xml

Deleted custom profiles, uninstalled RAASPRO and reinstalled a fresh copy via FS2Crew Product Manager

Created two new profiles (A320 & B737-800), defined A320 to be the default profile

Saved profile, exited program via MSFS Toolbar

Reloaded program, original default profile automatically loads and is still ticked

Again, appears user-preference to define default profile is not being written by the program to FS2Crew RAASPRO.xml

Out of interest, and just to localise the issue reported, have you tested this feature at your end?

9 hours ago, slicker55 said:

Again, appears user-preference to define default profile is not being written by the program to FS2Crew RAASPRO.xml

Then that seems to be the issue, if RAASPRO exe isnt writting the settings XML then probably...the "user" that is launching the program isnt the same as your windows username, or its impersonating another...in the context that...RAASPRO.exe isnt writting that same file.....do you have another windows user profiles? under your machine?....if thats the case probably RAASPO.exe is getting launched using another windows user...and the windows user that actually installed RAASPRO...installed in another AppData....as a result ..no matter how many times you change any settings....they will never be saved to the RAASPRO.xml (settings file)...because the program isnt writting to it...(thats the picture I have...)..But I'll cross check testing.... Has been a little busy with the development of SOP3 sorry by the delayed answer.

Manuel

@Manuel82 sorry to trouble you with this when you're busy with something else.

I didn't anticipate this becoming so complicated ...

I am the sole user of this computer but you may be on to something when you mention usernames. 

Inside C:\Users there are two folders and names that I recognise, (although, not sure how these have come about).

The first folder (grahj) contains;
full path to where MSFS2020 (Store Version) is installed.

The second folder (johngraham) contains:
AppData/Local\Microsoft\Internet Explorer
AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Accessories
AppData\Roaming\Adobe\Flash Player\NativeCache

If I log out of Windows, there is only one account available to log back into (john graham)

I would like to get the save 'default profile' preference working properly but, I must admit, I'm starting to get out of my depth now.

Please let me know if there is anything else I can provide which will be of further assistance.

10 hours ago, slicker55 said:

@Manuel82 sorry to trouble you with this when you're busy with something else.

No worries, we'll solve the issue.

On 1/26/2024 at 7:33 PM, Manuel82 said:

• Start MSFS RAAS
• RAAS will obviously load the "B737-800.xml" profile as Default
• Select the "A320.xml" profile in RAAS window from the dropdown
• Once loaded, check/tick the "Default Profile" checkbox
• Click on "Save Profile"
• Exit/close RAAS main window
• Restart RAAS, now it should be loadiung the "A320.xml" as Default profile.

After doing more tests, I found that I was doing 2 extra steps, that by my mistake, I didn't add to the list above:

Open and close the RAAS settings panel

This triggers the "Save to RAASPRO.xml" file action.So the steps would look like this:

• Start MSFS RAAS
• RAAS will obviously load the "B737-800.xml" profile as Default
• Select the "A320.xml" profile in RAAS window from the dropdown
• Once loaded, check/tick the "Default Profile" checkbox
• Click on "Save Profile"
• Open RAAS settings panel (with the "Gear" icon) <-------
• Close RAAS settings panel <------- (This was actually saving to "RAASPRO.xml" file)
• Exit/close RAAS main window
• Restart RAAS, now it should be loadiung the "A320.xml" as Default profile.

So again, sorry, by my mistake, but now thinking....its 2 unnecessary steps for the user....so I'm making a fix, so now when you actually close RAAS main window. To actually Save to the RAASPRO.xml and not only after closing the "Settings" panel. The change will be available on the next RAAS update. Again, apologies, and thanks by making this bug report. And you were correct.

Cheers,

Manuel

@Manuel82 you, that's sorted it ... thanks so - appreciated ... just to mention, correct me if I'm wrong but I seem to remember that with the PMDG, you managed to import the transition altitude and transition flight level automatically from the FMC .... very useful feature, any chance you can also do this for the FBWA32NX please?

Once again, many thanks for resolving the save as 'default profile' option 

Excellent!, any other question let us know!

6 hours ago, slicker55 said:

just to mention, correct me if I'm wrong but I seem to remember that with the PMDG, you managed to import the transition altitude and transition flight level automatically from the FMC .... very useful feature, any chance you can also do this for the FBWA32NX please?

I think it already does...can you take a screenshot or show me the FBWA32NX settings panel screenshot?, just to confirm.

Manuel

Edited February 1, 20242 yr by Manuel82

@Manuel82 Hi, yes, leave it with me, I will take screenshots showing altitudes set in MCDU and altitudes in RAASPRO (Extended Hold & Misc Settings) for comparison