Those demos renders utilizes a vertex component format that is not supported by NV hw. But it should work with dgVoodoo (internal virtual card).
Anyway, a file named error.txt should always be written by the demo, you can check that out as well as dgV error messages (dbg version).

Dege wrote on 2022-07-05, 10:45:

Those demos renders utilizes a vertex component format that is not supported by NV hw. But it should work with dgVoodoo (internal virtual card).
Anyway, a file named error.txt should always be written by the demo, you can check that out as well as dgV error messages (dbg version).

Thank you, I have attached them:

"Out of videomemory" error in the log...
Increase the VRAM amount in the dgv config.

Texture memory needs to be set to 512MB (more will probably work too), but the default of 256MB is insufficient allows me to reproduce the error .

EDIT : is 256MB the default ?

OP's error :

//=====================================================
// ATI Sushi Error Log Created 7/5/2022 5:13 pm
//=====================================================
[AwFn.cpp] (line 2892): D3DAw Error: AwTexImage2D - Unable to create texture object
[SuTexture.cpp] (line 3196): ERROR: Unable to load texture: color 'S:/Demos/R500/Ruby3/Art/sourceimages/optico/FaceBodSkinCombine_color_2048.bmp' alpha 'S:/Demos/R500/Ruby3/Art/sourceimages/optico/FaceBodSkinCombine_Spec_2048.bmp'
[SuTexture.cpp] (line 3198): width: 2048 height: 2048 bitdepth: 32 compressed: 5 mipmapped: 1
[SuTexture.cpp] (line 3202): bytesPerImage: 5592432 totalBytes: 5592432
[SOLInternals.cpp] (line 489): ERROR: Unable to load texture!
[SOLObjectManager.cpp] (line 546): ERROR: Unable to load static textures!
[Main.cpp] (line 1098): Normal Application Exit

My reproduced error :

//=====================================================
// ATI Sushi Error Log Created 7/5/2022 10:42 am
//=====================================================
[AwFn.cpp] (line 2892): D3DAw Error: AwTexImage2D - Unable to create texture object
[SuTexture.cpp] (line 3196): ERROR: Unable to load texture: color 'S:/Demos/R500/Ruby3/Art/sourceimages/optico/FaceBodSkinCombine_color_2048.bmp' alpha 'S:/Demos/R500/Ruby3/Art/sourceimages/optico/FaceBodSkinCombine_Spec_2048.bmp'
[SuTexture.cpp] (line 3198): width: 2048 height: 2048 bitdepth: 32 compressed: 5 mipmapped: 1
[SuTexture.cpp] (line 3202): bytesPerImage: 5592432 totalBytes: 5592432
[SOLInternals.cpp] (line 489): ERROR: Unable to load texture!
[SOLObjectManager.cpp] (line 546): ERROR: Unable to load static textures!
[Main.cpp] (line 1098): Normal Application Exit

Oops my bad. When I changed the VRAM, I changed the card to something else too and thus the game didn't work. Now it is working fine. Cheers! 5 years of using dgVoodoo2 is still never enough!

Toy Shop won't load unlike The Assassin.

Error.txt almost empty:

//=====================================================
// ATI Sushi Error Log Created 7/5/2022 9:43 pm
//=====================================================

Firtasik wrote on 2022-07-05, 19:54:

Toy Shop won't load unlike The Assassin.

Error.txt almost empty:

//=====================================================
// ATI Sushi Error Log Created 7/5/2022 9:43 pm
//=====================================================

I was about to post this one as well, but when I was making a deubugview log, the demo launched.

If you noticed correctly, the demo didn't end with Exiting Demo message but it ended abruptly.

So prbably you should use DebugView and dgVoodoo2 debug build to log the details of what's happening (and post here for a mature solution)

BEEN_Nath_58 wrote on 2022-07-06, 05:23:

I was about to post this one as well, but when I was making a deubugview log, the demo launched. […]
Show full quote

Firtasik wrote on 2022-07-05, 19:54:

Toy Shop won't load unlike The Assassin.

Error.txt almost empty:

//=====================================================
// ATI Sushi Error Log Created 7/5/2022 9:43 pm
//=====================================================

I was about to post this one as well, but when I was making a deubugview log, the demo launched.

If you noticed correctly, the demo didn't end with Exiting Demo message but it ended abruptly.

So prbably you should use DebugView and dgVoodoo2 debug build to log the details of what's happening (and post here for a mature solution)

Running it ( SushiDX.exe ) in Windows XP SP3 compatibility mode fixes it for me .

darry wrote on 2022-07-06, 05:34:

BEEN_Nath_58 wrote on 2022-07-06, 05:23:

I was about to post this one as well, but when I was making a deubugview log, the demo launched. […]
Show full quote

Firtasik wrote on 2022-07-05, 19:54:

