DW and Windows 8.1 ?

[ikalugin]

Also - it appears to me that AI is not working as intended, Burke failed to intercept any of the sizlers I fired against him (I have fired 4 on the carrier group but they all locked onto one escort)

[Pisces]

You might want to investigate if your host CPU has hardware support for virtualization. For Intel it is called Intel VT, for AMD it is AMD-V. You may also need to enable a bios option for this. If the cpu does not have it then it has to be done in software emulation. That obviously takes more resources. Maybe there are some tweaksettings for Virtualbox. But gaming on a virtual machine is often like winning a lottery. Your inching forward might vary.

[Pisces]

Originally Posted by ikalugin

Also - it appears to me that AI is not working as intended, Burke failed to intercept any of the sizlers I fired against him (I have fired 4 on the carrier group but they all locked onto one escort)

Have you checked with show truth on? The contact location is only as accurate as your identification of your sensors was, and the tma done on the lines of bearing. What you might have thought was real could have been a sensor ghost or at a wrong range. Also, the missile seeker locks on what it finds in the real world. It doesn't care if it is a carrier or a small tug. Even if you want it to be the Burke.

[ikalugin]

I did check truth, all 4 sizlers managed to hit the burke with 0 reaction from him.

[Pisces]

Originally Posted by ikalugin

I did check truth, all 4 sizlers managed to hit the burke with 0 reaction from him.

Well, AI is not perfect. And maybe you just got those weapons in the right launch parameters so it never had any chance. Hard to tell, as you haven't described much of which scenario or mission it was, with or without mods, or how/from where you launched the 3M-54 Klubs.

[ikalugin]

Ok.
- no mods were installed.
- fired on the Nimitz carrier group from around 50 miles using sonar solution.
- 4 missiles were fired in the following sequence - first, then pause, then 3 more.
- missiles were set for 20 mile/broad seaker.

[Komat]

Today I finished a early version of a directx wrapper which prevents the DW startup crash on Windows 8.1 (at least on my PC). It is new so there might be other issues I did not found yet with the game or the wrapper itself (one I know about is a crash when changing resolution in graphics settings) however during test I was able to play through one mission without any apparent issues. I you want to test it, you can find it at http://www.jiri-dvorak.cz/dangw/index.html

[Pisces]

Originally Posted by Komat

Today I finished a early version of a directx wrapper which prevents the DW startup crash on Windows 8.1 (at least on my PC). ...

Awesome work!!! I don't have windows 8, but if I did I would help test it.

The Windows 8 does not directly support 16-bit display modes anymore. ....

I suspected something like this. Strange that for those with SC it still seems to work around this.

[Komat]

Originally Posted by Pisces

Strange that for those with SC it still seems to work around this.

It is entirely possible that SC does things in a simpler way which does not have the problem. The DW seems to have some support for 32-bit mode however it seems to be broken. Initially I tried to just patch the conversion from 24-bit bmp to the 32-bit bitmap which was causing the crash however I ended with broken UI so there are likely other parts of the game which can not handle that.

[jaop99]

Originally Posted by ikalugin

I managed to get it working on win 8.1

What did I do?:
- install virtualbox.
- install xp there.
- install guest tools stuff.
- install the steam/dangerous waters.
- set the 3d acceleration on.
- set the few colours mode on for the game. (this allows you to use a proper cursor)

This allows me to run the game, however the 3d models do not work properly (under water objects do not render properly, only sea surface is present, there is no main water body or sea bottom).

Hi Ikalugin, if you want to see the underwater objects in 3D in your VM machine or VB, have to uncheck in the game avanced 3D options: BLEND TEXTURES (then you will see the sea floor) and CAUSTIC EFFECTS (then you will see the 3D objects)

Hope it works for your VB

[Arrowhead2k1]

Originally Posted by Pisces

Well, AI is not perfect. And maybe you just got those weapons in the right launch parameters so it never had any chance. Hard to tell, as you haven't described much of which scenario or mission it was, with or without mods, or how/from where you launched the 3M-54 Klubs.

I can confirm that this works! I applaud you!

Just one thing. How can I change the resolution via the ini file? The options don't seem to be there for me.

[Pisces]

I think it is hidden as the line:

[Graphics]
...
.ModeID somenumber

Which number you need is a matter of experimentation. I have 3 for 1280x1024.

[Komat]

It is the entry mentioned by Pisces. The number seems to correspond to index of the mode in the resolution dropdown list.

[Arrowhead2k1]

Originally Posted by Pisces

I think it is hidden as the line:

[Graphics]
...
.ModeID somenumber

Which number you need is a matter of experimentation. I have 3 for 1280x1024.

Awesome! Runs perfectly so far. 300 fps with all the bells and whistles on my Win8.1 machine.

Sonalysts should offer him a job! lol

[Arrowhead2k1]

Running fine with Reinforce Alert mod as well. So far, no issues to report.