AA & AF problem

Final8y · 24 May 2009 at 20:39

J.D said:
hehe Good man!!.

I was playing a few games of that on my m8's GTX 295 yesterday. It ran sweet at 1920x1200 4xAA I think. Will my 4870 run that fluently also?. He used v-sync but I don't usually enable v-sync in anything. Unless it's a requirement then I don't have that option of course.

V-Sync is on by default in the game.
Should play sweet with a 4870.

Add me Final8ty.

J.D · 24 May 2009 at 20:47

Final8y said:
V-Sync is on by default in the game.
Should play sweet with a 4870.

Brilliant. Thank you. I never seen him set the settings for this game.

Looks like I'll be grabbing this game then.

*I will when I get it.

up2nogooduk · 24 May 2009 at 22:27

Right then.
it seems like it's not working right. i set it to aplication to use in game settings. was fine, but i'm still getting tearing, even with v sync enabled in the control pannel. so i guess i'll have to try a refresh windows install. if that don't fix, then back to nvidia i guess. pain really, coz want this card to work

Final8y · 24 May 2009 at 22:43

up2nogooduk said:
Right then.
it seems like it's not working right. i set it to aplication to use in game settings. was fine, but i'm still getting tearing, even with v sync enabled in the control pannel. so i guess i'll have to try a refresh windows install. if that don't fix, then back to nvidia i guess. pain really, coz want this card to work

You cant force Vsync in games that don't have Vsync with vista 64 through CCC.
You need D3DOverrider.

What games exactly are not working with forced AA/AF through CCC

up2nogooduk · 24 May 2009 at 23:39

Final8y said:
You cant force Vsync in games that don't have Vsync with vista 64 through CCC.
You need D3DOverrider.

What games exactly are not working with forced AA/AF through CCC

I didn't know it wouldn't work with 64bit. are they going to fix that problem.
anyway, i downloaded rivatuner, and enabled D3DOverrider, and enabled Vsync.
which sorted that problem

