Volari screenshots

[incurable]

Hi all,

Here's the update using the new drivers...

http://www.driverheaven.net/reviews/Volari/update1.htm

Stu

Thanks for your update! After reading it, I can only image what PITA this card really is.

Anyway, two notworthy things:

... there was a drop in performance making the game even more unplayable.

MDolenc?s Fillrate Tester -
--------------------------
Display adapter: XGI Volari Family
Driver version: 6.14.10.1020
Display mode: 1024x768 A8R8G8B8 85Hz
Z-Buffer format: D32
--------------------------

FFP - Pure fillrate - 1397.547852M pixels/sec
FFP - Z pixel rate - 1033.910034M pixels/sec
FFP - Single texture - 213.602646M pixels/sec
FFP - Dual texture - 244.201492M pixels/sec
FFP - Triple texture - 231.460052M pixels/sec
FFP - Quad texture - 135.523285M pixels/sec

What do these numbers suggest regarding the V8's basic architecture? :? :?

cu

incurable

 

[vnet]

read what he wrote about it in the review.

I'm sorry, but if you say "the game does not run", but mean that "the game will freeze for a few seconds during cutscenes which is annoying" is simply not at all the same meaning. I'm sure everyone will agree on this.

If you go by this logic, then the word "unplayable" used could also mean "playable but below the 60fps bar" or the other way round and there's no telling where all this could lead to.

 

[Hanners]

I'm sorry, but if you say "the game does not run", but mean that "the game will freeze for a few seconds during cutscenes which is annoying" is simply not at all the same meaning. I'm sure everyone will agree on this.

The review update says it crashes. Now, I would say that a game that crashes every time is unplayable, wouldn't you?

 

[Veridian3]

I'm sorry, but if you say "the game does not run", but mean that "the game will freeze for a few seconds during cutscenes which is annoying" is simply not at all the same meaning. I'm sure everyone will agree on this.

The review update says it crashes. Now, I would say that a game that crashes every time is unplayable, wouldn't you?

Got it spot on Hanners, in a game where the story is advanced/relys on movie cutscenes so much, each of which crashes the Volari V8 DUO, then the game is unplayable imho.

Vnet, its not "freezing every few seconds" its a complete lockup of the pc which can only be resolved by killing the power or hitting the reset button. If we take the first level as an example there are 5 cutscenes that would cause a crash...not really acceptable/playable. I tried everything to fix this using ingame settings before going to XGI and Remedy about this. Remedy were not able to recreate this issue as its Duo only and XGI havent given them one and XGI's response was:

"it was the older driver which cause the crash,the newer driver shall have fix tht bug already."

That was sent to me weeks ago, yet this week new driver...no fix. I also had some interesting contradictory stories where one side was telling me one thing and the other another story...but thats a whole different issue.

On the DVD playback issue its not only power DVD, however thats the one i confirmed the bug on in 1.02.05. It happens in Media Player and WinDVD too. If you read the original review you'd see that i did comment on the fact that the settings could be manipulated to make the image watchable however is this really acceptable? We've now had 3 driver releases spanning many months where a customer cant just install their card and watch a movie! Instead they have to mess about and guess at acceptable settings.

 

[Lecram25]

Agreed. On another note, new drivers will be out towards the end of the month.

 

[StealthHawk]

Agreed. On another note, new drivers will be out towards the end of the month.

Hopefully these will be better, then.

 

[Ailuros]

Display adapter: XGI Volari Family
Driver version: 6.14.10.1020
Display mode: 1024x768 A8R8G8B8 85Hz
Z-Buffer format: D32
--------------------------

FFP - Pure fillrate - 1397.547852M pixels/sec
FFP - Z pixel rate - 1033.910034M pixels/sec
FFP - Single texture - 213.602646M pixels/sec
FFP - Dual texture - 244.201492M pixels/sec
FFP - Triple texture - 231.460052M pixels/sec
FFP - Quad texture - 135.523285M pixels/sec
PS 1.1 - Simple - 669.259460M pixels/sec
PS 1.4 - Simple - 182.736908M pixels/sec
PS 2.0 - Simple - 417.008362M pixels/sec
PS 2.0 PP - Simple - 417.005585M pixels/sec
PS 2.0 - Longer - 242.962524M pixels/sec
PS 2.0 PP - Longer - 242.989548M pixels/sec
PS 2.0 - Longer 4 Registers - 242.972504M pixels/sec
PS 2.0 PP - Longer 4 Registers - 242.963303M pixels/sec
PS 2.0 - Per Pixel Lighting - 19.593424M pixels/sec
PS 2.0 PP - Per Pixel Lighting - 19.593660M pixels/sec

