Forum

KerbalSpaceProgram crash

Författare Svar
DoubleW Tuesday 4 December 2012 at 18:28
DoubleWAnonymous

I tried to play KSP on linux by using playonlinux and wine 1.5.18

I installed KSP by installing it on a windows computer and then copying the game directory to the POL virtual drive. (Cause installing it on Linux didn't work)

I launch it, and everything works fine.

Until lately, when I start KSP now it says it crashed and when I start it in debug mode it gives me this:

[12/04/12 17:55:03] - Running wine-1.5.18 KSP.exe (Working directory : /home/wybe/.PlayOnLinux/wineprefix/KSP/drive_c/KSP_0.18)
Mono path[0] = 'C:/KSP_0.18/KSP_Data/Managed'
Mono path[1] = 'C:/KSP_0.18/KSP_Data/Mono'
fixme:win:EnumDisplayDevicesW ((null),0,0x7f8e4fc,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x7f8de38,0x00000000), stub!
fixme:dxgi:dxgi_output_GetDesc iface 0x13e218, desc 0x7f8e490 stub!
fixme:wbemprox:client_security_SetBlanket 0xf49cfa28, 0x142650, 10, 0, (null), 3, 3, (nil), 0x00000000
fixme:wbemprox:client_security_Release 0xf49cfa28
fixme:win:EnumDisplayDevicesW ((null),0,0x7f8d360,0x00000000), stub!
fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x5a574152 (as fourcc: RAWZ) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x5a574152) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x5a534552 (as fourcc: RESZ) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x5a534552) in the format lookup table
fixme:imm:ImmReleaseContext (0x4005e, 0x14f5a0): stub
fixme:win:RegisterRawInputDevices Unhandled flags 0x100 for device 0.
fixme:win:RegisterDeviceNotificationW (hwnd=0x4005e, filter=0x32f480,flags=0x00000000) returns a fake device notification handle!
fixme:d3d:query_init Unhandled query type 0xc.
fixme:win:RegisterRawInputDevices Unhandled flags 0x100 for device 0.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:dbghelp:validate_addr64 Unsupported address fffffffff7390000
fixme:dbghelp:validate_addr64 Unsupported address fffffffff7380000
fixme:dbghelp:validate_addr64 Unsupported address fffffffff7340000
fixme:dbghelp:validate_addr64 Unsupported address fffffffff70e0000
fixme:dbghelp:validate_addr64 Unsupported address fffffffff49b0000
fixme:dbghelp:validate_addr64 Unsupported address fffffffff4970000
fixme:dbghelp:validate_addr64 Unsupported address fffffffff4940000
fixme:dbghelp:validate_addr64 Unsupported address fffffffff4930000
fixme:dbghelp:validate_addr64 Unsupported address fffffffff4650000
fixme:dbghelp:validate_addr64 Unsupported address fffffffff4620000
fixme:dbghelp:validate_addr64 Unsupported address fffffffff3d80000
fixme:dbghelp:validate_addr64 Unsupported address fffffffff2870000
fixme:dbghelp:validate_addr64 Unsupported address fffffffff18a0000
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x7bc35677

(sorry for the long code, I have no idea if and how spoilers are done here)