New Det 43.51 WHQL Version!

Evildeus · 04-30-03, 12:04 PM

Well, fortunately after some month the WHQL are here:

http://download.guru3d.com/detonator/

digitalwanderer · 04-30-03, 12:24 PM

Well cool for nVidia!

Oh, here's a working link to the above...it didn't work for me for some reason.

I'll be buggered, the page just loaded and there is both the xp/2k AND 9x/me WHQL certified and everything!

I'm downloading now, more as sick kids and messy house permit.

Onde Pik · 04-30-03, 12:39 PM

YAY!!! Now I wish I had an FX.

Bopple · 04-30-03, 01:51 PM

Good for nvidia.
However, i think MS should have announced FP16 be enough, if they're accepting FP16 drivers.

PS) To those who think FP problem fixed with 43.51, no it's not fixed.

BigFish7 · 04-30-03, 02:05 PM

Quote:

Originally posted by Bopple
Good for nvidia.
However, i think MS should have announced FP16 be enough, if they're accepting FP16 drivers.

PS) To those who think FP problem fixed with 43.51, no it's not fixed.

pleas prove it first..
it should be fix...

Lezmaka · 04-30-03, 02:12 PM

Well obviously something has changed with 43.51.

1. You're wrong and they don't use FP16 in 43.51
2. MS changed the min to FP16
3. MS doesn't care since the drivers drop the precision only for 3dmark03.

Has anyone been able to show that it uses FX12/FP16 in something other than 3dmark03? Show me credible evidence where it forces FP16 or FX12 in an application other than 3dmark03. How about you write an app that requests FP32 and FP16 using non-hacked drivers to show the difference, then run it using FP32 and see what comes out.

BigFish7 · 04-30-03, 02:23 PM

any change in speed or IQ?
if yes, pleas post some numbers ...
thanks

Bopple · 04-30-03, 02:36 PM

Quote:

Originally posted by BigFish7
pleas prove it first..
it should be fix...

Browse the 43.51 thread.

**jAkUp** · 04-30-03, 02:45 PM

that really doesnt prove anything. nobody has come to the conclusion that those differences are indeed caused by fp16... until someone does im going to assume nvidia was using fp32 all along.

microsoft did not change the dx9 specs... you would of heard it already. and if they did that means ati will soon change their's to fp16 also.

EDLIM · 04-30-03, 02:48 PM

This latest 43.51 WHQL.....is this a Directx 9.0 driver or just a DX8.0 driver?

**jAkUp** · 04-30-03, 02:51 PM

ummm... its both

i dont understand what your asking

Bopple · 04-30-03, 02:52 PM

Quote:

Originally posted by jAkUp
that really doesnt prove anything. nobody has come to the conclusion that those differences are indeed caused by fp16... until someone does im going to assume nvidia was using fp32 all along.

microsoft did not change the dx9 specs... you would of heard it already. and if they did that means ati will soon change their's to fp16 also.

If you apply that kind of logic, the whole FP issues become mute.
We can't prove anything exactly till nvidia disclose everything.

04-30-03, 12:04 PM	#1
Evildeus Registered User Join Date: Nov 2002 Posts: 315	New Det 43.51 WHQL Version! Well, fortunately after some month the WHQL are here: http://download.guru3d.com/detonator/ __________________ But if they think they're going to hold onto it, they're smoking something hallucinogenic - Jen-Hsun Huang Last edited by Evildeus; 04-30-03 at 12:54 PM.

04-30-03, 12:24 PM	#2
digitalwanderer BANNED Join Date: Jul 2002 Location: Highland, IN USA Posts: 6,607	Really?!?!? Well cool for nVidia! Oh, here's a working link to the above...it didn't work for me for some reason. I'll be buggered, the page just loaded and there is both the xp/2k AND 9x/me WHQL certified and everything! I'm downloading now, more as sick kids and messy house permit.

04-30-03, 12:39 PM	#3
Onde Pik Thrakhath nar Kiranka Join Date: Aug 2002 Location: Kilrah Posts: 97	YAY!!! Now I wish I had an FX. __________________ Ek’rah skabak erg Thrak’Kilrah maks Ragnith

04-30-03, 01:51 PM	#4
Bopple Registered User Join Date: Apr 2003 Posts: 208	Good for nvidia. However, i think MS should have announced FP16 be enough, if they're accepting FP16 drivers. PS) To those who think FP problem fixed with 43.51, no it's not fixed. __________________ Handsome fighter never loses battle.

04-30-03, 02:45 PM	#9
jAkUp eat. sleep. overclock. Join Date: Dec 2002 Location: Chino, California Posts: 21,766	that really doesnt prove anything. nobody has come to the conclusion that those differences are indeed caused by fp16... until someone does im going to assume nvidia was using fp32 all along. microsoft did not change the dx9 specs... you would of heard it already. and if they did that means ati will soon change their's to fp16 also. __________________ 965xe \|\| evga x58 classified \|\| 2x evga gtx 295 \|\| 6gb g.skill \|\| win7 x64

04-30-03, 02:12 PM	#6
Lezmaka Registered User Join Date: Jul 2002 Location: Indy Posts: 638	Well obviously something has changed with 43.51. 1. You're wrong and they don't use FP16 in 43.51 2. MS changed the min to FP16 3. MS doesn't care since the drivers drop the precision only for 3dmark03. Has anyone been able to show that it uses FX12/FP16 in something other than 3dmark03? Show me credible evidence where it forces FP16 or FX12 in an application other than 3dmark03. How about you write an app that requests FP32 and FP16 using non-hacked drivers to show the difference, then run it using FP32 and see what comes out.

04-30-03, 02:23 PM	#7
BigFish7 Nvidia Join Date: Feb 2003 Location: Israel. Posts: 314	any change in speed or IQ? if yes, pleas post some numbers ... thanks

04-30-03, 02:48 PM	#10
EDLIM eVGA Senior Member Join Date: Sep 2002 Location: CA Posts: 113	DIRECTX9.O DRIVER? This latest 43.51 WHQL.....is this a Directx 9.0 driver or just a DX8.0 driver?

04-30-03, 02:51 PM	#11
jAkUp eat. sleep. overclock. Join Date: Dec 2002 Location: Chino, California Posts: 21,766	ummm... its both i dont understand what your asking __________________ 965xe \|\| evga x58 classified \|\| 2x evga gtx 295 \|\| 6gb g.skill \|\| win7 x64

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)