CH launcher runs VanHelsing_x64.exe in 32bit mode instead of VanHelsing_x86. Is it supposed to do that?
Looks like VanHelsing.exe autodetects your system and runs appropriate mode and CH launcher seems to target that one instead of x86.
I'm having crash trouble like others here and wonder if its because of that.
wrong: ch launcher only launches the x86.exe , cal changed the x64 into x86, so no matter what win32 64 bits you use it always starts up the x86 mode
that is if you renamed the original vanhelsing.exe and copied the ch exe to the game folder and renamed that one to vanhelsing.exe
if you did the latter the steam launcher makes use of the ch exe and always starts up in x86 mode.
Worst trainer ever I have to put a retarded file into my directory just to use it. Learn how to make a proper trainer major fail gents.
BYE BYE DOUCHE! NOW GO FIND ANOTHER TRAINER FOR THE GAME! OOPS THERE ARENT ANY ARE THERE..
the launcher is so you can actually train the game because the stupid developers are making it impossible to launch the game and access it like NORMAL GAMES... it was an AID, and shows how GOOD we are at what we do, ok GENT?
now go slog off somewhere and never come back..
What I do for every Steam game is to use a .txt file called steam_appid.txt since it allows for launching the game exe directly without Steam triggering.
(Steam will still be used of course.)
For this game, since launching the game exe directly or starting the game from Steam would otherwise run the launcher exe and automatically run the 64-bit exe if it detects a 64-bit version of Windows you can instead use that file and then start the x86 exe directly.
(Make a shortcut for it if desired.)
Steam_AppID.txt should contain the ID the game has on Steam which is 215530
However I also read a earlier post that one could simply replace the default launcher with the launcher included with the trainer and have the game default to the 32-bit exe that way which might be even simpler.
Oh and nice to see the trainer already updated for 1.0.0.2, however they still have a number of known issues (Several of them related to multiplayer.) so a 1.0.0.3 patch will probably follow shortly.
(NeoCore has this problem with their games, King Arthur: The Role-Playing Game series for example.)