Update on 4.35 U2
-
Thank you for the U2 update
-
Many thanks to the BMS team for your excellent work!
PS.
In version 4-35-1, KoreaObj.LOD file size = 2147 kb
In version 4-35-2, KoreaObj.LOD file size = 2501 kb
The change is significant.
Can anyone suggest which models (parents numbers) have been added or changed?I myself only discovered a change in some models of cockpits for the F-16.
-
**Seifer, thank you so much for your role in keeping us āin the loopā during this U2 update.
Iām in the middle of reconciling my falcon bms.cfg file. Could you tell me if the following line
set g_bStrictFogOfWar
has any effect whatsoever in this latest update? Thanks much.**
This one has been removed with 4.35 - no need for that anymore.
-
Many thanks to the BMS team for your excellent work!
PS.
In version 4-35-1, KoreaObj.LOD file size = 2147 kb
In version 4-35-2, KoreaObj.LOD file size = 2501 kb
The change is significant.
Can anyone suggest which models (parents numbers) have been added or changed?I myself only discovered a change in some models of cockpits for the F-16.
No significant changes (meaning no new model, only some fixes), it is only part of the process to update the 3ddb instead of rebuilding it from scratch (which is saving some space in the Incremental updates, we only rebuild the 3ddb from scratch in the major releases)
-
Heeere we goooo ā¦
:bdance::rofl:
Thanks for your hard work, and patienceā¦
Especially, @Seifer for PR
-
Thanks!!! Happy to have already seeded it to 1:22 ratio, and still going!
-
Thank you to the BMS team ! another super Update. It is very much appreciated by an old guy!
-
Thanks a lot for this big effort!!!
-
Just some critisim: In terms of falcon bms.cfg
My customers would kill me if I would build installers that completely reset user config files for just adding 2 lines or changing 3 existent values
so instead of complete overwritting a cfg file that is intended to be customized by the user I would advise to build the installer in order to add/edit parameters instead of completely replace it
I already answered at least 20 people on differrent channels why their display extraction is not working anymore. So most donāt read the instructions by the book.
Even worth with setting that might have been made by 3rd party to the cfg and the user has even harder time to find the root cause. i.e Having set multiple POV hats by AL
-
Just some critisim: In terms of falcon bms.cfg
My customers would kill me if I would build installers that completely reset user config files for just adding 2 lines or changing 3 existent values
so instead of complete overwritting a cfg file that is intended to be customized by the user I would advise to build the installer in order to add/edit parameters instead of completely replace it
I already answered at least 20 people on differrent channels why their display extraction is not working anymore. So most donāt read the instructions by the book.
Even worth with setting that might have been made by 3rd party to the cfg and the user has even harder time to find the root cause. i.e Having set multiple POV hats by AL
Fair point, I brought this discussion up. Weāll see.
-
Fair point, I brought this discussion up. Weāll see.
Hopefully as that issue can be achived at no cost/effort in a much user friendly way
-
The stick moves!!
-
The stick moves!!
Speaking of the moving stick. I always thought it moved just very slightly, barely visible. But in-game it moves rather much. Is that deliberate and a realistic representation?
-
Just some critisim: In terms of falcon bms.cfg
My customers would kill me if I would build installers that completely reset user config files for just adding 2 lines or changing 3 existent values
so instead of complete overwritting a cfg file that is intended to be customized by the user I would advise to build the installer in order to add/edit parameters instead of completely replace it
I already answered at least 20 people on differrent channels why their display extraction is not working anymore. So most donāt read the instructions by the book.
Alternative suggestion: instead of overwriting, rename the old one. falconbmscfg.old
Leave merge decisions up the end user.
Iām not a big fan of trying to make it foolproof, if only because there is always a better fool. Still, you could make it explicit: Have the new one added with the wrong extension, so you have a cfg.new and a cfg.old and warn the user on start that they need to merge and rename.
So thereās a few ways you could go about it that would avoid people getting stuck on display extraction stuff.
-
Speaking of the moving stick. I always thought it moved just very slightly, barely visible. But in-game it moves rather much. Is that deliberate and a realistic representation?
Difficult to tell but pretty close I would say.
-
Just some critisim: In terms of falcon bms.cfg
My customers would kill me if I would build installers that completely reset user config files for just adding 2 lines or changing 3 existent values
My āsimpleā solution to config file management for both BMS and DCS is git - easy to do diffs from git too and merge things back in.
-
My āsimpleā solution to config file management for both BMS and DCS is git - easy to do diffs from git too and merge things back in.
I personally run my whole BMS installation under git. But still the way BMS updates cfg changes is not the way I would be done in a proper way in software distribution process.
Gesendet von meinem SM-G930F mit Tapatalk
-
I personally run my whole BMS installation under git. But still the way BMS updates cfg changes is not the way I would be done in a proper way in software distribution process.
Gesendet von meinem SM-G930F mit Tapatalk
For sure. I was just suggesting ways for workarounds for users.
Sent from my iPhone using Tapatalk
-
Thank you everyone involved in the exe file and stuffs.
Also a great thank you to all the Devs tools, theaters and programs updates compatible for the new version.Best regards