@sbeachjr The location of the launch file depends on if you have the Steam version or the Microsoft Store version. If you have the Steam version it should be in "C:\Program Files (x86)/Steam/steamapps/common/MicrosoftFlightSimulator", unless ofcourse you have a different disk for your Steam library, in which case the "C:\Program Files (x86)" part will be different.
If you have the Microsoft Store version it should be in "C:\Program Files\WindowsApps\Microsoft.FlightSimulator_<version>_x64__<some_random_string_of_characters"
I cannot remember what the actual name of the .exe is, but it should be fairly obvious once you get into those folders. Something like "MSFS2020.exe" or simillar i would guess. One "little" thing is that Microsoft does not allow "ordinary people" to access the C:\Program Files\WindowsApps folder and subfolders unless you do some registry tweaking. So if you have that version, it might be a little tricky but just google it. If you have the Steam version all should work fine, just find the right .exe and change the "EXE Path" in the profile to point to that .exe.
If all else fails you can use just the global settings, e.g just set things up the way you want it on the Game Settings tab and then start the game and it will use those settings.
@sbeachjr I don't have MSFS2020 myself, but i do think it uses a launcher app, right?
So a little app that starts before the main game acutally starts? If so, then OTT has probably picked this up as the main executable, thinking this is the actual game process. What happens then is that it detects this when it starts and applies the profile. But when the main game is actually started, the launcher app shuts down and OTT then resets everything back to defaults, just as it does whenever a game exists. So you should update the profile and point the game exe to the actuall .exe process that is running the game, the one that stays up until you exit the game.
@sbeachjr The location of the launch file depends on if you have the Steam version or the Microsoft Store version. If you have the Steam version it should be in "C:\Program Files (x86)/Steam/steamapps/common/MicrosoftFlightSimulator", unless ofcourse you have a different disk for your Steam library, in which case the "C:\Program Files (x86)" part will be different.
If you have the Microsoft Store version it should be in "C:\Program Files\WindowsApps\Microsoft.FlightSimulator_<version>_x64__<some_random_string_of_characters"
I cannot remember what the actual name of the .exe is, but it should be fairly obvious once you get into those folders. Something like "MSFS2020.exe" or simillar i would guess. One "little" thing is that Microsoft does not allow "ordinary people" to access the C:\Program Files\WindowsApps folder and subfolders unless you do some registry tweaking. So if you have that version, it might be a little tricky but just google it. If you have the Steam version all should work fine, just find the right .exe and change the "EXE Path" in the profile to point to that .exe.
If all else fails you can use just the global settings, e.g just set things up the way you want it on the Game Settings tab and then start the game and it will use those settings.
Cheers!
Thanks for your reply.
Thanks for your reply.
@sbeachjr I don't have MSFS2020 myself, but i do think it uses a launcher app, right?
So a little app that starts before the main game acutally starts? If so, then OTT has probably picked this up as the main executable, thinking this is the actual game process. What happens then is that it detects this when it starts and applies the profile. But when the main game is actually started, the launcher app shuts down and OTT then resets everything back to defaults, just as it does whenever a game exists. So you should update the profile and point the game exe to the actuall .exe process that is running the game, the one that stays up until you exit the game.
Hope this helps.
Cheers!