Jump to content
Battlefront is now Slitherine ×

WWB

Members
  • Posts

    1,959
  • Joined

  • Last visited

Everything posted by WWB

  1. Manx, you hit the nail on the head. I would have had no problem with the scenario packs had I been contacted and asked ahead of time. I think most of us remember the scramble to get the permissions for the original CMMOS mod sets. Scenarios would be alot easier--you are just dealing with individual authors rather than entire chains of authorship. WWB
  2. No dynamic flags in QBs, so you can't do the map import thing. More of a design flaw than a bug. WWB
  3. Might well be a heat issue. Do you play any other CPU & graphics intensive games? WWB
  4. Gee, what do you all call the stalingrad pak? Or the runepaks? Scenario paks are good, when the authors give permission for redistribution. WWB
  5. Been out for the last few days, so I did not see this thread. But I stand with Dorosh and Franko--you really need to get permission before redistributing people's creative works, even if it is a pain. While I have little fear that you have modified anything save a filename or two, what happens when someone else wants to do something similiar and pass the work off as his own? It is a nasty situation I dont really want to see. Also note that redistributing the CMBB CD battles is a clear violation of your CM license. The damage is done now, but never, ever put one of my battles in your packs again. WWB PS: Nice EU2 section. Got me thru the growing pains of that game. [ January 05, 2003, 10:57 AM: Message edited by: wwb_99 ]
  6. Engine cannot handle dual turrets, so nothing where the real MA is a 75mm sponson mounted piece could get into the game. This includes the american Lee tank, aka a grave for seven brothers. It appeared in significant numbers after lend-lease got going. WWB
  7. There is apparently an irresolvable issue with the SiS650 graphics chip and CMBB. Do you have an AGP slot? WWB
  8. Actually, CMBB does better with a slow & low-ram card than a slow & high ram card. It downsamples things based on the amount of video ram, not the video core. Which means a TNT with 64mb of RAM ends up overwhelemed as it does not really have the bandwith to use all of it and gets bogged where a 16mb TNT would downsample quite a bit and do fine. One other thing about the problem at hand--what resolution are you running CM at? Toning that down a bit will probably help a bunch. WWB
  9. One common thing is that the CMBB AI hates wide open spaces. If there is a 350m wide field across the map, the AI will not cross it. Add in a few scattered trees and brush and to help it along. The other thing that draws the AI like a moth to the flame is flags. Use a few little ones leading to some big ones like a trail of breadcrumbs. WWB
  10. He's actually telling the truth, although it's the Depot that says that. Apparently there needs to be a large disclaimer at the Depot regarding the side best played as....</font>
  11. 256mb is a bit low for running XP to begin with. Are you running anything else while playing CM? I am a bit fuzzy on XP, but to find the graphics card info, go to the system part of the control panel then click on the hardware tab. Go to device manager and look at your display adapters section. WWB
  12. Did you extract it to your CMBB folder? If so, it will work. Easy way to check is to look at the version number in the bottom right corner of the menu. It should say version 1.01. WWB
  13. What kind of graphics card and how much ram are the key factors in this equation. I had issues with choppyness a while back until I jumped to 196mb RAM. In CMBB, I noticed huge speed pickups when I went to a 64mb graphics card. WWB
  14. You need to switch the active side in the editor using the backslash key. Then you can group select as normal for the allies. Hit backslash again to work as axis. WWB
  15. I suspect no squad disappeared, but a team recombined. WWB
  16. Keep it coming Kannonier. I am very pleased with the reactions so far. I think the battle will be released as it was played in the tourney, maybe with a little airpower added for flavor. WWB
  17. Aside from a BFC splashscreen there is no intro. WWB
  18. Is not it hard to shacle a disembodied brain to a desk? Also: This is my Seanachai. I made him mad so he would growl and show his teeth. WWB
  19. I can push things past 60 on my Athalon2000+/Geforce 4 Ti4400 combo in some battles. Why is CMBB slower: there are gads more polygons. You have many more per vehicle, per infantry model. You have doodads. Every texture is hi-res. Lots more going on can really bog the older, slower cards even if it hardly gives the monsters a hiccup. WWB
  20. I would stick with the 29s or 30s if possible, and I never upgrade DirectX until I have to upgrade directX. The key to video drivers is: WWB
  21. It is definitely the drivers. Alt-tabbing fixes the problem, as will turning off FSAA. AF does work as near as I can tell. WWB
  22. This is my NVA. I made him mad so he would show his teeth and growl. WWB
  23. Back in the beta days when we had a framerate counter (and a slightly slower game due to debug code) I noticed something. So long as it stayed above 7 or 8 FPS it CM was quite smooth, with no noticeable lag. Lower than that and it became an issue. Of course, then there was the .5 FPS one got with To the Volga . . . Moral of the story: don't try to squeeze too many framerates, the point of diminishing returns is quite low. WWB
  24. Just saw NWN in the double-sized CD case at best buy yesterday. Anyhow, one must remember that bigger name titles have alot more bargaining position than small-figure strategy titles in getting shelf space, including the coveted full-sized box space. WWB
×
×
  • Create New...