pford

Disabling the backside cache slows the performance way down. The cache transfer rate is far faster than regular ram so the wait states are diminished. In other words, the CPU is not twiddling its thumbs waiting for the next instruction. You may not notice a performance hit in CM because the graphics card is so important, but if you use a stopwatch to time the calculation on how long the computer is "thinking", especially big games, you will see a big difference.

Well, things are always more complicated than they first appear. Considering the market and priorities from BTS point-of-view, I should be happy that it even runs on a Mac. Spending the time now to convert to OpenGL just to make a small percentage of people happy who have already bought CMBO when there are so many other things to do does not make a lot of sense. I would probably be more successful starting a letter writing campaign to Nvidia or Apple to hire Ray Swartz to carbonize RAVE or write a RAVE -> OpenGL driver. [This message has been edited by pford (edited 02-27-2001).]

Try downloading the latest drivers. Also retrash the CM pref. http://www.3dfx.com/downloads.htm I believe there is an option somewhere in the software to do this, else just go there and get it. Re: further questions on Voodoo 4 search for threads where Baboon2 is in. He wrote the drivers.

Are you still having this problem? if so, do you still the background sound? If so this sounds like exactly the same problem I have been having ever since it was released, actually before. It even made it into the manual. Try disabling the backside cache. Don't ask me why it works. It took me hours of fiddling with Conflict Catcher to find it and CM won't always freeze with the cache on. For a while I thought it was speculative processing. You can try turning that off. Maybe it will work for you. go to https://www.powerlogix.com for the control panel to disable the backside cache.

I will assume that you are not getting any color distortion except in the graphic mode. (A bad or loose cable connection can cause this) Does this happen in other games that use graphics? If yes then 2 things I can think that might cause the problem are bad video drivers which could be fixed by re-installing them, or a bad video card. Re-seating the card in the PCI slot might fix a bad connection. Low chance that is the problem but at least it's cheap to fix. 3 things. A bad monitor sync(?)unlikely.

I am curious how well CM diplays on the newer Macs that are using the of Nvidia's card, in particular the new GeForce3. I know that Apple inc. is moving away from RAVE and I don't know how well the new cards handle RAVE. Anyone here who has first hand experiance? As a side note, would it be posible to open source the graphics portion of CM? This might speed up the conversion to OpenGL.

When driving to work you keep looking where you can pull off the road and get into defilade quickly.

Well it is sort of a pun . First some background. With MacOS X (ten) the OS will be BSD unix with a GUI interface. In order to do this the earlier MacROM calls and OS calls had to be converted if the application was to run native in MacOS X. To simplify this and to delete problem children, only a subset were converted, which form the basis of life, carbon. Older Mac programs MAY run under Classic, which sounds like a Mac emulating an older Mac. Classic will have all the problems that plague the Mac now, e.g. a single appl can bring it down forcing a restart, cooperative multitasking, etc. But MacOS X with still be running fine, so no warm reboot. So to carbonize a Macintosh program is to convert it to run native under MacOS X. (Corrections welcomed) [This message has been edited by pford (edited 02-02-2001).]

Are there any known extensions that cause Type 2 and 3 errors. V1.1 crashes on my iMac DV pre and post upgrade to MacOS 9.1. It did this with the last beta version also (in another thread). I have CM v1.1 running on my old PowerPC with a G3 upgrade so I am not desperate but I am getting there. CM crashes at the point where it should switch over to the game screen after all the setup has taken place.

Try turning off the Virtual Memory in the control panel Memory app and reboot. There are quite a few programs that have choppy sound when VM is on. Your's does not sound like it is this kind of problem, so you might want to reload the sounds in case they are corrupted.

Madmatt: Are there any known extensions that cause Type 2 and 3 errors. V1.1 crashes on my iMac DV pre and post upgrade to MacOS 9.1. It did this with the last beta version also (in another thread). I have CM v1.1 running on my old PowerPC with a G3 upgrade so I am not desperate. CM crashes at the point where it should switch over to the game screen after all the setup has taken place. FYI: (1) The Powerlogix G3/G4 control panel used to manage the backside cache crashes under MacOS 9.1 on my machine. (2) The Mac freeze that seems to go away with disabling the backside cache may be a problem with the GuardBit. When I used a GuardBit patch from PowerLogix the problem went away, at least for now. This makes a lot more sense than the previous fix.

<BLOCKQUOTE>quote:</font><HR>Originally posted by Beer_n_Pretzels: Remember these three things hwen engaging nasty German tanks with your wafer-armoured shermans: 1. Tophat & Lowsky 2. Flank attacks 3. Hull down positions search for them on this forum and also the CM Combat HQ.<HR></BLOCKQUOTE> 4. Use smoke 5. Use more smoke 6. Lucky HE may knock off a tread 7. In clear daylight conditions, a fighter bomber will "even" things up. 8. Snipers will button them up.

<BLOCKQUOTE>quote:</font><HR>Originally posted by L.Tankersley: Ok. I've got a Mac (actually one of the old Power Computing clones with a G3 upgrade card) with an ATI Rage Orion video card. I've been running with OpenGL 1.1.2 installed with no problems. I haven't seen any of the problems some Mac users have reported with blacked-out text, for example. About a week ago, I started having frequent freezes in CM. They can happen watching playback or while issuing orders, and everything just freezes. I can still move the mouse cursor, but CM stops responding completely, I can't ESC out to the Finder, and if I hit interrupt (or command-power) to enter Macsbug I get a blank grey screen. The only way out is to command-control-power to force a reboot. -deleted- <HR></BLOCKQUOTE> This sounds VERY similar to a problem I reported in the beta version and still have.It actually made it into the help section of the manual . My hardware is almost identical. Powerlogix G3, ATI Xclaim128. The "solution" makes no sense to me, but I have used Conflict Catcher twice and it came up with the same result. (And those were long runs, very time consuming) The solution is to disable the backside cache on your G3 upgrade card. I don't know if this fixes it of just makes it less common, a lot less. In the manual it has the http address to get the powerlogix utility to disable the backside cache. Regards Pat Ford

