TheRealAlan
Member-
Content Count
14 -
Joined
-
Last visited
Never -
Medals
Everything posted by TheRealAlan
-
nocabiwik, the w-buffer is only for if you're running in 16bit color. And it's to make it look better, not run better. In 32bit color you don't need it. And you're not going to be able to enable it anyway cus apparently in the last several generations of drivers it hasn't been supported.
-
Ok since I seem to be the idiot here, I have the following: 1.2ghz Tbird 384mb ram Geforce2MX 32mb DirectX 8.1 and a VIA chipset with lates 4in1 drivers and anything i've ever tried to run in 32 bit color has been very choppy, even scrolling through webpages with the desktop at 32bit. And I'm a tweaking nut, i'm always trying to get things to run better, but I"ve never gotten the performance out of my Geforce 2 that i've wanted but i thought that that why it was a $50 card. So if there's some trick or somethign to getting 32bit color playable, please let me know. The very newest detonator drivers that came out last week seem to decrease performance so i went back to version 22.83 or whatever they are.
-
Actually i've found that many people in the Czech Republic speak really good English-- in fact many of them speak 4 or 5 different languages, unlike us ignorant Americans. I was surprised when i went there this past summer. Language I doubt is the problem, more likely just attention to this board.
-
Ok I downgraded my Nvidia Drivers down to version 6.something and I could then enable the w-buffer-- whoohoo! But then I couldn't go into resolutions above 800x600 in OFP, not to mention it ran pretty poorly. Is there any way to hack the newer drivers to enable the w-buffer?
-
Haha Mister Frag, you try running OPF on a GeForce2 MX at 1024x768 in 32 bit color-- you'll be watching a slideshow. It runs smooth as silk on mine in 16bit color but crappy in 32bit, which is why i wish the w-buffer worked. Stinks that it's older drivers that work, I guess we either have to live with it running bad and looking good or running good and looking bad, if you've got a slower GeForce2.
-
Threre's no option in the regular utilities to turn it on but i've used the Geforce Tweak utility to try to enable it but it doesn't do anything for OFP.
-
Can anyone explain the inability to enable the w-buffer on GeForce cards that several peopel have mentioned? I'm having the same problem. I have everythign in 16 bit and it wont let me enable it (version 1.30). I have the latest detonator drivers, directX 8.1 (did it in 8.0 too). The polygons flicker like crap without it, but in 32bit they look great but the game runs like crap. It looked better on my old Voodoo3 that i had in my pc when i got the game, as it forces the w buffer. Can anyone from Codemasters explain this?
-
Arrghgh I set it to 1 in there, saved it, and every time i load up OFP it puts it back at 0. What gives man?! Thanks for the advice though, it's not your fault.
-
That's the w-buffer problem i've been on here griping about. It fixes that polygon flickering in 16 bit mode. If you can manage to enable it, the polygon flickering should go away.
-
CM/BIS: Get the hint? WE CAN\'T PATCH TO 1.30
TheRealAlan replied to Niblitz's topic in TROUBLESHOOTING
Do any people from the companies read this board? This is ridiculous, you'd think that theyd give some tech support on their own tech support message board. I have seen very few replies from technicians on here, and the few i've seen have been little or no help. -
Well man you can get a GeForce2 MX for about $50 nowadays, why are you buying a TNT2?
-
Well I had actually looked in the cfg file to try to manually enable it but the w buffer line wasn't in there. But now that I know what it is i'll add it in there and see if it works. I'm not at home right now to try it.
-
Game doesn\'t start no matter what (kernel32.dll error)
TheRealAlan replied to macand's topic in TROUBLESHOOTING
Also another thing to consider is that audio card. Do you mean it's SIS onboard audio? I have had awful problems in the past with using that type of onboard stuff. Try disabling the sound chip in your bios (temorarily) and removing the device in window, then try OFP even though you'll have no sound. But if you get that error again you'll know that's not the problem. I didn't know that stuff about the order of your ram chips, i'll have to try that. -
let me just give mine a bump so it doesn't disappear yet...