Solved Falcon BMS user.cfg
-
The last 30 days I’ve been trying to make the Morphine profile that Gastone has designed for 4.37.
There was no way, despite the fact that I have reviewed the installation a thousand times, the profile did not work in 4.37, even Gastone no longer knew what to tell me.One step of the installation consisted of including in Falcon BMS User.cfg a line for a certain key (In the warthog, the paddle).
Today I deleted that line from Falcon BMS User.cfg and copied it directly into Falcon BMS.cfg and the profile has finally worked correctly.
Falcon BMS user.cfg has not worked according to page 12 of the Thecnical Manual.
Question: Does this file simply rewrite a certain line with the new values?
If this line does not exist in Falcon BMS.cfg and we only put it in Falcon BMS User.cfg, does the system understand that it must be used or, since it does not exist in Falcon BMS.cfg, does it ignore it?
Thanks in advance
-
@fvelazdem the stuff in …user.cfg overrides the stuff in …bms.cfg, which in turn overrides various built-in defaults.
I have a ton of stuff in my user cfg that is not in main cfg… even undocumented stuff. It all works fine.
I’ve seen people have problems with messed up doublequotes copied/pasted from web browser or email… and messed up comments or line spacing.
I don’t know what BMS does when it encounters that kind of thing, but apparently there’s no obvious error message, else we’d have seen it a few hundred times by now.
So the natural end result is people get confused and frustrated, and eventually move a line from one to the other, and then things suddenly start to work.
If you want to share your broken cfg files, zip them up and I’ll take a look. But so far I have never encountered anything that worked in one but not the other.
-
-
Thanks a lot.
Well now in my isntallation everything works. This issue created a lot of doubts on the new file: Falcon BMS User.cfg so I will not use it.
I have log file where I have all the modifications I do on Falcon BMS.cfg so is a matter of updating it each time I make a modification, is not a big job.
-
@fvelazdem Keep a backup copy of the ‘falcon bms.cfg’ (and everything in User/Config folder really)
Because when updates are downloaded, they will overwrite ‘falcon bms.cfg’ back to default.
-
@airtex2019 please be careful there. We do that on purpose. We ask fix to disable bits here and there so we can overwrite in the next version.
If ppl start backinup the file and overwriting when a new release happens, we’ll start having problems in the future.
-
@Seifer of course… it was not my intention to suggest they overwrite what new settings come in the update(s). I just don’t want to see any anyone lose work, unexpectedly (which was the whole reason behind the user.cfg in the first place).
Is there any conceivable reason why settings from user.cfg would not be applied? (line endings? text encoding? unicode bom header bytes?)
If the parser fails – either causing some lines to be ignored, or bomb out of the cfg parse entirely, prematurely – would that show up in mono log?
Is it possible to make a more immediately visible error message, at startup? (and also do this for key files :))
This is not first thread I’ve seen people adamant that stuff in user.cfg doesn’t work but when they modify bms.cfg, it does.
My conjecture is it’s all due to fancy unicode doublequotes, copy/pasted from the forum’s formatting… but that doesn’t explain why people are saying things work when they modify bms.cfg instead.
-
@airtex2019 yes, the way this works is:
read Falcon BMS.cfg and sets the variables. Then read Falcon BMS User.cfg in the same directory and sets all vars found (override). This is the same code, same function. No reason why one would work and the other would not.
Making the parser stronger and more user friendly is a good idea, I will write that down.