Display adapter: RADEON 9700 PRO
Driver version: 6.14.10.6404
Display mode: 1024x768 A8R8G8B8 120Hz
Z-Buffer format: D24S8
--------------------------

FFP - Pure fillrate - 2227.627441M pixels/sec
FFP - Z pixel rate - 2203.179932M pixels/sec
FFP - Single texture - 2066.460205M pixels/sec
FFP - Dual texture - 1133.835449M pixels/sec
FFP - Triple texture - 565.126892M pixels/sec
FFP - Quad texture - 461.527985M pixels/sec
PS 1.1 - Simple - 1271.867065M pixels/sec
PS 1.4 - Simple - 1272.254517M pixels/sec
PS 2.0 - Simple - 1271.866333M pixels/sec
PS 2.0 PP - Simple - 1271.850220M pixels/sec
PS 2.0 - Longer - 641.254639M pixels/sec
PS 2.0 PP - Longer - 641.252136M pixels/sec
PS 2.0 - Longer 4 Registers - 641.269104M pixels/sec
PS 2.0 PP - Longer 4 Registers - 641.265442M pixels/sec
PS 2.0 - Per Pixel Lighting - 143.160461M pixels/sec
PS 2.0 PP - Per Pixel Lighting - 143.160507M pixels/sec

What do these numbers suggest regarding the V8's basic architecture?

Can't be sure yet. One thing is certain: it's definitely not an 8*2 setup per chip.

Veridian3,

Are the results the same with D24S8?

 

[Ailuros]

Did you try any of the following :
- change gamma settings
- disable the "Digital Vibrance Control" like feature called Coloramp (I believe)
- disable the "Vivid colours" setting in Power DVD or try different different video settings in Power DVD
- try different programs like Windows Media Player or Win DVD

I'm with Veridian3 on this. I don't see why a user should have to temper with settings or lucky guestimates for such a simple task as DVD playback. Monitor callibrated through the driver or 3rd party software or not.

 

[arjan de lumens]

Hmmmm ... the 'pure fillrate' number is close to the theoretical limit for 4 pixel pipelines, where the volari duo is supposed to have 16. Pixel fillrate is actually higher with triple-texturing than with single-texturing, but the numbers are so far removed from the theoretical maximums that I doubt we can extract any useful information about TMU count/organization from them.

 

[Arun]

Did you try any of the following :
- change gamma settings

Even though I also admit endusers shouldn't have problems due to simple gamma settings and shouldn't have to fiddle with them to make their games work, I've personally had problems on my GFFX 5900R using gamma settings not at 1.00 :s


Uttar

 

[Veridian3]

Veridian3,

Are the results the same with D24S8?

I'll try it tonight for you...

 

[Ailuros]

Hmmmm ... the 'pure fillrate' number is close to the theoretical limit for 4 pixel pipelines, where the volari duo is supposed to have 16. Pixel fillrate is actually higher with triple-texturing than with single-texturing, but the numbers are so far removed from the theoretical maximums that I doubt we can extract any useful information about TMU count/organization from them.

First beta driver MDolenc results could have led even to a 2*4 setup "conclusion", yet those are quite different. I'll see if I can find the old numbers somewhere.

***edit: thanks Veridian3; very kind of you

******edit Nr.2:

arjan,

These are results from the first ever beta driver:

Fillrate Tester
--------------------------
Display adapter: XGI Volari Family
Driver version: 6.14.10.1000
Display mode: 1024x768 A8R8G8B8 85Hz
Z-Buffer format: D32
--------------------------

FFP - Pure fillrate - 2822.892822M pixels/sec
FFP - Z pixel rate - 1713.361938M pixels/sec
FFP - Single texture - 495.003021M pixels/sec
FFP - Dual texture - 541.937439M pixels/sec
FFP - Triple texture - 521.537720M pixels/sec
FFP - Quad texture - 269.535889M pixels/sec
PS 1.1 - Simple - 1349.516235M pixels/sec
PS 1.4 - Simple - 361.774017M pixels/sec
PS 2.0 - Simple - 835.204102M pixels/sec
PS 2.0 PP - Simple - 835.240173M pixels/sec
PS 2.0 - Longer - 483.130280M pixels/sec
PS 2.0 PP - Longer - 483.130371M pixels/sec
PS 2.0 - Longer 4 Registers - 483.124023M pixels/sec
PS 2.0 PP - Longer 4 Registers - 483.122162M pixels/sec
PS 2.0 - Per Pixel Lighting - 38.662209M pixels/sec
PS 2.0 PP - Per Pixel Lighting - 38.663109M pixels/sec

 

