Deployment

Status
Not open for further replies.
You don`t have to incorporate the different Core Unit Files. There will be one Core Unit File for Axis and one Core Unit File Russians. Both seperate. The the game master can load up the Core Units Files for one side and then load the Core Unit file of the other side. Then both Core Units are in the Scenario Editor.
 
You don`t have to incorporate the different Core Unit Files. There will be one Core Unit File for Axis and one Core Unit File Russians. Both seperate. The the game master can load up the Core Units Files for one side and then load the Core Unit file of the other side. Then both Core Units are in the Scenario Editor.

As far as I know this can not be done. I tried this system in a campaign I once designed. If you want to use core units they both have to be in the same file.
 
That's just true for importing a Core Unit file in addition to already selected units on one side. For example you can't buy units for the Axis and THEN you want to import the Core Units (or campaign units as they are called I believe). Then the previous bought units are overwritten.
But you can import an Axis Core Units file and then a Allied Core Unit file and voila you got both Core Units in the editor. I tried it for a campaign I am designing by myself and just tried it again. It works.

Step by step explanation:
Open Scenario Editor
Adjust Mission parameters (date etc.)
Don't load a map you don't need it
Purchase units for one side
Save "Scenario" as for example RussianOOB
Do the same for the other side (with a blank "scenario" without the other sides units and call it GermanOOB
Open a new blank scenario choose parameters and the map you want to play on.
Import campaign units GermanOOB for the Axis (in Unit purchase screen)
Import campaign units RussianOOB for Allied
Now you just have to delete unused parts of the OOB! Also these OOB can easily be edited after the battles. And for a new battle you just load the edited OOBs. You can even add units to the OOB Core Unit later and save it as a new core unit file.

I tested it and it works like a charm but maybe I missed something and I am totally wrong.
For me it is the only way to deal with larger formations over the course of a operation and maintain something like continuity without a brutal workload.

@Ithikial : I uploaded two fake OOBs in the Russian Dropbox folder. Maybe you want to give it a try!
 
Strange because I did the exact same thing and it did not work. I shall give it a new try tomorrow. Perhaps they changed it with v3.0?
 
That's just true for importing a Core Unit file in addition to already selected units on one side. For example you can't buy units for the Axis and THEN you want to import the Core Units (or campaign units as they are called I believe). Then the previous bought units are overwritten.
But you can import an Axis Core Units file and then a Allied Core Unit file and voila you got both Core Units in the editor. I tried it for a campaign I am designing by myself and just tried it again. It works.

Step by step explanation:
Open Scenario Editor
Adjust Mission parameters (date etc.)
Don't load a map you don't need it
Purchase units for one side
Save "Scenario" as for example RussianOOB
Do the same for the other side (with a blank "scenario" without the other sides units and call it GermanOOB
Open a new blank scenario choose parameters and the map you want to play on.
Import campaign units GermanOOB for the Axis (in Unit purchase screen)
Import campaign units RussianOOB for Allied
Now you just have to delete unused parts of the OOB! Also these OOB can easily be edited after the battles. And for a new battle you just load the edited OOBs. You can even add units to the OOB Core Unit later and save it as a new core unit file.

I tested it and it works like a charm but maybe I missed something and I am totally wrong.
For me it is the only way to deal with larger formations over the course of a operation and maintain something like continuity without a brutal workload.

@Ithikial : I uploaded two fake OOBs in the Russian Dropbox folder. Maybe you want to give it a try!


Thank you for sharing this kind of information.
 
Ah I made a mistake in my previous posting.
The trick is not to import both campaign unit files.
Open Scenario Editor and load one of the files. For example GermanOOB.btt. Then import the Core Unit file from the other side in this case Russian.btt.
That works.
I am sorry for explaining it so complicated but it really isn't.
Create two separate btt files with the Units.
Load one of the btt files in the editor.
Import the second as core unit file.
Ready to go!

You guys are right that it is not possible to load two Core Unit files. but loading one as a scenario and adding the other via Import core unit works!
 
Ah.... if it overwrites existing purchases then we're in a bit of bother. It would delete all the fortification placements and destroyed vehicles already purchased and placed on the map.
 
If Ithikial has both sides' OOBs could he enter them manually into one saved game file based on the giant Radzymin map. Then for individual encounters just delete parts of the map and units where appropriate and save each scenario with a different name (eg Day 1, Turn 1, Encounter 1)? Once results form the various encounters are back in, the units in original 'grand' saved file could be modified to match the results of the last turn.
 
If Ithikial has both sides' OOBs could he enter them manually into one saved game file based on the giant Radzymin map. Then for individual encounters just delete parts of the map and units where appropriate and save each scenario with a different name (eg Day 1, Turn 1, Encounter 1)? Once results form the various encounters are back in, the units in original 'grand' saved file could be modified to match the results of the last turn.

It's not the purchase of the of units that's the issue. It's the placement of destroyed vehicles and fortifications which don't move for the duration of the campaign. (Which I think is one of the key features of our approach with this rule set. Give's the feel of a rolling series of engagements). I've always planned to have a master scenario file which I'm using to input terrain damage, destroyed vehicles and fortifications as the campaign progresses and then add on the active units for the engagement. If the active units are imported from a core unit file that's fine, but if it deletes the existing 'fixed purchases' then that means individually placing these every time. No matter how hard I try, I'm never going to get them in the exact same place which could be critical especially for something like trenches and TRP's etc.

The biggest reason we're looking at the Core Unit file is to maintain the 'little' settings like squad experience levels and names. If this is the only reason, it makes battle creation harder I don't think it's worth it. At least from my point of view as GM, not to mention it would dramatically increase the amount of time I need to get games ready for you guys to play. Especially later on in the campaign.

The Excel OOB is pretty detailed so I can see key details for company level units (platoons for tanks) and can use that as a shopping list on your behalf when creating a battle. Don't forget you have a column for comments if you need to inform me of anything specific.

If CMx2 had the same old feature from CMBB days of being able to import a saved game file map and units then all this wouldn't be an issue. :(

End of the day my suggestion, we use one core unit file for the force selection only if it doesn't delete existing purchases and positioning of items like fortifications and destroyed vehicles. Although I agree it would be a nice touch to be able to follow specific units across three days of battle, for something of this scale in the CMx2 engine, the specifics of each little squad are just not worth it. A few squads or individual vehicles going from Veteran to Regular status between two engagements isn't going swing the entire campaign. The decisions you make deciding objectives for your men each turn and putting them in practice on the field will.

Always teething problems with a new rule set. :D
 
Thanks for the long answer on this topic. I know what you are striving for. Especially with the destroyed vehicles on the map. This will be great. And I think this can be achieved. @Odin got I right. At least I hope it works that way. If @Dutch Grenadier and I deliver a OOB for our sides then both OOB can be loaded and the giant master map added. I could provide a OOB for a complete russian tank corps (that`s around 950000 points worth). From that pool we just tell which units we bring for the first 35k. The on day two we choose our 15k reeinforcements also from that pool. So bascially we would have, if Dutch also provides a bigger overall OOB (like for a Panzer Corps), a big pool of units to draw our units from.
Then fortifications are added and the master file saved. So all units are basically available and unused units can just be easily deleted (for example all exeeding units not used on day 1) and the map resized for different battles . After battles from turn 1 are over the original master files is loaded, unit casualties edited, map edited with the lost vehicles and saved. And we got a new master file for turn 2.

The more I think of it, playing with typical units (as we all want to achieve a semi-historical atmosphere) would be just possible that way. If not, unit experience from different units will differ from battle to battle. Explanation. Turn 1 you want to fight with Company 1 and 2 and both are manually purchased with typical settings. That gives you maybe a Green Company 1 and a Veteran Company 2. Now it`s Turn 2. Now Company 1 and Company 2 are purchased again. But this time Company 1 is a crack one and Company 2 a Green one. You could never tell which unit has which experience from battle to battle. So for example you can`t assign the best units to difficult tasks. You simply never know from battle to battle how good your units are. Kind of a lottery....

And I have to stress again: Thank you, thank you very much @Ithikial and @Odin you make all this possible. I really know how much work you have put into this project and your efforts can`t be appreciated enough! After we have straigthened out some small childhood ailments I think this will be great immersive experience for all of us!
 
Ah I made a mistake in my previous posting.
The trick is not to import both campaign unit files.
Open Scenario Editor and load one of the files. For example GermanOOB.btt. Then import the Core Unit file from the other side in this case Russian.btt.
That works.
I am sorry for explaining it so complicated but it really isn't.
Create two separate btt files with the Units.
Load one of the btt files in the editor.
Import the second as core unit file.
Ready to go!

You guys are right that it is not possible to load two Core Unit files. but loading one as a scenario and adding the other via Import core unit works!

You're correct, so I have to change my previous statement to: Importing a Core Unit file will erase ALL current Core units before inserting the imported Core Units. Doing it the way you describe above does work.
 
Has anyone else had the following issue when cutting the map down in the scenario editor to view it in 3D preview:

Once the map has been cut, you cannot expand it back to its original size in the map editor. The saved file will remember the terrain which has been cut, but to bring that part of the map back again, you have to cut part of the map somewhere else.

Does this happen to everyone else, or is there a way around it?
 
It does happen. Going to mean making sure the master map updated with terrain damage and destroyed vehicles is done first before importing the core unit file for each side. Think we can work around it but luckily I already have a large map in paint read to go to make manual markings if needed. Will only really know once we get started but I'm quietly confident.

Between engagements the GM will be required to:
1. Update the entire map with terrain damage.
2. Save. This become the most up to date master map in the editor.
3. Shrink the map down to the size required and import core unit files. Save each engagement separately.
4. Add the individual destroyed vehicles as required. (I already have a 120 mb detailed Paint.net canvas ready to go for this to record where vehicles are destroyed).
5. Tweak as necessary and add objectives etch.

The fortifications will probably have to be done the same as step 4 above which I was trying to avoid. However I'll record where you place them on this master map in Paint.net as well. Boy do I miss the CMx1 feature of importing maps from saved games now. :p
 
It does happen. Going to mean making sure the master map updated with terrain damage and destroyed vehicles is done first before importing the core unit file for each side. Think we can work around it but luckily I already have a large map in paint read to go to make manual markings if needed. Will only really know once we get started but I'm quietly confident.

Between engagements the GM will be required to:
1. Update the entire map with terrain damage.
2. Save. This become the most up to date master map in the editor.
3. Shrink the map down to the size required and import core unit files. Save each engagement separately.
4. Add the individual destroyed vehicles as required. (I already have a 120 mb detailed Paint.net canvas ready to go for this to record where vehicles are destroyed).
5. Tweak as necessary and add objectives etch.

The fortifications will probably have to be done the same as step 4 above which I was trying to avoid. However I'll record where you place them on this master map in Paint.net as well. Boy do I miss the CMx1 feature of importing maps from saved games now. :p

Phew! Glad you're doing all that ... (and a big thank you of course as well, that you are!)
 
Phew! Glad you're doing all that ... (and a big thank you of course as well, that you are!)

Hear, Hear - a big thanks

Just a quick question regarding forum threads, will there be one for each side to put up strategic planning/tactical analysis? It would rely on the other side being honest and not sneaking a peak, but I think something like that could be of interest to the wider FGM community.

Maybe if members of each side were banned by the moderator from reading the other's thread it would at least mean they would have to sign out of their account to look at the other's thread. This would prevent the opposition 'accidentally' clicking on the other side's thread (or doing so in a moment of weakness ;)).
 
Last edited by a moderator:
Hear, Hear - a big thanks

Just a quick question regarding forum threads, will there be one for each side to put up strategic planning/tactical analysis? It would rely on the other side being honest and not sneaking a peak, but I think something like that could be of interest to the wider FGM community.

Maybe if members of each side were banned by the moderator from reading the other's thread it would at least mean they would have to sign out of their account to look at the other's thread. This would prevent the opposition 'accidentally' clicking on the other side's thread (or doing so in a moment of weakness ;)).

What! We have to do strategic planning??? AND tactical analysis??? Sheesh! :D:D
 
Hear, Hear - a big thanks

Just a quick question regarding forum threads, will there be one for each side to put up strategic planning/tactical analysis? It would rely on the other side being honest and not sneaking a peak, but I think something like that could be of interest to the wider FGM community.

Um... that's why you have the separate Axis and Soviet HQ's. Start whatever threads you want in those sub forums. They are locked down so the only people that can enter are your teams mates and me as the GM.

Also thinking more on the mapping situation, I will make it work but may have to cut up the big map into thirds and work off those as 'the master maps'. All depends how the battles unfold once we get started.
 
Status
Not open for further replies.
Back
Top Bottom