<BLOCKQUOTE>quote:</font><HR>Originally posted by Fate: So if I understand you, the operations don't show up under the list of scenarios? Aaaaah! A light comes on as I had never noticed there were two buttons beside the scrolling thing on the scenarios screen. One says "battle", the other says "operations". Doh! Thanks for your help.<HR></BLOCKQUOTE> Doh! That was the same response I had when I asked this question. [This message has been edited by pford (edited 12-29-2000).]

<BLOCKQUOTE>quote:</font><HR>Originally posted by Madmatt: Patrick, Have you sent in a bug report with errorlog.txt file and save game? I don't recognize your name as any of the Mac people that have sent in reports with b24. There have been very few bug submissions so far and we can't fix something if you guys don't alert us to the problem. Madmatt<HR></BLOCKQUOTE> Yes, I did. You wrote me twice to a different email address. The first was completely irrelevant. In reviewing your reply, I may have left out some relevent information such as the type of error and when it occurred. I never got to the save game part since it bombed just after choosing a scenario, real early. BTW, the scenario was (is) Villers-Bocage - Tiger!.cmb . Contents of second: Whoops, sent you the wrong message. Disregard the part about the scenario. I was looking at someone else's. Sorry about that! Madmatt Ditto

Greetings: I recently downloaded the latest beta "24" and it has been crashing on me after selecting a scenerio. (V1.0.5 works still.) Unfortunately, like a fool, I deleted the previous beta which was working, although I never had the chance to try the TCP/IP part. I would appreciate it if someone would either e-mail an older MacOS beta or post where I can download it. Thanks Patrick Ford pford@Texas.net well I seemed to have had a typo in my e-mail address [This message has been edited by pford (edited 12-26-2000).] [This message has been edited by pford (edited 12-27-2000).]

Baboon2: Are the Voodoo drivers described at the site below the new ones you mentioned? http://www.macgamefiles.com/detail.taf?item=13703

Well, I am pleasantly surprised. I looks like Nvidia will support the Mac. I don't know if they or another party (such as Apple Inc.) will make Mac video cards. I hope Ray will be involved since he seems to have a good working relationship with BTS. http://www.go2mac.com/displaynews.cfm?newsid=7683 [This message has been edited by pford (edited 12-20-2000).]

<BLOCKQUOTE>quote:</font><HR>Originally posted by OsinO: So does anyone wanna mass market a copy of the show to the CM board? haha<HR></BLOCKQUOTE> Yes, it is called: http://www.historychannel.com

<BLOCKQUOTE>quote:</font><HR>Originally posted by Bruno Weiss: Why the devil anyone would care...? <HR></BLOCKQUOTE> Well, as a Mac user, it is unlikely that Nvidia will continue to support graphic cards for the Macintosh.

Thursday, December 14, 2000 60 US Dollar = 111.188 Australian Dollar (ouch) as per http://www.oanda.com/convert/classic?user=interhotel〈=en ------------------

Well I learned something new re: screeen snap shots. Is this a Voodoo5 problem only because with the Voodoo3 card and the beta driver I can get a screen shot?

<BLOCKQUOTE>quote:</font><HR>Originally posted by Baboon2: Sorry, I've been unable to locate a utility for taking V5 screenshots.<HR></BLOCKQUOTE> What happen to cmd-shift-3 for a screen shot?

<BLOCKQUOTE>quote:</font><HR>Originally posted by Baboon2: Sorry, I've been unable to locate a utility for taking V5 screenshots.<HR></BLOCKQUOTE> What happen to cmd-shift-3 for a screen shot?

<BLOCKQUOTE>quote:</font><HR>Originally posted by Rob/1: Matt I did try what you said but I still have to reapply the patch every time I fire up the computer if I want to play. Its weird I can still make scenarios but I cant always get at them. I have a conflict checker maybe there are some scenarios that are corrupt. Could this be a reason any clue? <HR></BLOCKQUOTE> Re ATI: Use the Apple system profiler to determine what you have. It is usually in the Apple menu. ATI drivers: Some times when installing the drivers, a driver for the 128 version will get installed. If you don't have that version, remove it. Where does your system hang/crash in CM. I was having a problem running CM on an original iMac 233MHz that it had run on before, until I lowered the resolution to 800 X 600. In the extension manager, create a minimal set of absolutely required extensions needed to run CM. Re: Backside cache You have it and it is turned on at boot-up. The control panel extension G3/G4 cache profiler will have to be manually run to disable it. Unless you are better at Applescript than I am. BTW, it makes no sense to me why this has any effect. Other non-specific things that screw-up Mac programs. Run Disk First Aid, or better DiskWarrior (first choice) or Norton Utilities (second, currently there is a free beta download). Catalog errors for some reason can cause havoc at unexpected places. Rebuild the desktop after you do the above. Reset the PRAM. you will need to reconfigure your system afterward, AppleTalk,etc. Re: Type 1 and 2 errors I have found these to be non-specific enough to be of little help in solving what is causing the problem. Sorry There is a new spell check button on these postings. Please use it. I am a poor speller and not the best typest either (and English IS my native language) so please don't take this as a slight or insult. It is quite good and can help one improve their spelling. Now if they would only add a grammar checker. Regards pford