aleader

You may be right, it may not be for me. My post may come off like I'm a wargame noob, but I'll match my record in CM PBEM victories against anyone's...ok, maybe not Fionn's . I'm just saying that soaking up the sun in an Abrams waiting to be attacked by suicide bombers might not make for the greatest gaming experience one can envision. Slamming T-72's in SBPro with M1's is realistic when playing the Easting scenarios, but it gets old pretty quick. Much more interesting is squaring off in a MP match with M1's vs Leopards, or even T-90's on a well-designed map. I'm not saying SF won't be a stellar game, but make me a believer. You're right, an AAR may go a long way towards that Steve. I suspect though that TOW (the long-awaited 'what Close Combat could have been') may be more what I've been pining for. And I was referring to the US attacking Syria to shore up security so that IRAQI oil may flow smoothly...to benefit the IRAQI people of course

This has probably been hashed over ad nauseum somewhere else on the site, but a search didn't turn up what I was looking for. That being some assurance that this game won't be like the IRAQ thingy over there. I don't really feel like fending off suicide bombers, booby traps, and hasty ambushes all game. I also can't see the fun in endless missions consisting of rooting out rag-tag groups of terrorists. I can understand sticking to the realistic conflict, but it doesn't strike me as 'fun' to play. A real war with Syria would be more of the same: army gets wiped out in a week, next 10 years spent 'rebuilding' (i.e. securing neigbour's oil supply ). So I guess what I'm getting at is will there be the option to play QB's with similarly matched forces\equipment? I'm thinking Leopards\T-90's vs M1's, large scale battles, not just urban search and destroy missions. I love modern equipment and the choice BF made to go there, so can someone please allay my concerns :confused: ?

Ok. I just emailed it to you.

I'm running the new demo and I get a total freeze on the screen right after the splash screen. Thought it may be Zone Alarm so I shut it down, which allowed me to ge past the splash screen. I can get to the initial screen (with the options tabs) but then get a total freeze and have to do a hard reboot every time. The sound starts during this time and the mouse cursor moves but I can't select anything, and after 30 secs or so the sound cuts out too. Can't Alt-Tab or CTRL-ALT-DEL or anything. My system: Athlon 64 3000+ Radeon X1600Pro w\Catalyst 6.5 1GB OCZ DC Ram XP SP 2 DFI Lanparty UT NF4 MB

I've now tried pretty much every combo of AA\AF in-game and out with no luck. Reducing the refresh rate (in the game config) from 85 to 75 seemed to help, but it still pulsates...just the gunner view!? Very frustrating.

I don't know if that's it Moon. I get the exact same error every time I run the game. It didn't start until about the 3rd or 4th time I ran it, and now it comes up each and every time. I don't get the error with any of my other games.

Ok, thanks. I'll try it and report my findings. Of note, it doesn't always happen right off the bat. I can sometimes shoot a few (or several) rounds before it starts pulsing. It only happens in the gunner view, which seems pretty odd.

Great, nice to get some answers. Are there any plans to fix this in an upcoming patch? Seems like a pretty glaring omission to leave joystick mapping out of a tank sim. Any answers for my previous question regarding the 'pulsating' gunner view? Known issue? Planned fix? Can't be fixed?

