StellarRat Posted August 20, 2012 Share Posted August 20, 2012 I can confirm this error too. It's happened on farm and industrial maps to me. I don't see any particular pattern to it. I can get around it by saving and reloading multiple times. Quote Link to comment Share on other sites More sharing options...
Spikehughes Posted August 20, 2012 Share Posted August 20, 2012 I know this is the Alpha, (version 13.2) but according to the news, you are close to Beta.... Now I have a game that under 13.2 is unplayable due to the freeze the disables the game at the start of the troop/hunter mission - every single time I might add. So basically it is unplayable. If I proceed with the save game and restart option I can get thru that mission, but it rears its ugly head again a little later. Another or related bug is the fighter display. - during the mission save and restore option to avoid the hunter bug - later on the fighter missions turned into a multiple fighters even though I only sent 1 fighter. during this air fight the computer eventually freezes. The only time I experience the fighter issue is after I try to save and move on from the land missions with the "hunter" bug. I have downloaded the game twice, switched from nvidia beta drivers to the last WHQL drivers - running windows 7, 64 bit with 8 gigs 1600 ram. Quote Link to comment Share on other sites More sharing options...
thothkins Posted August 20, 2012 Share Posted August 20, 2012 I know this is the Alpha, (version 13.2)but according to the news, you are close to Beta.... Now I have a game that under 13.2 is unplayable due to the freeze the disables the game at the start of the troop/hunter mission - every single time I might add. So basically it is unplayable. But to be fair to the game, the ground one has only been like this in this build. It's not as though the game has been unplayable all the way through. Once fixed, it'll be back, actually it will be even better, than it was previously. Quote Link to comment Share on other sites More sharing options...
StellarRat Posted August 21, 2012 Share Posted August 21, 2012 I know this is the Alpha, (version 13.2)but according to the news, you are close to Beta.... Now I have a game that under 13.2 is unplayable due to the freeze the disables the game at the start of the troop/hunter mission - every single time I might add. So basically it is unplayable. If I proceed with the save game and restart option I can get thru that mission, but it rears its ugly head again a little later. Another or related bug is the fighter display. - during the mission save and restore option to avoid the hunter bug - later on the fighter missions turned into a multiple fighters even though I only sent 1 fighter. during this air fight the computer eventually freezes. The only time I experience the fighter issue is after I try to save and move on from the land missions with the "hunter" bug. I have downloaded the game twice, switched from nvidia beta drivers to the last WHQL drivers - running windows 7, 64 bit with 8 gigs 1600 ram. Don't expect much stability from an alpha. Basically the programmers only try to debug enough to get the routines running, but no one is actually testing every possibility for bugs. When the beta comes out and a bunch of users have it that will nail down a lot of stuff. Quote Link to comment Share on other sites More sharing options...
lordfeff Posted August 22, 2012 Share Posted August 22, 2012 I am aware the devs know of this bug and probably already have the fix in the works but I thought to supply this added debug information in case it is useful. Dump Summary ------------ Dump File: XenonautsCrashDump.dmp : C:\downloads\Build_V13.2\XenonautsCrashDump.dmp Last Write Time: 8/19/2012 2:55:13 PM Process Name: Xenonauts.exe : C:\downloads\Build_V13.2\Build V13\Xenonauts.exe Process Architecture: x86 Exception Code: 0xC0000005 Exception Information: The thread tried to read from or write to a virtual address for which it does not have the appropriate access. Heap Information: Not Present System Information ------------------ OS Version: 6.1.7600 CLR Version(s): Modules ------- Module Name Module Path Module Version ----------- ----------- -------------- Xenonauts.exe C:\downloads\Build_V13.2\Build V13\Xenonauts.exe 0.0.0.0 ntdll.dll C:\Windows\SysWOW64\ntdll.dll 6.1.7600.16385 kernel32.dll C:\Windows\SysWOW64\kernel32.dll 6.1.7600.16385 KERNELBASE.dll C:\Windows\SysWOW64\KERNELBASE.dll 6.1.7600.16385 dsound.dll C:\Windows\System32\dsound.dll 6.1.7600.16385 msvcrt.dll C:\Windows\SysWOW64\msvcrt.dll 7.0.7600.16385 user32.dll C:\Windows\SysWOW64\user32.dll 6.1.7600.16385 gdi32.dll C:\Windows\SysWOW64\gdi32.dll 6.1.7600.16385 lpk.dll C:\Windows\SysWOW64\lpk.dll 6.1.7600.16385 usp10.dll C:\Windows\SysWOW64\usp10.dll 1.626.7600.16385 advapi32.dll C:\Windows\SysWOW64\advapi32.dll 6.1.7600.16385 sechost.dll C:\Windows\SysWOW64\sechost.dll 6.1.7600.16385 rpcrt4.dll C:\Windows\SysWOW64\rpcrt4.dll 6.1.7600.16385 sspicli.dll C:\Windows\SysWOW64\sspicli.dll 6.1.7600.16385 CRYPTBASE.dll C:\Windows\SysWOW64\CRYPTBASE.dll 6.1.7600.16385 ole32.dll C:\Windows\SysWOW64\ole32.dll 6.1.7600.16385 winmm.dll C:\Windows\System32\winmm.dll 6.1.7600.16385 powrprof.dll C:\Windows\System32\powrprof.dll 6.1.7600.16385 setupapi.dll C:\Windows\SysWOW64\setupapi.dll 6.1.7600.16385 cfgmgr32.dll C:\Windows\SysWOW64\cfgmgr32.dll 6.1.7600.16385 oleaut32.dll C:\Windows\SysWOW64\oleaut32.dll 6.1.7600.16385 devobj.dll C:\Windows\SysWOW64\devobj.dll 6.1.7600.16385 IPHLPAPI.DLL C:\Windows\System32\IPHLPAPI.DLL 6.1.7600.16385 nsi.dll C:\Windows\SysWOW64\nsi.dll 6.1.7600.16385 winnsi.dll C:\Windows\System32\winnsi.dll 6.1.7600.16385 wininet.dll C:\Windows\SysWOW64\wininet.dll 8.0.7600.16385 shlwapi.dll C:\Windows\SysWOW64\shlwapi.dll 6.1.7600.16385 normaliz.dll C:\Windows\SysWOW64\normaliz.dll 6.1.7600.16385 urlmon.dll C:\Windows\SysWOW64\urlmon.dll 8.0.7600.16385 crypt32.dll C:\Windows\SysWOW64\crypt32.dll 6.1.7600.16385 msasn1.dll C:\Windows\SysWOW64\msasn1.dll 6.1.7600.16385 iertutil.dll C:\Windows\SysWOW64\iertutil.dll 8.0.7600.16385 version.dll C:\Windows\System32\version.dll 6.1.7600.16385 dbghelp.dll C:\Windows\System32\dbghelp.dll 6.1.7600.16385 shell32.dll C:\Windows\SysWOW64\shell32.dll 6.1.7600.16385 SDL.dll C:\downloads\Build_V13.2\Build V13\SDL.dll 0.0.0.0 comctl32.dll C:\Windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7600.16385_none_ebf82fc36c758ad5\comctl32.dll 5.82.7600.16385 winspool.drv C:\Windows\System32\winspool.drv 6.1.7600.16385 comdlg32.dll C:\Windows\SysWOW64\comdlg32.dll 6.1.7600.16385 imm32.dll C:\Windows\System32\imm32.dll 6.1.7600.16385 msctf.dll C:\Windows\SysWOW64\msctf.dll 6.1.7600.16385 uxtheme.dll C:\Windows\System32\uxtheme.dll 6.1.7600.16385 profapi.dll C:\Windows\System32\profapi.dll 6.1.7600.16385 dhcpcsvc.dll C:\Windows\System32\dhcpcsvc.dll 6.1.7600.16385 ws2_32.dll C:\Windows\SysWOW64\ws2_32.dll 6.1.7600.16385 clbcatq.dll C:\Windows\SysWOW64\clbcatq.dll 2001.12.8530.16385 MMDevAPI.dll C:\Windows\System32\MMDevAPI.dll 6.1.7600.16385 propsys.dll C:\Windows\System32\propsys.dll 7.0.7600.16385 AudioSes.dll C:\Windows\System32\AudioSes.dll 6.1.7600.16385 dwmapi.dll C:\Windows\System32\dwmapi.dll 6.1.7600.16385 d3d9.dll C:\Windows\System32\d3d9.dll 6.1.7600.16385 d3d8thk.dll C:\Windows\System32\d3d8thk.dll 6.1.7600.16385 nvd3dum.dll C:\Windows\System32\nvd3dum.dll 8.17.13.142 psapi.dll C:\Windows\SysWOW64\psapi.dll 6.1.7600.16385 comctl32.dll C:\Windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16385_none_421189da2b7fabfc\comctl32.dll 6.10.7600.16385 avrt.dll C:\Windows\System32\avrt.dll 6.1.7600.16385 Assembly Break Line: 014558E3 mov edx,dword ptr [esi+1Ch] Hope that was helpful Quote Link to comment Share on other sites More sharing options...
TheUbiquitous Posted August 23, 2012 Share Posted August 23, 2012 Is there a ruling on whether this is actually useful? Quote Link to comment Share on other sites More sharing options...
Max_Caine Posted August 23, 2012 Share Posted August 23, 2012 Matthew seems to like the crash dumps. Quote Link to comment Share on other sites More sharing options...
Gauddlike Posted August 23, 2012 Share Posted August 23, 2012 He needs a hobby Quote Link to comment Share on other sites More sharing options...
LeftyRighty Posted August 23, 2012 Share Posted August 23, 2012 knowing for certain it's memory access range issue would be quite handy I expect out of curiosity, what language is the game written in? Quote Link to comment Share on other sites More sharing options...
Gorlom Posted August 23, 2012 Share Posted August 23, 2012 knowing for certain it's memory access range issue would be quite handy I expect out of curiosity, what language is the game written in? No idea, it's all Greek to me! Quote Link to comment Share on other sites More sharing options...
thothkins Posted August 24, 2012 Share Posted August 24, 2012 that explains why the prices are in euros....sorry drachmas...sorry euros... Quote Link to comment Share on other sites More sharing options...
Gijs-Jan Posted August 27, 2012 Share Posted August 27, 2012 C++; although I would have really preferred almost any other language :-P Anyhoo; do any of you guys have a savegame which triggers this bug? I might be able to gander a look at it in my downtime :-) Quote Link to comment Share on other sites More sharing options...
Max_Caine Posted August 27, 2012 Share Posted August 27, 2012 The problem is it's intermittant. You can have the same savegame, have it crash the first time, then work perfectly the second. The only consistant thing I havwe seen about it (for me) is that the crash seems to happen when you do one mission, then another. Quote Link to comment Share on other sites More sharing options...
Legadian Posted August 27, 2012 Share Posted August 27, 2012 As Max_Caine said, it is intermittent. I personally think it has something to do with the soldier files being screwed up, but that's just my pet theory. Here is a thread where I've posted some V13.2 save games that have crash sites on the map. Any one of the "before ground mission" saves will have a chance to trigger the fatal exception when the Chinook arrives and the ground mission loads up. Just start clicking on soldiers to find out. In my experience, I encounter it about 50% of the time. I SAR to avoid that particular bug. You should just have to reload a couple of times to encounter it Quote Link to comment Share on other sites More sharing options...
Verci Posted October 2, 2012 Share Posted October 2, 2012 yep! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.