Schrullenhaft

It seems a number of players are having this particular problem. I'm not sure if there is some sort of problem with the latest Voodoo3 drivers, some systems and certain settings in scenarios. This thread is related to your problem. I don't know if anyone has come up with a solution yet, however not everyone with this card has experienced this problem. All or Nothing is the scenario that causes the problem the most: http://www.battlefront.com/discuss/Forum8/HTML/000196.html

I actually like the idea of a "semi-campaign" system. Basically it wouldn't require a pre-generated list of scenarios or even branching. Basically it would allow you to create a company/battalion/regimental -sized unit and take it into several different scenarios (QB generated or designed scenarios). You could take what remains of your unit from one scenario to the next; getting reinforcements/replacements and non-permanent attached units every-so-often (but not all the time) between battles. A system to link and script scenarios together would be a nice addition to that. In fact a way of working with maps that could be pre-built and then have opponents generated for them would also be nice (random/parameter-based or designed). Admittedly this is a bit beyond the scope of CM, but I think it would be a nice direction to go in for the future.

3dfx usually recommends using the manufacturer's supplied drivers. The following link is for 3dfx's Voodoo2 1000 PCI card, which should work (I believe the SLI code should still be there, but I'm not sure): 3dfx Voodoo2 1000 (3.02.02 - 1/27/00): http://www.3dfxgamers.com/drivers/voodoo2/voodoo2_win9x_new.stm Creative Voodoo2 Drivers (3/19/99): http://www.creative.com/support/files/download.asp?reg=0&OS=Win98∏=db_voo&se lect=Get+Files Basically I don't think you can get high-quality smoke and transparencies with the Voodoo 1 & 2 series, but a user in this thread claims otherwise (but they get constant lockups): http://www.battlefront.com/discuss/Forum8/HTML/000339.html [This message has been edited by Schrullenhaft (edited 07-28-2000).]

What I'd do is to make a "101" and a "103" directory in the CMBO directory (assuming you're using a PC). Copy your current COMBATMISSION.EXE to the 101 directory and copy your new COMBATMISSION.EXE to the 103 directory. What you need to do is copy (not move) whichever version you want to run to the CMBO root directory and overwrite the the copy that is there. When you launch CM you'll be running that version. (I assume here that there are no big differences in the prefs file between the two versions) It's archaic, but I'd think that it would work.

Kunzler - That's definitely strange response from just changing your color depth. Does your internal/LCD display disable when you're plugged into an external monitor (being in a docking station probably prevents you from even looking at the LCD) ? I'd assume so, but I'm not absolutely sure with some systems. Driving both displays at the same time may cause some weirdness as more memory on the display adapter may be used to work with the different displays, etc. I suggest checking your CMOS/BIOS setup to see if there is any setting you could change to drive only one display at a time. Here are the latest drivers from Dell (the ATI Rage Mobility drivers are only available from the laptop manufacturer): A BIOS update doesn't exactly sound like it would do much, but it may be worth a try. The latest rev. is A08. Dell Inspirion 3700 BIOS update (A08): http://support.dell.com/us/en/filelib/system.asp?sid=INS_PNT_CEL_3700&m=l&p=1 The latest video driver, which you may already have. ATI Rage Mobility (12-10-99): http://support.dell.com/us/en/filelib/system.asp?sid=INS_PNT_CEL_3700&m=l&p=6 The latest audio driver that has been posted. This shouldn't be a factor in your current problem though. Audio Driver: http://support.dell.com/us/en/filelib/system.asp?sid=INS_PNT_CEL_3700&m=l&p=3 Do you still have the touchpad driver installed ? You may want to attempt to uninstall it or update it (probably uninstalling may be the best bet): Touchpad driver: http://support.dell.com/us/en/filelib/system.asp?sid=INS_PNT_CEL_3700&m=l&p=17

I don't think that BTS has shipped a 1.03 CDROM yet. The last pressing that I was aware of was 1.02 (which had some differences in the Quick Battle selections from 1.01). You'll probably want to patch with the 1.03 patch that is available for download.

I don't have their 21" monitor, but I do have some of their 19" VS-195/195e's at work. They are typically good monitors for the price. To be honest I've had problems getting warranty service from them in the past though (they have long warranties at least) - they never came by to pickup some monitors that they issued RMA numbers for... TWICE ! (and this was a business address). Anyway... they are fairly good monitors for the price. I'm not sure who's tubes they're using (possibly Samsung or Hyundai). Admittedly there can be quite a difference in quality between screen sizes since they could be using a completely different tube and manufacturer.

