• 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.

x1800 vs 7800 eval

Page 3 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Originally posted by: compgeek89

I think he means take footage from somewhere in the COD2 demo so that people without COD2 can try that stretch of area and see on their own machines.

Yup, I got it now. Good idea Morph.

 
Recording a demo will not replicate shimmering on other peoples machines. Unless of course other machines shimmer as well.

If it doesn't its probably not a driver issue, but related to his particular setup.
 
Originally posted by: Ackmed
Is Ani-AF selected in the game? Try forcing AF thru the drivers, and not have it set to app preference.

Yes, try it both ways. I often try AF and AA in the game or the control panel to see what gives me better results.

 
Originally posted by: rbV5
Recording a demo will not replicate shimmering on other peoples machines. Unless of course other machines shimmer as well.

If it doesn't its probably not a driver issue, but related to his particular setup.

Yah, I didn't know what he meant at first.

 
Watched the videos. I noticed what you are talking about. I recall COD1 and my Radeon 8500 would actually show full transtitions between mipmaps and that was really annoying. What you have is hardly a distraction. Set MipMap levels to Performance and then to Full Quality and see if you notice the difference between the 2.

 
Turn off all AF in-game and just leave on HQAF in CCC.

The flickering looks like the z-fighting thing. I know it happens sometimes on badly designed maps but this kind must be setup-induced if it doesn't happen on anyone else's machine with the same drivers. Are you SURE it doesn't? Not all surfaces will have this flickering. A mapper can make one mistake overlapping two faces, just one mistake in a large map, so definitely it's not going to happen all over the place, unless he's a horrible mapper. 😉
 
Originally posted by: xtknight
Turn off all AF in-game and just leave on HQAF in CCC.

The flickering looks like the z-fighting thing. I know it happens sometimes on badly designed maps but this kind must be setup-induced if it doesn't happen on anyone else's machine with the same drivers. Are you SURE it doesn't? Not all surfaces will have this flickering. A mapper can make one mistake overlapping two faces, just one mistake in a large map, so definitely it's not going to happen all over the place, unless he's a horrible mapper. 😉

Is it always a good idea to force AF and AA in CCC or just for this game? Because I was under the impression that if a game has those settings internally, it was better to let the game control them. For instance in BF2 I let the game turn them on and leave them off in CCC.
 
Originally posted by: M0RPH
Originally posted by: xtknight
Turn off all AF in-game and just leave on HQAF in CCC.

The flickering looks like the z-fighting thing. I know it happens sometimes on badly designed maps but this kind must be setup-induced if it doesn't happen on anyone else's machine with the same drivers. Are you SURE it doesn't? Not all surfaces will have this flickering. A mapper can make one mistake overlapping two faces, just one mistake in a large map, so definitely it's not going to happen all over the place, unless he's a horrible mapper. 😉

Is it always a good idea to force AF and AA in CCC or just for this game? Because I was under the impression that if a game has those settings internally, it was better to let the game control them. For instance in BF2 I let the game turn them on and leave them off in CCC.
I thought so too... so...
 
Generally you leave AF on in-game and just do app preference in CCC but I'm not sure about the HQAF thing. Is HQAF something you have to turn on or is it HQAF all the time? If you leave it at app preference the game isn't turning on HQAF probably, just AF, if I understand how it works...
 
Originally posted by: xtknight
Generally you leave AF on in-game and just do app preference in CCC but I'm not sure about the HQAF thing. Is HQAF something you have to turn on or is it HQAF all the time? If you leave it at app preference the game isn't turning on HQAF probably, just AF, if I understand how it works...

By default, HQ AF is not enabled. To enable it, you have to uncheck application controlled AF and then check the HQ AF box. Then you can select application control for AF and it will use angle independant modes with the application AF settings.
 
I press Ctrl+Esc, and it was fine when I had my GTXs, but now when I try to re-enter the game it says "DirectX encountered an unrecoverable error."
 
So "no" then. Also your CPU looks like it's overclocked as well.

Start another thread when you run your hardware at rated levels because your comments right now are quite invalid.
 
Originally posted by: BFG10K
So "no" then. Also your CPU looks like it's overclocked as well.

Start another thread when you run your hardware at rated levels because your comments right now are quite invalid.

HOW
 
Let me get this straight: you run your hardware outside of it's rated spec, post problems you're having and then can't figure out why your comments are worthless?

You see folks, this is what happens when kiddies get access to overclocking tools and gain the ability to post on the internet.
 
Originally posted by: BFG10K
My system isnt unstable,
but now when I try to re-enter the game it says "DirectX encountered an unrecoverable error."
That sounds like it's unstable to me.

I never had one problem with my GTXs.
That means what exactly?

You tell me how that means its unstable, sounds like bad drivers to me.

My GTXs were always fine in the same system, and they were overclocked a lot.
 
You tell me how that means its unstable, sounds like bad drivers to me.
:roll:

It's obvious that I'm talking to someone who knows how to move clock sliders backwards and forwards but nothing else.
 
Back
Top