Actually, when I play using Glidos, the Kernel CPU is close to 70-80% when the game is running OK, and fall down to less than 5% when I make the action which lead to the problem (open the 3rd time the menu).

For the other case, I open a dos box, run VDMSound (Dosdrv), and run the original version of Tomb. In this case, I have also about 100% CPU used by the process, but of which only 2 or 3% used by the kernel.

I have tried with the different resolution through Glidos. From the lower to 1024x768, I can acces 2 times to the menu without problem, with the uppers, only once.
Do you mean something else by trying to lower some graphics settings ?

Hi all, I have registered this time (I am the one who open this thread)

I restarted from scratch, as I realized that I'd updated my drivers only in the middle of my former tests.

The (very) good news is that I can now enter in the game with the "standard" 1.24 version of Glidos, and that the problem to access multiple times to the menu have disapeared 😁

Then, it sounds that these problems came from the version (OpenGLide_v007b4.zip) I installed.

The concerns I'm now facing :

- The "writtings" on the menu ("Load game', "new game", slots item in the save or load menu, ...) are not in a good shape, and very difficult to read.

- All the water surfaces are "black". I can't see what's under the surface (nor what's on the surface when I'm under the water)

- I see some strange black rectangles on some places, which size are changing when I move. It seems thats these black areas appears "behind" the vegetation (ferns and others), and depending on the proximity of the surface "behind" it ?

Any idea for this new situation ?

Try going into the ring menu, select the sun glasses and turn mipmapping off. This used to solve exactly the problem you describe, but since then I have fixed the bug that was the root cause, so probably it wont help.

I just tried, and as you guested, it has not change the effect.

Just one more detail : The background on the ring menu is black, event if I am with the original .ovl file (not the "nonLFBRead" one).

Bidgi wrote:

I just tried, and as you guested, it has not change the effect.

Just one more detail : The background on the ring menu is black, event if I am with the original .ovl file (not the "nonLFBRead" one).

It does sound rather like a broken OpenGL implementation. A look at the OpenGLid.log file might tell us something.

I attach the LOG file of (probably) the 2 last trials I have done.

Seen anything in the log file which could explain the effect ?

Thanks.

Back-up your OpenGLid.ini and try this one:

1Configuration File for OpenGLide
2
3Info:
4Priority goes from 0(HIGH) to 5(IDLE)
5Texture Memory goes from 2 to 32
6Frame Buffer Memory goes from 2 to 16
7All other fields are boolean with 1(TRUE) and 0(FALSE)
8
9Version=0.09rc5
10
11[Options]
12EnableMMX=1
13CreateWindow=1
14InitFullScreen=1
15EnableMipMaps=0
16IgnorePaletteChange=0
17EnableFog=1
18EnablePrecisionFix=1
19Wrap565to5551=0
20EnableMultiTextureEXT=1
21EnablePaletteEXT=1
22EnablePackedPixelsEXT=0
23EnableVertexArrayEXT=0
24EnableSecondaryColorEXT=1
25EnableFogCoordEXT=1
26PalettePrecision=16
27TextureMemorySize=16
28WrapperPriority=2
29FrameBufferMemorySize=8

Thanks to Kaminari, I get back to work, and did it this time 😁

Actually, the setting for OpenGLid.ini did'nt work better with the current release of Glide2x.dll.
But as the effects was different with the version 0.07b4 that Paul told me to install ("clear water", but problem to access several time the menu), and the current release (access to menu OK, but "dark water"), I decided to play around with the config settings of OpenGLid.

Then I found that my menu access problems was linked to the MipMaps which were enable with 0.07b4 tests, and not with the current.
It sounds my card drivers do not supprt midmaps, and that the software emulation does'nt work so well.
When turning it off, I have clear water and can access without trouble to the menu 😜

Sound good this time. I will go to my bank to get rid of the logo 😀

By the way, you will not get rid of me as easily, I will open another thread for TRUB ... 😎

Thanks, this is useful info.