[Tim Murray]

Originally Posted by JigenD

it's actually a little faster than the standard nv3x wrapper on a nv35 card. Wonder why double pass shaders are faster than long shaders... :?

Because of the register usage penalty?

[Colourless]

I would guess as much. My new shaders are going to use less registers. and by far in general the multipass shaders are probably only going to be around the 1.5x time number of instructions. If the number of registers required drops below 8, there could be a speed increase, although a small one.

[BetrayerX]

:bow: Colourles....that is SWEEET!

If you ever decide to retouch the wrapper, I experienced something odd.

At the moment Ruby jumps from the platform, her elbow extends to infinity. You can see it from the "bad guy's" perspective and at the very end before she winks.

When the demo restarts it does all fine until the same spot is reached again.

Here's a pic:

[digitalwanderer]

Originally Posted by Ratchet

I honestly never thought to BM it before. I guess I could check.

Ruby Rap v2
2004-05-17 15:20:32 - SushiDX
Frames: 1806 - Time: 101438ms - Avg: 17.803 - Min: 3 - Max: 36

Ruby Rap v1
2004-05-17 15:37:53 - SushiDX
Frames: 3371 - Time: 101141ms - Avg: 33.329 - Min: 7 - Max: 81

Thank you, you're a scholar and a gentleman...for being a tool and all.

[micron]

This is so cool!

[Chrispy_]

I've been watching this thread since the Ruby demo was released, and seeing as Colourless has put the effort in to bring us this newer wrapper, I thought I'd show my appreciation by registering an account specially for the purpose of saying thanks for all his hard work.

That's it. First, and quite possibly the last post you'll ever see from me

Here are some numbers running on an R300 for those that are curious, Sushi.ini at default (1024 and 4xAA)
-- AthlonXP Barton @2.5GHz, 1GB @400MHz, R9700Pro @400/700, Catalyst 4.4
-- Benchmark Range[min 10.16, avg 16.45, max 94.00]
-- No graphical glitches or infinite-elbows apparent with this setup.

[Wang]

Originally Posted by BetrayerX

:bow: Colourles....that is SWEEET!

If you ever decide to retouch the wrapper, I experienced something odd.

At the moment Ruby jumps from the platform, her elbow extends to infinity. You can see it from the "bad guy's" perspective and at the very end before she winks.

When the demo restarts it does all fine until the same spot is reached again.

Here's a pic:

[snip]

The infinite elbow is not a shader error.

It's an overclock/heat error from the graphics card.
I've seen it many times...... :0

[edit:broken quote]

[Xenrid]

Love the wrapper, great work Colourless, however I am having trouble with V2. Version 1 runs like butter for me, but when I try to run version 2 it crashes while attempting to load and opens an error.txt with this info:

//================================================== ===
// ATI Sushi Error Log Created 5/17/2004 10:05 pm
//================================================== ===
[Main.cpp] (line 894): Exception caught - BAD NEWS!

I'm running CAT 4.5 with an FIC A95P (9500 Pro)
If anyone has a suggestion, It would be appreciated.
Thanks.

[Zaphod]

Originally Posted by Joe DeFuria

Can someone with a GeForceFX (or 6800 for that matter) benchmark the three versions:

How about a FX5800? All results at 800x600 4XAA, which was just barely faster than 640x480 noAA. Still some errors woth the specular/glow-effect. These were edited out before benchmarking. I would like to see if a 256MB NV38 can run this at anything resembeling decent speed. No doubt the GF6800 would do just fine, but a comparison with a 9800 and a X800 could be interresting if the wrapper can make the shaders and workload comparable.

1) Original, non-touched shaders
Frames: 388 - Time: 100313ms - Avg: 3.867 - Min: 3 - Max: 7

2) V1 Rap
Frames: 383 - Time: 98250ms - Avg: 3.905 - Min: 3 - Max: 6

3) V2 Rap
Frames: 856 - Time: 100656ms - Avg: 8.504 - Min: 6 - Max: 22

[digitalwanderer]

DUUUUUUDE!!!!!

I just got done putting me rig back together and getting it up to speed and the first thing I did was run your new wrapper.....sweeet!

The subtles of the textures are mind-blowing, it's a night/day difference from your first wrapper to me!

