Detonator 6.49 RELAEASED!!! beta
- Thread starter Varborta
- Start date
Here are some basic, preliminary benchmarks for anyone wondering about these new drivers.
These are in no way meant to be comprehensive. This was just a quick & dirty way to test the speed change from the 6.47 drivers to 6.49.
My system:
Duron 700
192 Megs RAM
Hercules Prophet II MX (185 core, 205 memory)
I ran demo001 twice with each driver set. The results:
6.47 drivers: 99.3 fps, 99.6 fps
6.49 drivers: 99.9 fps, 101.3 fps
If you work that out, that works out to a 0.7% increase in my Quake 3 performance. Not exactly anything worth spooging in your shorts about.
--Arschloch
Note: I suppose I should have pointed out that I ran the demos at the default "High Quality" mode (800x600, 32 bit color, etc.)
These are in no way meant to be comprehensive. This was just a quick & dirty way to test the speed change from the 6.47 drivers to 6.49.
My system:
Duron 700
192 Megs RAM
Hercules Prophet II MX (185 core, 205 memory)
I ran demo001 twice with each driver set. The results:
6.47 drivers: 99.3 fps, 99.6 fps
6.49 drivers: 99.9 fps, 101.3 fps
If you work that out, that works out to a 0.7% increase in my Quake 3 performance. Not exactly anything worth spooging in your shorts about.
--Arschloch
Note: I suppose I should have pointed out that I ran the demos at the default "High Quality" mode (800x600, 32 bit color, etc.)
I ran mine It didnt have any impact on the performance I think it is mainly fixing up problems.
mine at 1024*768 32color is 88fps high Quality
Thats not low is it?
mine at 1024*768 32color is 88fps high Quality
Thats not low is it?
"I ran mine It didnt have any impact on the performance I think it is mainly fixing up problems"
all 40-some iterations of the Det3's have been dedicated to nothing but "fixing up problems", aside from 6.31
all 40-some iterations of the Det3's have been dedicated to nothing but "fixing up problems", aside from 6.31
<< all 40-some iterations of the Det3's have been dedicated to nothing but "fixing up problems", aside from 6.31 >>
It's all part of a branding strategy. More driver releases = more news = more brand recognition for nvidia. It's yet another vast chicken-wing conspiracy.
It's all part of a branding strategy. More driver releases = more news = more brand recognition for nvidia. It's yet another vast chicken-wing conspiracy.
I'm very dissapointed with nVidia's progress with the 6.xx drivers. There's still not a version which's as stable and glitch-free as 5.30 (reference detonator) and 5.33 (Asus OEM) releases I'm using. nVidia should look into the problem with KT133 boards more aggressively.
Perhaps nVidia sees VIA as a foe, as they're entering the chipset market as well. Then again, they could be just kissing Intel's butt, with the Xbox contract and all
Perhaps nVidia sees VIA as a foe, as they're entering the chipset market as well. Then again, they could be just kissing Intel's butt, with the Xbox contract and all
What problems?
I've been using 6.47 glitch free and stable with a KT133 chipset in an Abit KT7.
Even overclocking the Duron 600 to 935MHz (8.5x110), and rock solid.
V3 3k was never stable, and was full of glitches in this system.
Did you ever think that the stability problems might have something to do with your other parts such as:
<< 256mb generic PC100/PC133 mix@PC133/CAS3/Turbo timing, 230W ATX PS, >>
I've been using 6.47 glitch free and stable with a KT133 chipset in an Abit KT7.
Even overclocking the Duron 600 to 935MHz (8.5x110), and rock solid.
V3 3k was never stable, and was full of glitches in this system.
Did you ever think that the stability problems might have something to do with your other parts such as:
<< 256mb generic PC100/PC133 mix@PC133/CAS3/Turbo timing, 230W ATX PS, >>
6.35/DX8/28.11@650 6.49/DX8/2.12@650
4111 4101 3D marks
389 386 CPU 3D marks
79,9 79,8 FPS
59,3 59,2 FPS
27,8 27,9 FPS
83,6 83,7 FPS
56,7 56,2 FPS
35,2 34,8 FPS
297,3 297,3 MTexels/s
576,9 577 MTexels/s
6704 6910 KTriangles/s
4887 4888 KTriangles/s
2866 2866 KTriangles/s
192,9 193 FPS
185,4 185,4 FPS
140,8 140,7 FPS
75,2 74,8 FPS
110,2 110,1 FPS
133,5 133,4 FPS
196,6 196,7 FPS
Not supported Not supported FPS
my specs:
p3-650e
CL GF2-MX
160MB-RAM
4111 4101 3D marks
389 386 CPU 3D marks
79,9 79,8 FPS
59,3 59,2 FPS
27,8 27,9 FPS
83,6 83,7 FPS
56,7 56,2 FPS
35,2 34,8 FPS
297,3 297,3 MTexels/s
576,9 577 MTexels/s
6704 6910 KTriangles/s
4887 4888 KTriangles/s
2866 2866 KTriangles/s
192,9 193 FPS
185,4 185,4 FPS
140,8 140,7 FPS
75,2 74,8 FPS
110,2 110,1 FPS
133,5 133,4 FPS
196,6 196,7 FPS
Not supported Not supported FPS
my specs:
p3-650e
CL GF2-MX
160MB-RAM
What problems?
I've been using 6.47 glitch free and stable with a KT133 chipset in an Abit KT7.
Problem has to do with AGP4X and Fast Writes. Fast Writes cannot be disabled with current MSI K7Tpro BIOS version (1.3). It's an option on KT7, and since in addition 6.xx's revert to AGP2X on all VIA chipset boards without the reg hack, it's possible to run Det3's stably on KT133 mobos. However, as stubborn as I am, I refuse to give up AGP features which work just fine on all previous drivers.
Gotta try the 6.47's though, that's one revision I missed.
Did you ever think that the stability problems might have something to do with your other parts such as...
How could these be the source of problems since 5.3x Detonators work 100% stable with zero problems in all my programs? It's very easy to point what's at fault here, adn that's video drivers. RAM and PS issues cause generic system instability, which unlike my old BH6/Celeron, this rig has never experienced.
I've been using 6.47 glitch free and stable with a KT133 chipset in an Abit KT7.
Problem has to do with AGP4X and Fast Writes. Fast Writes cannot be disabled with current MSI K7Tpro BIOS version (1.3). It's an option on KT7, and since in addition 6.xx's revert to AGP2X on all VIA chipset boards without the reg hack, it's possible to run Det3's stably on KT133 mobos. However, as stubborn as I am, I refuse to give up AGP features which work just fine on all previous drivers.
Gotta try the 6.47's though, that's one revision I missed.
Did you ever think that the stability problems might have something to do with your other parts such as...
How could these be the source of problems since 5.3x Detonators work 100% stable with zero problems in all my programs? It's very easy to point what's at fault here, adn that's video drivers. RAM and PS issues cause generic system instability, which unlike my old BH6/Celeron, this rig has never experienced.
Nope I tried all the 6.XX series and could not get 4X or 3D games to run stably. Back to 5.45 and I can do every thing 4X etc etc and stable as my grandma.
Even used DX8 and 7.XX series still no go.
Its all a conspiracy on Nvidia's part - a numbers game to keep its head above waters.
Even used DX8 and 7.XX series still no go.
Its all a conspiracy on Nvidia's part - a numbers game to keep its head above waters.
hmmm, I have this problem too. I have an Asus A7V and in the bios I set the performance settings to normal instead of optimal and that fixes it for me (I use the 6.31 drivers). By doing this I lose 300/400 points in 3dmark though...
I am going to experiment what's faster : optimal bios settings with 5.30 drivers or normal settings and 6.31 (or 6.49) drivers. What do you think?
I am going to experiment what's faster : optimal bios settings with 5.30 drivers or normal settings and 6.31 (or 6.49) drivers. What do you think?
I run 6.31 with agp 4x and fast writes enabled with absolutely no problems on my Abit KT7. I just installed the 4in1 drivers after a fresh format, then installed the 6.31's.
Mem
Lifer
- Apr 23, 2000
- 21,476
- 13
- 81
jpprod fastwrites can be disabled on the MSI K7T Pro board,also I`m using AGP4X with 6.31 drivers with no problems gaming wise,btw it`s worth upgrading to the lastest Bios of MSI K7T Pro (1.8) since it increased my 3DMARK2000 by more then 70 points.
Btw why are you using 1.3 bios still?,1.6 or 1.8 are better.
Btw why are you using 1.3 bios still?,1.6 or 1.8 are better.
mem: Yeah, I was using the 1.3 since I never bothered to upgrade the BIOS - I don't like booting my computer
Where can the fast writes be disabled? I just flashed to 1.8, but Fast Writes disable option doesn't seem to be anywhere. Only settings that seem to even resemble Fast Writes are AGP Master 1WS Write and AGP Master 1WS Read, they're under Advanced Chipset options.
Where can the fast writes be disabled? I just flashed to 1.8, but Fast Writes disable option doesn't seem to be anywhere. Only settings that seem to even resemble Fast Writes are AGP Master 1WS Write and AGP Master 1WS Read, they're under Advanced Chipset options.
Mem
Lifer
- Apr 23, 2000
- 21,476
- 13
- 81
jpprod,
Good question on the 1.4,1.6 Bios it was easy to find,but this new Bios 1.8 well I had a look for fastwrites myself, being this Bios is about a week old in my PC & to had trouble finding it,btw this new Bios as changed quite a few options like ram timings etc,so lots of things are new,anyway what does "Fast r-w turn around" do?I presume it means, "Fast read-write turn around" so it could be this anybody know?Btw you only have two options enable & disable ,mine is set at disable.
Good question on the 1.4,1.6 Bios it was easy to find,but this new Bios 1.8 well I had a look for fastwrites myself, being this Bios is about a week old in my PC & to had trouble finding it,btw this new Bios as changed quite a few options like ram timings etc,so lots of things are new,anyway what does "Fast r-w turn around" do?I presume it means, "Fast read-write turn around" so it could be this anybody know?Btw you only have two options enable & disable ,mine is set at disable.
jppord
when u said "no problem with 5.30", did u mean it "doesn't slow down the performance and is without stability problem at the same time"?
If this is true, maybe FW ISN'T working at all with 5.30?
when u said "no problem with 5.30", did u mean it "doesn't slow down the performance and is without stability problem at the same time"?
If this is true, maybe FW ISN'T working at all with 5.30?
jpprod
A hack and a patch are not the same thing.
A simple patch is used with VIA chipsets to enable AGP 4x.
As I said, no problems here with 6.xx, and 3DMarks 2000 scores of 7000 without any lockups or errors, should confirm they work. You mention problems with nVidia and KT133 boards, but I just wanted to point out that it is not the case. Many of us KT133 chipset owners (Abit) do not have the problems you have. So it is NOT a KT133 chipset issue that nVidia needs to check into.
A hack and a patch are not the same thing.
A simple patch is used with VIA chipsets to enable AGP 4x.
As I said, no problems here with 6.xx, and 3DMarks 2000 scores of 7000 without any lockups or errors, should confirm they work. You mention problems with nVidia and KT133 boards, but I just wanted to point out that it is not the case. Many of us KT133 chipset owners (Abit) do not have the problems you have. So it is NOT a KT133 chipset issue that nVidia needs to check into.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes + WCL Discussion Threads
- Started by Tigerick
- Replies: 24K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter