• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

ForceWare 52.70 Leaked

If they work good with BF1942 and the DC mod then i'll downloading them maybe i'll try over the weekend .. or maybe i'll just wait for Nvidia to release the offical drivers .. i dont like wasting time.
 
If you read through some of the replies at guru3d, they say it fixed the DC problems of missing textures, and problems w/ certain maps.
 
DC works ... I've been playing it since my last post... I tried 4 different maps and they all work fine. Good news for all of you who wouldn't use ForceWear cause of the DC problems!
 
Originally posted by: ELopes580
ahh gotta ya, thx.. i havent played BF1942...
Click to expand...


It's quite simple then...you haven't lived.

Got these Forcewares a couple days back, wondered if anything noteworthy was different from the 52.16s. Well if they've got some DC fixes, might as well try 'em out. I prefer regular BF to DC by far, but I do play both.

Further feedback to come.
 
Wow. That is amazing. I just arrived at the video forum to scrounge around for information on potential problems with the 52.16 detonators and DC. I just rebuilt my machine and installed the 52.16s fresh. Previously, I'd had the 41.09s which worked perfectly.

Stunning. 5 minutes of searching. Question answered. Thanks, guys.

-DSP
 
Originally posted by: Jeff7181
Originally posted by: JustStarting
anyone 3DMark with them??
Click to expand...

Scores identical to the 52.16's... as I said before, there's no work around for the 340 patch for 3DMark2003.
Click to expand...

So I take it your 6157 is with the old 3DMark2003 build?? I just installed a remix of the 3.13's (3.14C) from NforcersHQ, and my 3DMark2003.3.0 went from 6002 to 6547!! Same 52.16's, but the auto detect OC feature got me 512/1020 on my FX5950!! Don't know why, but I couldn't OC my 5950 at all on the core before I loaded these new drivers. New Gart's I guess??

If you want to check it out, go to the driver forum on NforcersHQ and get the 3.14C remix. I installed them right over top of the 3.13's- No problem.

 
Yes, 6157 was with build 330. I really don't see any difference in image quality between build 330 and 340, so it's not like nVidia sacrificed image quality and FM corrected it with build 340. I think it's just become "cool" to harp on nVidia about their drivers and them using different methods to accomplish the same goal. I think it's pretty juvenile of FM to release that 340 patch and claim it creates an apples to apples comparison, it simply doesn't, and it never will, because nVidia and ATI are not both apples.
 
Originally posted by: Jeff7181
Yes, 6157 was with build 330. I really don't see any difference in image quality between build 330 and 340, so it's not like nVidia sacrificed image quality and FM corrected it with build 340. I think it's just become "cool" to harp on nVidia about their drivers and them using different methods to accomplish the same goal. I think it's pretty juvenile of FM to release that 340 patch and claim it creates an apples to apples comparison, it simply doesn't, and it never will, because nVidia and ATI are not both apples.
Click to expand...


Best I've heard it put yet.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top