Falcon BMS.cfg changes
-
@Bad-Boy said in Falcon BMS.cfg changes:
Don’t modify the Falcon BMS.cfg any more. Always add your new/modified lines into the Falcon BMS User.cfg file
I’ve changed the FOV lines in Falcon BMS.cfg, should I set them back to OEM and add those lines to my BMS User.cfg file? The cursor lines I will do so, just not sure if the User.cfg overrides the Falcon cfg file or it’s just the place to ADD new lines? The FOV works as it was in 4.35 now…
-
Read Technical Manual, chapter 3.1
-
@Icer said in Falcon BMS.cfg changes:
the User.cfg overrides the Falcon cfg
The User.cfg overrides the Falcon cfg, so if the same setting is in both files, the value from User.cfg wins
-
@jayb said in Falcon BMS.cfg changes:
@Icer said in Falcon BMS.cfg changes:
the User.cfg overrides the Falcon cfg
The User.cfg overrides the Falcon cfg, so if the same setting is in both files, the value from User.cfg wins
Thank you, I have set the Falcon BMS.cfg back to original and added all changed lines to the user.cfg file…
-
@Bad-Boy ehm, one caveat … just checked, if using old config editor (f4patch) via launcher , changes are saved in original config file, and not in new, user.cfg…
So… if not critical ok , just fyi.
Cheers
-
@white_fang said in Falcon BMS.cfg changes:
@Bad-Boy ehm, one caveat … just checked, if using old config editor (f4patch) via launcher , changes are saved in original config file, and not in new, user.cfg…
So… if not critical ok , just fyi.
Cheers
Thx for the heads-up @Bad-Boy, I did all my changes manually with Notepad+…
-
@white_fang not critical at all
-
@Bad-Boy said in Falcon BMS.cfg changes:
@white_fang not critical at all
Correct.
But I have a solution for that in the future -
@Kolbe-49th said in Falcon BMS.cfg changes:
First, of course you can change anything you want in the Falcon BMS.cfg. But like before, you might lose your personal settings with an update. Hence we advice to store your settings in the User file.
Regarding the problem you describe, as far as I know there are no differences between the files other than priority.
I’m telling you that if you put the lines for 2 POV hats in the user file it doesn’t work. Maybe it’s because those lines don’t exist in the falconbms.cfg file at all. But if the point of the user file to not have to touch the standard config file, doesn’t work for missing entries.
-
@Frederf I don’t know but it works for me…
Do you really think we skip those tests during beta testing?
-
@Frederf said in Falcon BMS.cfg changes:
@Kolbe-49th said in Falcon BMS.cfg changes:
First, of course you can change anything you want in the Falcon BMS.cfg. But like before, you might lose your personal settings with an update. Hence we advice to store your settings in the User file.
Regarding the problem you describe, as far as I know there are no differences between the files other than priority.
I’m telling you that if you put the lines for 2 POV hats in the user file it doesn’t work. Maybe it’s because those lines don’t exist in the falconbms.cfg file at all. But if the point of the user file to not have to touch the standard config file, doesn’t work for missing entries.
Not sure what you are referring to, but I can assure you my changes do work and the stock Falcon BMS.cfg file is back to as it was installed… This is my Falcon BMS User.cfg contents (I had to space here to avoid wordwrap, no spacing in the file of course) -
set g_sNonCompatibleChanges “all-DURANDAL-NC_CHANGE_DEAGGED_LOADOUT”
set g_sCompatibleChanges “all-C_CHANGE_DYNAMIC_SMART_SCALING”
set g_nAxisExp_AXIS_CURSOR_Y 70
set g_nAxisSat_AXIS_CURSOR_Y 0
set g_nAxisExp_AXIS_CURSOR_X 70
set g_nAxisSat_AXIS_CURSOR_X 0
set g_fDefaultFOV 120
set g_fMaximumFOV 160
-
@MaxWaldorf
I’m not trying to have an emotional event with you. I am telling you my Falcon BMS User.cfg looks like this///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
// User can place here his or her specific configurations lines that will superseed the main ones located in the Falcon BMS.cfg file //
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////set g_nNumOfPOVs 2 set g_nPOV1DeviceID 2 set g_nPOV1ID 0 set g_nPOV2DeviceID 3 set g_nPOV2ID 0
-
@Frederf said in Falcon BMS.cfg changes:
@MaxWaldorf
I’m not trying to have an emotional event with you. I am telling you my Falcon BMS User.cfg looks like this///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
// User can place here his or her specific configurations lines that will superseed the main ones located in the Falcon BMS.cfg file //
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////set g_nNumOfPOVs 2
set g_nPOV1DeviceID 2
set g_nPOV1ID 0
set g_nPOV2DeviceID 3
set g_nPOV2ID 0
This puzzles me.
Has anyone else also encountered issues with this? -
I mean… I have to use those little ones for the warthog and never had any issues…
Unless you’re not on windows but that’s another story
-
I use those lines in the user cfg and works.
-
Thank you.
But what is the problem for @Frederf then?
-
I have no idea. Here are my config files (2). When I delete the POV lines from the standard file the POV behavior changes.
https://www.dropbox.com/s/7qtfjk3nqfodo08/Falcon BMS User.zip?dl=0