Do you know what chip your All-in-Wonder is based on ? Is it a 3D Rage II/II+ (maybe with "DVD" also on it) or is it a 3D Rage 128 (which would be an All-in-Wonder 128) ? For the first one I would suggest upgrading to these drivers if you don't have them already: Rage II: http://support.atitech.ca/drivers/3drageII+.html If you happen to have the card based on a Rage 128 then upgrade to these drivers: Reactorcritical Rage 128 drivers: http://www.reactorcritical.com/download.shtml I can't exactly picture what you're looking at, but it may be normal (at least with the ATI drivers) or it may not be fixed by the latest ones. I saw some graphic anomalies with the Rage 128 Pro and the Beta Demo and the latest drivers fixed those (but they weren't related to the smoke).

ARCHANGEL - I wouldn't necessarily blame the install problem on your Voodoo5. I don't know why your running into a copying error with CM. If you have any other programs or applets running you may want to close them down (especially "uninstallers" and other system monitoring utilities). If that doesn't work, then you'll just need to create a C:\PROGRAM FILES\CMBO directory and copy almost all the files off the CDROM into their respective subdirectories under CMBO (in other words copy the BMP directory and its contents by draggin the BMP directory to the C:\PROGRAM FILES\CMBO directory, etc.). I believe you will only need to copy the COMBATMISSION.EXE file from the root of the CD to the CMBO directory. Other than the lockup when you press GO in CM what other problems are you seeing with your Voodoo5 ? These are the latest drivers for the Voodoo5 under Win9x (updated July 21st): http://www.3dfxgamers.com/drivers/voodoo5/voodoo5_win9x_new.stm What sound card do you have in your system ? Some problems end up being related to the audio drivers.

