Redbone
| | Seemingly random crashes Playing Twisty Castle on 0.2.1, the game has crashed twice during gameplay. I don't see anything that could be causing it, it just tells me vox.exe stopped working. Never happened on previous versions and there doesn't seem to be a crash log anywhere.
If it's any help, here's the problem signature:
| | Problem Event Name: APPCRASH
Application Name: vox.exe
Application Version: 0.0.0.0
Application Timestamp: 500ef3dc
Fault Module Name: vox.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 500ef3dc
Exception Code: c0000005
Exception Offset: 0005b560
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 4105
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
| |
Computer specifications:
Windows 7 Home Premium (64-bit)
AMD Athlon(tm) II X4 645 Processor 3.1 GHz
6 GB RAM
ATI Radeon HD 4200 with 2.9GB Video RAM
P#6364 Posted at 2012-07-28 20:11
|
zep
| | :: The most common cause of unexplained crashes was using DirectX to blit to screen (still don't know why exactly though). The most recent version should default to dib blits instead but just in case, please make sure that in config.txt (YourHomeFolder\AppData\Roaming\Voxatron\config.txt) windib is set to 1.
Thoses crashes appear to only occur during fullscreen mode. You could also try running in a window to see if that has any relevance.
There's also log.txt in YourHomeFolder\AppData\Roaming\Voxatron that might be useful. If using windib 1 doesn't help, please send me a copy after a crash (joseph at lexaloffle dot com).
P#6377 Posted at 2012-07-29 18:23
|
zep
| | :: Weird that you weren't having this problem before 0.2.1 though. Have you updated/changed any drivers or hardware since then?
P#6378 Posted at 2012-07-29 18:24
|
|
|
