Nasty. Seems like the game is crashing outside of psVoodoo, but it must be something to do with psVoodoo if other wrappers work ok. Have you tried any other Direct3D-based wrappers?

That is an old version of psVoodoo. You can always get the latest version by installing Glidos and pulling it out of the install folder. I'll attach it to this post though, to save you the trouble.

Is there a demo of the game I could download to try out? Unlikely, but I might be able to find what's going on.

Many thanks for your answer!

I tried the latest version you provided but get the same crash with exactly the same log file contents, except for the version of course.
I stated earlier that OpenGlide works, but it doesn't. What was happening was that OpenGlide crashed early on because it couldn't find SDL, then the game continued using its own software renderer. Installing SDL caused the game to crash with OpenGlide, although with a different error than with psVooodoo.

The wrapper dgVoodoo, which uses Direct3D, works fine with the game.

I'll investigate further.....

...and a debug build of psVoodoo yields the same result, but with the following log file:
psVoodoo v0.12
Warning: grGlideInit called
Warning: grSstQueryHardware called
Warning: grSstSelect called
Warning: grTexMinAddress called
Warning: grTexMaxAddress called
Warning: grSstWinOpen called
Shader Version: FFFF0300
Number of texture stages: 8
Number of simultaneous texture: 8
Warning: TEXOP_PREMODULATE not supported
Warning: grClipWindow called
Warning: grFogMode called
Warning: grChromakeyMode called
Warning: grChromakeyValue called
Warning: grGammaCorrectionValue called
Warning: grBufferClear called
Warning: grBufferSwap called
Warning: grTexDownloadMipMapLevelPartial called
Warning: unsupported grTexMipMapMode called
Warning: grTexTextureMemRequired called
Warning: grSstWinClose called
Warning: grGlideShutdown called

Useful. Perhaps grTexTextureMemRequired is returning a rediculously large value, and the attempt by the program to allocate such a buffer fails.

Thanks. I put in a trace, hopefully in the right place, to log the value that is returned from that function and now the last part of the log looks like this:

Warning: grTexTextureMemRequired called
grTexTextureMemRequired:4096
grTexTextureMemRequired:4096
grTexTextureMemRequired:4096
grTexTextureMemRequired:4096
grTexTextureMemRequired:65536
Warning: grSstWinClose called
Warning: grGlideShutdown called

That 65536 seems to stand out somewhat....

Thanks. Can you get the arguments passed in?

Sure....if this is what you mean:

Warning: grTexTextureMemRequired called
evenOdd :3
aspectRatio :3
format :5
LargeLod :2
SmallLod :2
returned size:4096

evenOdd :3
aspectRatio :3
format :5
LargeLod :2
SmallLod :2
returned size:4096

evenOdd :3
aspectRatio :3
format :5
LargeLod :2
SmallLod :2
returned size:4096

evenOdd :3
aspectRatio :3
format :5
LargeLod :2
SmallLod :2
returned size:4096

evenOdd :3
aspectRatio :3
format :5
LargeLod :0
SmallLod :0
returned size:65536

Warning: grSstWinClose called
Warning: grGlideShutdown called

Where:
evenOdd 3=??
aspectRatio 3=GR_ASPECT_1x1
format 5=GR_TEXFMT_P_8
Lod 2/0=GR_LOD_64 /GR_LOD_256

Hmmm! 🙁 65536 is correct, in that case. It's not a huge amount anyway. Not sure where to go from here

OK, thanks. I'll plug away at this as time permits.
I downloaded a 3dFX demo from the olden days which works fine with psVoodoo, so at least I can see what a log of a working application looks like.

Stumped right now...

So, the basic problem is that TAW crashes with psVoodoo with 'Insufficient Memory for Clamp Textures'.
I can get the same error with the otherwise functioning dgVoodoo by limiting the texture memory to 1024kB in dgVoodoo's config utility.

psVoodoo reports 16MB texture memory available by default, but changing this up or down makes no difference.

Running TAW in a debugger(IDA) seems to indicate that the game is getting to the point where it compares the texture memory required with the maximum available before it knows what the maximum available is. This is at odds with the psVoodoo log, which shows that it has reported back this value.

...investigation continuing.....

