I split this post to a separate topic because it's not a regressive bug.

So, from a quick try and examination, I get to the following: the game checks if D32 depth buffer format is supported, and chooses it if it is. The problem is that this format (like D16 for 16 bit modes) doesn't contain a stencil component but the game renderer relies on stenciling. So, it won't work, dgVoodoo even throws Clear operations back with an error because of that. This seems to be a programming error to me from the game side.

I tried 2.75.1 with GF 5700 Ultra which doesn't support D32 but only the traditional D24S8 format and the game works perfectly. Even the framerate is smooth 60 FPS.
Didn't you copy the d3d8 dll from the _dbg version of dgVoodoo?

I used the debug version d3d8.dll and this was the result

It's strange then. Even with the dbg version (which is not recommended, that's only for developer/bug checking purposes) I get 60fps.
And it's rendered as expected. (Using d3d8 of dgVoodoo, not a d3d8to9->d3d9 chain.)

Do we have different game version? Or do you have some patch applied to the vanilla game?

I am using the base game with no patches (fan made patches) and Cricket 2007 had no such game update from EA as it was discontinued then and there. How's the game using 15-17 GB RAM. The game barely even uses 1 GB RAM. I played using dgvoodoo's dx8 dll only and i still have fps in 30-40s. When the camera angle goes away from the players (models) the game gets 60 fps. Strange

That data (GPU, MEM, RAM) is system global, not per-process. 17GB is about my 100+ tabs open is the browser + VS + other things summarized.

Btw, I forget what video card you have. You mentioned NV Profile Inspector, so I guess you have nvidia. dgVoodoo has problems with AMD+D3D11, so I thought of recommending to your attention D3D12 as output API.
Does the dbg version dump any error or warning to the debug output anyway?

I have a GeForce GT 730 4GB DDR3 Version. I don't know if my gpu is the culprit although it supports dx11. It worked fine with dgvoodoo in Arma Cold War Assault with 60+fps with no graphical/renderer glitches like in Cricket 07 and other old games with proper framerates. I don't get any type of dump, error or debug log anywhere.

KvynB, I sent you a private message.

For me, It worked with dgvoodoo2, but I got graphical glitches while using it.
I tried using dxwrapper, copied dll files and enabled some options in .ini, but i experience a crash.

kols23 wrote on 2025-03-19, 06:15:

For me, It worked with dgvoodoo2, but I got graphical glitches while using it.
I tried using dxwrapper, copied dll files and enabled some options in .ini, but i experience a crash.

It produces glitches with the default "internal" virtual video card because that card exposes D32 depth buffer format as a capability, the game picks that up but cannot handle it properly because it tries to clear the non-existent stencil buffer during rendering and the related D3D call fails in dgVoodoo.

Set the virtual card type to, say, GF9800 and it should work.

I added a dbg message for that situation in the latest version but I'm thinking of removing D32 support as it seems to cause more harm than good in general.

It produces glitches with the default "internal" virtual video card because that card exposes D32 depth buffer format as a capability, the game picks that up but cannot handle it properly because it tries to clear the non-existent stencil buffer during rendering and the related D3D call fails in dgVoodoo.

Set the virtual card type to, say, GF9800 and it should work.

I added a dbg message for that situation in the latest version but I'm thinking of removing D32 support as it seems to cause more harm than good in general.

yeah, now it's working for me.
i use windows 11. at first the game didn't open, but now it opens using dgvooodoo2 and doesn't show graphical glitches after choosing gf9800.

but i don't know how some users got the game running in windows 11 without using dgvoodoo2.

kols23 wrote on 2025-03-19, 13:59:

but i don't know how some users got the game running in windows 11 without using dgvoodoo2.

Probably because they have better drivers. I am luckily one of them

one of my friend tried to run it with dgvoodoo2, the game opened, then he saw some glitches. so he removed those dgvoodoo2 dll files and then pasted the dxwrapper dll files.
then the game opened successfully without any glitch.

so after sometime, he removed those dxwrapper dll files and tested whether the game can be opened.
suddenly the game opened successfully without using dgvoodoo2 or dxwrapper.
I don't know how that is possible.

He did the same steps in another windows 11 pc
But the game didn't open.

Some users say that this game works on Intel but not on AMD CPUs.

kols23 wrote on 2025-03-28, 05:12:

Some users say that this game works on Intel but not on AMD CPUs.

nothing like that. The game code looks standard enough and works fine on my AMD.