Jump to content

Blanar

Members
  • Posts

    68
  • Joined

  • Last visited

Posts posted by Blanar

  1. Hedoth,

    I've been happily using my Voodoo 5500 with

    CM for the past three months now and am quite

    disappointed with the recent turn of events.

    However, after much playing and tweaking,

    I've found the following:

    - Set the FSAA settings in the Direct 3D

    screen to anything other than "Fastest Perf."

    This solves the garbled text when just

    starting the game. I run at 4xFSAA and it

    runs and looks great.

    - If you ESC to your desktop and then go

    back into the game, the text will be garbled

    unless you select the single chip rendering

    mode. You'll lose FSAA if you do this, so

    unless you ESC out alot, I wouldn't recommend

    it.

    If you do a search in this or the regular

    Combat Mission forums there's been many

    threads with good ideas on settings to try

    for both PC and MAC Voodoo cards. Good luck.

    Carl

  2. I built an almost identical box back around 3 or 4 months ago.

    AMD Tbird 800

    Gigabyte 7ZX-1 (the one without the sound card)

    128Meg RAM

    20 Gb hard drive

    SBlive value sound card

    10/100 NIC

    still using just CDs, no DVD

    And a Voodoo5 5000 (Yes, it was probably my decision that put 3dfx over the edge)

    The system has been running great and handles

    large scenarios in CM easily. The latest

    version of Gigabyte's Easy Tune III software

    has it running at around 900mhz using

    auto-optimize without any problems.

    Originally, I installed Win2K but couldn't get CMBO to run. I know others have gotten

    it running there but, since I needed a fix

    bad, I backed off to Win98SE. I'm still on

    Win98SE and still happy.

    Make sure you get a case with at least a 300

    watt power supply and you should be all set.

    Good luck.

  3. Running a Voodoo5000, I have the same "feature" and I know it's been mentioned in this forum before. Once in a while I have to jump between screens or scroll back and forth on a scenario description, if the dropping happens to be on some critical piece of info. But, as it doesn't show up during actual game play, I mostly just ignore it.

  4. Imagine my joy and surprise as I read the Boston Globe Sports section and came across the following headline and first paragraph:

    "Cesspool stinks? Shocking

    (By Bob Ryan, Globe Columnist)

    Is it possible to make a farce out of a farce? "

    What was next, daily AAR's from yesterday best battles? Complete updates of the latest ladder results? Updated odds and point spreads for upcoming PBEMs?

    No, it turned out to be an article about boxing. Guess I'll just have to stick to this forum for CM news.

  5. What a tease! I go to download and get the following:

    The Download limit for the FreeDrive account that owns this file has been exceeded. There is a limit of 500 megabytes of downloads in a 24-hour period for all FreeDrive accounts. Please try again later.

    Now I'll have to continue with those old worn out sounds (which are great by the way!)

  6. I installed CM on my Win98, Celeron 400, 128 Mb machine with a Voodoo 3 2000 card using the original drivers. I played for three weeks, happy as a clam, and everything was running fine. Or, at least I thought it was until I read the many posts out here and was informed that I wasn’t seeing the good smoke, but the blocky square smoke. So, I set off and downloaded the latest and greatest WHQL 1.05 drivers. Immediately launching a quick battle, I fired smoke from all my mortars and paraded all my vehicles in front of the Germans. (You know, when I play for real and hide behind a building those tanks seem to flame up on the first shot, while in this case it took five abandoned vehicles before that sixth finally went up!) The smoke was magnificent and I was even happier!

    During the next full length QB, about turn 15 or so, all infantry units seem to have dropped their weapons and replaced them with white baseball bats. Shortly after, all vehicles, houses and trees were so terrified by the appearance of the bat wielding units that they engaged their all white cloaking devices and hid. Luckily, a few seconds later, a freak blizzard moved in and turned everything white causing a delay in what was becoming a very bizarre battle. A save, exit the game, restart of CM, and reload of the saved game got everything on back on track.

    That was when I used the search feature and found this thread. Seeing that version 1.05 and 1.04 were mentioned as having these problems, I figured that down grading to 1.03.00 Dx7 was worth a try. Smoke still works good, but now my units arm themselves with pink, tan and light green bats before a Technicolor blizzard suspends the battle.

    Has anyone tried any of the other archived versions of the drivers?

    Maybe the old smoke wasn’t that bad after all…

×
×
  • Create New...