Jump to content

Mad Mike

Members
  • Posts

    350
  • Joined

  • Last visited

Everything posted by Mad Mike

  1. I'm quite sure it means "zur Verfügung", which I would translate to "under direct/immediate control". In this case, it means that the 95. Infanteriedivision was not under operational control of a corps HQ (normal case), but under direct control of a higher HQ (in this case 3. Panzerarmee).
  2. Nope, you're quite correct and this is a weak point of ScAnCaDe. But I was never able to properly figure out the location of the core unit file information in the final campaign file.
  3. Hi Tempestzzzz, as the creator of the tool you're using, some comments and (hopefully) help. First of all, I would urge you to not use the CMBN_Scenario_Organiser_v0.22 any more. It is quite ancient by now (released 2011) and has been superseded by CMx2 ScAnCaDe. RockinHarry has already provided a download link to the last version of ScAnCaDe, which also works pretty much in the same way as the previous Scenario Organiser. Secondly, it is entirely possible to re-compile campaigns, it just requires a little bit of extra work. You already found out about having to rewrite the campaign script. It shouldn't be too difficult since basically ScAnCaDe provides all the required info in a different format. What ScAnCaDe does not provide is the Core unit file used to originally compile the campaign. This means that the original campaign briefing will be missing from the recompiled campaign, since this would be included in the Core unit file. I think you can take a copy of any scenario file of a campaign and just use it as the core unit file. This will not necessarily give you all the core units, but it should be good enough if you don't want to change the troops too much. Out of interest, I did decompile the Devon - Basic Training campaign. This gave me the following three scenario files (using CMx2 ScAnCaDe v1.8): Devon - Basic Training #00_Bn Cmpn 01 Out on Patrol.bttDevon - Basic Training #01_Bn Cmpn 02 Firing Range.bttDevon - Basic Training #02_Bn Cmpn 03 Battle Drill.bttI then renamed those files as follows, since there could be problems with the "#" or "_" characters in the filenames: Bn Cmpn 01 Out on Patrol.bttBn Cmpn 02 Firing Range.bttBn Cmpn 03 Battle Drill.bttI then copied the first file and renamed it Devon Core.btt, which represents the core unit file. Then I used the following script: /* Campaign Header*/ [PLAYER FORCE] blue [HUMAN OPPONENT ALLOWED] no [BLUE VICTORY TEXT] You won! [BLUE DEFEAT TEXT] You lost! [RED VICTORY TEXT] You won! [RED DEFEAT TEXT] You lost! /*Battle #1*/ [BATTLE NAME] Bn Cmpn 01 Out on Patrol [WIN THRESHOLD] draw [NEXT BATTLE IF WIN] Bn Cmpn 02 Firing Range [NEXT BATTLE IF LOSE] Bn Cmpn 02 Firing Range [BLUE REFIT %] 0 [BLUE REPAIR VEHICLE %] 0 [BLUE RESUPPLY %] 0 [BLUE REST %] 0 [RED REFIT %] 0 [RED REPAIR VEHICLE %] 0 [RED RESUPPLY %] 0 [RED REST %] 0 /*Battle #2*/ [BATTLE NAME] Bn Cmpn 02 Firing Range [WIN THRESHOLD] draw [NEXT BATTLE IF WIN] Bn Cmpn 03 Battle Drill [NEXT BATTLE IF LOSE] Bn Cmpn 03 Battle Drill [BLUE REFIT %] 0 [BLUE REPAIR VEHICLE %] 0 [BLUE RESUPPLY %] 0 [BLUE REST %] 0 [RED REFIT %] 0 [RED REPAIR VEHICLE %] 0 [RED RESUPPLY %] 0 [RED REST %] 0 /*Battle #3*/ [BATTLE NAME] Bn Cmpn 03 Battle Drill [WIN THRESHOLD] draw [NEXT BATTLE IF WIN] [NEXT BATTLE IF LOSE] [BLUE REFIT %] 0 [BLUE REPAIR VEHICLE %] 0 [BLUE RESUPPLY %] 0 [BLUE REST %] 0 [RED REFIT %] 0 [RED REPAIR VEHICLE %] 0 [RED RESUPPLY %] 0 [RED REST %] 0Then using the scenario editor (in CMBN v3.11), I could create a campaign file, which after decompiling showed the exact same structure as the original campaign file. I hope this helps, campaign compilation is sometimes not so easy due to the minimalist feedback you receive as a user. Cheers, Mike
  4. Two scenarios that came with the module have snowy conditions: A Temple to Mars: Weather: Blizzard Temperature: Freezing Ground: Patchy Snow The Keep of Majella: Weather: Flurries Temperature: Cold Ground: Patchy SnowAt least one user made scenario has been made with snowy conditions: Di Saronno: Weather: Flurries Temperature: Freezing Ground: Light SnowDownload here, for example (couldn't find it on the Senario Depot): http://www.theblitz.org/scenarios/b-15.htm?action=download&id=11191 You can always make scenarios with "full" snow conditions, so these weather / ground options are not restricted to QBs. Btw, if you're interested in information about the scenarios without having to open them individually, you could always give my program "CMx2 ScAnCaDe" a try. For download link see my signature.
  5. I'm currently reading "Snow & Steel - The Battle of the Bulge 1944 -45" from Peter Caddick-Adams. I find it to be very well written, it gives a good overview from both sides, including short biographies / background on principal commanding generals. It also has some first-hand accounts, which are presented as little snippets in the overall narrative. Quite well done, IMHO. I'm currently at around page 200 and the battle hasn't started yet. It's a very thorough account of the circumstances and the setting of the offensive. Highly recommended.
  6. This bug has been around since the release of CMBN, and yet this is the first time I see it recognised as such, including a workaround. Well done, Vanir Ausf B.
  7. Well done, agree with most of what you've written. It's just that you seem to miss my point: Whoever translated this, intended "Halbe" to mean "half speed". That's the only way this whole sentence construction as it stands in the translation makes sense. There is no "Der Halte" in German. "Der Halt" would be the closest, correct equivalent. I guess this all is a case of a translator with mediocre understanding of German translating the original into English, which then in turn has been translated back into German. Would be interesting to see the original, maybe someone can provide a scan?
  8. I don't think the original is flawed. It says: There should be only two speeds for a tank: half speed (for firing) and full throttle. "Halbe" does not mean "halt" or "stop" and it is not a typo. The reason it can't be a typo is quite logical: Nobody would refer to a halting tank as having any speed at all, it does have no speed since it is standing still. So when point 8 refers to two speeds, this does by itself exclude standing still. Don't try to overthink this or make it more complicated than it really is .. it simply means what I wrote above and it was also meant to say this.
  9. Bulletpoint, can you confrm that this is the QB map pack you are referring to: http://www.battlefront.com/index.php?option=com_remository&Itemid=314&func=fileinfo&id=1716 If so, I had a look at these and the maps are not the problem. They have all been created with CMBN v1.01. Also, the submission date into the repository (beginning of 2012) is clearly before either the CW or MG module even were released. The maps do not require any module to be present in order to play with them. My guess: The AI force selection is somehow "broken" by being allowed to select forces for which you don't have the module. This does not seem to be a problem for playing straight away (there seems to be no check for available modules as there is when loading a saved game). So my guess so far: Bug in the game. But I'm sure Ian will take a good look at it and report it if it is a real problem.
  10. There is a modtag [mainland] for CMFI, which should be doing what you're after. It would be great if these "system defined" modtags could be listed and explained somewhere - i.e. in the manual. Has been asked for before, maybe one day..
  11. Thanks Ian, so it works as expected, meaning it will decompile the campaigns and it can handle the files, it just doesn't recognize all the data / parameters. That is not surprising, since I have to code these into the program. But I'm not going to do this for CMBS, since I don't own it.
  12. You won't find the "original" Scenario Organisor anymore, since it became obsolete with ScAnCaDe and I have removed it from GaJs site.
  13. For the latest version - v1.8 - of CMx2 ScAnCaDe, follow the link in my signature. It will work for all current WW2 games. No idea if it will work for CMBS though.
  14. H2H campaigns only work for Hotseat, NOT PBEM. Since this is the case, H2H campaigns are a non-starter. This has been established in some other threads, which I can't find at the moment.
  15. It's true that ScAnCaDe won't extract the campaign script file, since this file is only used for campaign compilation (construction of the .cam file). It is not saved in its original text form anywhere in the .cam file. However, ScAnCaDe will extract all the relevant information which is contained in the original script file and present it in the "Campaign_Listing.xml" file. It should be easy to use this information to create your own campaign script file. Or to say it with Walter White (Breaking Bad): "Apply yourself!"
  16. Thank you very much, GaJ. By far the best tool ever produced for CMx2.
  17. Thanks for the kind words, I'm happy that the tool is of use to some.
  18. Hi all, I've released an update to CMx2 ScAnCaDe, which now recognises the new versions CMBN v2.20 and CMFI v1.20, so this is only a minor "housekeeping" release. Download at the link in my signature. Cheers, Mike
  19. Hi all, I've released an update to CMx2 ScAnCaDe, which now recognises the new versions CMBN v2.20 and CMFI v1.20, so this is only a minor "housekeeping" release. Download at the link in my signature. Cheers, Mike
  20. Hi all, I've released an update to CMx2 ScAnCaDe, which now recognises the new versions CMBN v2.20 and CMFI v1.20, so this is only a minor "housekeeping" release. Download at the link in my signature. Cheers, Mike
×
×
  • Create New...