Comments on 4.37.2 release
-
Thanks on behalf of all for these regular updates. May I suggest:
The 4.37.1 update *.exe was formatted as “Falcon BMS_4.37_Update1.exe”
The 4.37.2 update *.exe was formatted as “Falcon BMS_4.37.2.0_Update.exe”I think formatting consistency, especially with filename formats, is important for several reasons. There was no reason to format the .1 and the .2 filename updates so differently. There is also no reason to use a space character between ‘Falcon’ and ‘BMS’ as a separator, then start using an ‘_’ character for the rest of the filename as a separator. Further, underlines are never a good idea as a separator because they are hard or impossible to see if the entire filename is underlined for whatever reason or put in a bordered textbox. A space character is perfectly legitimate now that we are beyond MS-DOS, and should be used for clarity, or a ‘-’ dash character as a poor second choice.
So I would suggest one format or the other. Either
Falcon BMS 4.37.1.0 Update.exe
Falcon BMS 4.37.2.0 Update.exe
Falcon BMS 4.37.3.0 Update.exe, etc.which I recommend, or
Falcon BMS 4.37 Update 1.exe
Falcon BMS 4.37 Update 2.exewhich I don’t recommend, but at least it’s consistent.
Secondly, there was a warning that the Falcon bms.cfg has been changed, but no mention that all of the F4Patch selections have also been reset to default values. That would have been good to know.
By the way, why
‘Falcon bms.cfg’, but
‘Falcon BMS User.cfg’???Why is bms all lowercase in one and all UPPERCASE in the other? Again, consistency is more professional and clear. Why not
‘Falcon BMS.cfg’ and
‘Falcon BMS User.cfg’ -
@SoBad said in Comments on 4.37.2 release:
Why is bms all lowercase in one and all UPPERCASE in the other? Again, consistency is more professional and clear. Why not
-
Oh, man…
If you have installed the update and not found out yet, almost every config & setting has been restored to their default settings, including your custom keyfile!
If you haven’t updated yet, and you don’t have detailed notes somewhere of all your custom settings, I strongly suggest that you cover your butt before downloading this update. The only thing the update announcement said was that there was a new ‘falcon bms.cfg’ file, but it goes far beyond that.
-
-
@SoBad
Quickly…The update name change is due to a major change to the update process.
I am no able to do hotfixes within an update if needed (which was not the case before)So the format will remain 4.XX.YY.ZZ Update for a while.
Now to be honest it doesn’t matter at all because the offline updater is almost not used and everything will be done throught the updater executable.Since windows isn’t case sensitive, I don’t think the case format matter much in the end.
I won’t extend too much on this topic as I consider it more cosmetic than anything else.
And in the end, the only problem you have is the naming convention… I would say that we made a very good progress…
-
I will tap this very lightly, I suspect for the old hands this was not a big deal, a year from now it might not be for me too
But being what 3-4 weeks in and just getting bms, heilos and VA working and everything kind of sorted so i can practice starts and takeoff/landing, nav , the very basic stuff… It really tossed me into a tail spin trying to figure out “what I just broke” and where I F’ed it up… what ever changed seemed to break jan-jan and heilos profile It caught me off guard.
-
Re: Comments on 4.37.2 release
I agree that naming convention consistency is mildly important, but not as important as all the amazing work these guys do to improve our experience in this sim. Huge Thank You to the BMS Team. You guys ROCK!
NOTICE: there are a few AI Commands/ATC Commands/Approach…etc. command changes that affected my Voice Attack Profile.
I am working on * Many* Voice Attack Profile changes to get my Voice commands to work properly. Dancing my way to the stars!I’m not complaining, just advising.
There have been many changes in the AI Commands/ATC Commands/Approach Commands order of communications…For instance when requesting overhead approach from Approach, I now get radar vectors instead. Not a mistake on their part at all, but a bit of a workload challenge for me to get my Falcon back to normal.
The CFG changes to defaults are a bit of shocker too, but easily overcome; just a few more steps added to the “dance”.
I can’t wait to enjoy the improvements.
Thanks guys!
-
Thanks for the new update.
I only have a small problem with it, maybe someone can help me out .
If I click the updater in the launcher it says that please download the downloader application.
But I already did it last time . So why not recognize the downloader application or why not start download the new update straight the updater ? -
@repvez look here in the troubleshooting bit (Updater.exe Update).
https://wiki.falcon-bms.com/en/start-with-falcon-bms/install-update
-
Just want to thank the devs again. Our hobby wouldn’t be possible without you all.
-
@SoBad said in Comments on 4.37.2 release:
If you have installed the update and not found out yet, almost every config & setting has been restored to their default settings, including your custom keyfile!
Other than the need to update the updater, I had no issues with my keyfile except that the default “BMS - Full” profile was loaded in setup. It was just a matter of loading “BMS - Auto” and I had all my previous settings back. Mind you I do set all my key-binds via the Launcher so that might be a factor.