This turned out to work really well, so I stopped being lazy and made a proper installer using nsis.
https://drive.google.com/open?id=0B_lQD ... 3NwOHVEelE
*** This only works for Directx11 enabled video cards (most video cards)***
What the installer does:
- Installs dgVoodoo to the Gabriel Knight 3 directory
- Turns off Incremental Rendering and Mip Maping
- Turns on Trilinear Filtering
- Selects dgVoodoo as the game's graphics adapter
- Turns on compatibility mode of the game's executable with Windows XP (Service pack 2)
With my setup this is working wonders! If anyone who can't run the game with Windows 8 or Windows 10 wants to try this, please give me some feedback.
All the best.
GK Games and Newer OS
Re: GK Games and Newer OS
Absolutely fantastic on my Windows 10 machine. Thanks for your efforts!
- el_pombo
- Sierra Obsessed
- Posts: 107
- Joined: Sun Jun 15, 2014 11:31 am
- Location: Portugal
- Gender: Male
- Location: Sintra, Portugal
Re: GK Games and Newer OS
That's great! Thanks for your feedback!Purduecoz wrote:Absolutely fantastic on my Windows 10 machine. Thanks for your efforts!
All the best!
- el_pombo
- Sierra Obsessed
- Posts: 107
- Joined: Sun Jun 15, 2014 11:31 am
- Location: Portugal
- Gender: Male
- Location: Sintra, Portugal
Re: GK Games and Newer OS
Windows defender is detecting my installer as malware!
https://www.microsoft.com/security/port ... le.B!plock
I don't know why this is happening, the installer is completely innocuous, it was generated with an nsis script and does nothing out of the ordinary.
I wonder if this is because the installer changes GK3 registry keys and sets the executable (via registry) to compatibility mode.
I'll see if I can submit this to Microsoft as a false positive.
Has this happened to any of you before?
EDIT: It seems to be OK, now! I submitted it anyway.
https://www.microsoft.com/security/port ... le.B!plock
I don't know why this is happening, the installer is completely innocuous, it was generated with an nsis script and does nothing out of the ordinary.
I wonder if this is because the installer changes GK3 registry keys and sets the executable (via registry) to compatibility mode.
I'll see if I can submit this to Microsoft as a false positive.
Has this happened to any of you before?
EDIT: It seems to be OK, now! I submitted it anyway.