Cavtroop

not removed, just crippled. Anyone know how I can ambush in WEGO?

This happens to me almost 100% of the time now. The game is completely unplayable for me. Battlefront knows about this, but no news on when they anticipate a patch for the issue.

what the heck is this?

great news, thanks for the update

deleted - triplicate post! [ August 12, 2007, 08:58 AM: Message edited by: Cavtroop ]

deleted - duplicate post [ August 12, 2007, 08:58 AM: Message edited by: Cavtroop ]

I just ran a test mission myself. I had a Tall Stone Wall running through the map, and had 4 units (two red, two blue) 100m away from the wall on either side. Neither could see each other. I then told one unit from each red and blue to 'quick' towards the wall. At about the 50m point, the unit that did NOT move, could suddenly see the moving unit on the opposite side of the wall (remember, the terrain is perfectly flat, this should not happen). The stationary units then both opened fire, and the fire went right through the wall. By the time the moving units were at the wall, the stationary units had pretty much decimated them. Once the moving units reached the wall (about 5m from it), they started shooting at the stationary units. Through the wall. At no time could the moving units see or fire at each other. Something is very, very broken here, and this is another issue that makes the game both not fun, and unplayable.

I think the review is pretty spot-on, and similar to the review I gave the game. No terrain shading? Makes it very tough to see dips and depressions in the terrain. Needing a CPU patch? Funny, nothing else I run needs that. Crippled WEGO is the big killer for me. I have yet to figure out how to properly ambush in WEGO. I don't think you can, the proper features are missing. And the stability is very poor for me. I can't save or load most games without a crash, so the campaign is completely unplayable. and without any sort of usable Quick Battle functionality, I'm limited to battles. But the AI in most of the battles is broken, and just sits there for the duration. So those aren't fun, either. I haven't booted the game up in days, except to see if 1.02 fixed my crashing issues (it didn't). I still think this game has potential, but I'm not sure that BF is focused on making this the game that I want to play - a WEGO based wargame. We'll see. I'm not deleting it off my HD just yet, and sill give BF some time to fix the major issues they have. Hopefully they'll put out a gameplan on what they intend to fix/add, once they get the game working for the majority of people (8800 users?).

Yeah, I keep scanning the thread to see if anyone was in at the same place/time as I was. None yet, but still hope!

yeah, but playing in RT and just pausing frequently doesn't get you the replay. so in large battles, you can miss lots of interesting stuff going on.

Steve - Thanks for the input, good to know you are aware of it, and looking into it (even if it is obscure and difficult). Not sure if it helps, but I've seen this both manually saving a game in the middle of a battle (i.e.: for dinner or whatnot) and with the auto-save at the beginning of a campaign mission. Appreciate the reply! cav

rune - yes, thanks - just some kind of acknowledgment that its being looked at. appreciate it!

This game is so frustrating to me - I see a good game under here, somewhere. I even experience it from time to time, where I have a 30 minute stretch that I really enjoy it. Then one of the major bugs pops up - vehicles driving in circles, infantry running down the main street so they can go in the front door of a building rather than the covered back door, etc. Generally at this point, I'd turn the game off, but more often than not, it has crashed on me, so I don't need to. It looks like 1.02 will start taking care of the AI issues - but no word on the crashing that so many of us are having. My big problem with this whole process, is paying for what should be a beta release. And its not just BF doing this, it is endemic to the software world now, which is sad. Having said that, I'm giving this game a patch or two before I throw the baby out with the bathwater . There is a good game under here, somewhere, I hope. Edit: I didn't address the missing features of WEGO. I still can't ambush in WEGO. Are hiding/cover arcs/ambush markers on the way? that will go a long way to making WEGO more playable....

Bump for comment. support@battlefront.com told me to come here for tech support.

Steve - Any insight into the problems that some of us are having saving and loading games? I know you had mentioned that someone was sending you some files. I can't play the campaign at all, as any loads or saves are now crashing (see post in tech support forum). I'm excited about the 'defensive' AI improvements

