Mission Commander beta release
-
The editor reads the skinsets of squadrons after the start of the campaign, all values are set to 0. After saving in the editor with these values, all squadrons will continue to use standard skins. The values in the source files - save1.cam, save2.cam… show correctly. Is there a way to solve this, there used to be a camo.cfg file, but this MC build doesn’t use it anymore.
-
@ad02081985 said in Mission Commander beta release:
The editor reads the skinsets of squadrons after the start of the campaign, all values are set to 0. After saving in the editor with these values, all squadrons will continue to use standard skins. The values in the source files - save1.cam, save2.cam… show correctly. Is there a way to solve this, there used to be a camo.cfg file, but this MC build doesn’t use it anymore.
MC does not have the CAMO.cfg anymore as BMS doesn’t use it anymore.
Which skin is used by a squadron is stored directly in the mission file.
But it goes even a step further. You can set it for each aircraft in a flight. So you can have a 4 ship flight and each aircraft has a totally different skin.
All stored in the mission file.The editor reads the skinsets of squadrons after the start of the campaign, all values are set to 0. After saving in the editor with these values, all squadrons will continue to use standard skins
Not really clear what you mean here. What do you mean with values set at 0? Do you mean value you can see in MC
As long as you don’t change anything a squadron will always get the skin as it was set in the SaveX.cam file.
Don’t have time and need to check. Value 0 could mean pick random, but I need to double check that. -
@Falcas said in Mission Commander beta release:
Not really clear what you mean here. What do you mean with values set at 0?
-
@Falcas said in Mission Commander beta release:
As long as you don’t change anything a squadron will always get the skin as it was set in the SaveX.cam file
If nothing is changed in the MC, then the squadron skinsets will be as in the source files.For example, the 80th FS on the F-16 CM-40 uses a skinset with values of 6. After loading the campaign save, this value will be 0 in the MC and if you do not use the save in MC, the squadron will continue to fly with skinset 6.But if you use saving MC, from that moment skinset 0 will be applied and all squadrons of F-16 CM-40 fighters will use skinset 0 - 510th FS Buzzards.
-
@Falcas said in Mission Commander beta release:
Which skin is used by a squadron is stored directly in the mission file.
Yes, but after saving to MC, all values take on like this.
-
New version released, latest is now 0.5.23.735
Main- Possible fix for Win11.
Map
- Added, Filter selection for Land Units exact type.
- Changed, Make sure if multiple units are at the same location the Brigade will be shown (yellow infobox).
- Added, If multiple units are at the same position a “M*” is added to the yellow infobox to indicate multiple units.
Squadron
- Changed, Max Roster is now a button.
- Improved, For adding a Offmap Squadron the calculation can now be done for North, South, East and West coordinates.
Battalion
- Changed, Max Roster is now a button.
POL/PAK
- Fixed, CTD when clicking on the POL list.
- Fixed, Value color drawn in the wrong cell (Flags iso Prio)
- Changed, Better sorting of the number values.
TePlanes
- Added, Further checks for DogFight, DF_Flight.scf file.
- Added, DogFight check colors to List.
- Added, TePlanes list also checks DogFight IDs now. Including a nice management.
TeUnitList
- Changed, Adding a new TE Unit (Battalion) option to manually change values.
- Changed, Major overhaul of the system. Name now come from the strings.txt iso hardcoded
Strings
- Fixed, Correctly saving of strings.txt.
Stats
- Changed, Better sorting of the number values.
-
@Falcas possible bug in 735
When using the assign flight to other package feature the cancel / apply buttons are not visible. Therefore have to end program with task manager. -
@Badger
Thanks, will take a look -
@Badger said in Mission Commander beta release:
@Falcas possible bug in 735
When using the assign flight to other package feature the cancel / apply buttons are not visible. Therefore have to end program with task manager.Fixed, will be in the next update
-
New version released, latest is now 0.5.24.739
Units
- Fixed, Change package screen size.
- Added, Change Battalion and Taskforce now shows its vehicles.
-
Conversion from 4.36.3 to 4.37.0 for KTO was perfectly smooth with MC here.
-
Thx Falcas for the quick update for 4.37! MC is an essential tool for BMS!
-
I installed this latest version. Started it up and it defaulted fine to my 4.37 install but came up with error of Unable to create HDR. Have I done something wrong or is another update needed?
Thanks
-
Disregard this msg and continue.
-
Same warning.!
-
Ok thanks = will do.
-
Yep, just ignore for now.
Will come with an update soon. -
@Falcas Thanks
-
New version available, latest is : 0.5.25.743
-
@Falcas Helooo, long time no hear, happy new year.
Confirming , missing HDR message.
Also, I can see many, many, new very nice things, eg… brigade supply, AD protect… - for sure whole bunch were busy last year. Maybe BMS will become “Sims” (for ai calcs) in near futureNow for the fun part… Essence of NO_PLAN(ning)… how to.
From what I’ve reckon, in ATM, this forbids squadron relocation, and ok… not biggie here.
But how does it work in reality for GTM context? - forbids AD units relocation/moving = stationery? - why it is important (orange box) …
Many Thanks.
(btw, for future endeavors, … I can’t see the way to remove supply/protect unit from brigade, … if there’s need… can be deleted tho… so, low pri/no fix)