Daiwilletti
Charter Member
Whilst putting together a BOB campaign for ETO Expansion, I did a radical thing and actually read the campaign SDK .
Nothing like actually reading the manual once you've exhausted every other possibility :d. ****!!
Anyway, the SDK indicates it is possible to repeat the "layer" parameter as many times as you like in the GlobalLayer section, with a .lib file for each layer.
So that got me thinking: did the ETO Expansion Group consider simply including multiple .lib files in the Global layer folder, rather than having to run a .bat file to select a global layer before each run?
It would be possible for each campaign xml to specify a different .lib file - eg. BoB.lib. 1936.lib. etc.
The mission sdk also allows for multiple .lib files to be defined for missions.
I haven't thought this through as to implications for reducing the complexity of the .bat system used for ETO Expansion. Is there some limitation around the naming convention for the csv file?
Interested in any feedback, thoughts, etc
cheers
D
Nothing like actually reading the manual once you've exhausted every other possibility :d. ****!!
Anyway, the SDK indicates it is possible to repeat the "layer" parameter as many times as you like in the GlobalLayer section, with a .lib file for each layer.
So that got me thinking: did the ETO Expansion Group consider simply including multiple .lib files in the Global layer folder, rather than having to run a .bat file to select a global layer before each run?
It would be possible for each campaign xml to specify a different .lib file - eg. BoB.lib. 1936.lib. etc.
The mission sdk also allows for multiple .lib files to be defined for missions.
I haven't thought this through as to implications for reducing the complexity of the .bat system used for ETO Expansion. Is there some limitation around the naming convention for the csv file?
Interested in any feedback, thoughts, etc
cheers
D