It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Hello, I'm trying to play GK3 on my brand new Win10 x64 machine with a radeon RX 5700 XT card. Original software or directx modes don't work, but dgvoodoo, as explained by HannesKakkiainen, works (thank you !).

But if I set dgvoodoo to use any real D3D11 output api the result is as image attached. As you can see almost all textures close to the camera are whitened, only far ones are displayed correctly. I really don't know much about graphic settings so does anyone have an idea how to fix that ?

I toyed around a bit with dgvoodoo settings and the best solution I found is to set output api to "Direct3D 11 MS WARP (software)" and indeed the 3D scene is displayed correctly, but then movies stutter as hell and the quit confirmation dialog is not shown at all (even though the game is paused and awaits input from it). I fear other important dialogs may not display either so that's not so good a solution.

Btw, I also applied the fix provided by MoreGamesForMe (thank you too) to allow only one processor core, doesn't change anything display-wise but can't do no harm I suppose.
Attachments:
gk3.jpg (332 Kb)
Post edited April 15, 2020 by Wronschien
This question / problem has been solved by Gudadantzaimage
Probably you tried it but make sure that you select "dgvoodoo2 virtual 3d accelerated card" as virtual graphic card and/or disable mipmapping. Sometimes forcing mipmapping into dgvoodoo causes glitches. Try to disable any forced texture effect,anisotropic or goraud shadowing to be in the safe side to discover the cause of the glitch by elimination, and see if things get better.

Greetings
Thank you for your answer, so yes I set to virtual dgvoodoo card, I tried others but failed to see any difference. Same for mipmapping, antialiasing and filtering that I let appdriven. I can't find any setting for gouraud though.
Ok.

Well, I am running Gabriel Knight3 from my original CD Installed with the sierra installer. I know that intsaller does not make any compatibility fix in new OSes, It just Installs the game at full installation without the need of changing CD ingame.

I am also running the game with DGVoodoo2 2.55 version. It is an older version but I presume that any version should work fine because I am running it with all the graphic features ( anisotropic, mipmapping and Pong shadownig, this is, some kind of goraud shadowing) without any glitch and at good framerate. But if you like you could try this version for testing.
But you can try another thng:

Other thing you should be aware of is which graphic card you have selected ingame, not in dgvoodoo, but in game options. It let you select software, your physical Card or the virtual card enabled into dgvoodoo. Keep an eye if you have chosen specifically the virtual card previously selected in dgvoodoo2.

Just an idea. Greetings.
Post edited April 16, 2020 by Gudadantza
That's it !

Dgvoodoo was the culprit, v2.55.4.1 is the last one which works well, I haven't tested every other versions but v2.6 already has the whitish problem.

Thank you, I really don't think I would have tested earlier versions on my own.
avatar
Wronschien: That's it !

Dgvoodoo was the culprit, v2.55.4.1 is the last one which works well, I haven't tested every other versions but v2.6 already has the whitish problem.

Thank you, I really don't think I would have tested earlier versions on my own.
Glad to see your problem solved.

One of the things I use to do when I have a game running with an older dgvoodoo version is update it. It would have been an error from my side :) Now we know which specific dgvoodoo version does run well or which does not. So, Thanks! :)

Greetings
Update : I went to the dgvoodoo forum on vogons.org to explain this somewhat regression. Dege is aware of the problem on newer AMD cards (that I have), there are other games concerned. It just so happens he had just made an experimental early build which fixes the problem, so future releases of dgvoodoo should work correctly.
avatar
Wronschien: Update : I went to the dgvoodoo forum on vogons.org to explain this somewhat regression. Dege is aware of the problem on newer AMD cards (that I have), there are other games concerned. It just so happens he had just made an experimental early build which fixes the problem, so future releases of dgvoodoo should work correctly.
Well, a year later just to say that indeed, the new dgvoodoo2 versions render the game correctly. Previous legacy versions of the app are not needed anymore, just the newest one is enough

greetings