Page 1 of 1
Crashes on start up
Posted: Tue Jul 12, 2016 1:00 am
by upsidedownsideup
Hi, currently running into a problem with playing the game. I have played perfectly fine on my computer before but now it cant make it past the first 10 seconds. The game will load to the main menu and then windows will say it has stopped working. Not sure where an error occurs but here is the pastebin of the te4_log.txt
http://pastebin.com/dwU5NBH4
Re: Crashes on start up
Posted: Tue Jul 12, 2016 7:30 am
by Stuntofthelitter
Re: Crashes on start up
Posted: Tue Jul 12, 2016 3:33 pm
by upsidedownsideup
Nah that did not work for me. I took the file and renamed it, replaced it in the install folder but still nothing. Thanks for helping though
Re: Crashes on start up
Posted: Tue Jul 12, 2016 11:31 pm
by Stuntofthelitter
Looks like you're running through steam. If you haven't already you could tell it to try and validate the files, although I suspect this isn't the issue. You could try to disable the steam overlay for the game and see if that helps. If you're on windows 10 you could force the game to run in win7 compatibility mode and see if that fixes it. Looking at the log I see it's running at 800x600; you could check C:\Users\%username%\T-Engine\4.0\settings\resolution.cfg to see what is set there and try forcing what seems to be your native resolution of 1920x1080.
Re: Crashes on start up
Posted: Wed Jul 13, 2016 10:55 am
by Droddo
I have runned into the same issue of the OP,
tried the fix of the dll but no luck.
Tried clearing profile, reinstalling game and so on.
Any clue?
Re: Crashes on start up
Posted: Thu Jul 14, 2016 3:24 pm
by Droddo
Droddo wrote:I have runned into the same issue of the OP,
tried the fix of the dll but no luck.
Tried clearing profile, reinstalling game and so on.
Any clue?
After dozillion of reinstall of the steam version I've tried the standalone version on the site tome4: it went ok.
After that installed steam version still KO.
I've ended up with a scandisk of the drive which hosted tome4 w/ steam and it fixed it.
So, OP, give it a try