• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.

Peutschika

Recruit
4 Badges
Dec 27, 2024
2
1
  • Hearts of Iron IV: Cadet
  • Hearts of Iron IV: Death or Dishonor
  • Hearts of Iron IV: Expansion Pass
  • Crusader Kings III
Just like the title says. I have my Steam and games installed on D:drive. Got the game working just fine when I tried installing it through the launcher to the C:drive. However, I don't want the game let alone my steam folders on my C:drive and I do want the game to be linked to Steam (which it wasn't here as Steam did not register play time etc.) so the D:drive is the only option. I have also tried deleting the launcher files (just reinstalls them automatically when launching the game from Steam), disabling Vsync (did nothing) and ticking the "disable fullscreen optimization" from the ck3.exe properties (did nothing).

I would also like to add that some years ago when I purchased the game it worked just fine on the D:drive.
 
If you installed to the C: drive though the standalone Paradox launcher interface, that is a really old game version (as the game is not supported there any more) so it is no surprise it behaves differently to the modern version from Steam. You can uninstall the game from there.

The game works fine from D: drive - that's where I have mine - your issue is elsewhere.

What happens if you run ck3.exe directly from the Steam/CK3 folder in File Explorer? That bypasses Steam and our launcher.
 
Thanks for your response. Tried now both the Steam start and running ck3.exe directly and both actually do work... after 9-10 minutes of initializing. After this the game runs just fine as it should. Is the game really that slow to start running nowdays or is there some potential problem here?
 
  • 1Like
Reactions:
5-10 minutes is fairly normal, depending on your hardware. Mine takes about 7 minutes on a most rig.