Page 2 of 2

RE: heartache

Posted: Thu Aug 30, 2007 11:54 pm
by Richrd
What I had been doing up to now is modifying the units one at a time so that I didn't screw up the event list. I guess what I have to do now is start a new scenario with nothing but an OOB. The OOB work I can do, it's computer skills I lack. So my object is to create such a credible OOB that someone will be willing to help me get it into my own game. Here goes. Charles Sharp's books are a great resource, but they don't go below brigade level. 'Boevoi Sostav Sovetskoi Armii' gives OOB info down to separate battalions for every month, but only unit names and numbers.

RE: heartache

Posted: Fri Aug 31, 2007 12:09 am
by SMK-at-work
And I believe its in Russian??[:(]

RE: heartache

Posted: Fri Aug 31, 2007 9:51 am
by Monkeys Brain
ORIGINAL: SMK-at-work

And I believe its in Russian??[:(]

battalion level to fit in 2000 units limit hmmm very hard to do

I know that both German and Soviet OOB is wrong. Authors had to do much of improvisation. As I read books on Eastern Front I have seen that German OOB is also wrong - esp. later years. They did much of the shuffling, rehabilitations, etc... also they had collection of smaller units just like Russians - they are not in the game only partially.

RE: heartache

Posted: Fri Aug 31, 2007 10:25 am
by golden delicious
ORIGINAL: Richrd

Start from scratch it is. Is there any way to depopulate the force list without having to click delete for each and every unit?

Well, as has been said, this isn't necessary, but:

Start a new scenario, create one unit and formation per force. Export the OOB. Open the scenario you want, import the OOB. Voila- a (mostly) blank OOB.

Even if you weren't going to do that, you can cut chunks out of an OOB pretty fast with repeated use of the "cut formation" menu item. Much faster than deleting the units one by one.

RE: heartache

Posted: Sat Sep 01, 2007 11:52 am
by pete1967
I know this is late to help you salvage your work now, but for the future, install and use either Subversion (http://subversion.tigris.org/project_packages.html) or CVS (http://www.wincvs.org/download.html) (Subversion being more modern and better in general) that way you not only have backup, but also you can go back in at any point in history of your modifications. You also only need to backup the database to an external media and restore it and you still have full revision history at your disposal.

They may look daunting at first sight, but trust me, for simple use they are not.