Hi
@rejot
Very peculiar about the NVIDIA reference. Even more peculiar that the game works if it thinks it is running on a video card no longer in your machine?
Maybe the log can be explained by a dirty video card driver setup, and the logs are just showing the first video card found, yet the game ends up running on the ATI? That might be something we need to look at, but it is a tricky situation to investigate. Maybe a driver cleanup utility would clear up your system and even the log (but not improve the logs to better show available cards)
What crashes you might be if you still have an old homedir, like from back when you originally forked the project long ago? I'm seeing a couple clues in the log:
Code:
Java: 1.7.0_25 in C:\Program Files\Java\jre7
C:\Users\Rejo\Downloads\Terasology\modules\Core-0.45.1-SNAPSHOT.jar
The latest version of the game shouldn't even run on Java 7, and that version of Core predates our Alpha release back in March. It is possible you're running a newer engine but are getting outdated modules from the game data dir. That could easily cause crashes. Try deleting:
C:\Users\Rejo\Saved Games\Terasology
And rerun the game. Alternatively maybe I'm just looking at the log from one run and you're describing more than one (the v1.2.0 engine release is way newer and wouldn't run on Java 7)