@Snake122 One problem with my proposal to copy-down profiles from subdirectories … if you make any edits to your cfg or bindings in the Config directory (either via AL or by hand) it will be way too easy to accidentally overwrite them.
A better way, is to make ‘Config’ a directory-symlink which points to either ‘Config_ProfileA’ or ‘Config_ProfileB’ directories. Then you’ll always be editing the normative copy of one of the profiles…
Here’s a sample startup script to flip the Config symlink to point to ProfileA, then launch BMS:
@echo off
::
:: Start BMS with 'Profile A'
cd /d "C:\Falcon BMS 4.37"
:: remove existing symlink, if present
if exist .\User\Config\. rd .\User\Config\. || goto :eof
:: set Config symlink to point to Config_ProfileA directory
mklink /j .\User\Config .\User\Config_ProfileA
:: start BMS .. todo: also start RTT, OpenTrack or voice or other companion processes
start "BMS" ".\Bin\x64\Falcon BMS.exe" -window -nomovie -novr
Save that cmd file somewhere, make a copy for ProfileB, then make yourself a pair of desktop shortcuts.
Disclaimer: I can’t say this is “supported” … swimming is at own risk! But it seems fine so long as you’re not targeting a remote network share or making a cyclic-loop or something crazy.
