Jump to content

JaguarUSF

Members
  • Posts

    205
  • Joined

  • Last visited

Everything posted by JaguarUSF

  1. I didn't need to do this once I uninstalled the Dual Core Optimizer, but here is how you do it: 1. Run the game. 2. Press CTRL+ALT+DELETE to bring up Task Manager. 3. Go to the Processes tab. 4. Right click on CM Shock Force.exe 5. Select Set Affinity... 6. Uncheck one of the boxes.
  2. I'm curious which scenarios specifically you are talking about. Go into the scenario editor and check the AI plans for the side that doesn't seem to be moving.
  3. I am using all caps because I am shouting: UNINSTALLING THE DUAL-CORE OPTIMIZER FIXED THE LOCKUPS
  4. I am using all caps because I am shouting: UNINSTALLING THE DUAL-CORE OPTIMIZER FIXED THE LOCKUPS
  5. Are there any files in your Quick Battle Maps directory? Other than that, I have no idea what the deal is.
  6. Changing the affinity did not solve my lockups (in fact, it made it worse). Changing the trilinear optimization did not solve my lockups either. Here are my system specs (I don't think I've posted them before): 1. Battlefront 1.01 2. AMD Athlon 64 X2 4200+ 3. nVidia GeForce 8800 GTS 320 MB version 162.18 4. 2 GB RAM 5. Windows XP Home Edition SP 2
  7. Changing the affinity did not solve my lockups (in fact, it made it worse). Changing the trilinear optimization did not solve my lockups either. Here are my system specs (I don't think I've posted them before): 1. Battlefront 1.01 2. AMD Athlon 64 X2 4200+ 3. nVidia GeForce 8800 GTS 320 MB version 162.18 4. 2 GB RAM 5. Windows XP Home Edition SP 2
  8. Do you have the Battlefront or the Paradox version of the game? The training scenario is included in the 1.01 patch, which, if you have the Paradox retail version, can be downloaded here .
  9. Did you guys see this post? http://www.battlefront.com/discuss/ultimatebb.php?ubb=get_topic;f=70;t=000013;p=2#000034
  10. I also turned Threaded Optimization OFF and I'm still getting the lockups. My mission of reference is the first turorial mission, by the way. [ July 28, 2007, 06:14 AM: Message edited by: JaguarUSF ]
  11. For reference, here are my settings for my GeForce 8800 GTS (and I am getting the lockups): Anisotropic filtering OFF Antialiasing - Mode OFF Error reporting OFF Extension limit OFF Force mipmaps BILINEAR Multi-display SINGLE Texture filtering - Anisotropic OFF Texture filtering - Negative LOD bias CLAMP Texture filtering - Quality QUALITY Texture filtering - Trilinear optimization ON Threaded optimization AUTO Triple buffering OFF Vertical sync FORCE OFF I also have vert sych and antialiasing OFF in the game. Made things a lot smoother.
  12. OK. Try: Battle Type = Attack Environment = Open Leave everything else alone. Or you could set both Battle Type and Environment to random.
  13. Actually, it looks like I was having two overlying problems, one that got corrected in 1.01, and another that everyone else is seeing that they are working on now. They think the corrected problem (which had to do with models) was overlapping the second problem that everyone, including myself, is now experiencing. Rest assured that they are working on it, going so far as trying to secure a similar computer configuration to get to the bottom of this nonsense
  14. See this: http://www.battlefront.com/discuss/ultimatebb.php?ubb=get_topic;f=70;t=000035
  15. See this: http://www.battlefront.com/discuss/ultimatebb.php?ubb=get_topic;f=70;t=000035
  16. Which specific movement command are you using? If you are expecting enemy contact, "hunt" is pretty much the order you want to use. Or "fast" if you want them to dash into a building and hope they don't get shot.
  17. Did you click on the wall you wanted to blow up? Getting the blast command to work correctly is difficult when there are a lot of buildings or walls around you...takes some practice and precision targeting with the mouse.
  18. The bottom line is: don't play Quick Battles as single player games It's not the same as the QBs in previous CM games (which I almost exclusively played myself). Do the more scripted and more enjoyable battles instead.
  19. Yeah, pathfinding can be quite wacky. Feel free to upload the scenarios wherever, as long as you don't alter the file.
  20. There are victory conditions you can use to simulate this. Commonly, I assign unit objectives for the opposing side, say 100 points for the HQ and 50 points for each platoon. The game will give "partial credit" for destroying some of each of the unit objectives. So, here's what I would do to simulate what you have said: 1. Make a short time limit, like 20 minutes 2. The attacking force's only objectives are unit objectives of the opposing team. 3. The defending force gets a friendly bonus parameter (set in the scenario editor) equal to 75% of the possible points the attacked can get. This would mean the attacked would have to destroy 75% of the enemy to earn a draw.
  21. You can set up a meeting engagement or assault in a forest, but NOT an attack or probe. Check the very first option for battle type.
  22. Were you shooting through the door or windows?
  23. The AI for quick battles is scripted very generally, since the designer doesn't know what units will be involved: it's basically a "set up here" and a "move here" order and that's it.
×
×
  • Create New...