i force aa/af in all my games, from bf2, fc2, Race07,FIFA 09,AssassinsCree, DiRT,(which i just reinstalled to test with the card, but when i select race, the screen stays white and dont load, there is a way to sort this with vista64 bit, but can't rememeber lol) which i always done before. i tired most of them games with aplication applied in the CCC. better, but not 100% like it would be when forcing aa/af etc. im still seeing some jaggers, where i never did before. i did also notice, when driving or walking, i get this micro stutters, which is a pain. never had that before.... i guess a OS reinstall is on the cards....

Final8y · 25 May 2009 at 01:00

up2nogooduk said:
I didn't know it wouldn't work with 64bit. are they going to fix that problem.
anyway, i downloaded rivatuner, and enabled D3DOverrider, and enabled Vsync.
which sorted that problem i force aa/af in all my games, from bf2, fc2, Race07,FIFA 09,AssassinsCree, DiRT,(which i just reinstalled to test with the card, but when i select race, the screen stays white and dont load, there is a way to sort this with vista64 bit, but can't rememeber lol) which i always done before. i tired most of them games with aplication applied in the CCC. better, but not 100% like it would be when forcing aa/af etc. im still seeing some jaggers, where i never did before. i did also notice, when driving or walking, i get this micro stutters, which is a pain. never had that before.... i guess a OS reinstall is on the cards....

Dirt uses an older engine version of GRID, GRID does not allow overriding its in game AA settings if you try to force AA settings then you will get no AA at all. you have to use the in game AA settings by themselves.

Micro stutter is as multi GPU phenomenon so its not really possible on a single GPU & is a different issue to what your experiencing.

What is the rest of your setup BTW.

The no force V-sync is one of the Vista 64 rules that ATI seems unwilling to break.

thegoonden · 25 May 2009 at 07:21

A man after my own heart!
Re-installing windows takes 60 mins, getting it into a usable, non-fischer-price condition takes days and getting your DAW kit installed and working takes the same again.
I can't understand why ATI cards would try and load nvidia drivers or vice versa, I know windows has appalling hardware detection and support, but all it has to do is read a text file and load the files listed in it.
I think that either this is a myth, or windows is even worse than I thought.
Anyway, I'd rather sit on a cactus than re-install windows so if this is true I shall never be able to have an ATI card.

thegoonden · 25 May 2009 at 07:22

the microstutter mentioned will be vsync related unless you have flawless 60fps, 55 fps looks flickery and jumpy and downright horrid with vsync (and is tear-city without it).

Final8y · 25 May 2009 at 08:58

thegoonden said:
the microstutter mentioned will be vsync related unless you have flawless 60fps, 55 fps looks flickery and jumpy and downright horrid with vsync (and is tear-city without it).

Indeed.

Final8y · 25 May 2009 at 09:05

thegoonden said:
A man after my own heart!
Re-installing windows takes 60 mins, getting it into a usable, non-fischer-price condition takes days and getting your DAW kit installed and working takes the same again.
I can't understand why ATI cards would try and load nvidia drivers or vice versa, I know windows has appalling hardware detection and support, but all it has to do is read a text file and load the files listed in it.
I think that either this is a myth, or windows is even worse than I thought.
Anyway, I'd rather sit on a cactus than re-install windows so if this is true I shall never be able to have an ATI card.

Windows loads the drivers, not the cards.
There must be some reason why NV & ATI feel that they need to leave some stuff behind & some of it is obvious like configuration but there should be an option to remove everything like some other programs prompt you with that option.

thegoonden · 25 May 2009 at 09:31

I know windows loads the drivers, it reads a .inf file and loads the files listed there to drive the card.
So either ATI reference NV files in their .infs or windows really is just toally insane and a law unto itself.

up2nogooduk · 25 May 2009 at 10:48

Final8y said:
Dirt uses an older engine version of GRID, GRID does not allow overriding its in game AA settings if you try to force AA settings then you will get no AA at all. you have to use the in game AA settings by themselves.

Micro stutter is as multi GPU phenomenon so its not really possible on a single GPU & is a different issue to what your experiencing.

What is the rest of your setup BTW.

The no force V-sync is one of the Vista 64 rules that ATI seems unwilling to break.

Hi,
My set up below.
And i didn't pay that price for the card at the time BTW

the system was brought few months back. so the i7 D0 Stepping wasn't out then

it's running @ 3.6. i'm sure i can get more, but im odd, i like to run them in lol.

You're right about grid. but don't explain the why rest which worked fine by overriding with my NV card

everything works ok if i set it to application for in game AA etc. but dont look as good as when overriding

strange how other don't have this issus.
I did sort the miro stutter out

i had the ingame refresh rate set to 75hz, set it to 60, and sorted it, runs smooth now.
i'm going to do a reinstall of 64bit vista now, as i'm setting the raid0 back up.
so hopfuly this will sort the problem out for me. if not, then this sucks lol
as i really want this card to work. the price and peformance from what i read, if exellent. hopfuly the new (slighty of topic lol) dirt2 engines is going to be a lot better then the last one

Cheers.

up2nogooduk · 27 May 2009 at 22:04

It did need a window reinstall. as now the override is working. but in my view, nvidia just edges it in sharpness. as i got everything max, AA/AF etc etc. and in every game i still can see some jaggers. maybe some might not notice it. even when i play bf2, the flag has jaggers. i installed my old 8800GTS 512. and no jaggers at all

part from them jaggers(which when u look hard enough ya see them) it's a great performer ati card.
But i'm a fussy fcker.. so I get refund and go for the 275 me thinks. that's just my personal view.

Final8y · 28 May 2009 at 05:34

up2nogooduk said:
It did need a window reinstall. as now the override is working. but in my view, nvidia just edges it in sharpness. as i got everything max, AA/AF etc etc. and in every game i still can see some jaggers. maybe some might not notice it. even when i play bf2, the flag has jaggers. i installed my old 8800GTS 512. and no jaggers at all part from them jaggers(which when u look hard enough ya see them) it's a great performer ati card.
But i'm a fussy fcker.. so I get refund and go for the 275 me thinks. that's just my personal view.

AA reviews test many games between NV & ATI cards as it varies between games.
its not the same across the board, on one game NV would do better depending on the objects & on another ATI would do better depending on the objects.
The only modes worth using on ATI are Box upto 16AA & Edge detect upto 24AA. Both the Tent modes are rubbish as they blurr the whole scene.

Edge detect needs a minimum of 4XAA level set in game= Edge detect 12AA to 8XAA level set in game= Edge detect 24AA & with the Edge detect filter on in CCC. Going more than level 8XAA in game will lose Edge detect 24AA mode & will only give you 16XAA standard Box mode.

If game does not have 8XAA level to get Edge detect 24AA then Override the AA level in CCC as usual.

thegoonden · 28 May 2009 at 10:34

I assume the above rather convoluted way of getting it to play nice, while being a very good reason why an ATI equivalent of Nhancer would be so brilliant, is also the basic reason why one doesn't exist?

up2nogooduk · 28 May 2009 at 21:23

Still no joy getting rid of the jaggers

it's so in my face i hate it lol i soooooo want to keep this card. well get my replacement to a XFX one. hope it's ok to show this link below.

This guy has different settings in his CCC then me ? why is that. he has stuff like supersamplerling etc.. how comes i dont get this with my 9.5 driver. maybe thats why i can't get rid on the jaggers ?. everything else look spot on, apart from silly jaggers

Still no joy getting rid of the jaggers

it's so in my face i hate it lol i soooooo want to keep this card. well get my replacement to a XFX one. hope it's ok to show this link below.

p.s, just forward the clip to where he shows you the aa etc
http://www.youtube.com/watch?v=8GIJbjFxBgQ

Final8y · 28 May 2009 at 22:14

thegoonden said:
I assume the above rather convoluted way of getting it to play nice, while being a very good reason why an ATI equivalent of Nhancer would be so brilliant, is also the basic reason why one doesn't exist?

No you just select the filter in CCC & set your AA level in game.

Its looks complicated as i was making sure the OP understood what level of AA each filter offered.

Monkeynut · 28 May 2009 at 22:15

Have you enabled adaptive anti-aliasing and set it to "Quality"?

up2nogooduk · 29 May 2009 at 21:14

Well i tried alsorts. and still get some jaggers. i think it's a great card.
But at first i didn't know i had to download D3D overrider to get vsync to work. what are ati DOING BLIMY. they can't even sort that out in there driver on my vista64. i just find that so odd.
nvidia has none of these issues. and i have found to much messing around with the CCC to get it 98% spot on. hmmm guess i'll go back to nvida and get a 275. just my view.
oh well. thanks for you're help anyway

Final8y · 29 May 2009 at 21:28

up2nogooduk said:
Well i tried alsorts. and still get some jaggers. i think it's a great card.
But at first i didn't know i had to download D3D overrider to get vsync to work. what are ati DOING BLIMY. they can't even sort that out in there driver on my vista64. i just find that so odd.
nvidia has none of these issues. and i have found to much messing around with the CCC to get it 98% spot on. hmmm guess i'll go back to nvida and get a 275. just my view.
oh well. thanks for you're help anyway

As i mentioned before the No Force V-sync IN drivers is a part of the official Vista rules. ATI have decided not to break that rule.

Also part of the Vista rules is games res & refresh selection must be generated from what is available to the display through the driver so that there should not be a chance of out of range for the display that results in a black screen...ect.. but rules do get broken.