Jump to content

76mm

Members
  • Posts

    1,366
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by 76mm

  1. I am in violent agreement with kipanderson--not to beat a dead horse here, but there is, ahem, a very vocal minority which is very interested in being able to edit saved games either via data import/export or another editing the saved files directly. Steve cited the need to avoid cheating in PBEM games as a reason to encrypt scenario files, but (not to open this can of worms again) how many people play PBEM? What about selling a PBEM module to enable PBEM and otherwise leave scenario files unencrypted? I don't care about creating hordes of Hamstertruppen, but I would very much like to be able to save and manipulate basic OOBs from completed scenarios. I realize that this is all probably much more complicated than I imagine, and that decisions on these matters have almost certainly already been taken, but I wanted to at least raise the issues... 76mm
  2. I am in violent agreement with kipanderson--not to beat a dead horse here, but there is, ahem, a very vocal minority which is very interested in being able to edit saved games either via data import/export or another editing the saved files directly. Steve cited the need to avoid cheating in PBEM games as a reason to encrypt scenario files, but (not to open this can of worms again) how many people play PBEM? What about selling a PBEM module to enable PBEM and otherwise leave scenario files unencrypted? I don't care about creating hordes of Hamstertruppen, but I would very much like to be able to save and manipulate basic OOBs from completed scenarios. I realize that this is all probably much more complicated than I imagine, and that decisions on these matters have almost certainly already been taken, but I wanted to at least raise the issues... 76mm
  3. Dear Steve; Thanks for the response. From my perspective, what you guys are doing makes a lot sense--I still play CMBB extensively but virtually never play the Rumanians, Hungarians, or some of the less common German/Soviet types (even if knowing that I COULD play them if I wanted to is very cool), and as a non-grog I don't really care much for the difference between the four types of BT-7, etc. That said, I have three suggestions: 1) You make it as easy as possible for non-Battlefront parties to coordinate with you to release new modules, with these other parties bearing the risk. It sounds like given the vast number of periods/theaters that the new engine will open up, Battlefront alone will never have the time or interest to bring out the "Rumanian" module or the "Sedan 1940" and hundreds of similar modules that would make the game a real gem for a multitude of small audiences. My concern is that even vetting/tweaking/releasing these types of modules would take up too much time for you to consider it worth your while. I have no problem paying for modules, but I am concerned that the selection will ultimately be rather limited. 2) In a related point, for many modules, it seems like much less additional programming, etc. would be necessary. For example, if an "East Front" module consisted of a Stalingrad period To&E, etc. it seems like you wouldn't need to do much to release a "Barbarossa" module covering 1941-1942--just add the new vehicles, etc. It seems like this would be much less work than, say, a D-Day "On the Beaches" module, with amphibious vehicles, funnies, etc. Hopefully these "easier" modules would be released even quicker than the more complicated ones. 3) Consider including data import/export in a "Developer's Module" or something--just as long as I can get it, I don't care how! 76mm
  4. Dear Steve; Thanks for the response. From my perspective, what you guys are doing makes a lot sense--I still play CMBB extensively but virtually never play the Rumanians, Hungarians, or some of the less common German/Soviet types (even if knowing that I COULD play them if I wanted to is very cool), and as a non-grog I don't really care much for the difference between the four types of BT-7, etc. That said, I have three suggestions: 1) You make it as easy as possible for non-Battlefront parties to coordinate with you to release new modules, with these other parties bearing the risk. It sounds like given the vast number of periods/theaters that the new engine will open up, Battlefront alone will never have the time or interest to bring out the "Rumanian" module or the "Sedan 1940" and hundreds of similar modules that would make the game a real gem for a multitude of small audiences. My concern is that even vetting/tweaking/releasing these types of modules would take up too much time for you to consider it worth your while. I have no problem paying for modules, but I am concerned that the selection will ultimately be rather limited. 2) In a related point, for many modules, it seems like much less additional programming, etc. would be necessary. For example, if an "East Front" module consisted of a Stalingrad period To&E, etc. it seems like you wouldn't need to do much to release a "Barbarossa" module covering 1941-1942--just add the new vehicles, etc. It seems like this would be much less work than, say, a D-Day "On the Beaches" module, with amphibious vehicles, funnies, etc. Hopefully these "easier" modules would be released even quicker than the more complicated ones. 3) Consider including data import/export in a "Developer's Module" or something--just as long as I can get it, I don't care how! 76mm
  5. Wow! tom_w, thanks for the thread. The game/module idea sounds like it will work great to me, unless the game and subsequent modules are just too narrow...For instance: --I think I understand that a game might focus on a theater such as Normandy (fine) rather than a battle such as St. Lo (too narrow)? --In a Normandy game, would we have access to Winter weather / ground conditions, or would that have to wait for the "Bulge" module? I would hate to wait several months/years before being able to gin up some DYI winter scenarios... --I haven't seen any discussion of my favorite topic--data import/export capability (to allow for better player-designed campaign tools) or being able to modify TOE, etc. via XML or text files--any news on this? 76mm
  6. Wow! tom_w, thanks for the thread. The game/module idea sounds like it will work great to me, unless the game and subsequent modules are just too narrow...For instance: --I think I understand that a game might focus on a theater such as Normandy (fine) rather than a battle such as St. Lo (too narrow)? --In a Normandy game, would we have access to Winter weather / ground conditions, or would that have to wait for the "Bulge" module? I would hate to wait several months/years before being able to gin up some DYI winter scenarios... --I haven't seen any discussion of my favorite topic--data import/export capability (to allow for better player-designed campaign tools) or being able to modify TOE, etc. via XML or text files--any news on this? 76mm
  7. I have had this happen with large scenarios; I think it might be memory-related. Usually it works again if I exit CMBB and enter again, or worst case, if I reboot. TMR
  8. Pyewacket, sorry for the dumb question, but what exactly does your dll do? Can it only be used for editing maps? 76mm
  9. Isn't there also an issue about the size or width of turrets not being taken into account, leading to too many hits on thinly armored, but narrow turret fronts? Thought there was a thread on that some time ago... 76mm
  10. OK, I'd like to post as someone that plays exclusively solo. First, I suspect (but have no more data than the other posters on this issue--ie, none) that the author of the article is right that most games are played in solo mode. I play solo because I want to play when I want to play. I don't want to take weeks to finish a PBM game-I would just lose interest. I have been meaning to try some TCP/IP games but haven't gotten around to finding an opponent, etc. Also, sometimes I'll start a game and find that for whatever reason I don't want to finish, and I can just abort the scenario without a lot of angst from the other player. While the quality of games against the AI is not consistently good, on occassion it can really give me a run for my money; one of the chief reasons I terminate games early is if the AI blunders too much too early and makes the game uninteresting. tmr
  11. Dear John: I share your enthusiasm for Heckman's book, and several excerpts from it are included in the Reader. Tom
  12. Dear Beady: Thanks for your comments. In response: 1) The companion was never really intended to provide an overall history of the Mediterranean campaigns, but rather a series of snapshots of tactical encounters similar to what would be encountered in CMAK. That said, a few people have mentioned this point, and if I do any future volumes I would probably include more of a summary (very summary) covering the operational/strategic context of the tactical engagements. 2) I agree that the readings are weighted toward the English/American sides, much more so that I would have liked. But I had two problems: first, I had a hard time finding readings I liked in the various German/Italian materials that I found (and frankly, I didn't find all that many, especially for the Italian theater. Second, the bigger problem was that it is much harder than you might expect to find the orignal copyright holders for a lot of this material, and to get permission to reprint even if you found them. This was really, really hard, and I had a couple of great source books that ultimately I had to abandon because I couldn't get permission... Hope you enjoy the book anyway! Regards, Tom
  13. Dear danbob: Thanks for the kind words; I am very proud that my humble volume has earned an honored place in your personal reading sanctuary. Good luck in the game; the idea for the book was that people would actually be able to apply the tactics, etc. described in the book to their gameplay. Happy Turkey Day! Tom
  14. Dear Japanzer: I changed my resolution to 1024x768, but the mouse continued to jump. Also, I paid more attention to what happened with the scenario, and it appears that the program is opening an existing scenario ("A Deadly Affair", this time) rather than generating a new one based on the CSV files. I've been working on something that might complement your work. Please send me your e-mail and I'll try to send you a copy. 76mm
  15. OK Japanzer, Now I'm really having problems. I tried to run ScenarioCVSReader.uws, and loaded parameters.csv, alliedunits.csv, and axisunits.csv. CMBB launched into a quick battle or scenario which did not seem to correspond to the units in axisunits.csv or alliedunits.csv. Moreover, I basically lost control over my mouse (it was leaping all over the screen) until I ctl-alt-dlt to shut down UWSC.exe. Kind of frustrating. I am running XP Pro. Suggestions? 76mm
  16. OK, success there, thanks...I'll sure I'll have more questions as I go. Tom
  17. Sigh...I ran the check and it shows that many directories don't exist: AxisListDir, AlliedListDir, German directory, Soviet Directory, and Paramter directory. I then installed the Grand Campaign thinking that it would install these directories, but it did not. I'm really interested in this tool but at this point maybe I'll wait for the non-beta version...any idea when that will be? Tom
  18. OK, still trying here...downloaded uwsc, loaded ScenarioCSVsReader.uws clicked through a few dialog boxes, then it asked me to choose the "CMBB Directory"--is that the main directory or scenario directory, or what? Either way when I clicked OK I got an error message saying "C/enigma/uwsc28d/cmbbpath.txt could not be written to." What now? TMR
  19. Dear Japanzer: I don't seem to have UWSC.exe, although I have ScenarioCSVsReader.uws. Am I supposed to download something else? Thanks, 76mm
  20. Dear Japanzer: Sorry, but I don't see the Scenario Reader file...is it a seperate downloaded file? On your website I see Solo Grand Campaign, Scenario Maker beta01, and Scenario Shuffler...where is the Scenario Reader? It sounds very useful! 76mm
  21. Dear Japanzer: I tried running the Scenario Maker but received a message box announcing an "HSP Error", which also included some gibberish--any idea what the problem could be? 76mm
  22. Japanzaer: I've downloaded your program, but before I install it, could you explain more what it does? Can I use it to import units into CMBB? TMR
  23. From what I saw in my research for the CMAK Companion, many US units left the .50 cals in the unit trains and only used them in established defensive positions such as Anzio--they were just too heavy to lug around, and LMGs and MMGs gave maneuver units sufficient firepower. Tom
  24. Yes, this is similar to what I had in mind, but I always prefer printed versions, and I also would like to have more than just the data in the web tables--stuff like unit costs & availability dates, etc. Just wondering if I'm the only one? Tom
×
×
  • Create New...