Solved Is BMS -Full.key file replaced/overwritten by U3?
-
Here’s a little bat file i use to regularly backup my user config file so I can always roll back/compare. I have it run automatically each time the pc starts. Needs 7z installed. Note it will delete anything which looks like delFilter in DESTFOLDER, older than DELDAYS.
REM 06 =============== BACKUP BMS435 USER CONFIG FOLDER =================== SET SOURCEFOLDER="E:\BMS435\User\Config" SET DESTFOLDER="D:\Drive\BACKUPS\Daily\BMS\435" SET DESTNAME="Config435" SET SECRET=111111 SET OPENFOLDERFLAG=true SET DESTEXT=".7z" SET SEVENLOCATION="C:\Program Files\7-Zip\7z.exe" SET delFilter="Config*.7z" SET DELDAYS=100 SET killFlag="true" SET openFolderFlag="true" SET HOUR=%time:~0,2%_ SET timelong=_0%time:~1,1%%time:~3,2%%time:~6,2% SET timeshort=_%time:~0,2%%time:~3,2%%time:~6,2% if "%HOUR:~0,1%" == " " (SET dtTime=%timelong%) else (SET dtTime=%timeshort%) SET today=20%DATE:~6,4%%DATE:~3,2%%DATE:~0,2% forfiles /p %DESTFOLDER% /s /m *%DESTEXT% /D -%DELDAYS% /C "cmd /c del @PATH" REM with secret REM %SEVENLOCATION% a %DESTFOLDER%/%DESTNAME%_%today%".7z" -p%secret% -mhe %SOURCEFOLDER%"\*" %SEVENLOCATION% a %DESTFOLDER%/%DESTNAME%_%today%".7z" -mhe %SOURCEFOLDER%"\*" if %killFlag% == "true" forfiles /p %dest% /s /m %delFilter% /D -%deleteDays% /C "cmd /c del @PATH" if %openFolderFlag% == "true" START "" %dest%
-
Have anybody taken the falcon bms.cfg file from U2 and directly into U3?
-
@mlu the cfg has not been touched by U3
-
I use the AL and didn’t lose my latest DX buttons across 2 devices changes BUT lost my long standing custom keyboard combos. It could be worse since even if I lost all them, the combos are still on my devices and just have to reprogram via the AL.
So for future reference, how does the AL write to the .key(figured out in edit)? Is it the Full.key by default(yes). Does it save the keyboard combo changes someplace so I can pull them out of someplace (so far not seeing anything in the AL folder, seems to be no). If I make a change in the BMS UI, does the AL automatically overwrite it on next load or incorporate the change (no)?
This would be nice to know still: Can you change which .key AL writes to?
EDIT: I can see it writes to The BMS - FULL.key and Falcon UI changes will stay (I also remember that also at least used to be not recommended to do, but was testing). Moral of the story is like I used to, keep a backup of my prime .key (this case the standard Full one). So AL saved my DX assignments because how it ties DX inputs to specific controllers so it can keep them in place in case you left one unplugged/added a new one, etc…
-
This post is deleted! -
…this is an example where playing with stock BMS file through Alternative Launcher creates issues…
@chihirobelmo , Would be very useful to be able to use a ‘custom named’ key file with alternate launcher.
-
The way DCS does it is really nice. If you have a modified file and run an update it will make a copy of your custom file and put it in a backup.001 folder. That’s saved my butt a few times. If practical having the installer check for files which are modified and making backup copies in that way would be a nice feature.
-
@fish44 said in Is BMS -Full.key file replaced/overwritten by U3?:
…this is an example where playing with stock BMS file through Alternative Launcher creates issues…
@chihirobelmo , Would be very useful to be able to use a ‘custom named’ key file with alternate launcher.
Plus One on this, Fish. I like Frederf’s idea. But , I’m always experimenting, so having an “Airwolf.key” that AL would look at would work best for me.
No matter. C, IMHO, AL is an absolute blessing. So, I’ll do what i have to do … -
@maxwaldorf said in Is BMS -Full.key file replaced/overwritten by U3?:
I would emphasize on the fact that it is much needed to use a custom key file…
@chihirobelmo , this is an example where playing with stock BMS file through Alternative Launcher creates issues…
Maybe you should copy it and work on a separate file to avoid such situation?Cheers
Hi,
AL rewrites BMS - FULL.key because:
- if the user launches BMS the first time after installing it, Viper.pop will be created and it defines FULL.key as a profile.
- AL can edit <callsign>.pop and change the selected key file to any other file. like: “BMS - AUTO.key” for AL use. I tried it and it worked.
- However, AL can rewrite key files, pop files, and axis settings only before launching BMS
- This means the first time we launch BMS with AL, AL doesn’t have a pop file to edit.
- Therefore AL can not provide a proper joystick setup for the first installation of BMS
- So AL can not work properly for their first setup of BMS and it should make “Huh? why it’s not working” troubles.
- I also tried generating pop files by AL but somehow it didn’t work well, maybe some format I tried to generate was not correct, and BMS recreate fresh <callsign>.pop that looks for FULL.key
I might need a help for generating a pop file with AL properly so that it can use a different key file than stock FULL.key.
-
@chihirobelmo said in Is BMS -Full.key file replaced/overwritten by U3?:
@maxwaldorf said in Is BMS -Full.key file replaced/overwritten by U3?:
I would emphasize on the fact that it is much needed to use a custom key file…
@chihirobelmo , this is an example where playing with stock BMS file through Alternative Launcher creates issues…
Maybe you should copy it and work on a separate file to avoid such situation?Cheers
Hi,
AL rewrites BMS - FULL.key because:
- if the user launches BMS the first time after installing it, Viper.pop will be created and it defines FULL.key as a profile.
- AL can edit <callsign>.pop and change the selected key file to any other file. like: “BMS - AUTO.key” for AL use. I tried it and it worked.
- However, AL can rewrite key files, pop files, and axis settings only before launching BMS
- This means the first time we launch BMS with AL, AL doesn’t have a pop file to edit.
- Therefore AL can not provide a proper joystick setup for the first installation of BMS
- So AL can not work properly for their first setup of BMS and it should make “Huh? why it’s not working” troubles.
- I also tried generating pop files by AL but somehow it didn’t work well, maybe some format I tried to generate was not correct, and BMS recreate fresh <callsign>.pop that looks for FULL.key
I might need a help for generating a pop file with AL properly so that it can use a different key file than stock FULL.key.
Hi, C. I figured there was a reason for how you set it up. And, IMHO, it’s a small price to pay. If I had known that Full was going to be rewritten, I would simply have saved it before U3. As has been written elsewhere, it is generally a good idea to back up important files. I’m used to that in config., the Full keyfile took me by surprise.
But in my case at least, the fix was painless. I simply launched via AL and all my switch/button assignments were there. That, BTW, is something else I like about AL. You can assign something to a switch or button and it doesn’t matter what key board assignment you use. All I had to do, again using AL, is to go through and reset keyboard commands I’ve changed.