U2 update config
-
When updating U1 we had to make some dev settings updates. I see that they have been reverted in U2. Are they still required?
-
no
-
@Badger thanks
-
@Badger
With two different config files, how are we going to know what’s relevant and what’s not? Where exactly will these obsolete options be documented?Will we be forced to follow every section of this forum to find out what is outdated and what is not?
This is the difficulty of having different configuration files, especially since the user.cfg is not reinitialized during an update (example U1 to U2). Very difficult to follow.
-
@101-Spyder the whole point of the user.cfg is that it won’t be touched by the update process, or config.exe tool.
The guidance was to put the post-release hacks/workarounds in ‘falcon bms.cfg’ and future updates would zero them out, as appropriate. I think U2 did that … no?
-
Ok, thank you airtex2019 for clarifying this point.
It will indeed be easy to follow up if each time an update is released, we assume that the “User Cfg” should “normally” be reset to be standard with the current version.
Thank you for this very important clarification, because this is very important as a commander of a virtual squadron so that all our members use a stable multiplayer configuration that meets our needs.
-
@airtex2019
My intervention on this subject simply makes it clear that as the commander of a virtual squadron, I must now ensure that each of my teammates in my squadron will manually perform the removal of option lines that have become obsolete and this each time an update is released, since this user’s file (Falcon BMS user.cfg) is not reset.It is an operation of verification of this file within all my members which must be carried out each time.
It is therefore a heavier administrative process than in the past when there are several members in a virtual squadron.
If the reset of the user configuration file were systematically reset to zero, it would be much simpler in my opinion, but I understand the principle.
-
Not here to complain. Just want to clarify: the entries in the user config file from U1 can be deleted right?
-
Falcon BMS.cfg should not be touched, unless the team tells you to do so. It will be overwritten by each release. User specific setting should go to the user file (for example, zoom level). So we will honor it and never delete.
-
@Seifer so for triple monitors I need 120 it goes here?
-
@spotdott
Yes, you must remove the two options lines in «Falcon BMS User.cfg» file, since U2. These two options in the «Falcon BMS.cfg» are now ok with;set g_sNonCompatibleChanges “all”
set g_sCompatibleChanges “all” -
@101-Spyder ok thx!!!