After a hiatus following the conversion of the game I purchased (TSW) to what is now marketed as “TSWL”, I tried to start my old TSW installation but it seemed to do nothing. No window opened, no hdd activity, no feedback at all. So I checked the running tasks and found ClientPatcher.exe *32 running at 17% CPU. Killing it and restarting didn’t make any difference.
So then I uninstalled the game and downloaded the installer anew, but that gave the exact same issue; the launcher was installed but won’t actually show up or do something useful, sitting at 17% CPU untill killed manually.
Since the TSW and the TSWL patchers are essentially the same, I tried starting TSWL, which also happened to be on my system due to the initial issues with the relaunch.
This, too, spawns “ClientPatcher.exe *32” and leaves it sitting at 17% CPU, albeit with a 4 times larger memory footprint.
Then I read about directX apparently not being launched by the standalone installer, and went to use the steam install.
Guess what… after downloading all the data, it would ALSO spawn “ClientPatcher.exe *32”, sitting at the same 17% CPU and the same memory footprint as the standalone TSWL installer.
I ran dxdiag 32 bit and 64 bit, no errors reported. I have absolutely no issues with other games, so directx clearly is working.
I then ran dxwebsetup.exe from the installation folder as suggested by the other post, which proudly told me that a newer version of directx was installed and that no action needed to be performed (which is both correct and expected). That did, however, not change the problem at hand at all.
What I did change between back then and nowadays is the graphics card. It however uses the same driver as the previous one (radeon unified driver), has the same specs and, again, no other game even cared about the change. Even other Funcom games run perfectly fine, like Conan Exiles.
So… how do I get the launcher to tell me what the hell the problem is? Why can’t you gaming companies produce software that will tell the user what the problem is anymore? Why am I being kept in the dark about issues that very likely are easily fixed by myself without causing endless support tickets if only I was given the information needed to do so by the software causing the problems in the first place?
Obviously, the launcher is waiting for something, but for what? A connection to the internet (why bother until the main window is created and shown)? A driver to be loaded (why not time out gracefully after a sensible time like 30 seconds and then tell me what the problem is)? Some other condition to be met (again, why not pop up a standard dialog box informing me about the requirement)?
So, now I am here, asking you to guess and tell me what the software definitely knows but refuses to tell me…