• 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 84.21 WHQL available

Page 3 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
I haven't tested Fear yet but OpenGL is slower across the board compared to 81.98. In Call of Duty I lost almost 14% performance.
 
Originally posted by: BFG10K
I haven't tested Fear yet but OpenGL is slower across the board compared to 81.98. In Call of Duty I lost almost 14% performance.
Click to expand...

FFS, just use the 84.20's and quit whining! Also, check your ARS thread and learn to configure games correctly before inventing driver bugs that don't exist!
 
Originally posted by: SpeedZealot369
Originally posted by: Megatomic
I just played all the way through the Lost Coast level with great results. I'm 3 for 3 so far. 🙂
Click to expand...

What it lost coast? I have half life 2 but is that an expansion or what?
Click to expand...
Its a free level you can download that was cut from the original game.
It also shows off the Valve HDR lighting effects.

 
Originally posted by: Mem
Well, I guess this driver works for some and not for others, as with all drivers. Im happy with the 84.20 though. I doubt the latest games would give any problems with 84.21, its the support for the older games that made me revert back. So maybe some of your older games wont work too well, that is if you play any older games...if not then IGNORE.
Click to expand...


Try using Driver Cleaner in safe mode before installing the drivers might help.


Driver Cleaner link.
Click to expand...

Of course I use driver cleaner everytime I uninstall stuff, but I guess I shouldve stated that. Anyways, 84.20 makes me happy, dont really need the WHQL certification. My rig is an SLi one as well with two different brands, so that might've had something to do with it, though I doubt it since it all 80.XX drivers support it...eh I dunno.
 
FFS, just use the 84.20's and quit whining!
Click to expand...
The word on the street is that the only difference between the two drivers is WHQL certification.

Also, check your ARS thread and learn to configure games correctly before inventing driver bugs that don't exist!
Click to expand...
While I appreciate the time you took to suggest a solution I've already posted a response detailing the flaws in your suggestion.

Basically you don't appear to grasping what the actual issue(s) is and are instead trying to blame it on user error.
 
Originally posted by: BFG10K
FFS, just use the 84.20's and quit whining!
Click to expand...
The word on the street is that the only difference between the two drivers is WHQL certification.

Also, check your ARS thread and learn to configure games correctly before inventing driver bugs that don't exist!
Click to expand...
While I appreciate the time you took to suggest a solution I've already posted a response detailing the flaws in your suggestion.

Basically you don't appear to grasping what the actual issue(s) is and are instead trying to blame it on user error.
Click to expand...

On the surface it would appear that WHQL is the only difference, but, judgeing by user reports something is up the putt with OpenGL in 84.21, never mind just use 84.20. This is one of the benefits of nVIDIA's way of releasing drivers IMO - you aren't stuck for a month waiting fro a fix - just try another beta.

I can only tell you that I don't suffer the issues that you list with the games, and I've had them sitting on my drive for years now.
 
Here are my SoF settings:
pic1 pic2 pic3 pic4

Here is a video of the SoF intro at the above settings (never mind the frame rate or quality - it was captured with fraps and converted to DIVX I also stripped the audio to save on file size - I have the orginal capture available, but that's 306mb, I'm not about to upload that on my puny so-called "broadband" connection)

video

As you can see SoF works for me. I could work my way through all the titles like this, but I can't really be bothered at the moment.
 
