nVidia HQ AF problems again

[5150Joker]

Originally posted by: keysplayr2003

Originally posted by: beggerking

Originally posted by: keysplayr2003

Originally posted by: crazydingo
People who dont notice shimmering; good for you! dont click on this thread and related topics.

People who notice shimmering; participate and hope it gets fixed.

Honestly if you are in former group, why do you have a problem. Its not a problem to you, good for you. Enjoy. Why do you have a problem with others wanting it to be fixed.

But didn't you try to point out that this thread was not about shimmering? And even went as far to say that I should "read" the thread and quote and bold someones statements?
I truly wish you all would make up your minds and actually know what the point is that you're trying to convey. One guy says its not about shimmering, but about optimizations not being turned off when HQ is set. Another guy says, If you don't notice shimmering, don't click on this thread (inside the thread :roll: ) but if you do, you are welcome.

Joker:
Boogertroll, read>comprehend>post. It's been stated quite clearly what this thread is about.

JokerTroll, care to explain what this thread is about? or are you just going to reply with pure trolling statement as without providing an answer to the question? again..

Beggerking, some of us are here to discuss. Some are here to be caught on a hook by baiting trolls, and some are just plain trolls. Which are you?

In the very post above yours, Joker explained things in a decent manner. I would go read that and edit the post of yours I quoted here, because it does nothing to stabilize this conversation. Calm down, stop being so defensive and emotionally thin. Or go away.
Please.

Thanks in advance,
Keys

Thank you keys, I think I'm just going to ignore him from this point on. IMO nVidia can fix this issue quite easily if they correct the problem with HQ AF in OGL retaining opts. If this issue gets enough attention it shouldn't take more than one driver revision for them to fix.

 

[Keysplayr]

Originally posted by: beggerking

Originally posted by: keysplayr2003
Beggerking, some of us are here to discuss. Some are here to be caught on a hook by baiting trolls, and some are just plain trolls. Which are you?

In the very post above yours, Joker explained things in a decent manner. I would go read that and edit the post of yours I quoted here, because it does nothing to stabilize this conversation. Calm down, stop being so defensive and emotionally thin. Or go away.
Please.

Thanks in advance,
Keys

well, Joker called me name first, didn't he?
I'm stating that this forum on the old old topic of shimmering is unnecessary since most of us knew already about the shimmering problem.
we might as well recreate a thread on the purple dot problem since both are reposts.

What is the purpose of this thread? seriously. Obviously this thread is not about finding a solution since the only solution for both problems are driver updates, which isn't up to any of us.

Actually, this is not an old topic per se'. This is about using HQ AF settings in the driver and optimizations not being turned off. A side effect of this would be in part but not limited to, shimmering. So it is not exclusively about shimmering. Shimmering is just a part of it. If nvidia states that optimizations should be turned off when using HQ, then they should be turned off. If it is a bug in the driver, then nvidia becomes responsible for coming up with a new driver or a fix for this.

If all you wish to do is "will" this thread away, then you can make that happen. Just by not entering it any longer. Or, just maybe you can get some useful info from it instead of the "getting really old" arguments.

 

[1Dark1Sharigan1]

When I switched from my X800XL to my 7800GT, I could clearly see more shimmering in almost every game I played (OpenGL & D3D). Especially games like HL2. I never experienced shimmering with my X800XL except for COD2.

 

[BFG10K]

Some people just don't deserve to own nVIDIA cards.

This is quite a silly thing to say.

Welcome back Rollo

Indeed; it appears the AEG aren't giving up without a fight.

 

[Gstanfor]

The following is a quote from Grestorn, the creator of nHancer and explains quite nicely why the whole OpenGL bruhah is a total non-issue (at least for those intelligent enough to install and use nHancer).

B3D Link

Quote:
Originally Posted by Deathlike2
Apparently there's a horrible bug with the profiles specifically with OpenGL games in that the optimizations are not turned off when the High Quality setting is selected unless you manually disable the optimizations before you select High Quality.
The bug is not with the profile system but the control panel.

