The more useful the information you provide, the more quickly you will get help.
So what is useful?
If the game doesn't run at all, or the graphics are messed up, say what your OS is and try disabling the shader options.
This game uses OpenGL shaders which are not always properly supported by your drivers.
If the crash happened in game, the MOST important thing you can post here is the error message.
Even if you submitted it via the in game error popup, still post it, as only DarkGod can see those.
Even if you don't think there was an error message, there likely was: 99% of all freezes are a lua error, it will be in the log file.
NB: Every time you run the game, the log file is erased and a new one is started. If you forget to grab the error message from the log file straight away, you can now get it from an error dump in ENGINEHOME/4.0/tome/error-logs/'date'.txt
Finding the log file:
For Windows users, it will be called te4_log.txt and it will be in the same folder as the t-engine.exe.
For Mac users, I think it is called te4_log.txt and it will be in the same folder as the t-engine program.
For Linux users, the log is not automatically generated. You will need to run the game with something like > /home/te4_log.txt added to it. You can also add this to the launch options via Steam if you are using it.
What to copy from the log file:
You are looking for something like this:
Code: Select all
Lua Error: /engine/interface/ActorTalents.lua:175: /engine/interface/ActorTalents.lua:153: .../addons/verdant/superload/mod/class/interface/Combat.lua:89: attempt to perform arithmetic on local 'add_chance' (a nil value)
stack traceback:
.../addons/verdant/superload/mod/class/interface/Combat.lua:89: in function 'physicalCrit'
/mod/class/interface/Combat.lua:465: in function 'attackTargetWith'
...wandir-weaponry/superload/mod/class/interface/Combat.lua:312: in function 'attackTargetWith'
/mod/class/interface/Combat.lua:168: in function 'attackTarget'
...wandir-weaponry/superload/mod/class/interface/Combat.lua:203: in function 'attackTarget'
/data-verdant/talents/gifts/sharkaspect.lua:41: in function </data-verdant/talents/gifts/sharkaspect.lua:32>
[C]: in function 'xpcall'
/engine/interface/ActorTalents.lua:148: in function </engine/interface/ActorTalents.lua:135>
At [C]:-1
At [C]:-1 error
At /engine/interface/ActorTalents.lua:175 useTalent
At /engine/interface/PlayerHotkeys.lua:169
At /engine/interface/PlayerHotkeys.lua:161 activateHotkey
At /mod/class/Game.lua:1967 f
At /mod/class/Game.lua:1562 fct
At /engine/interface/PlayerHotkeys.lua:316
At /engine/KeyBind.lua:229 In some situation it can be useful to have a page of lines before the error message so that it can be determined what talent/weapon was being used to cause the error.
If the error message is repeated a hundred times, it usually means the error happened in the UI code. You only need to post one copy of the error.
Sometimes the log file is cut off before the error occurs. In which case, you should enable flush logging (there is an option in the launcher for windows, or there is a command line option (--flush-stdout)). Then if possible, you do whatever you did before and the log will print correctly. Remember to turn off flush logging afterwards, as it makes the game run slowly.