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 cannot remember the name of the option offhand, but it's in tsfix.ini and should be called something flip. The guide should also mention it.
AllowFlipEx=true
Replaced "true" with "false" but it still doesn't work. :(
Anything else that I can do?
From the Nvidia control panel either add a profile for the game exe and set the "preferred graphics processor" option to Nvidia or set it up so you can right click and select the GPU you want to use via a shortcut to the game which you can easily create by just right clicking on the game on Steam and selecting the "create desktop shortcut option" but these are just suggestions after reading the d3d9.log file where it looks like the Nvidia GPU is initializing (The 820M Fermi.) and then Intel's GPU driver (igdumdim32.dll) goes in and you get that game crash.
08/30/2017 12:17:15.700: [ D3D9 ] [@] Return: D3DERR_INVALIDCALL
https://forums.geforce.com/default/topic/555317/geforce-drivers/where-is-the-quot-use-high-performance-gpu-quot-option-/post/3857300/#3857300
That's an odd one though, is one of the default game options interfering? So whenever the settings file is removed the game works but then on next start it crashes again, only thing I could possibly think of is MSAA which was patched in some time after launch though I doubt it's that.
(The game is using DirectX9 so 2x or 4x MSAA if enabled should be supported even by very old GPU's.)
Not much more than a suggestion, if it helps that's good but the issue is kind-of worked around rather than solved and why would the Intel GPU initialize anyway? Especially after the Nvidia one is already being utilized unless it's just the driver interfering.
EDIT: Being on AMD I can't easily check the Nvidia driver options myself though but the log files show you're using a very recent driver so there shouldn't be any problems there. :)
(And Intel tends to manage their drivers via Windows Update and it's probably kept up to date too via that.)
Thanks for helping me. I tried what you said but it still doesn't work. Gives me the same white screen splash and then force closes. :(
EDIT: Or if it's the save files but why would those cause any problems.
(And only with SpecialK loaded at that, if it was trying to sync to Steam cloud and that caused some issue it would be one thing but it's not that.)
I tried removing the save file but now it does not start even with the save file removed. Is it because i installed the update for the TOS game?
That's beyond my knowledge unfortunately, Kaldaien has made several posts about this and from the sounds of it some of these mess things up a bit so it's possible it comes down to this even if it pointed to a D3D9 related error initially.
SpecialK doesn't go out of it's way to do this or that from my understanding of it but if the Steam_api.dll or other related files aren't following the what the official version does you might run into problems so that's a possibility but as I said my own knowledge on the Steam API features and functionality isn't that great. :)
Sorry for being able to provide a better answer.