If you swap you monitor cable to the other video connection you will probably see your start menu, etc. Apparently the video card you are connected to right now is the secondary display. If you want one to be the primary and the other to be the secondary, you will need to go into your BIOS/CMOS setup. In there you will need to find (probably under PNP/PCI or Integrated Peripherals or Advanced Setup, etc.) the setting that selects the Primary display (usually you'll have a choice of AGP/PCI - the first or displayed value being the primary). In your case you'll probably want to select the Primary display as PCI. Save your settings and hook up your monitor to the PCI video card. When you reboot you should see the memory count, etc happening on the display. If you don't, then the built-in video is still being considered the primary display. [This message has been edited by Schrullenhaft (edited 07-27-2000).]

To a certain extent that info is available in a panel on screen. With a unit highlighted and pressing Enter you will get the info screen that provides a lot of details on the unit, including brief penetration tables for the main weapon. Of course the unit you want info on has to be on screen. [This message has been edited by Schrullenhaft (edited 07-26-2000).]

You may have to check your CMOS/BIOS setup to see if you can disable your on-board video from a setting in there. Otherwise there may be a switch or jumper on the motherboard that disables the on-board video. A number of motherboards would disable their on-board video when a video card was detected on any of the buses. It is also possible that the routine for disabling the on-board video requires that your plug your monitor into the new PCI video card (VESA DDC detection of the monitor). Sometimes a BIOS may leave the on-board enabled, but depending on settings in the CMOS setup or other factors may make it the primary or secondary display in a Win98 setup. If none of this helps then you will either need to check your system/motherboard manufacturer's website and/or check out any BIOS updates that may be available for your system.

When you startup CM the main screen (where you select to play a scenario, create one, etc.) will have a set of small white numbers in the lower right hand corner. That's the version number.

My guess is that it would work. A QB generated at 5000pts on 1.02 and sent to another player with 1.01 should be no problem. I believe it is just the same as any other scenario file and there's no hard-coded point limit on those. Now generating a QB w/ 5000pts obviously would require 1.02.

Apparently Allied forces reached your rear area (or something to that effect). In an advance operation (I'm not sure if this West Wall op is an advance) when the opposing forces reach close to the enemy held edge of the map the op will end at the conclusion of that battle. There are a few issues that are being patched in 1.03 in regards to operations and victories.

I think it would be an excellent option to allow for the opponent to choose his force selection (which wouldn't have to be revealed to the initiating player) with the allotted points. That way you would have to take a more balanced approach to your force structure. Go heavy with tanks and you could be facing all infantry and find yourself swamped, etc. It just increases FOW that much more. So, basically I'd like to see the following options in QB: 1) An option for PBEM (or possibly even against the AI) for the initiator to select one side, the battle type, his force composition, the point total and the terrain options. Then allow for the other side to get a terrain preview (if their the defender) pick their force composition (the selections would remain hidden from the respective opponents). In the case of a meeting engagement the computer can select the terrain randomly (or just as a plain option for any QB) and not allow any terrain preview. If the receiver is the attacker they wouldn't get a preview, just a listing of the selected options for terrain. Both players would get to know time of year and weather conditions before making their force selections. 2) Although this violates the idea of a Quick Battle (instead I'd look at it as a quick scenario generator) - I'd like to see some reinforcement options available to the player much like operations have (this would be nice for scenarios in general). Like the Battalion - Regiment - Divisional reinforcements. Though most battles would technically be too short for such options, a longer battle could be a possibility for situationally-dependent reinforcements (again based on a point total). Reinforcements could be based on a modifier that would be dependent on the ratio of on-board force points to those set aside for reinforcements (with a max #or percentage of points that could set aside for reinforcements). So at a certain ratio of on-board to reinforcement points your reinforcement points could be multiplied by 1.5X (as an example). Again a maximum number or percentage would limit the abuse of such a reinforcement system. Admittedly there are an endless number of options that could be requested for QB (or CM in general) and the details of their implementation for CM1 may be too much at the moment. [This message has been edited by Schrullenhaft (edited 07-26-2000).]

There are two discrepancies you may not notice because they aren't in the demo: your video card's compatibility with CM's fog effects and your sound card's capability to handle heavy amounts of 44kHz audio (the Demo's audio is 22kHz). An older, but more compatible method of generating fog was used for CM. However a number of cards don't support CM's fog-tables and instead support newer methods of generating fog. Usually this is a driver issue. Since most newer games push the envelope of the hardware, they quite often support the latest DirectX effects (rather than attempting to support hardware that won't support them). Apparently the video card manufacturers have aimed their driver development at this segment of the market, so their drivers may not perform all of the DirectX calls correctly. Hence you'll see some people complain about the lack of fog, transparencies or correct-looking explosions. Other than this the Demo is a good example of what you could expect with the full version. If you were having problems with it they would manifest themselves in the full version also.

"Program error could not initialize direct 3D" is the error you'll get once you've run out of resolution options to select from. The program will only go through the available resolutions once before this error comes up (the available choices are dependent on your current desktop resolution and your video card/monitor's capabilities as defined by Windows). If you haven't selected a resolution after the first round, then you'll get this error. If you want more options then you'll need to increase your desktop resolution. Once you've selected a resolution with CM's selection process it will continue to use that resolution and refresh rate until you delete the "prefs" file in the CMBO folder. Then you'll go through this process again to select a new resolution.

CPU-wise you should be OK. Are you running at 100Mhz or 66Mhz for your front-side bus ? If you run at 100Mhz your memory has to be PC-100 compliant. A little more memory would be nice, but it isn't absolutely essential. It can help with the larger scenarios. The Voodoo3 3000 should work, but some players (some of whom have a similar setup to yours) have been complaining of graphics degeneration during play. Other users haven't experienced this. So be on the look out for this particular problem. Make sure you have DirectX 7.0a and the latest drivers installed (v. 1.04 or 1.05 for the Voodoo). Your sound card may also make a difference, so make sure those drivers are updated too. Also you may want to check to see if you are sharing any IRQs (i.e. - your sound card and your video card are both sharing IRQ 10 for example). Shared IRQs may cause possible lockups in CM.

I assume you mean that you have a Voodoo3 2000 PCI, is that correct ? What Operating System are you running Windows 95, 98, 98 Second Edition or Windows 2000 Professional ? As you've already read some users claimed to have had no problems with either the 1.04 or 1.05 drivers, while others have. It's possible that some combination of drivers and hardware may be causing this problem. Cardinal Fang had a problem with lockups (not your deteriorating graphics problem) and he had to disable DirectX's 3D audio acceleration and disable weather effects in CM to get around the problem. What sound card are you using and do you have any other hardware (ISA or PCI cards) installed in your system ? You may want to experiment with CM's settings by turning off weather effects, turning off transparencies and using "fast & compatible" smoke. This is going to kill a bit of the eye candy for you, but it may point to something in particular that is causing your problem. If changing one or more of these settings solves the problem then you can start to experiment with other settings and changes to your system to see if you can find the culprit. It still may be the Voodoo3 driver, but it may be having a problem with another driver in your system.

I'm not familiar as to what the baseline should be on the 3DMark 2000 benchmark. Have you installed Via's latest 4-in-1 driver ? I'm not absolutely sure it will affect your benchmarks (it should have a specific VXD for the AGP port). They had problems with one of the AGP drivers at Tom's Hardware (but I believe the ASUS CD came with the older, but faster version): Via 4-in-1 Driver: http://www.via.com.tw/drivers/index.htm What version of the BIOS do you have. They're up to 1.05 now (though it shouldn't really make a performance difference). Asus BIOS Slot 1: http://www.asus.com.tw/products/motherboard/bios_slot1.html Is your memory capable of handling CAS2 ? You may want to check your BIOS/CMOS settings to see what your memory timing is set to. Plus you may want to check (though the default should be fine) your AGP Aperture; I'd suggest 64Mb or larger (unless you're having a problem with that size). Are you sharing any IRQs in your system, especially with the video card ?

My guesses about TCP/IP - 1) It will only support two players. I don't know if there are plans to support more, but probably not until CM2 (since more than two players would probably require quite a few other changes). 2) The TCP/IP support might not make the game any faster than Hotseat play (other than the need for a password at each turn). I'm guessing that the data is going to be similar to PBEM-type files (though you won't have to conciously post them to the other player) with execution being handled by one computer then the other and then allow for simultaneous viewing of the results (with of some sort security implemented). 3) TCP/IP support can be quite a chore to program. Getting everything down the way gamers want it (and cross-platform to boot) will be time consuming. Everyone was anxious six months ago to get their grimey paws on the game and voted to have TCP/IP support come out in a patch. I still agree with that vote. TCP/IP will be nice once it is available (if your opponents are in a time-zone close to you), but it doesn't ruin the game's appeal for me without it. [This message has been edited by Schrullenhaft (edited 07-22-2000).]

Rewriting CM's code for fog is something that is solely up to Charles. He went with Fog Tables instead of Vertex Fog so older cards could support fog. I'm not sure of the quality differences between the two (I'd guess that vertex fog might look nicer, but be more of a CPU hog). I'm not sure how much of a pain it would be to support both types (like CM's support of transparencies). The choice of fog-tables on PCs has become an issue since a number of (usually newer) video cards have either dropped support of fog tables or their drivers haven't been written to support that feature in the hardware (in favor of vertex based fog). This is the kind of issue Charles is running into. A variety of companies haven't written their drivers to support all DirectX calls correctly. Sometimes it is a hardware issue, but quite often it is a choice of what to support in the driver. [This message has been edited by Schrullenhaft (edited 07-22-2000).]

Srider - Do you know what revision of the motherboard your SD11 is (you can usually find it on the back of the motherboard near the last ISA slot - it will usually be the same color as the traces and will not be silk-screened on) ? Looking at FIC's website the only BIOSs I see posted are for the 1.7/1.8 rev of the motherboard and there doesn't really seem to be much about AGP in any of the updates. Apparently the SD11 has a VIA southbridge chipset, so downloading and installing some of the VIA drivers may be appropriate: http://www.via.com.tw/drivers/index.htm The 4-in-1 driver has device drivers for AGP, IDE, IRQ routing, etc. I don't know how much of an improvement the AGP driver may make, but it is worth trying. The only details in FIC's FAQ for the SD11 that pertained to AGP mentioned that it is only AGP 1.0 complaint and therefore can't work with 32Mb video cards well because of their higher current requirements. However this isn't an issue for you.

There's no way to run the program from DOS. It is dependent on Windows and DirectX to run. The "memory program" that was mentioned in another thread (can't seem to recall what it was) might be your best bet. You may also want to experiment with your virtual memory settings. Go to Control Panel > System control panel > Performance tab > Virtual Memory button > select the "Let me specify my own...". Here you will now be creating a permanent swap file (so the amount you specify as the minimum will be unavailable for file storage on your hard drive). If you have the free space specify a minimum of 200Mb - 400Mb and a maximum of 300Mb - 600Mb. You may want to experiment with these settings to see if you get any different results or not.