1FX_ENTRY FxBool FX_CALL grSstQueryHardware(GrHwConfiguration *hwconfig)
2{
3    LOGCALL(ECALL_grSstQueryHardware);
4
5    hwconfig->num_sst = 1;
6
7    hwconfig->SSTs[0].type = GR_SSTTYPE_VOODOO;
8
9    hwconfig->SSTs[0].sstBoard.VoodooConfig.fbRam     = 8;
10    hwconfig->SSTs[0].sstBoard.VoodooConfig.fbiRev    = 2;
11    hwconfig->SSTs[0].sstBoard.VoodooConfig.nTexelfx  = 1;
12    hwconfig->SSTs[0].sstBoard.VoodooConfig.sliDetect = FXFALSE;
13
14    hwconfig->SSTs[0].sstBoard.VoodooConfig.tmuConfig[0].tmuRev = 1;
15    hwconfig->SSTs[0].sstBoard.VoodooConfig.tmuConfig[0].tmuRam = TEXMEMSIZE;
16
17    return FXTRUE;
18}

Isn't that reporting 8MB?

TEXMEMSIZE is hardcoded to 16MB here:

1#define TEXMEMSIZE (16*1024*1024)

and this is reported back in the grTexMaxAddress call:

1Warning: grGlideInit called
2Warning: grSstQueryHardware called
3Warning: grSstSelect called
4Warning: grTexMinAddress called
5grTexMin       :0
6Warning: grTexMaxAddress called
7grTexMax       :16777216
8Warning: grSstWinOpen called
9Shader Version: FFFF0300
10...etc

I thought maybe the game was having trouble with too much memory, but changing this value made no difference.

Seems to be a timing issue. The object 'glide' is not created until 'grSstWinOpen' is called but 'glide' is somehow involved in the 'grTexMinAddress' and 'grTexMaxAddress' calls which precede it.

I moved the line:
glide = new CGlide(&config);
into the 'grTexMinAddress' function and now the game starts. 😀

I can fly round a bit, then the game crashes with 'ERROR : Failed to read region.' This is probably related to the last entries of the psVoodoo log:

1..
2Pixel Shader:
3ps_1_1
4def c0, 0.0, 0.0, 0.0, 0.0
5def c1, 1.0, 1.0, 1.0, 1.0
6tex t0
7mul r0.rgb, c1, t0
8mov r0.a, v0
9
10Warning: unsupported grSstIdle called
11Warning: unsupported grLfbReadRegion called
12Warning: grSstWinClose called

Is that serious?

bored wrote:

Seems to be a timing issue. The object 'glide' is not created until 'grSstWinOpen' is called but 'glide' is somehow involved in […]
Show full quote

Seems to be a timing issue. The object 'glide' is not created until 'grSstWinOpen' is called but 'glide' is somehow involved in the 'grTexMinAddress' and 'grTexMaxAddress' calls which precede it.

I moved the line:
glide = new CGlide(&config);
into the 'grTexMinAddress' function and now the game starts. 😀

Excellent. Well spotted. I'll need to find a better way to initialise that.

I can fly round a bit, then the game crashes with 'ERROR : Failed to read region.' This is probably related to the last entries […]
Show full quote

I can fly round a bit, then the game crashes with 'ERROR : Failed to read region.' This is probably related to the last entries of the psVoodoo log:

Copy code to clipboard

1..
2Pixel Shader:
3ps_1_1
4def c0, 0.0, 0.0, 0.0, 0.0
5def c1, 1.0, 1.0, 1.0, 1.0
6tex t0
7mul r0.rgb, c1, t0
8mov r0.a, v0
9
10Warning: unsupported grSstIdle called
11Warning: unsupported grLfbReadRegion called
12Warning: grSstWinClose called

Is that serious?

Pretty sure grSstIdle does nothing very complicated. Should be easy to implement. grLfbReadRegion will probably be a little more work, but should be just a variation on grLfbReadBuffer. I'll have a look when I get the chance.

Thanks for all the analysis. This is the first time I've had any benefit out of making it open source.

Thank you for making it open source. It's been a pleasure investigating this. 😀

The game looks great before it crashes and if I select a 'Smartview' mode, where the camera follows different active units, it doesn't crash at all.

If it's easier in the short term just to provide some dummy data so that the game can continue, then the parameters associated with the 'grLfbReadRegion' call are as follows:
src_buffer=GR_BUFFER_BACKBUFFER
src_x=0
src_y=0
src_width=800
src_height=600
dst_stride=1600

I've implemented grLfbReadRegion and updated grTexMinAddress/grTexMaxAddress so that they don't rely on the glide object. If you pull from the repo, you should get the changes.

Cheers,
Paul.

Many thanks for that 😀 , but now I get this 🙁 :

1..
2Warning: unsupported grSstIdle called
3Warning: grLfbReadRegion called
4Warning: unsupported grLfbWriteRegion called
5Warning: grSstWinClose called

I guess that's to be expected. What's the point of reading the screen if it's not going to be written back to cover up some activity?

I did think to myself that I should add grLfbWriteRegion too, but laziness won. I'll add it soon.

Okay, try again now.