Jump to content

WWB

Members
  • Posts

    1,959
  • Joined

  • Last visited

Everything posted by WWB

  1. I live in a row house. In DC, not the soviet union, but I have lived in them in europe as well. There is no way in hell to move through this building into the neighbors house without explosives. CM actually simulates this to some extent. If anything, they need to have thinner buidings with impassible walls. WWB
  2. Pretty simple. The view you see when you open the preview mode from the editor is the opening view for the germans (in CMBB at least). If you hit slash, you can then set the opening view for the soviets. I have had a few tonight so I might be reversed here. But in any case, the opening view is the last view that one sees before hitting ok to quite the preview mode. WWB
  3. It does 1280x960 and 1152x864 IIRC. WWB
  4. As I understand things the basic graphics routines for CMBx are pushing five years old. They are having driver issues with video cards and operating systems that were not even in beta when the code was written. Moreover, the game fundamentally works now--maybe not with features which did not exist on video hardware when the code was created. So now BFC should go and rewrite what is essentially legacy code due to changes amongst hardware which could not be envisioned? Things are actually quite rosy now. You were not around for the first few batches of nVidia Win2k/XP drivers a few years back. They were a nightmare. At best one had to alt-tab through every screen. The 41.09s are wet dreams compared to them. Gee, you get some 2d issues with FSAA. Issues that are easily worked around to boot. The other very, very valid issue now is that the 30.8xs are the fastest, most stable and most compaitible win 2k/xp drivers about. There really is no compelling reason to upgrade from them, save to be one of the cool people who change drivers weekly. When it comes to your video drivers, I follow a simple rule--if it aint broke, dont fix it. And I have not seen the 30s broken yet, save they are a few points shy on 3dmark now. WWB
  5. Industrializer, that test is flawed. There is clearly a hill between your tank and the building. It is not completely flat as you claim. I would bet a tank in the same spot as the building would be "hull down." Did you think of aiming for a different spot on the building after the first turn's shots went arwy? Still, I will try and set up some more scientific tests here. This anecdotal "Waa, waa, I lost the game because I could not take out something I should have manuvered on anyhow" evidince is worthless. If one can find some hard data, using at least 100 tests, then so be it. Otherwise this is just idle chatter. WWB
  6. I can see that the map is not completely flat. There are obvious breaks in your LOS line. Maybe it is the JPEG compression, but you should post the map for examination. I did design the scenario in question from the beginning of this thread. The gun is in just about a perfect position. So perfect the TacAI would not see it. I also remind you all that the StratAI has issues seeing linear cover, like walls. Much less LOS advantage cover like hillcrests. These positions are easy to see, at least to me. Place the gun where it can barely see over the hill and it pays off, big time. Which is not gamey--the germans and soviets did such all the time. Why risk getting hit when mother nature provided you with natural cover. In fact, such traditions ran thru artillerymen for a long time. Just after the advent of mobile field artillery, someone realized it was a damn good idea to use the slope of hills to your advantage. Why die needlessly? WWB
  7. Run the test 100 times. If it never hits the building, it might be a bug. But it sounds like it is a random situation. WWB
  8. I second the reccomendation of the 30.8xs as the best fecking nVidia drivers known to man. But I am fairly certain my install of the 42s was not botched--I did go back to the SVGA driver and I was installing over the 41.09s anyhow. Bottom line--stick with the 30.8xs until they come up with something better, probably in late 2004. WWB
  9. The problem is, Beckman, that IRL there were such things as positions nearly unhittable from direct fire. Therefore CMBB should simulate such positions, which it does quite well. How to defeat such positions? Use alternate tactics. Like targeting your DF HE on the hill slope just in front of the position, keeping thier heads down. Suppressing them with MG fire. Or call in indirect fire on the position to take out the fieldpiece. In any case, it is not a bug. It is a good deployment. WWB
  10. Would I be the one with the sig . . . WWB
  11. DirectX is a deeply involved windows component. It is a very hard thing to disentangle. As for drivers, anytime you do a DX install, you usually need to reinstall sound and video drivers too. I am running DX9 with no issues thus far. WWB
  12. I suspect it will not shoot because it is rotating the turret to compensate for the rotating hull. Which actually makes sense. Damn hard to aim the shot when you are concentrating on keeping the turret lined up. WWB
  13. All is not lost. You just need to find an exatly matching hard drive--down to exact model number. Buy it. Swap the logic boards (that thing with teh towers). Note that this violates any warranties you might have on either drive. But it does work. WWB
  14. Half a bottle? In a night. Try half a bottle in a half an hour . . . WWB
  15. Something to add: Got tech problems? Visit the CM tech support page! WWB [ February 25, 2003, 01:28 PM: Message edited by: wwb_99 ]
  16. This is a fundamentally wrongheaded idea in CM. The nature of the game and the AI do not lend itself to making one battle suitable for head to head and solitaire play from both sides. In fact, I suggest one does not even attempt it. When I design battles (and I have done a few here and there) I make them to work one way--H2H, allied, axis, etc. If they happen to work other ways, great. If not, no loss. Remember that the AI is generally a piss poor attacker, especially when it comes to coordination which is exactly what you are demanding. You will be better off making the battle single player as soviet or head to head. One other trick to get the AI to prebombard bombard--try padlocking the FOs out of LOS. That has been known to work. WWB
  17. Go with the 30.87s. They are not the newest, but they are the most compatible. Regarding FSAA, 4x works, although there were some issues with 2x. WWB
  18. Not quite. In CMBB there are linked to map reinforcements in non-static operations. They show when the map rolls over the flag. WWB
  19. Actually, that is an alterable parameter--it is called battle window size, minimium 1200m. Also, do not rely entirely on location based reinforcements, especially for the attacker. Wierd things can happen if someone gets stalled somewhere. WWB
  20. No, they dont clear up the Text/FSAA issue to begin with. But they do slow your CM to a crawl, even if they give you +500 points in 3dMark 2003. WWB
  21. #2 is intractable. Cant modify MG ammo loads anywhere, including the scenario editor. As for #1, should not fitness settings be ignored for pre-existing troops? WWB
  22. Hehe. Problem is it depends on CPU. I have only had to put a warning on 1 thing that is currently released and another thing that I actually have been sitting on due to turn-crunching time. Other than that, I really see no need to warn folks. Poor Kingfish plays just about everything on a P-233. If he can do that, I am sure folks with P2-450s can handle anything they are willing to put up with. WWB
  23. HQ cannot be hidden to spot for mortars. That is the likely culpert. Also, it will not target as a tank would, but you instead will area fire. WWB
  24. To post pics here you need a webhost that allows direct linking of pictures. Oftentimes your ISP will give you a small amount of webspace to call your own, and those generally work. To post and image, just upload the file, find the link (eg http://www.mysite.com/myimage.jpg) and post it using the UUB codes. WWB
×
×
  • Create New...