No, really, ...I came to the conclusion that the best way to take advantage of your new development is to use it as a basis for new campaigns using all the new maps, planes, that it will allow us to employ.
Legacy campaign sets, that involve only the components available on its time (stock), would only deserve your valuable time if you could fix them with ease. It´s not the case; I think now that anyone revisiting legacy material would have to spend an amount of time that does not pay the effort, and would divert you from the relevant task: The upgrading of the new Dgen itself.
One of the reasons why some of the old campaigns don't start in the new DGen is, that the new version is less tolerant to mistakes in the campaign files than the old Dgen. It is sometimes just a minor mistake in a single file that is causing these incompatibility issues. If they are found, a corrected version of the campaign file can be added to the next release of Asura's DGen, this was already done for a mistake in the Coral Sea subcampaigns.
Let's use the problem with the Africa campaigns you had reported as an example. I have taken a look at the files and noticed, that the campaign builder made a small mistake in the last line of the db files:
"[Operations] <<ops41afr.dat"
There are two blanks after [Operations] instead of one. Remove one of the blanks and the campaigns will work correctly.
I have uploaded the corrected files here:
http://www.axis-and-allies-paintworks.com/Skins/Juri_JS/Africa_fix.zipJust put them in you DGen folder. Maybe Asura can include them in his next release.
It would be a great help, if people could report other campaigns that don't start in the new Dgen, so we can check them systematically for such mistakes.
Author
Topic: Project DGen_mod (Read 377061 times)