I'm having the same joystick problems. It's keeping me from buying the game until I get an answer (and once the 30% discount on downloads is over, I won't be buying it . Support seems pretty sparse for this game.

Thanks for the help. Anyone having the 'shaking' gunner view problem? I don't see any option to adjust water or dust detail levels. 'Add dust' (yes\no) is the only option in the list. What is with water and ATI cards anyways!? I have the same issues in Pacific Fighters with water...it looks like crap on ATI cards (it can only be set at level 2 on ATI cards). Here I thought I was getting a decent, modern card. What's with the joystick mapping? I noticed someone else has asked that same question in the forum. I really want to buy this game (I'm starving for a tank game that isn't as complex as SB Pro PE), but some of these issues are showstoppers for me (joystick mapping, shaky gunner view). [ June 16, 2006, 10:06 PM: Message edited by: aleader ]

I've been getting the exact same error recently with the 1.3 demo. I use a joystick and turning left hasn't been an issue.

Not much action in tech support, so I've moved it here hoping for a response: Just d\l the 1.3 demo for my new rig: -Athlon 3000+ -MSI X1600 Pro - 256MB -1 GB OCZ Premier DC Ram -DFI Lanparty UT NF4-D -XP with SP 2 -Saitek X45 throttle and stick -ATI 6.5 reference drivers Tried the demo and it runs pretty fast on the highest settings at 1024x768, 2X AA, 8X AF, but the water (when fording) acts funny. It looks ok (like a silvery oil slick actually), but it moves veeery slowly, even though the rest of the action is fairly fluid. Also, when firing in gunner view (F6), the dust cloud brings the frame rate to a crawl. Is this the case in the final version? What settings can I adjust to increase the frame rate in relation to the dust? Is this system really not fast enough!? A much bigger problem is the 'pulsating' in the gunner view. When in this view, the area within the 'circle' pulsates rapidly in and out, obviously making it very difficult to aim\fire. I've changes several settings, including disabling AA\AF and turning detail down to 'high', but it's still there. Leaves the game broken really if I can't use this view. I've had trouble programming my Saitek in-game as well. I click the key in the menu to assign it, and then the button on my stick, but nothing happens. Am I missing something?

Been playing it some more. Found the config option and I've been playing with the settings to get a reasonable frame rate. One LARGE issue I'm having is 'pulsating' when in the gunner view (F6). The screen shakes in and out continuously when in this view. Doesn't so it in any other view. Suggestions?

Just d\l the 1.3 demo for my new rig: -Athlon 3000+ -MSI X1600 Pro - 256MB -1 GB OCZ Premier DC Ram -DFI Lanparty UT NF4-D -Saitek X45 throttle and stick - Tried the demo and it runs pretty fast on the highest settings at 1024x768, 2X AA, 8X AF, but the water (when fording) acts funny. It looks ok, but it moves veeery slowly, even though the rest of the action is fairly fluid. Also, when firing, the dust cloud brings the frame rate to a crawl. Is this the case in the final version? What settings can I adjust to increase the frame rate in relation to the dust? Is this system really not fast enough!? Is there a FPS counter that can be turned on anywhere? I've had trouble programming my Saitek in-game as well. I click the key in the menu to assign it, and then the button on my stick, but nothing happens. Am I missing something?

Same here (with 1.3 demo). I don't get an error, the game just won't start at all. I install, run the .exe, a screen comes up asking me to purchase the game, I hit 'Purchase Later' and nothing happens. The purchase screen disappears and I drop to desktop. This is on a brand new computer with XP. Any thoughts?

Agreed. I'm a CM freak, but after playing a little Battlefield 2, I'm wetting myself waiting for CM:SF to come out!

I have some good sound mods for explosions(specifically 200 - 231.wav) in CMBB that are in 16-Bit stereo (mp3's). They need converting, otherwise they corrupt the sound in the game. How do I do this? I checked the "16 bit mono" box when converting in CDex, but it didn't work. Any suggestions?

Ok. Thanks guys. I'll play around with them. No way to make one uninterrupted movie of an entire battle eh (on the PC, not Mac)? Other games have replay features, I don't see why this couldn't be considered for CM 2. I can't think of anything cooler than watching the full-length battle unfold after it's over! :eek:

By stringing the turns together or something? I'm thinking QuickTime or some other method? I seem to remember reading that it's possible somewhere. Does anyone know?

Don't feel bad Tank Ace...I found the whole CMMOS thing confusing as well...and I am computer savvy I don't even bother d/l the CMMOS mods because they never seem to install properly. If it was just 'unzip to here, press this button' I probably would, but it's far more complicated than that. Maybe it's improved since CMBO (I haven't tried it with CMBB yet). [ July 27, 2003, 12:26 PM: Message edited by: aleader ]

I didn't have problems with text until just recently when I installed the 3.6 drivers. Now I can't see any text after I end a PBEM turn and have to name it. I'll try that text patch.

Schrullenhaft: you're a god!! I applied the VIA latency patch and voila, sound fixed! I'd heard of the patch before, but didn't realize that it was a sound fix. They also have another file that disables the Turbo mode on the SB cards if the patch doesn't fix the problem. It's like having a whole new computer! Thanks for all the tips everyone!

How do you know which one is selected? I just figured the secondary may be screwing up my sound (that other thread I have running here), so I disabled it. Didn't help though.

Yes, I did that already, and did all of the Windows Updates. My brother-in-law had an interesting suggestion. He thinks it may be the jumper settings on either the sound card or MB. That's what I'll try next when I get a chance.

It lists no conflicts, but I can't imagine why they would both need to share the same IRQ. In any event, I should be able to change the settings if I wish. Something just doesn't seem right. I just finished pulling BOTH cards, only putting the Video card back in, installing the video drivers, etc., and then I put the sound card back in, and it still assigned the sound card to the same IRQ (12) as the video card. I've looked through my CMOS settings, but I can't find anything obvious in there. I'm using an ABIT KT7 with the newest BIOS. I'm at a total loss here...