Go into the game and disable shadows (it's under the second icon from the right).

Now you should be able to replicate the issue.

My cinematic works with shadows enabled as well. The issue is only present if the game shadows are disabled.
 
Just tried disabling shadows, no change in the cinematic for me(other than lack of shadows obviously). Are you fully patched (v1.06)?
 
Didn't realise there was another patch out for the game. Oh well, off to grab it. Yeah, everything else was the same (exactly as I showed it in the config screens).
 
If you still can't replicate it with 1.07f we'll have to chalk it up to driver differences (I used 81.98 and 84.21), and/or possibly some other setting.

For instance running triple buffering is quite pointless without vsync, and you appear to be doing this.

Another possible scenario is to remove your SoF profile and to force settings through the global profile like I am.

Oh, and one other thing: the stock GLQuake from ID works for me too.

The issue I've having is the modified version which follows the stock version closely but adds extra features like coronas and bump mapping. Both 81.98 and 84.21 crash the program on startup while ATi drivers have no such issues (the HUD however flickers on ATi and I mentioned this in the other thread).
 
Yeah, 1.07f works for me. I'm only using stock GLQuake, on a sidenote I don't suppose you are aware of any rewrites/emulators for Hexen II? I can't find any, the game works ok, but it's terribly creaky nowadays.
 
I've checked out CoD for you also and replied @ ars, for those here curious, this is the post:

I get 110.00 fps prior to suiciding, upon death framerate hits 50 fps, click continue, level starts at 93 fps and quickly bounces straight back up to 110 fps as you look around and face the foliage.

My personal opinion is that you need to carefully go through game directories, system32 and the registry, look for any leftover Ati bits and remove them.
Click to expand...
 
I get 110.00 fps prior to suiciding, upon death framerate hits 50 fps, click continue, level starts at 93 fps and quickly bounces straight back up to 110 fps as you look around and face the foliage.
Click to expand...
Did you do a renderer restart after you looked at the foliage the second time?
Are you running 4xAA through the global profile and using that for the game?

My personal opinion is that you need to carefully go through game directories, system32 and the registry, look for any leftover Ati bits and remove them.
Click to expand...
Both the 6800U and 7800GT were installed onto clean Windows XP installs. Also the CoD config was wiped and rebuilt from scratch on both cards.

In any case I have doubts that you'd admit you had the issue even if I managed to educate you sufficiently to replicate it (and it's not my job to train you how to find driver bugs anyway).

You've proven your blatant nVidia bias in the past by downplaying and even ignoring nVidia issues and you've also posted gross misinformation like claiming you can delete nVidia built-in profiles through the base driver control panel when this is blatantly false.

You also claim to not be affected by the Star Trek Elite Force issue yet at least five other people (in addition to my report here) are reporting the same issue in the nvnews thread you linked to. Not only that but the guy who posted the autoexec "fix" came back to say the "fix" doesn't even work and that he is afflicted by the issue as well.

I guess you didn't figure this little detail was important when you singled out his first post but ignored the rest of the posts, huh?

In a nutshell that you can't replicate the nVidia driver bugs I'm reporting (or rather claim you can't replicate them) is quite meaningless in the context of your past actions.
 
Yes, BFG10K, I did do a vid_restart, I performed the test several times.

If you would like I can make a FRAPS video...

I'm not pretending to claim anything, I'm merely stating the plain and simple truth.
 
If I had some web space I'd make a FRAPS video of the issue and put it up.

In any case, even if you genuinely can't replicate the issue there could be dozens of reasons as to why not. Likewise for the SoF issue.

I have no reason to make up nVidia driver issues nor do I have any reason to make up ATi driver issues.
 
Soldier of Fortune video.

I only captured the section with the thug and cop plus the start of the outside section to show the video was continuing after the pause.

The pause is not a glitch with FRAPs, this is what actually happens in the game cinematic with 8xAA or 16xAA enabled. 4xAA works fine though.

Capturing the Call of Duty issue was not possible as FRAPS drops the framerate when capturing and if I bump up the FPS value up it doesn't work.

Instead here are two screenshots taken in identical places in the game, one before dying and one after. As you can see the FPS difference (116 vs 42) is apparent and it would be much worse if I was looking at the vegetation behind me.

Before death.
After death.
 
BFG10K, use imageshack - http://www.imageshack.us for any images you want to upload, less painful than rapidshare.de.

Regarding the CoD issue you experience, does it only happen @ 16x12? If not we can hook up a DVD recorder to TV out and record the output that way. Max res (for my cards at least is 1024x768).

In the case of SoF i'm wondering if it isn't the CPU at fault? I have a Socket A cpu, only capable of 3dnow! and SSE1 (all that was available when SoF was released), Athlon64 goes all the way up to SSE3. There could potentially be some sort of issue with the driver using SSE2 & above math when the game was expecting 3dnow or SSE or FPU to be used.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top