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
Likewise, it'd tell you in tsfix.log as well.
Sometimes the D3D9 device will fail to reset and that will bring the entire game down with it. My borderless window mod is designed to avoid those problems though.
This is one of the reasons VMProtect sucks. Random executables with untraceable crash events.
http://steamcommunity.com/sharedfiles/filedetails/?id=618359790
You mean I fixed the game. You responded to the wrong person :)
TSFix automatically does this and then automatically restores input services when the game exits.
I do agree, 60 FPS would be nice, unfortunately VMProtect is preventing that :-\
0.2.1 is when I began forcefully disabling the service.
That keyboard app is the least of your problems, any random program can start and then load input services on-demand if the service is not disabled. I found that during debugging, which is what lead to my policy change from simply suspending to actually disabling touch input services in version 0.2.1.
What you've done here, kills the program but doesn't prevent it from randomly launching again in the future.
By all accounts, the former solution should work better than the latter. Something's not adding up :-\