ladner -> RE: WitE Not Responding, Game Crash (3/29/2014 4:19:55 PM)
|
quote:
ORIGINAL: Apollo11 Hi all, quote:
ORIGINAL: ladner I realize there was a post about no longer supporting the game, but it is going to be real hard to justify spending about ~$100 US to buy another Matrix 2by3 game and have physical back up, if you cannot run the software even though I supposedly am within "recommended system" specifications. Where did you find official post stating that WitE is no longer supported? [&:] As for crashing - the WitE is one the the games with almost perfect record... just go through this "Tech Support" thread and look for crash reports from before! There were just handful of crash reports and almost all of those were related to the state of the PC of the game owner and not to the WitE itself! BTW, if there is a bug found in WitE that we can determine it crashes the game - it will be fixed (just as it was fixed in all similar rare cases before)... Leo "Apollo11" support comment here http://www.matrixgames.com/forums/tm.asp?m=3336030 which is stickied above. Game crashed again, today, this is certainly a codec issue, not the game itself. Have no idea of how to fix at this stage. Have updated all of my device drivers, aside from reinstalling Windows, which will cause massive headaches, cannot get the sound to work. I went to save, the game crashed. From windows event viewer Faulting application name: WarInTheEast.exe, version: 1.0.7.14, time stamp: 0x532779ab Faulting module name: WarInTheEast.exe, version: 1.0.7.14, time stamp: 0x532779ab Exception code: 0x40000015 Fault offset: 0x0024a167 Faulting process id: 0x11e4 Faulting application start time: 0x01cf4b6441a3b28c Faulting application path: C:\Matrix Games\Gary Grigsby's War in the East\WarInTheEast.exe Faulting module path: C:\Matrix Games\Gary Grigsby's War in the East\WarInTheEast.exe Report Id: f84ef388-b75c-11e3-9e00-00252258a6f1 Everyone time there has been a crash one of these logs has been generated, unfortunately I don't know how to decipher this into meaningful information. I agree though, I somehow, broke my codecs, and it is causing the exceptions.
|
|
|
|