Page 1 of 1

Crash on Launch Open Beta

PostPosted: Fri Sep 25, 2015 9:50 am
by Duckaerobics
I think I have a driver issue. I had the game working on Windows 10. The game is currently crashing on launch. Here is the text from the game log:

[16:31:02] Lua: Lua Version: "Lua 5.1"
[16:31:02] Lua: LuaJIT 2.0.3
[16:31:02] Lua: Starting initialization process...
[16:31:02] Lua: Game Version: 150924
[16:31:02] Lua: Loading User Settings
[16:31:02] Lua: Loading Display Settings from XML
[16:31:02] Lua: --------------------------------------
[16:31:02] Lua: Display Settings:
[16:31:02] Lua: Resolution: 1280 x 720
[16:31:02] Lua: Mode: Windowed
[16:31:02] Lua: SSAO: true
[16:31:02] Lua: FXAA: true
[16:31:02] Lua: Viewport Res: 1
[16:31:02] Lua: --------------------------------------
[16:31:02] Lua: Starting Kee Engine...
[16:31:02] Engine: Loading Resource Kee.dll
[16:31:02] Engine: Creating Viewport Manager Instance
[16:31:02] Engine: Engine initialisation: WindowManager - Created
[16:31:02] Engine: D3D ERROR: D3DERR_DEVICELOST
DESCRIPTION:
Device lost
[16:31:02] Engine:
[16:31:02] Engine: resizing window: width 1280, height 720
[16:31:02] Engine: Engine initialisation failed. Could not initialise render manager.

It seems like it's a direct3d error, but dxdiag says I have no issues. I think my display drivers updated since I had Automation working, but with Windows 10 auto updating I'm not sure. I need to try rolling back drivers and testing. Any advice would be appreciated. My graphics card is an AMD HD7900 series.

I'll leave this open for now in case anyone has a similar issue, but I have the game running. I tried rolling my driver back to when I know the game ran, but I still got the same error. I then re-updated to the driver I had previously and the game works now. I have the exact same driver as before so I can only assume it didn't install correctly. Although it is all very strange to me, the only two programs I saw errors on were Automation and Nestopia.

Re: Crash on Launch Open Beta

PostPosted: Fri Sep 25, 2015 10:52 am
by zeussy
You are along the right lines that it probably appears to be a driver issue.

I have seen atleast one other person do an update to windows 10, and it rolled back onto default Windows drivers that are 'good enough' for hardware acceleration for Windows itself, but failed for Automation.

So if you have not done already. To to AMD site and grab the latest Windows 10 drivers for your machine. And see if that fixes it.