Hey buddies!
I'm having an issue with the game where if I play more than 15 minutes into it, the game causes a hard freeze / lockup on the computer that it cannot recover from. All sound stops and it either freezes on the last image or the screen just goes blank.
It is possible that this may simply be on my end of course, but I haven't had this happening on any other game or any other roguelike, so I figured it's better to be safe than sorry and report it. If there's any more information you need, please let me know here and I'll try and get it to you asap. Thanks!
[b37] Freeze / Lockup on Windows 7 /AMD HD 6970
Moderator: Moderator
-
- Low Yeek
- Posts: 5
- Joined: Sun Jan 15, 2012 2:55 pm
Re: [b37] Freeze / Lockup on Windows 7 /AMD HD 6970
Hey Tiny Turtle, a few more details would be nice: what OS are you running? 32-bit or 64-bit? What's your gfx card? Is your graphics driver up to date? Have you watched memory usage while playing? etc.
I would suggest trying the "t-engine.exe" and "SDL.dll" files that are posted here:
http://forums.te4.org/viewtopic.php?f=36&t=30981
Hope this helps and good luck!
I would suggest trying the "t-engine.exe" and "SDL.dll" files that are posted here:
http://forums.te4.org/viewtopic.php?f=36&t=30981
Hope this helps and good luck!
-
- Low Yeek
- Posts: 5
- Joined: Sun Jan 15, 2012 2:55 pm
Re: [b37] Freeze / Lockup on Windows 7 /AMD HD 6970
Of course!
My OS and graphic cards are:
Windows 7 64-bit Home Premium
AMD HD 6970
The graphics driver is up to date, and I just double checked to make sure. I haven't watched the memory usage, but I'll download the SDL.dll and the t-engine.exe and give them a run, with the memory usage window open.
EDIT: No noticeable change in memory usage or CPU usage. Screen flickered, then the computer locked up. That's with the SDL.ddl and t-engine.exe from the linked thread.
Double edit: This is 100% on my end. This was the first game to actually crash, but turns out if I play another java game (King Arthur's Gold) for a few minutes the same crash happens. Except this time it locked up so bad the restart button on the box didn't work. So you don't have to worry about this being an in-game bug. Sorry! I'll head somewhere else to fix this and hopefully I'll be playing again in no time.
My OS and graphic cards are:
Windows 7 64-bit Home Premium
AMD HD 6970
The graphics driver is up to date, and I just double checked to make sure. I haven't watched the memory usage, but I'll download the SDL.dll and the t-engine.exe and give them a run, with the memory usage window open.

EDIT: No noticeable change in memory usage or CPU usage. Screen flickered, then the computer locked up. That's with the SDL.ddl and t-engine.exe from the linked thread.

Double edit: This is 100% on my end. This was the first game to actually crash, but turns out if I play another java game (King Arthur's Gold) for a few minutes the same crash happens. Except this time it locked up so bad the restart button on the box didn't work. So you don't have to worry about this being an in-game bug. Sorry! I'll head somewhere else to fix this and hopefully I'll be playing again in no time.
Re: [b37] Freeze / Lockup on Windows 7 /AMD HD 6970
Seems to have happened to a few people running 6900 series GPUs. http://forums.te4.org/viewtopic.php?f=42&t=30831
Reduced to playing ToME on my lappy for the moment
Reduced to playing ToME on my lappy for the moment

Re: [b37] Freeze / Lockup on Windows 7 /AMD HD 6970
Have to report no crashes for me since updating to the 12.1 preview driver (an hour and a half game time)
-
- Low Yeek
- Posts: 5
- Joined: Sun Jan 15, 2012 2:55 pm
Re: [b37] Freeze / Lockup on Windows 7 /AMD HD 6970
Oh dang, so it wasn't just me! Thanks a lot man. 

Re: [b37] Freeze / Lockup on Windows 7 /AMD HD 6970
trev wrote:Have to report no crashes for me since updating to the 12.1 preview driver (an hour and a half game time)
Now about 5 hours - still fine.
-
- Low Yeek
- Posts: 5
- Joined: Sun Jan 15, 2012 2:55 pm
Re: [b37] Freeze / Lockup on Windows 7 /AMD HD 6970
Confirming that getting the preview drivers fixed this issue. 