Toy Shop won't load unlike The Assassin.

Error.txt almost empty:

I was about to post this one as well, but when I was making a deubugview log, the demo launched.

If you noticed correctly, the demo didn't end with Exiting Demo message but it ended abruptly.

So prbably you should use DebugView and dgVoodoo2 debug build to log the details of what's happening (and post here for a mature solution)

Running it ( SushiDX.exe ) in Windows XP SP3 compatibility mode fixes it for me .

The demo gets PCA set on itself after a few crash. So by that theory, if you remove the XP SP3 compatibility mode, the demo will still work. To make it crash again, rename the executable to something else, such as "defrsjnhigkbtr.exe"

Removed: log had issues.

BEEN_Nath_58 wrote on 2022-07-06, 07:08:

darry wrote on 2022-07-06, 05:34:

BEEN_Nath_58 wrote on 2022-07-06, 05:23:

I was about to post this one as well, but when I was making a deubugview log, the demo launched.

If you noticed correctly, the demo didn't end with Exiting Demo message but it ended abruptly.

So prbably you should use DebugView and dgVoodoo2 debug build to log the details of what's happening (and post here for a mature solution)

Running it ( SushiDX.exe ) in Windows XP SP3 compatibility mode fixes it for me .

The demo gets PCA set on itself after a few crash. So by that theory, if you remove the XP SP3 compatibility mode, the demo will still work. To make it crash again, rename the executable to something else, such as "defrsjnhigkbtr.exe"

Removing the XP SP3 compatibility mode makes it crash again. Putting it back fixes it . I have toggled a couple of times to confirm this .
EDIT : Setting Windows 8 compatibility or XP SP2 fixes it too . Again, if I toggle compatibility mode off, it crashes again in both cases .

darry wrote on 2022-07-06, 07:29:

BEEN_Nath_58 wrote on 2022-07-06, 07:08:

darry wrote on 2022-07-06, 05:34:

Running it ( SushiDX.exe ) in Windows XP SP3 compatibility mode fixes it for me .

The demo gets PCA set on itself after a few crash. So by that theory, if you remove the XP SP3 compatibility mode, the demo will still work. To make it crash again, rename the executable to something else, such as "defrsjnhigkbtr.exe"

Removing the XP SP3 compatibility mode makes it crash again. Putting it back fixes it . I have toggled a couple of times to confirm this .
EDIT : Setting Windows 8 compatibility or XP SP2 fixes it too . Again, if I toggle compatibility mode off, it crashes again in both cases .

Ok that confirms it, it's PCA doing this, but not writing that PCA is enabled to registry. Let's see what dgVoodoo2 can do to remove this issue as well. If you use ACT, it is probable that selecting all the Windows 8 shims instead of the compatibility mode directly will cause this issue to still occur.

I updated my log, earlier one had issues. Mr Dege please check this one instead:

I forgot that this demo has a memory overwrite bug so when initializing, it either survives or not, depending on the randomized address space addresses.
Anyway, I patched it some time ago for myself for debugging purposes.

Change bytes in the executable at offset 0x1643 from

18B 44 24 74 8B 4C 24 78 56 89 44 24 10 0F BF F1 0F BF C0 0F AF F0

to

156 8D 74 24 78 AD 89 44 24 10 0F BF C8 AD 98 8D 70 03 0F AF F1 91

and it should run without any compatibility mode set and with any file name.
There is a rendering issue with this demo that I didn't dig into. Also, rendering technique of water droplet stripes does not like forced resolution AFAIR.

It runs fine after hex editing.👍

Dege wrote on 2022-07-06, 13:46:

I forgot that this demo has a memory overwrite bug so when initializing, it either survives or not, depending on the randomized […]
Show full quote

I forgot that this demo has a memory overwrite bug so when initializing, it either survives or not, depending on the randomized address space addresses.
Anyway, I patched it some time ago for myself for debugging purposes.

Change bytes in the executable at offset 0x1643 from

Copy code to clipboard

18B 44 24 74 8B 4C 24 78 56 89 44 24 10 0F BF F1 0F BF C0 0F AF F0

to

Copy code to clipboard

156 8D 74 24 78 AD 89 44 24 10 0F BF C8 AD 98 8D 70 03 0F AF F1 91

and it should run without any compatibility mode set and with any file name.
There is a rendering issue with this demo that I didn't dig into. Also, rendering technique of water droplet stripes does not like forced resolution AFAIR.

Ok it is working fine now. Did the memory overwrite bug affect the original intended OS (XP as well)?
I look forward for the rendering issue to be fixed which apparently I haven't noticed yet.

Memory overwrite bug is always a bug under any OS. XP might have had a kind of fault tolerant heap allocator, I don't know.
But anyway, the demo itself runs (mostly) with fault-tolerant-heap compatibility option applied.