Torchlight game problems cant change resolution

#Torchlight game problems cant change resolution windows#

Is it a handful of minutes, or many hours? Users on the Runic Games forum are complaining about diminished performance over time, so much so that they are restarting the game after 20 minutes I have to restart my laptop, there is nothing else I can do. When I start Torchlight, freshly installed just with the settings.txt, it freezes after some time the whole system (fedora 11, GNOME). All the particle effects and such appear to be in-tact, I don't assume it disables high-end graphical effects.?ДЇloxyz wrote:I did now everything mentioned in this thread but I have big problem. I'm also not exactly sure what 'safe mode' disables. Not sure if this is intended or not.ДЇullscreen would be very nice, probably my only real complaint. I have avoided using items with added fire damage because they seem to cause a quarter of the screen to appear 'on fire'. *Changing resolution works, but the game crashes - the resolution change does take effect when the game is restarted.ДЄnd I believe this is a 'fairly minor' graphical issue : *Enabling fullscreen causes the game to crash and will not load again (until settings.txt is replaced with the one from the archive). The things that don't seem to be working (causing a crash) are :

and so far not a single crash caused by gameplay. I have been into multiple dungeons, back and forth to town many times, character level 8, created another character, and swithced between the two, morphed my pet into different creatures multiple times, fished for a good 20 minutes, sold hundreds of items, enchanted my weapons, gemmed items, and changed every piece of equipment except an amulet many times, accepted and completed multiple quests.

#Torchlight game problems cant change resolution windows#

According to people on the Runic Games forums, Windows users are also having this issue.ДЄll I did was copy the settings.txt from the file above into the location that was specified, and I have been playing since then just fine. I'm using wine version 1.1.29 and got the exact same error message.