Each of the issue claims look like a fiction to me. Although I should admit I never saw anything as described on Windows 7, can you upload some screenshots or camera shots as to how they look.

About the other 8-bit issue you exaplained I probably misunderstood what you said or never have really used that workaround

in-game screenshots (F9) create .pcx image files that show up normal, so I had to take photos:
-in-game color problem (only in software mode on an unmodified game).
-normal color in the windowed gui menu.
-normal color in-game (in software mode with DGvoodoo2, and also in 3d-accelerated mode)
-desktop-screenshot showing the DGvoodoo2 DLL files added in the game folder.

note:
I'm using nvidia graphics driver 471.96 (using nvslimmer tool to install only the driver and physx).

As for the other easier problem which causes odd colors on old games on Windows 7+, it's quite common and you can find links like this:
https://metropalaboy.wordpress.com/2015/01/09 … y-in-windows-7/
which mention solutions like killing the explorer.exe process, but this is not my problem on the Geforce card.

The Geforce 960 launched the same year as Windows 10. 8 and 16 bit color support was already gone with Windows 8. Drivers probably just don't have good support for low color modes. Windows 10 is a better match for that hardware. It will at least attempt to emulate the low color modes.

Try downgrading drivers to 2015 versions, it might help.

I remembered what games had a similar issue. Frogger renders in B/W colour on post Windows 10 (1803+?).

The issue there was simple: a bugged d3dim.dll that has incomplete D3D Ramp mode.

What I am assuming is a corrupted d3dim.dll. You could try throwing in some d3dim.dll from the internet (since you are on Win7, try XP, 7 or Vista ones). It could help.

The other place where I have a black and white colour is in the D3D7 Immediate Mode demos (especially the globe demo). It is probably due to a driver bug. Maybe installing an older driver would help there, but I decided to stay with dgVoodoo2 or DDC. This problem started around the same time as your game problem, so driver is a pretty good culprit too.

That did it, thanks!
Now using Nvidia driver 347.25.
As a bonus, this old driver is not even trying connect to the internet constantly like the newer versions do.

Yea, if you want to stick to 7, you'd have to use an older driver.

I'm using driver 511.23 with a GTX 1060, and software mode looks fine on windows 10, so I suppose it got fixed with a later driver (haven't tried a newer one though).

Sorry for posting here after such a long time. I have finally found exactly what I've been going through. It started happening to me after upgrading to a GTX1660. Before that I was using a GTX460 with its latest supported drivers (391.35) and never had this issue. I was wondering which driver introduced this problem.

filipetolhuizen wrote on 2024-03-06, 04:17:

Sorry for posting here after such a long time. I have finally found exactly what I've been going through. It started happening to me after upgrading to a GTX1660. Before that I was using a GTX460 with its latest supported drivers (391.35) and never had this issue. I was wondering which driver introduced this problem.

Btw I tested the game on Win11 with the lates 551 driver on 1050Ti and the problem doesn't exist. Probably they fried their old driver

s997863 wrote on 2023-09-04, 20:36:

That did it, thanks!
Now using Nvidia driver 347.25.
As a bonus, this old driver is not even trying connect to the internet constantly like the newer versions do.

Did you get a chance to find out which driver introduced this problem? With the GTX1660 I cannot go back that far, but I know the 391.35 driver still does not have this issue, as it was my driver of choice for my earlier GTX460.

filipetolhuizen wrote on 2024-03-07, 04:07:

s997863 wrote on 2023-09-04, 20:36:

That did it, thanks!
Now using Nvidia driver 347.25.
As a bonus, this old driver is not even trying connect to the internet constantly like the newer versions do.

Did you get a chance to find out which driver introduced this problem? With the GTX1660 I cannot go back that far, but I know the 391.35 driver still does not have this issue, as it was my driver of choice for my earlier GTX460.

Meanwhile I am trying to solve a white-texture issue in Direct3D apps, that seems to be affected in the391 drivers as well. I wonder if I should go as back as 2016