Solved Temporary fixes for 4.36.0
-
Hello
Should the following two lines be deleted: in the “falcon bms.cfg”
set g_sCompatibleChanges “all”
set g_sNonCompatibleChanges “all-DURANDAL”after adding :
set g_sNonCompatibleChanges “all-DURANDAL-NC_CHANGE_DEAGGED_LOADOUT”
set g_sCompatibleChanges “all-C_CHANGE_DYNAMIC_SMART_SCALING-C_CHANGE_STORE_DAMAGE”Thanks
-
@Rouge1512 Use only the lines given by the team…
Only when U1 comes out can you remove those lines…
-
-
Thank you for the answer.
But I’m not sure I understand.
What does “only” mean here?
H1: we have to remove the lines set g_sCompatibleChanges “all” and set g_sNonCompatibleChanges “all-DURANDAL” to leave ONLY the lines given by the team?H2: you should ONLY put the lines given by the team and do nothing else, so do not delete the lines set g_sCompatibleChanges “all” and set g_sNonCompatibleChanges “all-DURANDAL” which already exist?
Thank you for clarifying this a bit more.
Anyway, at the next release, shouldn’t the bms.cfg config be overwritten?
-
@Rouge1512 To be clear…
ONLY keep the lines mentioned in:
https://forum.falcon-bms.com/topic/22302/temporary-fixes-for-4-36-0 -