Ok, granted it's also a slideshow a lot of the time now....but the image quality is breath taking!

Thank you Colourless, thank you very much. 8)

[radiATIon]

Originally Posted by Xenrid

Love the wrapper, great work Colourless, however I am having trouble with V2. Version 1 runs like butter for me, but when I try to run version 2 it crashes while attempting to load and opens an error.txt with this info:

//================================================== ===
// ATI Sushi Error Log Created 5/17/2004 10:05 pm
//================================================== ===
[Main.cpp] (line 894): Exception caught - BAD NEWS!

I'm running CAT 4.5 with an FIC A95P (9500 Pro)
If anyone has a suggestion, It would be appreciated.
Thanks.

I got the same error news with CATALYST 04.5 (Omega) but the error is gone with Official CATALYST 04.5. Then I edit the omega inf & remove all tweak but the error still appears. Then I replace all driver files (not cp files) with the official files & then uninstall & install again. The same error appears. Then I install the official driver and everything OK.

Can't detect what's wrong with Omega driver.......

I'm a little confused. :? :? :? :? :?

[CopyCat]

Hi
first, thanks for the great wrapper. Really impressive.
But I have a little problem with ist: The Subsurface Demo works perfect, but the Ruby Demo freezes allways at the point, when you see Ruby's face closely (before she enters the building)
I tried ist with the first wrapper and the second. With the Ati 4.4 and 4.5 drivers and the Omegas. I changed the settings to 640x480 with 1xMultisampling. But allways the same

[Bambers]

Is it totally freezing or is it just trying to load the new info?


if you've only got a 128mb card and 512mb of ram then you will get major hdd thrashing. I have the same and it hangs at that same point and will take a few minutes to load everything properly, by which time the pc has finished the demo

[CopyCat]

I don't know exactly. The video freezes and the audio goes on.
But I have a 128MB Card and 512MB RAM. Bad luck

[Colourless]

Just let it continue to play. Because of the extreme memory requirements, windows pages out the textures. This tends to cause some rather long pauses. After 2 runs though the demo things will stabilize and the demo will begin to run somewhat smoothly.

I myself only have 512MB of Ram and a 128MB Card. Testing all the changes I was making was 'really' painful.

[radiATIon]

With Detonator 61.11, I can't run ruby demo in my FX 59XT 128MB.

Sometime it says:

[AwFn.cpp] (line 3402): D3DAw Error: AwCreateRenderableTexture - Unable to create color texture object
[StartEnd.cpp] (line 2044): Error creating color buffer "cBlurPingBuffer"!
[Main.cpp] (line 880): Normal Application Exit

Sometime:

maybe u r assigning more in a registar type error

also sometime says BAD NEWS.


I tried Someruby.zip, wrongruby.zip, r300 1.0, r300 1.1, nv3x 1.0, nv3x 1.1, r300 2.0. But no work. R300 2.0 wrapper is working with 56.72 driver, but with 61.11, nothing works.

BTW, The Demo runs fine with my 98P with any r300 wrapper. But what is wrong with 59XT & 61.11 driver???

[BetrayerX]

Originally Posted by Wang

[snip]

The infinite elbow is not a shader error.

It's an overclock/heat error from the graphics card.
I've seen it many times...... :0

[edit:broken quote]

I have it running at default speeds.... no oc/ here. I thought the same but double-checked on that

However, I ran the demo several times and It has not happened again.

[Wang]

Originally Posted by BetrayerX

I have it running at default speeds.... no oc/ here. I thought the same but double-checked on that

However, I ran the demo several times and It has not happened again.

Aye, you have a point there. I forgot that in F1 99-02 with 2xAA, I'd get
lots of those "vertices" spiking from polygons into space, which I surmised
were from OCing. They went away with 4xAA odd enough.

[rooked_one]

Well, the demo starts up just fine - no errors - and proceeds to run, giving quite a few errors, plus some pretty ... funny ... views...

Ruby doesn't have skin or hair or eyes - you can see her eyelashes, clothes, suitcase, gloves, ect....

The same goes for Cid Opitcal, the jewel thing that ruby gives Cid, and the monsters that jump down. You can see their swords, but not their skin.