[Veridian3]

Here you go...

Fillrate Tester
--------------------------
Display adapter: XGI Volari Family
Driver version: 6.14.10.1020
Display mode: 1024x768 A8R8G8B8 85Hz
Z-Buffer format: D24S8
--------------------------

FFP - Pure fillrate - 1343.432983M pixels/sec
FFP - Z pixel rate - 1217.607056M pixels/sec
FFP - Single texture - 211.818344M pixels/sec
FFP - Dual texture - 241.873444M pixels/sec
FFP - Triple texture - 229.363663M pixels/sec
FFP - Quad texture - 134.800323M pixels/sec
PS 1.1 - Simple - 652.011047M pixels/sec
PS 1.4 - Simple - 181.433945M pixels/sec
PS 2.0 - Simple - 410.220795M pixels/sec
PS 2.0 PP - Simple - 410.228180M pixels/sec
PS 2.0 - Longer - 240.647751M pixels/sec
PS 2.0 PP - Longer - 240.650864M pixels/sec
PS 2.0 - Longer 4 Registers - 240.651627M pixels/sec
PS 2.0 PP - Longer 4 Registers - 240.647888M pixels/sec
PS 2.0 - Per Pixel Lighting - 19.563841M pixels/sec
PS 2.0 PP - Per Pixel Lighting - 19.563091M pixels/sec

 

[MuFu]

Need For Speed: Underground 1024x768 0xAA 0xAF
Reactor 1.01.51 – Avg: 10.3 - Min: 7 – Max: 15
Reactor 1.02.05 - Avg: 6.8 - Min: 1 - Max: 16

Does anybody else think that's impressive, in a weird sort of way? I'd love to see FSAA benchmarks.

 

[PaulS]

They're clearly protesting at nVidia's driver tactics by going backwards in the performance stakes. Nice to see a company with a backbone nowadays!

 

[Veridian3]

Need For Speed: Underground 1024x768 0xAA 0xAF
Reactor 1.01.51 – Avg: 10.3 - Min: 7 – Max: 15
Reactor 1.02.05 - Avg: 6.8 - Min: 1 - Max: 16

Does anybody else think that's impressive, in a weird sort of way? I'd love to see FSAA benchmarks.

NOOOOOO!!!!!!! There is only so far i will go...NFS+Volari+AA/AF= death

 

[Lecram25]

Need For Speed: Underground 1024x768 0xAA 0xAF
Reactor 1.01.51 – Avg: 10.3 - Min: 7 – Max: 15
Reactor 1.02.05 - Avg: 6.8 - Min: 1 - Max: 16

Does anybody else think that's impressive, in a weird sort of way? I'd love to see FSAA benchmarks.

NOOOOOO!!!!!!! There is only so far i will go...NFS+Volari+AA/AF= death

 

[Ailuros]

Need For Speed: Underground 1024x768 0xAA 0xAF
Reactor 1.01.51 – Avg: 10.3 - Min: 7 – Max: 15
Reactor 1.02.05 - Avg: 6.8 - Min: 1 - Max: 16

Does anybody else think that's impressive, in a weird sort of way? I'd love to see FSAA benchmarks.

NOOOOOO!!!!!!! There is only so far i will go...NFS+Volari+AA/AF= death

Interested in an update concentrated on just FSAA? There are testing utilities for that too as I'm sure you know. I wouldn't be in the least surprised if it's just an edge blur filter as shots so far suggested. As far as AF goes...errrr what AF?

 

[Mendel]

What is the difference between d24s8 and d32?

Should it really halve the bandwidth?

Or is it a driver issue?

The other core disabled? Would that wxplain the performance drop across all the game benchmarks too?

 

[see colon]

Even though I also admit endusers shouldn't have problems due to simple gamma settings and shouldn't have to fiddle with them to make their games work, I've personally had problems on my GFFX 5900R using gamma settings not at 1.00 :s

for me, gamma controll in opengl was broken with the newest cat's, which is just sightly less annoying than the last sets that kept resetting the gamma of my desktop. i run a dual monitor system, and one monitor is darker than the other so i have to use gamma correction. with the newest set (4.2's) i have to change the gamma of my main monitor (the one that normaly doesn't need correction) to be able to see in opengl games.
c: