bifutake
05-18-18, 12:39 PM
First, my specs:
MBO: ASUS M5A97 R2.0
CPU: AMD Athlon II X4 630 BOX (2.8 GHz)
GPU: Sapphire ATI Radeon HD 5770 1GB GDDR5 (running 1920x1080 at 60 Hz)
RAM: 8 GB (2x2 DDR3 1333 Mhz + 1x4 DDR3 1333 Mhz)
SSD: Samsung 850 EVO Basic 250 GB (divided into two partitions: C, D)
HDD: Western Digital Black 4 TB (divided into four partitions: E, F, G, H)
Windows 10 Enterprise 64-bit (10.0, Build 17134) is freshly installed on my C partition. D is only used by my three favourite Steam games (because of multiplayer). Most of my Steam library is on E (along with the Silent Hunter games).
My DxDiag shows I'm using DirectX 12 but I'll c/p some other potentially relevant information:
Driver Name: aticfx64.dll,aticfx64.dll,aticfx64.dll,amdxc64.dll
DDI Version: 11.2
Feature Levels: 11_0,10_1,10_0,9_3,9_2,9_1
Driver Model: WDDM 1.3Does this mean my system is backward compatible with DirectX 11.2, 11.0, 10.1, 10.0, 9.3, 9.2 and 9.1? But am I wrong or does SH4 use 9.0c? Could this be the reason why the game won't start properly?
So, the game ran fine in Windows 7 (with minor adjustments (http://www.subsim.com/radioroom/showthread.php?t=202192) when using mods) but I recently switched to Windows 10 (clean install, no upgrade) and now it won't start. Neither will SH5. SH3 works just fine, so you can imagine my surprise. But that's a topic for another thread.
When I click to play Wolves of the Pacific (with or without the U-boat expansion installed), I hear my HDD spinning up but nothing happens. My Task Manager shows SH4 running and using resources (much less than a gig of ram and a very small CPU percentage) but nothing other than that. Same thing happens when I try running sh4.exe directly in compatibility mode (xp, vista, 7).
I tried browsing this subforum for any similar experiences but I just can't find them. Can someone please help me?
Edit: Well, I got it working in 1024x768 windowed mode after stumbling upon this thread (http://www.subsim.com/radioroom/showthread.php?t=231193). No luck so far in trying to adjust it to my native resolution in full screen though.
MBO: ASUS M5A97 R2.0
CPU: AMD Athlon II X4 630 BOX (2.8 GHz)
GPU: Sapphire ATI Radeon HD 5770 1GB GDDR5 (running 1920x1080 at 60 Hz)
RAM: 8 GB (2x2 DDR3 1333 Mhz + 1x4 DDR3 1333 Mhz)
SSD: Samsung 850 EVO Basic 250 GB (divided into two partitions: C, D)
HDD: Western Digital Black 4 TB (divided into four partitions: E, F, G, H)
Windows 10 Enterprise 64-bit (10.0, Build 17134) is freshly installed on my C partition. D is only used by my three favourite Steam games (because of multiplayer). Most of my Steam library is on E (along with the Silent Hunter games).
My DxDiag shows I'm using DirectX 12 but I'll c/p some other potentially relevant information:
Driver Name: aticfx64.dll,aticfx64.dll,aticfx64.dll,amdxc64.dll
DDI Version: 11.2
Feature Levels: 11_0,10_1,10_0,9_3,9_2,9_1
Driver Model: WDDM 1.3Does this mean my system is backward compatible with DirectX 11.2, 11.0, 10.1, 10.0, 9.3, 9.2 and 9.1? But am I wrong or does SH4 use 9.0c? Could this be the reason why the game won't start properly?
So, the game ran fine in Windows 7 (with minor adjustments (http://www.subsim.com/radioroom/showthread.php?t=202192) when using mods) but I recently switched to Windows 10 (clean install, no upgrade) and now it won't start. Neither will SH5. SH3 works just fine, so you can imagine my surprise. But that's a topic for another thread.
When I click to play Wolves of the Pacific (with or without the U-boat expansion installed), I hear my HDD spinning up but nothing happens. My Task Manager shows SH4 running and using resources (much less than a gig of ram and a very small CPU percentage) but nothing other than that. Same thing happens when I try running sh4.exe directly in compatibility mode (xp, vista, 7).
I tried browsing this subforum for any similar experiences but I just can't find them. Can someone please help me?
Edit: Well, I got it working in 1024x768 windowed mode after stumbling upon this thread (http://www.subsim.com/radioroom/showthread.php?t=231193). No luck so far in trying to adjust it to my native resolution in full screen though.