Selected Test Results (selected in 'Test Results' table below)
Installing the game
Launching the game
Multiplayer mode (Lan and Online)
What does not
Shadows aren't drawn correctly (mostly in the outside map of Act 1)
What was not tested
Walkthrough the whole game
-The random "Out of memory" crash can be workaround by launching steam using setarch ( 'setarch i386 -3 wine Steam.exe' )
Done several sessions of 2-3Hours without crash anymore.
-Sometimes the game doesn't close properly, had to killall Torchlight2.exe in order to close steam properly.
-The game run flawlessly : http://www.youtube.com/watch?v=jFMTtMMXNXs
Shadows do not work in Act 1, once in Act 2 I enabled shadows on very high detail and they worked perfectly. Went back to Act 1 and the blending issue showed up again. Once back in Act 2, shadows worked.
WARNING: Shutdown problems
It appears the game doesn't always shut down properly. For the all versions, this will waste RAM (and possibly CPU time). For the Steam version, this will also prevent cloud syncs, and you will not be able to re-launch Torchlight 2 until the old process is gone.
Use killall Torchlight2.exe2 to force-kill it. In my experience, this has no negative effects (if you do it after trying to shut down the game properly first).
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
Steam Installed How?
by Daniel R. Koris on Wednesday May 22nd 2013, 16:26
For this particular install, does Steam have to be installed using Wine? Because there is the new linux version out which I am using. I assume the install would probably not work for it in that regard?
I've installed Torchlight II but whenever I try to run the game import_dll complains about missing DLLs:
err:module:import_dll Loading library MSVCR100.dll (which is needed by L"C:\\Program Files (x86)\\Torchlight II\\LIBEAY32.dll") failed (error c000007b).
err:module:import_dll Library LIBEAY32.dll (which is needed by L"C:\\Program Files (x86)\\Torchlight II\\torchlight2.exe") not found
err:module:LdrInitializeThunk Main exe initialization for L"C:\\Program Files (x86)\\Torchlight II\\torchlight2.exe" failed, status c0000135
I didn't have libeay32.dll (as well as another DLL it was complaining about, ssleay32.dll) and downloaded it from dll-files.com and placed it in the game's folder. It still didn't work so I placed it in system32 and still it complains. VC runtime 2010 was previously installed via winetricks *.
How can I at least go about diagnosing this?
* The following DLLs exist in system32:
Torchlight 2 is grey screen in wine
by heather on Sunday March 10th 2013, 13:46
I installed wine 1.4.1 and steam on ubuntu 12.10. That all went fine and I installed Torchlight 2 but when I want to play it, the Torchlight 2 screen is solid grey. There is sound and the process is not hung (doesn't need to be killed). Please help?
Here are my installation steps in case that helps:
1. Downloaded installer and:
env WINEDEBUG="fixme-all" WINEPREFIX="/home/heather/.wine" wine msiexec /i SteamInstall.msi
2. Went through the steam setup using my existing account and then exited steam.
Can't see LAN Servers
by Thomas on Saturday March 9th 2013, 7:53
If you can't see any LAN servers its maybe because Torchlight is sending UDP packets to 255.255.255.255 to check for running servers.
255.255.255.255 as a destination broadcast address is translated by M$ Windows to something sane (say 192.168.1.255) before put on line. Wine does not copy this strange behavoir. In Linux these packets are leaving the PC as they are. Servers don't see these because packets can not get past input filters in OSes.
Write netfilter rule to substitute pseudo Windows broadcast address with real one (as Windows does internally).
1. Get real broadcast address. For example by running:
ifconfig eth |grep -o "Bcast:[^ ]*"
Command will print something like Bcast:192.168.1.255
2. Write netfilter rule by executing this:
sudo iptables -t nat -A OUTPUT -p udp -d 255.255.255.255 -j DNAT --to-destination 192.168.1.255
3. Verify. Folling command
sudo iptables -L OUTPUT -t nat -n
should print something like:
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
DNAT udp -- 0.0.0.0/0 255.255.255.255 to:192.168.1.255
Solution2 (Linux only LAN-Session as Windows does not allow this):
Simply switch to 255.255.255.0/24 as IP network configuration.
1. In config dialog choose IP-addresses between 255.255.255.255.1 and 255.255.255.255.254 for your LAN-PCs
2. As usal set subnetmask to 255.255.255.0
Now 255.255.255.255 is an valid broadcast and does not get filtered.
by Johan on Tuesday March 5th 2013, 10:22
I experience "random" crashes. The crashes give the following, or similar (VGL does not provide the same error every time), messages:
D3D9 : Loading 2D Texture, image name : 'media/ui/icons/skills/skills4.dds' with 0 mip map levels
D3D9 : Loading 2D Texture, image name : 'media/ui/icons/skills/skills3.dds' with 0 mip map levels
D3D9 : Loading 2D Texture, image name : 'media/ui/icons/skills/skills.dds' with 0 mip map levels
[VGL] ERROR: in readpixels--
[VGL] 274: Could not set PBO size
From reading the other comments, random crashes can occur it the setarch is not used, so I started using that - did not help. In Path of Exile I had similar crashes - VGL giving a message - however the same fix (openal32) did not work.
Why I say "random" is that the crashes started when I arrived at the area "The Salt Barrens". IT could be a new sound, new graphics effect that is used for the first time here. I have not been able to identify what - Once, it was when I clicked a "skull" (usually no crash), once I shot at a monster too far away for a hit (usually no crash), etc.
Hi all. I hope this discussion isn't dead yet.
I've been playing this game for a while now, about 2 months, and managed to finish the game once.
There are some minor issues, but there is one that bothering me a lot.
Every times a animation involving a lot of small particles, like sand and dust, the game freezes for a while.
Examples of when this problem occurs:
- every time I destroy a breakable with an enemy inside it.
- every time Rock Ogre (I forgot the name, it's the one that cast stone pillar) casts stone pillar, and also when the stone pillar collapse.
- when I cast "bramble wall" (one of outlander skills) and also when the walls collapse.
- when I fought manticore mate, one of it's skill is summoning a series of falling rocks. So, whenever the rocks hit the ground the problem happens.
The freeze duration varies, depending on the particles intensity shown on the screen. When an enemy pops out from an urn or crate for instance, the game only freeze slightly, almost unnoticeable. But when that rock monster cast stone pillar, the screen freezes for about 5 seconds or so. And when pillar collapsed, it could reach 20 seconds or more. And there is one time, when I encountered 2 of these. Each one of them cast stone pillar one after another, the screen froze for about a minute or more when the pillar collapsed.
At first, I thought the problem came from the game, or from my driver.
But now the game has reached version 1.20, and I just updated my system two days ago, I began to realize the problem probably because of my hardware.
So, I ask for anyone who knows the solution or workaround for my problem? Please..
I play on a Lenovo G460 laptop with 512 MB GeForce 310M. I use Arch and just updated two days ago.
Random crashes (more in LAN play)
by JoSch on Saturday September 29th 2012, 2:37
we experience random crashes of Torchlight 2 when playing in LAN.
We both run 64 bit Debian testing, wine 1.4.1-2, have 4GB ram and intel X2000 and X3000 graphics, respectively. We also tried to run the game in a 32 bit Debian Sid chroot to rule out 64bit as the source of the problem and experienced the same problems. We play at 800x600 resolution with lowest gfx settings in the game.
The same kind of crash would also happen in single player but just much more seldomly. We can play until level 17 or 18 until it crashes. When playing in multiplayer though, we can play the game until level 4 or 5 and then the crashes start. Now we are level 17 and crashes come more often after roughly 7 or 10 minutes of gameplay.
After a crash a window either says "Out of memory error" or shows the Runic Crash reporter. In both cases, my terminal says:
err:d3d:resource_init Out of memory!
fixme:d3d_texture:texture_init Failed to create surface 0x1aa43a08, hr 0x8876017c
This is for both of us. Anybody having similar problems?
Unable to determinate file type
by mzneverdies on Thursday September 27th 2012, 5:51
When running the demo (not buying prior to making the demo work), I get the following error:
"Unable to determinate file type(best guess Ascii).You need to save the file as unicode" refering to "my games/runic games/torchlight 2/local_settings.txt". Making that file unicode, results in direct crash (poping up the t2 crash report tool).
I've also noticed weird directories inside "my games/runic games/torchlight 2/save", like "9654014[chinese symbols][chinese symbols]".
by Kevin Whitaker on Wednesday September 26th 2012, 16:10
Ever since this weekend's update in Steam, Torchlight hasn't operated the same. After just playing for a minute, the frames drop to about 5-10fps. Has anyone else had this issue? I can't seem to have other games recreate this.
RE: slowdowns by Kevin Whitaker on
Friday September 28th 2012, 0:18
by Steve on Tuesday September 25th 2012, 12:25
If I set the torchlight settings to run in windowed mode or fullscreen windowed the game crashes. If i override the screen options through the wrapper to be fullscreen and leave the game settings to windowed it works. I would like to be able to have the game in windowed mode and the wrapper in windowed mode as well, but it crashes every time. I know that I can run the game in windowed mode, because when the wrapper is in fullscreen mode, the game still appears in windowed mode, but there is black all around it blocking out my desktop.
Multiplayer disconnect when player enters same zone
by Charlie Byce on Tuesday September 25th 2012, 0:21
Okay, this must not be a common bug because others have reported multiplayer to be working perfectly, so I'd love it if there were a workaround so I don't have to play on Windows.
When a friend connects to my server and loads in a different zone, everything is perfect. As soon as he enters the zone I'm in, though, we both see eachother disconnect but we both remain in-game, albeit alone. It doesn't make much sense.
I tried the game on Windows and it works perfectly fine. Any ideas? Steam version, BTW.
steam version runs great
by Pierre-André Leclair on Monday September 24th 2012, 10:55
I confirm that torchlight works (almost) perfectly with wine 1.5.13. Like most people, shadows are a bit of a problem until turned off.
I'd like to point out that the demo version on runic website does not work with wine. First there is the black window obscuring the launcher window, can be moved with alt-dragging the black window out.
However launching the game resulted in the same crash everyone had with the runic version (demo or bought).
Pretty odd to me that the steam version works fine and the original one doesn't.
Anyway, great game. It is everything I wished D3 to be.
by BadDreams on Friday September 21st 2012, 14:47
After i run the game i gen only black screen and i can hear the sound of the game which mean that the game is running. I find that in windows this can be fixed by running in window mode by adding -window to properties of executable file. but i don't know how to do this in wine or playonlinux. My VGA is intel
Sound Stuttering Problem and Solution
by Dane Mutters on Friday September 21st 2012, 1:15
I'm using Linux Mint 13 AMD64/Mate; WINE 1.5.13 (from Scott Ritchie's PPA), and Torchlight 188.8.131.52 (I think that's the version number) from Steam.
Everything works great, but I've encountered a sound stuttering problem. Every 3 seconds or so, the sound cuts out for about half a second and resumes. I had Firefox and some other things open at the time, but given my computer's hardware, this seemed odd. I have a Core 2 Quad @ 2.66GHz, 8GB DDR2 RAM, and a GeForce 560 Ti.
I was able to work around the problem by doing this as the launcher icon's command: