New D3D FSAA Viewer

Joe DeFuria said:
that note...it is my understanding that triple buffering can NOT be forced via drivers in D3D, it must be supported by the app. (Is that correct?) In GL, on the other hand, it is possible for the driver to force triple buffering.
That's my understanding too, but this temporal AA seems to be breaking that rule all to sheeit from my observations.

What up with that? I ain't complaining as I love it, I'm just kind of curious.
 
digitalwanderer said:
Joe DeFuria said:
I'm sure we won't get any official comments on it until Tuesday. (R420 launch).
I'm afraid to even e-mail anyone at ATi about it. I figure they must be pissed that it leaked.

Yeah...maybe a little....though it leaked only "one week" before launch, which isn't too bad. ;)
 
digitalwanderer said:
Joe DeFuria said:
I'm sure we won't get any official comments on it until Tuesday. (R420 launch).
I'm afraid to even e-mail anyone at ATi about it. I figure they must be pissed that it leaked.

I'm surprised thet no other sites are talking about it. Fuad must have missed the thread here. :)
 
Moose said:
I'm surprised thet no other sites are talking about it. Fuad must have missed the thread here. :)
I actually told him about it yesterday when I e-mailed him a thank-you for linking me, I was kind of surprised not to see anything on it on the Inq this morning too.
 
reever said:
Why is this a hiden option though, does anybdy have any comments from Ati about it?

its stated as being leaked information - you dont think someone just stumbled across this do you? the entry isn't even in the reg - you have to add it manually, so unless someone pulled apart the drivers and figured it out :oops:

i'm sure ATI will comment on this with the launch of the X800 - its sure to feature it.

perhaps before.

Cheers Joe too, makes sense :D
 
Colourless said:
Sites may not be posting info about it because they might actually be under NDA regarding it you know.

I was just thinking that. Although many sites are probably not under NDA.
 
Actually, I found out it wasn't leaked. tEd figured it out with a bit of snooping around in the drivers after our T-AA speculation two days ago (which I duplicated on R3D a little).
 
MuFu said:
Actually, I found out it wasn't leaked. tEd figured it out with a bit of snooping around in the drivers after our T-AA speculation two days ago (which I duplicated on R3D a little).

Its amazing how you stumble on something like Temporal AA though?
 
MuFu said:
Actually, I found out it wasn't leaked. tEd figured it out with a bit of snooping around in the drivers after our T-AA speculation two days ago (which I duplicated on R3D a little).
So did he find that string in some drivers or did he just guess it? (If he guessed it, he's a DAMNED good guesser! :oops: )
 
mreman4k said:
MuFu said:
Actually, I found out it wasn't leaked. tEd figured it out with a bit of snooping around in the drivers after our T-AA speculation two days ago (which I duplicated on R3D a little).

Its amazing how you stumble on something like Temporal AA though?

lol indeed :rolleyes:

however, i salute you for doing so, however it happened 8)
 
MuFu said:
Actually, I found out it wasn't leaked. tEd figured it out with a bit of snooping around in the drivers after our T-AA speculation two days ago (which I duplicated on R3D a little).
I am sure it was a big surprise to you. :LOL:
MuFu said:
Well, it's based on R3x0, so assuming similar limitations - 12x12 sparse grid (?), 6 sample positions max - how can they get higher FSAA quality? Would be a shame to waste all those excess FPS at low resolutions, huh? :D

MuFu said:
Still much faster than nV when running full precision shaders in the vast majority of cases; sometimes by ~100% in synthetic benchmarks (and that's just the X800 Pro, heh).

Going to have to revise that, sorry - a very occasional ~100% lead for the XT in synth tests, not the Pro. It's not getting any slower, but I am.

BTW I would ignore the talk of 600MHz R420s etc. Sounds like 500/1000MHz max for the XT, IMHO.
 
Yep, what a shocker. :)

You can often reverse engineer drivers to the point of being able to derive hidden reg strings etc.
 
MuFu said:
You can often reverse engineer drivers to the point of being able to derive hidden reg strings etc.
Ah, thanks. I was afraid it was a beta-tester leak and just wanted to make sure there was another way it could have been found out.

Faboo find, many thanks and happies! 8)
 
digitalwanderer said:
Kombatant said:
It is not launched yet.. it's just hidden in the drivers, and probably not in its final form.

As for the surprise ATI has for us... well... nope, that's not it ;)
I forget, can I call you a "penis" on this forum or not? :|

So it seems... but i <3 you anyway :mrgreen:
 
MuFu said:
Yep, what a shocker. :)

You can often reverse engineer drivers to the point of being able to derive hidden reg strings etc.

Haven't Catalyst Beta Testers had access to this? Some catalyst tester (I believe it was GandalftheWhite) over on R3d mentioned like 2 weeks ago that there would be new AA features soon for R3x0 cards, so I just assumed they've been testing it recently.

and I would further assume that somebody using beta cats checked their registry and leaked the info.
 
digitalwanderer said:
Kombatant said:
So it seems
Good.

YOU PENIS!!!!

heart.gif
 
Back
Top