tarball

Not hardly a resolution for anyone who perhaps has a new PC/laptop which came with Vista.

The web of problems is certainly entangled - however, I think you would want to isolate this combination as among the unique problems: ATI's OpenGL driver for Vista doesn't like the game. I am not too certain that the mouse-click-game-stops problem is as related to the processor.

The problem is this: A company the size of Battlefront is not likely employing a professional testing company to check for hardware compatibility. It would seem that missing among the beta testers was a single tester with this combo: Windows Vista 32-bit ATI Core 2 (although this may be less of the issue) This is the difference between a small-budget title and a larger title. Those of us in this boat - certainly a reasonable software/hardware combo - are truly up the creek for what might possibly be weeks. I can see how OpenGL would be great for cross-platform - unfortunately, OpenGL is a weak-spot for Windows Vista drivers.

H E L P ! ! !

This is the combo causing the problem - this is not an esoteric combination of gear. I think we're screwed until ATI becomes aware of the problem and incorporates it into one of the next Catalyst driver releases. Until then, this demographic of the customer base is screwed.

Battlefront, since you've combined my original problem thread into this one, could you change the title? This problem seems to be more related to those of us clicking on the game map than actually starting up the game. What we all seem to have in common is ATI OpenGL drivers not getting along with the game.

Most of the symptoms of those posting here seem to be related to OpenGL and ATI. There is another post in here about that issue - would you please also post there? The developer needs to know that a whole class of customers are not able to play AT ALL at the moment. Again, if you are running an ATI card and have lock-ups due clicking on a unit, you are experiencing a problem that is turning out to be common. Let's get the word out so that some relief is found quickly.

Sorry pal, the title has PROBLEMS - you'll have to wake up to that reality. All of the rest of us waited 4 years as well - Image that we too are sad and angry. I really liked CMx1 - it is difficult to like CMSF at the moment. The answers on this particular issue seem reasonable enough, but there is a chorus of issues at the moment and that is hard to ignore. [ July 27, 2007, 10:23 PM: Message edited by: tarball ]

Some followup: No amount of fussing with the settings in the Catalyst Control Center (which came with the 7.7 drivers) seems to be changing things. Anytime I click the mouse on the 3D map - things go sour. atioglxx.dll is the consistent culprit.

I should mention that, when I get the crash, the in-game cursor switches to the windows cursor. Someone else mentioned this behavior and it is replicable - each and everytime the game crashes on account of a problem with atioglxx.dll the "in game" mouse freezes and the "windows" mouse shows up.

KnockOnWood, would you mind posting your specs or, better yet, making a post in the technical support forum? I think some of us with ATI cards may experiencing this with the latest Catalyst drivers.

Changing to 1024 x 768 (32-bit color) made no difference in my case either.

My CMSF settings are default (desktop, balance, fast) My CCC settings are default (let app decide, etc.) ATI note regarding Vista: "Note: Because Windows Vista™ provides the same functionality as this option, VPU Recover is not available on systems running Windows Vista™. " So, I am uncertain if VPU recover is on or off. I am now realizing that it is an OpenGL game and I am aware of the benefits of OpenGL. Vista drivers seem to be OpenGL unfriendly.

I would like to chime in as well. I have all of the same symptoms as the other ATI people in this thread: I also get this in the error description when the game crashes: Fault Module Name: atioglxx.dll This is a show-stopper - the game is unplayable and my pre-order money seems wasted at the moment.

I am a pre-order customer - The game is absolutely unplayable for me (very disappointing). Requested Data: 1. I am running the Battlefront version (downloaded on 07/27/2007) 2. I have an Intel Core 2 X6800 Processor (2 x 2.93Ghz) 3. I have an ATI X1900XTX (Catalyst 7.7 drivers) with 512 of Video RAM 4. I have 2.0 Ghz of system memory. 5. I am running Vista Ultimate 32-bit 6. The EXACT problem is: When I am in the orders and planning phase with a unit selected, if I hit any movement orders button, the game crashes/freezes. The problem details are This is an OpenGL/ATI issue, but I wonder why DirectX wasn't used?

What about the international dateline? Zulu? EDT? "The 27th" is a bit vague when there's no brick-and-mortar.

Ordered and downloading as I type. Thanks

