Just like to post again here. for me, the wrapper is a very imperfect solution. it works, but is very unstable for me and my system. occasionally i'd be able to get some of the lighter missions to run for about an hour. usually I end up having issues in less than 15-20 minutes.

my best solution so far has been to run VMWare (free version) loaded with a free copy of WinXP SP3. this works fantastic, although the FPS aren't exactly stellar and i've had to turn the graphics down, it runs pretty much like it would on a machine from 2004. I'm getting a solid 20-30 frames.

now, if we could get a wrapper that functions similar to however VMWare is doing it, I think we'd be golden. but that's probably a pipedream.

the only issue i've run into is if I accidentally resize the VMware window (wish there was a way to lock it, i'm not that familiar with it) it crashes the game. you can even run the game windowed, however its still limited by the 16-bit color depth, which makes it IMO pointless, besides the fact that you can just run the game "fullscreen" in the VM, which can be a window by itself, so its not like you absolutely need windowed mode, as the VM is functioning as such.

if anyone is interested in this and doesn't know how to get started, I can provide help.

There's this Voodoo Wrapper that allows DW to work in window mode on win10.

Link here: http://dege.freeweb.hu/temp/dgVoodooWIP35.zip

Just copy all files from the MS folder plus dgVoodooCpl.exe folder to DW root.
Set the Dangerouswaters.exe to run in 16bit color mode and edit dangerouswaters.ini to run in window mode.

Game also crashes with this wrapper when changing resolution and window mode in the game settings, so same rule of changing in the dangerouswaters.ini file also applies here.

Komat's wrapper works but it takes some hit on performance as it's constantly doing regex operations on the background to intercept graphics calls.
Don't know about the performance on this one.


EDIT: Looks like this wrapper only works with DW on window mode...

Hi folks,

I recently decided to resurrect my old copy of DW and am running it in Win10.

I am also using the above wrapper DLL to get glorious 1600 x 1200 resolution on my 1920 x 1200 monitor which IMO looks fine and seems stable.

However..... I am having an issue with the messaging text at the bottom of the screen and the data in the top left of the navigation screen, being corrupted. All other text is fine.

(Sorry - how do I add an image to this post??)

The only way to fix it is to change the ini file ModeID value back to 1, in which case I lose the nice resolution and go back to ugly graphics.....

I tried running the windowed mode fix above, but whilst it allows me to run in windowed mode it does not fix this problem (unless I revert back to ModeID 1).

I can't seem to find any mention of this in this forum but I'm sure I can't be the only one to have this issue!

Any suggestions would be gratefully received :salute:

RBG


Never mind......all fixed - did a complete fresh install! Why didn't I think of that in the first place?! :doh:

Hi Guys.

I post to point an alternative about how to run DW and Sub Command in Windows 10 without the need of the known wrapper.

Of course If the wrapper d3d8.dll works for you there is no need to use my solution. It is just an alternative. The wrapper worked great for me but gave me some graphical glitches like garbled sonars in some russian subs.

Sub Command

-Use DGVoodoo2. There is an advantage of using this because you can configure details like VSync, Anisotropic Filtering and Antialiasing options and it looks great.
-In subcommand.ini Change "SoftwareCursor" to "Yes" if your mouse cursor in game dissapears erratically and flickers.

Dangerous Waters

-Use DGvoodoo2 as well but now the game must be 16 bits windowed, so you need to change this in the exe compatibility.

One thing to note is that the wrapper dll and the dll used in dgvoodoo2 are named the same "d3d8.dll" so they seem incompatible.

I hope it is useful as an alternative. Greetings

EDIT: One more advantage I have noticed using dgvoodoo2 in DW is that now the 3D graphics render as expected, without the common color banding typical in 16 bit color.

Unfortunately you can't adjust gamma with the voodoo wrapper so you're stuck at hunting for ghosts on the sonar screen. With the regular wrapper you put gamma to 0.8 and everything is nicely visible.

DW Help with resolution issue
 

Hello all, I ran DW on my laptop with this fix for a long time. Recently my laptop crashed I fixed it and have gone through all the steps to fix it but cannot get it to work like it did before. It will run and play fine but I am getting 3/4 black screen and then the program itself. Any help would be great. I have also tried the DWXnd program I saw from FPSchazly's video but the current version of that file differs from his video and so some of the input parameters are not the same as his video. Thanks!

welcome aboard!
 

Yeah, I'm having no luck either. I can use the Voodoo method described above to get it to run in a teeny little window, but that's not going to fly on my 4K screen. If anybody knows how to get it to stretch out, I'd be grateful for further suggestions.

Try to set: 90% contrast, 110% brightness - it works for me (I used windowed mode with ModeID 3)

Flickering
 

Hello again, people.


I cannot seem to get rid of the flashing problem for the RH-60 HUD, the fact that the digital map in RH-60 cockpit is missing, the software mouse "trails", and the fact that no lines show up on the FFG TMA even after the wrapper has been installed.


Any news on this? I don't care much for graphic issues, but the FFG motion analysis is something I want to be functional.


Running through bootcamp on a AMD R9 M370X, win 10 and vanialla DW.

You should check dgVoodoo2
link

Thanks, I've tried every wrapper that anybody has mentioned on forums, but still no luck.


Maybe there are some specific settings for the Voodoo wrapper that make this work?

What's Voodoo mode in ini anyway?

Voodoo/3DFX were a family of video cards back in the late 90's and early 2000's. They were different from today's Intel and AMD GPUs, kind of like a Chrysler to Intel/AMD's Ford and GM.

Meaning, the chip sets were different and proprietary. Voodoo graphics only ran on Voodoo cards.

No, I know what they are/were (I've been gaming since Test Drive, the 1987 one :) ), I'm asking what mode number is it in the ini file.


"Mode" in *.ini refers to resolution, I just remembered, I meant the render mode. What number do you put in DeviceID?

Let me rephrase the question entirely - how do you set up the VooDoo renderer?



And what settings should I use on the VooDoo setup menu for the wrapper application itself?



When I place it in the folder, it does let me start the game (despite copying any of the Glide dlls or dlls from the MS folder), I do see the text at the bottom right corner "dgVooDoo" for a couple of seconds, but the game quits on me.


I see there was already one discussion about this https://www.vogons.org/viewtopic.php?f=59&t=54985


I seem to have a similar problem.

Never mind. Due to other issues I am going to reset my laptop to the factory image and start over.

Guys, how do you configure dgVooDoo wrapper for DW?


Nothing seems to work.


dgVooDooo tutorial posted here does not work - DW CTDs.

Add this file to your install directory. It worked for me.

http://www.subsim.com/radioroom/down...o=file&id=5474

Thank you. It worked for me too. Been waiting for a bit but now I can play DW....woowoo!

I want to change my resolution on Windows 10, but when I go to the folder that's supposed to have the .ini file I need to edit in it, it's empty. Does anyone know about this or what to do?

dangerouswaters.ini is in main DW folder.

For example:
D:\games\Dangerous Waters