Pipedream Demo running on NV34

Z

Zephyr

Newcomer
Some interesting information I found today:

1) ATi’s 9700 Demo also can run in NV3x. It is a pity that only PipeDream demo can work correctly. One reason for this is NV3x cannot support MRT, another reason is current Detonator FX drivers (44.03, 44.10 and 44.60) cannot support some render target formats, such as: D3DFMT_A16B16G16R16F and D3DFMT_A32B32G32R32F.

NV34 is running PipeDream Demo:

snap014.png

snap019.png


Bear Demo, poor bear, its body is lost.

snap009.png


Chimp Demo, both chimp's body and butterfly's wings are lost.

snap023.png


2) It seems NV3x's PS2.0(3DMark03) IQ is correct now, when using 44.60.

NV34 (44.10)

pic00660-44.10.png


NV34(44.60)

pic00660-44.60.png


DX9Ref

pic_sdk_00660.png


However, I see some abnormals when I run TreasureChest Demo, ShaderMark and rthdribl on NV34 with 44.60.
 
If the drivers do not support Multiple Render Targets (DX9 Spec is 3 right ??) how are these drivers getting DX9 WHQL certification ??
 
Doomtrooper said:
If the drivers do not support Multiple Render Targets (DX9 Spec is 3 right ??) how are these drivers getting DX9 WHQL certification ??
Click to expand...

Oh, quite simply because MRT is not required for DX9 compliancy :)


Uttar
 
Doomtrooper said:
If the drivers do not support Multiple Render Targets (DX9 Spec is 3 right ??) how are these drivers getting DX9 WHQL certification ??
Click to expand...

Is MRT one of those "required" things like FP24 or higher, or is it like partial-precision?(Forgive my weak DX9-fu)
 
Doomtrooper said:
If the drivers do not support Multiple Render Targets (DX9 Spec is 3 right ??) how are these drivers getting DX9 WHQL certification ??
Click to expand...

I also checked Caps in 44.03WHQL(NV34) and Catalyst 2.4(R300) today, here are the difference:

1) HOS, R300 is the winner:
a, support 8 level NPatch
b, support Pre-sampled Displacement Map

2) VS2.0, NV34 is better:
a, support dynamical flow control (depth up to 24)
b, support predication
It should be noted that R300 has more temp registers: 16 vs 13

3) PS2.0, NV34 is also better:
a, support Arbitrary Swizzle
b, support Gradient Instructions
c, support Predication
d, no Dependent Read Limit
e, no Tex instruction limit
f, more temp registers: 28 vs 12

4) Texture formats and Render-Target Formats, R300 does a better job:
supports many new formats, such as D3DFMT_A2B10G10R10, D3DFMT_A16B16G16R16, D3DFMT_A16B16G16R16F, D3DFMT_A32B32G32R32F etc.

It is strange, because NV34 supports NV_float_buffer.

As you can see, no one can support Adaptive NPatch or RTPatch, at least in the current driver release, but both of them still can get the WHQL logo. So I don't think they need to satisfy all of DX9 features to get WHQL certification.
 
MRT is no requirement for DX9.

But where are the cymbals on the first pipe dream shot? And which noise function does 3DMark03 use?
 
DirectX doesn't require specific features (other than basic rendering) to be WHQL compliant. A video card doesn't even need to support PS/VS 2.0 in order to get DirectX 9 certified WHQL drivers.
 
2) It seems NV3x's PS2.0(3DMark03) IQ is correct now, when using 44.60.
Click to expand...

Try running it with the 3.3.0 patch which forces it to FP32.

Xmas said:
And which noise function does 3DMark03 use?
Click to expand...

Marble:

Code: 
Color = lerp(DarkMarble,
LightMarble,
sin((turbulence(Position + Frequency)+ Position.x * Scale) * PI)

Wood:

Code: 
Color = smoothpulsetrain(LightWood,
DarkWood,
turbulence(RingOffset))
 
DaveBaumann said:
2) It seems NV3x's PS2.0(3DMark03) IQ is correct now, when using 44.60.
Click to expand...

Try running it with the 3.3.0 patch which forces it to FP32.
Click to expand...

I have already used 3.3.0 patch with both 44.10 and 44.60. And there is almost no performance drop between 44.60 with 3.3.0 patch and 44.03 with 3.2.0 patch.
 
Doomtrooper said:
Again there is something that prevents IHVs from being DX9 'Qualified' vs 'Compliant'.
Click to expand...
As far as I know, there is no specific, official definition of what makes a video card "DX9" vs. "DX8." It's all just colloquial definitions.

What makes DX7:
Hardware T&L, DOT3 bumpmapping

DX8:
VS/PS 1.0+

DX9:
VS/PS 2.0+

One thing that will throw a wrinkle in all of this is PS/VS 3.0, as cards will have significantly more functionality without a new DX version. An easier way may be just to call them by the first digit of their model number (it's been consistent since the GeForce/Radeon):
GeForce/Radeon: 1-series
GeForce3/Radeon 8500: 2-series
GeForce FX/Radeon 9700: 3-series
Next gen: 4-series

That, or just by the PS version.
 
Zephyr said:
Some interesting information I found today:

1) ATi’s 9700 Demo also can run in NV3x. It is a pity that only PipeDream demo can work correctly. One reason for this is NV3x cannot support MRT, another reason is current Detonator FX drivers (44.03, 44.10 and 44.60) cannot support some render target formats, such as: D3DFMT_A16B16G16R16F and D3DFMT_A32B32G32R32F.

NV34 is running PipeDream Demo:
Click to expand...

Well, if this screen shot is accurate it doesn't appear PipeDream is rendering correctly, either. Notice in your first shot the absence of the several cymbals that were not rendered...

Edit: I see xMas beat me to it...;)
 
DaveBaumann said:
Sorry - try running it with 44.03 and the 3.3.0 patch and look at the quality of rendering.
Click to expand...

the quality of rendering is just like 44.10 picture with many black dots.
 
WaltC said:
Well, if this screen shot is accurate it doesn't appear PipeDream is rendering correctly, either. Notice in your first shot the absence of the several cymbals that were not rendered...

Edit: I see xMas beat me to it...;)
Click to expand...

Yes, I have noticed it, however it is already much better than other demos :LOL:
 
Zephyr said:
I have already used 3.3.0 patch with both 44.10 and 44.60. And there is almost no performance drop between 44.60 with 3.3.0 patch and 44.03 with 3.2.0 patch.
Click to expand...

Wanna try these 44.60 deto's with 5800 Ultra :)
 
I cannot provide the driver's link due to no such link, sorry.

However, I believe we can try Denotator FX wich FP render target formats support soon.

post-1-1054808211.png
 
You must log in or register to reply here.
Back
Top