Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I mean the only thing I can think of at this point is that the game is using a process the current hardware or software simply cannot initiate no matter which update version is installed.
I'm using the same OS and i7 6700 and have an Nvidia gtx960m running on a MSI brand device.
You mentioned reinstalling DX9. And you're likely on the right track, but the rest may be experimentation to see if it can be resolved.
First up, I'd see if you installed the following:
DirectX End-User Runtimes (June 2010)
https://www.microsoft.com/en-us/download/details.aspx?id=8109
That's a full installer (so everything gets rewritten), not a web-based (which will only reinstall missing components).
I don't like uninstalling Windows updates (though I had to do it on one of my servers last week, coincidentally enough) however there was mention in another thread elsewhere that an update (KB3091424) from MS might have replaced one of the DX9 DLL's in the Windows folder. I'd start with a full install of the DX package I linked to before moving to uninstall a Windows update, then maybe if you can the ogre.log from the documents\my games\runic games\torchlight 2\ folder and (if you're up for it) the nfo from msinfo32.exe to get a better overview of the whole system.
Otherwise... we could tinker with the local_settings.txt file (also in documents\my games\runic games\torchlight 2), as that's where the game graphics settings are stored.
Could either delete the file entirely (so it would create a default copy on [attempted] launch), or play with for example switching it from fullscreen to windowed - I can't test (and wouldn't rule out, if it applies) but could it be an ultra-wide monitor resolution causing it, or something else related to sync with the monitor for instance?
Setting lines to the following in local_settings.txt would force it to windowed with a small res, just as a test to see if it would launch for instance.
WINDOWED_FULLSCREEN :0
FULLSCREEN :0
WINDOW_WIDTH : 800
WINDOW_HEIGHT :600