if you have an ATI card (no idea if Nvidia has a similar option), disable the 'WMV acceleration' option in the Catalyst Control Center (It's in there somewhere). This can cause all kinds of problems with .wmv files. No idea if thats the issue here (the logo works fine for me), but its a thought.

Active duty 2.5 years. 19D 1990-92 Hq 3rd Bde 8th inf/1st Armored Division (got reflagged 1/2 way through). Was a gunner on a Bradley at the end. 90-92 National guard 6 years 1992 - 98 A trp. 1/110 Cavalry. M901 ITV commander/squad leader

Just FYI, I can't save any campaign mission now. it started with not being able to save every now and then, but every time it crashes out now, almost instantly.

Sure - Lenovo/IBM T60p ATI FireGL V5200 (same as X1600 mobile vid card) w/512MB ram Latest vid drivers striaght from IBM (I've tried various drivers, from omegadrivers, to ATI reference drivers, to various IBM drivers, same problem with all of them) 2GB system ram Centrino Duo processor I'm playing CMSF with the affinity set to one processor. I'm now completely unable to save ANY campaign game - it immediately crashes out with the info above. So basically, CMSF is completely unplayable for me.

This is getting crazy. I sent an email to support@battlefront.com, and you told me to come to the forums for help. I have, but have not received any tech support to date. Almost every time I same a mission after I complete a campaign battle, I get this crash. This means I have to reload an old, working save, and 'cease fire' until I get to the point where I was - or I could replay all of these missions, but that is tedious. Is there anyone from BF reading this, and providing any kind of tech support, or are we hanging out here on our own? Even just an acknowledgment that you've read this, and added it to your list would be nice. I know you are probably focused on the ATI/Visat/OpenGL issues right now.

Some missions hang for a loong time at 50%. others will not load at all, or crash. It seems totally random, though, I can't find a pattern.

Bump.

Bump.

Is anyone else having stability problems? A significant amount of time (probably 50% of the time) that I save the game between campaign missions (when it automatically saves), the game will crash out. This renders that save game useless, and I have to revert to an old save. Additionally, a significant amount of time I load a game, it crashes. And sometimes (probably 40-50% of the time) that I'm in a mission, CMSF will crash out, or sometimes simply hang. For the record, I am having zero problems with any other game or application (I'm a Systems Engineer in real life, and do this stuff daily). Every time, its the same thing: "CM Shock Force.exe has generated errors and will close" I get the following in my Event Log (application): Evend ID 1000 Faulting application cm shock force.exe, version 0.0.0.0, faulting module cm shock force.exe, version 0.0.0.0, fault address 0x000e1a39. 0000: 41 70 70 6c 69 63 61 74 Applicat 0008: 69 6f 6e 20 46 61 69 6c ion Fail 0010: 75 72 65 20 20 63 6d 20 ure cm 0018: 73 68 6f 63 6b 20 66 6f shock fo 0020: 72 63 65 2e 65 78 65 20 rce.exe 0028: 30 2e 30 2e 30 2e 30 20 0.0.0.0 0030: 69 6e 20 63 6d 20 73 68 in cm sh 0038: 6f 63 6b 20 66 6f 72 63 ock forc 0040: 65 2e 65 78 65 20 30 2e e.exe 0. 0048: 30 2e 30 2e 30 20 61 74 0.0.0 at 0050: 20 6f 66 66 73 65 74 20 offset 0058: 30 30 30 65 31 61 33 39 000e1a39 0060: 0d 0a .. Thoughts? FYI, Windows XP SP2, BF 1.01 download version. Also, I'm setting processor affinity to one proc. [ August 03, 2007, 04:52 PM: Message edited by: Cavtroop ]

All - Ive seen some people say their problem is fixed by changing the processor affinity after launching the game. It didn't help my crashing issues, but I thought I'd post this here. It's a utility that starts the game using only the 1st processor (CPU 0) on a multi-proc machine. I use it on XP, no clue if it works on Vista or not. http://www.activeplus.com/us/freeware/runfirst/ Basically, you put "C:\pathtorunfirst.exe\runfirst.exe" infront of the executable in the CMSF shortcut. It will start CMSF using only CPU 0, saving you from having to alt-tab out to set the affinity. happy gaming! [ August 03, 2007, 03:20 PM: Message edited by: Cavtroop ]