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.
Works with Wine 1.7.7
by Carlos Rodriguez on Wednesday December 18th 2013, 9:32
Wine 1.7.7 (compilado)
Nvidia Drivers 331.20 (.run package)
Linux Mint 15 KDE 32Bit - Kernel 188.8.131.52 PAE
CPU: INTEL Pentium G3220 (Nucleo Haswell a 22nm) 3.0Ghz (Dual-Core) Stock Clock
MEM: 8GB DDR3 1333 (2x4) Patriot value (128 bit dual channel: 21.3 gb/s)
GPU: Zotac Nvidia Geforce GT630 (GK208 28nm: 384 Shaders / 8 ROPS) Zone Edition Passive Cooling 2GB DDR3 1800Mhz a 64Bit (14.4Gb/s)
MAINBOARD: MSI H81M E33
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.