Slitherine

I have the same problem, but installing OpenAl made no difference, I still see nothing on the start screen, no buttons, just German soldiers in a trench, any ideas?

I have the Steam version of CTGW, when I start the game (even when setting the compatibility option to Run as Adminstrator), the game won't progress beyond the initial splash screen of German Soldiers in Trenches. No buttons or other links to progress beyond this screen are displayed.

I have all the latest drivers installed on my computer for both the integrated Intel HD 4600 graphics and dedicated Nvidia 970M graphics (I've tried running the game using both - same problem).

I have re-installed the Open AL audio driver

I have Microsoft Visual C++ Redistributable 2012 installed - both x64 and x86

I am running the game as administrator

My computer is running Windows 8.1 64 bit with all latest patches installed

My hardware is: 2.6GHz Quad Core i7 4720HQ CPU, 16GB RAM, Nvidia 970M and Intel HD 4600 GPUs

I am running at 1920x1080 resolution

My ctgw.log file looks like this (also attached):

Log date: 2015-03-18 07:55:04
[07:55:04][8432]Running Steam build
[07:55:04][8432]Renderer: GeForce GTX 970M/PCIe/SSE2 version: 4.5.0 NVIDIA 347.52
[07:55:04][8432]Commander: The Great War(v 1.6.2)
[07:55:04][8432]Audio device used: OpenAL Soft
[07:55:04][8432]Loading main script
[07:55:04][8432]Loading app script
[07:55:04][8432]App version:1.6.2
[07:55:04][8432]Today is: 18.3.2015

This is as far as the game gets:



I have read this post and tried everything in it: viewtopic.php?f=214&t=38738

I have run the DX test (all tests passed) and have attached a zipped version of DxDiag.txt

Any ideas? It's very frustrating as the game did run fine on my old MacBook Air (under Windows 7)

Okay, I've sorted it - my screen resolution was set to 125% DPI scaling, it works when I set it to 100% DPI

Also now works if I set the compatibility setting "Disable display scaling on high DPI settings" on the .exe files, even when running Windows 8.1 at 125% scaling. This should be in the FAQ, if it isn't already

Happy to know that you have fixed it.
Thanks for reporting back on how you solved it.