I haven't got as far as Tihocan yet, but I have been getting a "read error" crash on first start up

Oops! I've broken something I guess.

Can you tell me exactly the sequence of events up to the crash?

Does removal of the equiv file stop the texture confusion?

There is one potiential problem I know about. In the past, you have had to deal with repeated textures by adding link files in the new leves that refer to the old. Now the equiv file should be doing that for you. But that may mean that you have texture packs now that give several ways to load a single texture (via the equivalence and via the link). I think Glidos may load both, and if that happens a lot, the graphics card may run out of texure memory.

I've noticed weird problems with older versions of Glidos if you have both the bitmap and a link file in a folder for any given texture -- precedence seems to vary.

Antonijadis, could you post your equiv file? I've had one idea what it could be. If you accidently applied the equiv-file generator to a folder that wasn't a direct capture, and had some links or png files in it. Then you might get an equiv-file out that said "all textures are the same".

And any information about the crash would be handy. Any little details about the order of events.

Crash occurred when ring menu should appear and when level that have been chosen trying to load.

I don't use link files. In the Textures file I put root file and in that file I put files named by level.

Antonijadis wrote:

Crash occurred when ring menu should appear and when level that have been chosen trying to load.

Is that two different points at which it crashes? Sometimes when the ring menu should appear, and sometimes when a level is loading?

Does Glidos crash so that an error dialog appears, and the main Glidos dialog disappears? Or is it just the dialog that says "Write error" that appears, with Glidos staying running?

I don't use link files. In the Textures file I put root file and in that file I put files named by level.

In any case, the equiv file looks ok. Are you getting these strange texture mapping all the time?

Yes two different. Sometimes when the ring menu should appear at start of the game just after FMV scene, but not when you cal it from the game (pause).
Well, sometimes Glidos crash when you try to go back in the game from ring menu.In that case dialog box appears, and "error 996" is written on it.
Textures error appears only in tomb of tihocan level every time.
I see this

Also, sometimes Glidos crash when camera pass thru the surface of water and dialog say "error 996".

Antonijadis wrote:

Yes two different. Sometimes when the ring menu should appear at start of the game just after FMV scene, but not when you cal it from the game (pause).

Does Glidos close after this error, or is it just the little "Write error" Dialog?

Well, sometimes Glidos crash when you try to go back in the game from ring menu.In that case dialog box appears, and "error 996" is written on it.

Again is this a little dialog, or the type that asks you whether to send info to Microsoft? If it is the send-to-microsoft type, can you get any more info from it?

Textures error appears only in tomb of tihocan level every time.
I see this

Could you upload your complete Textures folder somewhere, so I can try to reproduce the problem here?

Do any of these problems go away if you turn off texture override?

Are all these new problems in v1.33rc2, or have you seen them before?

How many questions! 😵
When I turn of texture override everything looks fine.

Earliest version of glidos are work without this problems (except one with camera).

The 996 error appears in small box with OK button. When I confirm OK button Glide server had been rejected but DOS loader still run.

About uploading, I'll try tomorrow.Happy raiding 😉

Antonijadis wrote:

How many questions! 😵

We haven't even gotten started. 😁

When I turn of texture override everything looks fine.

Looks fine and no crashes?

Could you copy out and paste the contents of that error report?

Glidos wrote:

Antonijadis wrote:

How many questions! 😵

We haven't even gotten started. 😁

I can bet on that. 😉
I hope you were talking about these files.
Also, I notice that error with textures meshes come out when I combine st. Francis folly or palace Midas or both levels with tomb of Tihocan level. When I neglect these two levels in root directory, textures in tomb of T. level looks just fine.

Ah, no, I don't know what these appcompat things are. probably the most useful thing would be your complete Textures folder, although that's probably pretty big.

I would like to help, but I don't know how to copy data from that report.
Have you an idea why things work fine without that two level?
Maybe this can help a little?

I found what caused texture meshes. Simply I forget to delete some .bmp files( silly me ) 😊 , and they made confusion. It's OK now. 😁