and now?

Moon, just about a month has passed, I'm ready with my money, can a full-download version be available soon?

Read this, the answer is plainly stated by the Marines: YES! http://www.military.com/forums/0,15240,79595,00.html EXERPT: ************************************************* Demolitions The majority of explosives used during the fight for Fallujah will not be mentioned here. The few that will be explained have the common theme of being obscure and may be forgotten if they are not written down. Each explosive device was developed in response to the enemy's tactics and has been proven to work. The following is a list of explosives, a description, and their uses: * "Eight ball." A one-eighth stick of Composition 4 (C4) explosives used for breaching both interior and exterior doors-effective and doesn't use a lot of C4. * "House guest" (named by 2d Squad, 1st Platoon, Company I, 3/5 (1/3/5). Propane tanks placed in the central hallway with C4 used to ignite them. Creates a fuel air explosive. Used for bringing down a house when contact is made inside. Propane tanks must be full. * A 60mm or 81mm white phosphorous mortar round, wrapped three times with detonation cord, and a one-quarter or one-half stick of C4. Used when contact is made in a house, and the enemy must be burned out. * Molotov cocktails. One part liquid laundry detergent and two parts gas. Used when contact is made in a house, and the enemy must be burned out. All Marines should be familiar with explosives and proper placement of the charge for breaching. Any Marine should be able to cut a time fuse, crimp a blasting cap, and put the blasting cap in C4. *************************************************

You have my attention...

This so reminds me of some of the horror stories people have shared with me about offshoring/outsourcing: "...We just can't get this through to Bangalore... they don't understand" "...Why can't the Kiev team get on this?" Again, I'm not hypothesizing, these are complaints I've heard over beers with buddies who have to deal with this sort of thing. Perhaps Battlefront is learning more about publishing 3rd party titles. I'll personally stick with the Combat Mission titles in the future as I believe they are in-house affairs.

I'll hand it to Martin and Madmatt, they seem to care about the freezing problem. However, now that it's been 3 or so months since I bought this (I didn't wait for the demo, my bad), this thing is really not any closer to being fixed. too bad. Something wasn't effective about the beta testing done on this as this show-stopper seems to bufuddle defy fixing. Craq, I shelved this two months ago and have added to my "learn from experience file." Let's face it folks, this title is in the small-time sales category and battlefront is essentially a "boutique" or "mom-and-pop" operation. If you are a part of the 10% (perhaps the number is even lower than that) of us who are just stuck with this, keep in mind that such a percentage is almost an acceptable "error rate" in terms of gauging the success of this title. I'll admit that I bought the title only at being frustrated at the endless wait for Steelbeasts Pro PE. So, again, Kudos to the publishers for trying (I believe they are honest and sincere). However, I wouldn't hold my breath on this one folks. It's clear that things are at the grasping for straws stage now. Greetings to those for whom this title works, seems like you're having fun.

Just some feedback readers... Matt is a very straight-up individual and level-headed about all of this. There's just a small minority of us that are mostly out-of-luck at the moment. While I'm bowing personally, I'd like to say that Matt and Martin have been really good, of late, at owning up the facts on this title. I express my appreciation for this. You'd never get this kind of consolation with a large publishing house. Good luck with the tanks all, J-

Thanks for all the discussion. Let's face it folks, there's a small cohort among us who are just not going to be able to run this title at this time. As others have said, no amount of twiddling and tweaking is going to amount to much. I don't know what the root of the problem really is, but I'm personally out of this game. Battlefront have been very good at owning up to this problem with me personally and I'm just going to throw in the towel and wash my hands of this problem. While I believe the publisher has responded to me in good faith, I have no confidence in this developer and wish to cease any support for them post-paste. I guess I've been around long enough to know that when it walks like a duck and quacks like a duck, it's a duck. By this I mean, to me, the air with this title smells foul and I've had a noseful by now. Hey, if it patches and all is right with the world, y'all have fun with it. Life's too short for me to taste bricks like this. The T-72 software's off my drive and I'm leaving this one behind in the "bad experiences" pile. Kudos to the publisher for being upstanding in the face of adversity. For us 1%ers, this title's a wash. J- [ August 23, 2005, 09:36 PM: Message edited by: tarball ]