Gurra

It´s already wavs.

I reckon MikeT wrote something about that a while ago, but I have been unable to find the post when searching. Does anybody have a clue? CMMOS just tells me that it´s unable to locate file or something.

You almost did it a couple of days ago, in World Cup...almost...as usual. It was a great game, wasn´t it?

Ignore. I have found it.

Where can I find it? Someone knows? :confused:

Well, except for the fact that there´s no King Tiger in CMAK, I´d say go for this game. There are so many improvements over CMBO, and there´s a lot of Western front scenarios to download already, with many also yet to come, I suspect. And moreover, I suspect that with time, there will be top notch mods for Western front too. I think Tanks a lot has some buildings in progress, along with Tom's upcoming Battle of the Bulge mod.

Well, except for the fact that there´s no King Tiger in CMAK, I´d say go for this game. There are so many improvements over CMBO, and there´s a lot of Western front scenarios to download already, with many also yet to come, I suspect. And moreover, I suspect that with time, there will be top notch mods for Western front too. I think Tanks a lot has some buildings in progress, along with Tom's upcoming Battle of the Bulge mod.

You have now ascended on my "top ten most sympathetic people I know of list". And this is just because you did this.

First, I ran CMAK with OC:ing as before mentioned in this topic (441/850) - front hatch closed. Result: crash after 1 turn. Secondly, I ran CMBB with OC:ing 441/931 - front hatch open. Result: 10 turns + no crash. I have to upgrade my front hatch Genuinly bizarre is the fact that, with lower OC:ing and closed hatch, temperatures are LOWER than with the higher settings and open hatch. In the no crash scenario, VGA temp stays around 62 degrees C.

Yes, I can understand that. At first glimpse I felt like: let´s vamp things up here! But soon enough, I also felt the uncertainty of the project. Concerning the OC:ing results for memory speed, I will try adjusting the slider manually to approx. 930 mh´z and see if it stays when done this way.

Ok, first things first. You are wrong about the 700 mhz memory speed. The factory settings for both the Ultra and non-ultra are 850. You can check this here http:/www.firingsquad.com/hardware/msi_geforce_fx5900-td128_review/page2.asp The drop in refresh rate does happen to me too at all times I try the OC:ing option. I have Fast Write enabled. I will try disabling this and do some tests. I report back on this later. Regarding Aperture size, it is set to 128mb. I have never been able to come across an advice that speaks clearly on this one, as to what size is appropriate.

No, that doesn´t matter...

Thanks Nothing really new, just a slight change.

Back to topic... Hpt.Lisse, any temperatures given here is taken during a non gaming session with Asus Probe. P4S8X/latest BIOS Revision(1005) - temp ~ 34 CPU ~ 33 No OC:ing regarding the CPU. I actually did a Sandra scan a some days ago. It didn´t reveal anything critical, as far as I could see. Regarding my initial problem, it still appears. And it seems it´s due to heat. I have done some testing with open/non-open front hatch on the chassi by the fan, which is installed together with another one at the back, according to all professional air flow instructions, and no crashes ever seem to happen when the hatch is open. I do find this a bit absurd anyway, since it started to occur all of a sudden and temp readings show quite low results, I think.

@ junk2drive done.

Off topic for Hpt.Lisse I actually have a redo of that version on my HD, that I have made specifically for my remake of Magua open ground. As I always strive for subtlety, it blends in better, colourwise. It also has more "greenish" water. If you´re interested, I could upload it.

With nature, what exactly do you mean? Specs? Condition? Temps? 2.53 ghz (have no temp on this one at the moment) 1024 mb RAM VGA OC:ing - clockspeed 441 mhz but down to default 850 mhz for memory after two restarts(very odd). It ran at 932 mhz right after OC:ing. with core slowdown threshold at 145 deg.C

I´m looking forward to that. A shame that I have to go back to work by then, though.

Hi, may I make a suggestion or two. I have come to notice over the years, that when playing large battles, one shifts focus from determining the right angle of ONE tank to overall tactics and angles of all forces. You can of course still check every tanks angle to perfection, but I find this halting the fluidity of the battle too much. And yet, you really have to do this to be victorious. I would really appreciate the option of a " seek line of sight " for AFV's, comparable to " seek hull down ". The advantages of this, if desired, I guess, is pretty obvious. And in the same manner as this " command shortcut ", I would also appreciate the option to select two or three formations for AFV's in platoon size or bigger. Column, side by side, and german keil, for example. Say you could choose where to go and then the appropriate formation. I don´t know if this would be possible with either the current or future engine, but it would nevertheless eliminate some of the parts I find less entertaining. I know that this last suggestion has been up before in some way. Sorry for emphasizing.

Hi WindyCity, just wanted to jump in and say hi and welcome and that I look forward to see more mods from you. Like your wheatfield mod.

Just want to praise this very battle. It sort of reinvented my fascination for Combat Mission. Good work! * * * * * * * * * ***SPOILER*** It would be interesting to learn of someone else's use of armour in this battle. First time I more or less used the default setup for Axis forces, with all PIV's advancing in the middle of the map and the Tiger's approaching the little village on the leftmost of the map. Eventually I got brewed up this way by all those freaking Fireflies. The other time around I swapped places and let the heavy panzers fire away from the distance against the advancing enemy, during which time my PzIV's advanced SLOWLY on the left. This seemed to work much better, and it also seems that a slow approach is the key to this battle. It sort of reminds you of the necessity of letting the guns work effectively.

I looked around a bit, and it seems that the answer to my overclocking question is a brake function in Nvidias drivers due to heat sensoring. If anyone should be interested in some more OC:ing, I learned that there´s a bios flash mod for the FX5900 128. It´s actually possible to flash the card with a 5950 ultra bios and thus turn the frequences up even higher. The amount of memory doesn´t offer any problem, and your card will show up as a 5950 Ultra. Read more here Club Overclocker

Problem update: Following Hpt. Lisse's instructions, I thought my trouble was over. It wasn´t. For a while, I anxiously considered the option of reinstalling Windows, building everything up from scratch. However, I first uninstalled applications I rareley use and which could be considered "less WHQL", like some cd cover printing software. I´m now twenty turns into a quite heavy battle that surely puts a load on both CPU and GPU, and everything is fine. Before, I was never allowed to reach that far. I´m pretty sure the problem is gone. My card is a MSI FX5900 TD128. Maybe you can help me with another little thing: I installed coolbits and tried some overclocking again. In the appropriate tab, I checked "manual overclocking" and pressed "detect optimal frequences". Both memory and core clock went up quite a bit and it seems everything is running fine with that. But, even though I checked "Apply these settings at startup" and exited by Apply and OK, after a reboot, the frequencies has gone down to almost factory settings. Why is this? How can I keep the higher frequences?

No... :mad: ´ Problem persists.

It was actually after I read that very post I tried coolbits reg. Maybe I should try OC with my current driver, that doesn´t seem to give me any unexpected reboots or crashes.