Obviously the panel "thinks" that HQ will also turn off all optimizations. But that's not the case - at least not with OpenGL games.

If you don't use the control panel at all to define your profiles (or to change the global settings) but a third party tool like nHancer, you won't have a problem with that, since nHancer allows you to change any optimization settings regardless of which quality setting you're using.

 

[5150Joker]

Originally posted by: Gstanfor
The following is a quote from Grestorn, the creator of nHancer and explains quite nicely why the whole OpenGL bruhah is a total non-issue (at least for those intelligent enough to install and use nHancer).

B3D Link

Quote:
Originally Posted by Deathlike2
Apparently there's a horrible bug with the profiles specifically with OpenGL games in that the optimizations are not turned off when the High Quality setting is selected unless you manually disable the optimizations before you select High Quality.
The bug is not with the profile system but the control panel.

Obviously the panel "thinks" that HQ will also turn off all optimizations. But that's not the case - at least not with OpenGL games.

If you don't use the control panel at all to define your profiles (or to change the global settings) but a third party tool like nHancer, you won't have a problem with that, since nHancer allows you to change any optimization settings regardless of which quality setting you're using.

This doesn't add anything new to what we already know. If opts can be shut off manually then it obviously suggests a problem with the CP but the point is that 99% of users out there don't use nHancer to adjust their CP settings, they stick with nVidia's CP. Even some sites that may bench using the CP rather than in-game settings will get skewed results. Simple problem that nVidia should have fixed in the next driver revision, at least one would hope.

 

[Gstanfor]

nVIDIA should just rip their CP out and replace it with nHancer IMHO. Various bits of the CP UI have been flaky in many driver versions for a long time now. To be honest I don't really like certain parts of the CP UI that much and the profile control section has always seemed cumbersome.

And there is no "If" about manually shutting off optimizations, you can activate and decativate them in any combo you like as I showed with a screenshot in the old shimmering thread (High peformance on with all other opts off for instance). Just because the CP allows you certain preset combos doesn't mean they are the only combos possible.

 

[5150Joker]

Originally posted by: Gstanfor
nVIDIA should just rip their CP out and replace it with nHancer IMHO. Various bits of the CP UI have been flaky in many driver versions for a long time now. To be honest I don't really like certain parts of the CP UI that much and the profile control section has always seemed cumbersome.

And there is no "If" about manually shutting off optimizations, you can activate and decativate them in any combo you like as I showed with a screenshot in the old shimmering thread (High peformance on with all other opts off for instance). Just because the CP allows you certain preset combos doesn't mean they are the only combos possible.

I personally didn't care for nHancer when I tried it, I much preferred the nVidia CP. I don't think nVidia should really change it much in the future either because right now it's nearly perfect IMO. They just need to fix this problem and it should be fine.

 

[thilanliyan]

Originally posted by: beggerking
I don't see how graphics can be rendered differently in benchmarks as compared to games. If the bug exist in the benchmark, it exists in the game. A behchmark is simply a game with timing.

3DMark is NOT a "game with timing". That would be a timedemo, which 3DMark is NOT. Timedemos are usually of an actual playable game. I know it's been beaten to death but you CANNOT play 3DMark.

 

[beggerking]

Originally posted by: thilan29

Originally posted by: beggerking
I don't see how graphics can be rendered differently in benchmarks as compared to games. If the bug exist in the benchmark, it exists in the game. A behchmark is simply a game with timing.

3DMark is NOT a "game with timing". That would be a timedemo, which 3DMark is NOT. Timedemos are usually of an actual playable game. I know it's been beaten to death but you CANNOT play 3DMark.

??? lol
of course its not a game, but it uses the same dx or opengl calls as in the game, with a timer running to calculate execution time. 3dmark then mix the result with system configuration to produce a score.