Jump to content

chrisl

Members
  • Posts

    2,098
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by chrisl

  1. I'm using a PB G3/300, 192 MB, OS 8.5, and was having trouble with CM bailing out to the desktop the first time it loaded graphics, but subsequently loading fine and not showing fog or transparency. I turned off a bunch of extension (Norton, OpenGL), and restarted. No effect. A few hours (and several restarts later), I restarted in 640x480 and it suddenly stopped quitting to the desktop and started showing transparency! (Yes, I had cycled through all the switches, and left them in the transparency settings, which is why I got smoke, fog, and buildings all at once)

    I've since turned all the extensions back on and even restarted in 1024x768 and it all still works. I don't understand, but I'm not going to complain.

    The machine has a RageLTPro,with I think 4 MB VRAM.

    My drivers:

    ATI MPP Manager 1.0

    ATI Resource Manager 1.2.4

    ATI 3D Accelerator 4.3.6

    ATI Driver Update 1.4.6 (I think 1.4.8 started all my troubles...)

    ATI Graphics Accelerator 3.4

    ATI Video Memory Manager 7.5

  2. Play the demo a little more. I can only play in 640x480, and it's still awesome. It's not going to compete with the Emotion Engine for graphics on your laptop, but the graphics are just the icing on the cake. The game system underneath is really awesome, and has unlimited replayability (because of the possibilities for scenarios).

    Play a little more and you'll get hooked like the rest of us.

  3. <BLOCKQUOTE>quote:</font><HR>Originally posted by iggi:

    The problem with all those hexgames that looked really cool was all those rules.The host of errata and the various interpretations.They were good for thier time.

    <HR></BLOCKQUOTE>

    Turns out that later in life it was useful to have played games like SL with so many rules, but most of them were pretty simple. Longest Day only had a few pages. With SL you could pick which rules you were using, and many of the rules only applied to limited circumstances (Ghurkas, etc) and you could read them again just before the scenario.

    That said, now I'd rather let the computer worry about the details of the rules.

  4. <BLOCKQUOTE>quote:</font><HR>Originally posted by tailz:

    Does anyone else here have AH's The Longest Day? Now there is a monster! Days just to set up... kitchen table (not for the map... just the support sheets!)

    <HR></BLOCKQUOTE>

    Always thought it was cool, but never got to play. It cost too much for a 14 year old when it came out, and the geometry of the board wasn't quite right to work in my mom's basement.

  5. I've assaulted a few and they aren't very frightening. They have little cover for the crew and a squad of riflemen can make them bail out.

    One caveat--I've been doing it in night or foggy scenarios where I can get really close without coming under fire. At long range they could maybe make a mess.

    [This message has been edited by chrisl (edited 07-06-2000).]

  6. Some of each.

    The units pause at some waypoints because of command delay. If you give a unit a set of orders in one turn that takes it to the tree line, then another set in the next turn to crawl onward to somewhere else, there will be a pause at the waypoint at the treeline, even if the units don't get there until a few turns later. If you gave the full set of orders in one turn there will be no pause.

    You can take advantage of this. In an attack I usually give units orders to go quite far, sometimes enough for 4-5 turns, especially for a platoon sent around the flank. Usually one half-squad will be moving slightly ahead of the rest to draw fire, while the rest will have paused slightly and be sneaking along behind, ready to provide covering fire.

    All of the orders will originally be sneak, but as areas are identified as clear I'll change the orders to move, or even fast, as there is no command delay for changing the type of movement. I'll also reroute the existing waypoints slightly as enemy positions that might have LOS from other flanks are revealed. There's also no penalty for grabbing and moving a waypoint slightly, just a limit on how far you can move it.

    Always keep your units in C&C as much as you can. They'll be more responsive and get benefits (stealth, combat, etc) that will help the attack. Also, if they're in C&C you'll be less likely to have the lead squad sneak over a small hillock and disappear in a hail of gunfire that's backed up by the fog of war.

    For climbing a steep embankment I'll put waypoints very close together, same as for careful maneuvering of armor in close quarters. Micromanage the positions, but let at least some of the units pick their own targets-- if something pops up and everyone is sticking to their assigned targets you could be unhappy.

    [This message has been edited by chrisl (edited 07-06-2000).]

  7. Stole this naming convention from Robert Hall:

    [scenario abbrev][Player1 initials][player2 initials][file creator](Movie)[turn number with leading zeros]

    e.g.

    The turn 3 orders created by the German played by Robert against me would be

    VoTRHCLGE03.txt

    The US player then puts in orders and creates movie named

    VoTRHCLUSMovie03.txt

    This lets you sort by name and have nice lists of files by each player. It is a little confusing in that files are labeled by the side that created them, and not the side that can watch them.

    [This message has been edited by chrisl (edited 07-06-2000).]

  8. My background is not only hex based, but cardboard. I never got into computer wargames (I find it odd when people here sometimes talk about wargaming as if it were a solely a computer thing). I would really rather not go back. I can play a full game of a fairly large scenario in less time than a single turn used to take, and without taking up a 4x8 foot sheet of plywood in the basement.

  9. I lost some Elite Paratroops because they got it into their feeble little elecronic heads to charge an MG42 (LMG) position. I also had an MMG spontaneously pick up and move into a victory location house to provide covering fire for some guys advancing alongside the house. A fine line between bravery and stupidity.

  10. <BLOCKQUOTE>quote:</font><HR>Originally posted by grunto:

    oh no didn't he get something like 2 vehicles and a gun? i didn't see his half-squad cargo but i think his was the lead t8 which came around the corner and almost... almost got past the 37mm aa. it looked like he was going to start firing his mg again but the 37mm got him just as he was running past.

    is that the same murphy you're talking about?

    andy<HR></BLOCKQUOTE>

    Same Murphy, and that was someone elses T8, since Murphy was almost out of ammo. I double checked and he doesn't get credit for the first gun-- I think it was a greyhound behind him that got that.

  11. I guess you weren't watching Cpl Murphy's T8 all that carefully...

    I think the guys you slaughtered under your halftrack had ridden up on Murphy's T8.

    I'm starting to really like the T8, except the ammo load is *way* too small. How can a vehicle be that heavy and carry so little MG ammo? I realize it's not supposed to park and get into a standup MG battle, but even driving fast and shooting at things that pop up you run out of ammo really fast.

    [This message has been edited by chrisl (edited 07-04-2000).]

  12. I've been having this problem pretty reliably with my PB G3/300, also 192 MB. The odd thing is that it almost always loads properly the second time (and later). I usually launch, load, crash, launch, load (the PBEM, bit the autosave), play. It seemed to develop only after I defragged my hard drive with Norton. I haven't had the patience to sit down and track down the problem. It's not ideal, but it works.

    I've been suspecting the control strip, since it tends to want to write to the screen on top of CM (and manages to do so in the set up and editor). I had some problems also with norton disklight that seemed consistent enough to turn off disklight.

    [This message has been edited by chrisl (edited 07-02-2000).]

  13. Yes, it's the "Ohmygod the're everywhere" and they're usually all King Tigers, too. I've gotten used to it-- you have to take it seriously, but also with a big grain of salt. I think better troops are more reliable, but sound contacts usually aren't worth shooting at, except with arty if you have plenty to go around.

  14. This brings up a something I've been wondering about: How well does the AI know and understand turret speed differences? Sometimes when a Panther suddenly appears at close range the best thing to do is charge past it, rather than pop smoke and retreat. I can't imagine a green crew doing this, but vets or higher might be able to.

×
×
  • Create New...