Unfortunately, that way dosn't work here.
I now run several AMS1 instances, all in different graphics settings, however silly grasping one and same config.ini file from my OneDrive.
I have now renamed the auto-generated "config.ini to "configVR.ini" at same OneDrive AMS1 location (so for a test there is no standard "config.ini" available) and trying to run this command:
Code:
AMS.exe --config=ConfigVR.ini
This both as direct command prompt from within my dedicated AMS1VR folder, as batch file and by adding my VR instance of AMS to Steam, and adding Steam Launch Option for this instance to "--config=ConfigVR.ini".
Unfortunately, nomatter which of the 3 ways I use, starting up AMS1 just results in config.exe to startup, and when saving a new standard "config.ini" is created in my OneDrive AMS1 folder
I don't know if it is possible with AMS1, but I would prefer that config.ini files could be saved locally per AMS1 install folder.
Otherwise, I would like hint as to what I'm doing wrong here