Heres the errors its giving me.... sorry if its long... also, heres my system specs, and I do have my apurture set at 256. I've tried Omega's drivers, and the latest Cats, with no luck either way. Both look the same.

p4 2.4 @ ~2.8
Radeon 9800Pro 128 megs flashed to a 9800XT
512 megs RDRAM (heh)

//================================================== ===
// ATI Sushi Error Log Created 5/28/2004 12:39 am
//================================================== ===
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[qDOF.ssh] (line 490): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[qGlow.ssh] (line 317): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[qGlow.ssh] (line 397): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[qGlow.ssh] (line 1015): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[qTextureLit.ssh] (line 114): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[qTextureLit.ssh] (line 169): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[qTextureLit.ssh] (line 224): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[qTextureLit.ssh] (line 279): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[qTextureLit.ssh] (line 330): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[qTextureLit.ssh] (line 422): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[qTextureLit.ssh] (line 514): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[qTextureLit.ssh] (line 754): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[qTextureLit.ssh] (line 962): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[qTextureLit.ssh] (line 1021): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[qTextureLit.ssh] (line 1080): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[qTextureLit.ssh] (line 1139): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[oTextureLitSkGirl.ssh] (line 1216): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[oTextureLitSkWmGirl.ssh] (line 1338): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[oGirlNoTLSkinSk.ssh] (line 260): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[oGirlEyeLidWetSk.ssh] (line 254): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[oKingpinPlateSk.ssh] (line 303): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[oTextureLitSkKingPin.ssh] (line 1198): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[oTextureLitSkWmKingPin.ssh] (line 1272): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[oHair.ssh] (line 476): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[oHair.ssh] (line 617): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[oHair.ssh] (line 758): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[oEyeballSk.ssh] (line 301): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[oCorneaSk.ssh] (line 232): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[oGirlColorLeatherSk.ssh] (line 248): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[oGirlGlassSk.ssh] (line 276): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[oGirlLeatherSk.ssh] (line 258): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[oKingpinlNoTLSkinSk.ssh] (line 263): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[oNinjaSuitSk.ssh] (line 252): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[oNinjaSuitSk.ssh] (line 432): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[oGemSk.ssh] (line 384): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[oStarChromeSk.ssh] (line 294): Error creating Pixel Shader
[SSGenericAPI_D3D.cpp] (line 1312): No D3D Error message. You might be specifying more than one component on a source register.[oStarChromeSk.ssh] (line 506): Error creating Pixel Shader
[Main.cpp] (line 880): Normal Application Exit



It actually looks exactly like what the pictures on page one of this thread look like.... no skin... Whats wrong with what i'm doing here?

Also, thanks Colourless for all your work!

[robbeh]

For everyone with Exception caught - BAD NEWS! errors, i have tracked this down to qGlow.ssh in the rhino directory. Replacing this with the .ssh from V1 fixed this for me. Any idea what this could be colourless?

[robbeh]

I had a little look in the new qglow.ssh file and edited it, which has solved the Exception caught - BAD NEWS! problem for me. I opened the .ssh in notepad and searched for the line

o = WrecklessBloomFilterRGB (tPing, i.t0, i.t1, i.t2, i.t3,
under the "Wreckless5" shader

Simply deleting the empty line above this and saving the file was enough to get it working again. Anyone want to give this a try?

[robbeh]

ATi has released a new crowd demo that looks pretty wicked. Anyone else notice that with it theyve released a new version of the ruby demo, version 1.2?

get it here: http://www2.ati.com/misc/demos/ATI-X...-Demo-v1.2.exe

Anyone know if colourless's wrapper works on any of the new demos?

[shadow85]

The doublecross V1.2 work with the warpper2 ( thank's colourless's )

I hope colourless's creat a warpper for the crowd demo !!!!!




PS: sorry for my english, i'm french. )

[Mendel]

Originally Posted by rooked_one

blahblah

Seems like you never extracted the shaders folder from the rubyrap packet to the directory of the demo. You just moved direct3d9.dll to the directory?

Be sure to also extract the shaders folder and you will be fine.

[Xenrid]

Thanks robbeh. Your fix worked great for me. Seems strange that a blank line should have caused the problem Oh well. colourless's wrapper seems to work fine with V1.2 as well.