How long before a X800 wrapper (Ruby demo) appears?

[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]

Re: Endless Elbow

[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]

Re: Endless Elbow

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]

Got some issues running it

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-X800-DoubleCross-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]

Re: Got some issues running it

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]

BAD NEWS! fix

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.

 

[fileedit]

Thank you very nice job!!!!

Aslo,I am still looking for the crack which can make R3xx runing
Nv3X Demoes. It is really hopless?????

 

[OneCool]

This is by far one of the best threads i've read in a LONG TIME!!!!!!!!!!!
8) good stuff

 

[ChrisRay]

I cant get this demo to work on my 6800 Non Ultra with either the 3danalyze or Nv3x fix with the 61.34 drivers,

Any suggestions?

 

[Kaiser]

Hey all,

I got Ruby up and running on my GF 5900XT thank to Colourless' handiwork, and she looks great for the most part! Albeit at 3 frames/sec...

Pertinent system specs:
128MB GF 5900XT @ 440/790 (v56.72 drivers)
3.3GHZ P4
1GB PC3200 RAM
SATA-150 HDD
(oh and AGP aperture set 256MB...made a huge performance diff, i.e. 3-4fps vs. 1 )

- Kai

 

[Mendel]

hmm the 2nd pic seems weird. is that b/c of fp16?

 

[Rage2Wrath]

Help

I'm trying to get this ruby demo to run well, and no matter what i do it runs terribly. I set my AGP Apeture size to 256 megs, turned the resolution to 640 by 480, but no matter what I do I still get like 1 frame every 5 seconds. Is that what I should be expecting with my system? Or is there something else I have to try?

 

[Mendel]

Re: Help

I'm trying to get this ruby demo to run well, and no matter what i do it runs terribly. I set my AGP Apeture size to 256 megs, turned the resolution to 640 by 480, but no matter what I do I still get like 1 frame every 5 seconds. Is that what I should be expecting with my system? Or is there something else I have to try?

0.2 fps with that system

No, that's definitely not what you should be expecting.
I have a similar system that runs ruby just fine.

What you should try? Well... there could be number of things, something must be eating your resources. Try program called enditall... try with ati catalyst instead of omega, check for viruses etc...

Does other heavy benchmarks, like 3dmark and aquamark... even games run ok?

 

[KimB]

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

Either lower the resolution or inrease your AGP aperture size. You're running out of memory.

 

[vnet]

Second pic: Ruby has the mark of the beast.

 

[kaoman]

The r300rubyrap2 works great with the crowd demo - minus the fact that the soldiers are missing in normal mode. You can see their shadows though.

I tested this with a 9800xt - the framerate was very smooth.