Failed to connect with local client steam process while building cubemaps/nav file

[akshtsaklani7]

Describe the bug A clear and concise description of what the bug is.

• Whenever you try to build Cubemaps or Nav File, the program fails to launch the game as soon as it comes to building cubemaps/nav file.

• says that steam needs update. The steam is updated though.

• When you close the error, the compile process completes and the map runs, but without cubemaps/nav file.

• The logs still capture it as "Cubemaps built successfully".

Steps to reproduce Steps to reproduce the behavior.

• Add CSGO map and compile it with Cubemap and/or Nav File options checked.

Expected behavior

• The cubemaps and the nav file should get built.

Debug.log Please upload the debug.log file found in your Compile Pal folder. debug.log

Crash logs If applicable, please upload crash logs found in the CrashLog folder. NA

Additional context

• Happens for both version 27 & version 27.11.

• Tried only with CS:GO.

• Attaching screenshot.

[Exactol]

Is Steam running when you try to build cubemaps?

[akshtsaklani7]

Tried it with steam running, steam not running, game already running, game n iij t running. Doesn't work in any of the scenarios. I get the same result with -game parameter. It fails to launch the game. The default hammer compiler however never had a problem launching the game.

[Exactol]

Can you try using version 26? v27 changed how the game/nav/cubemap commands launched games, this might be a regression.

[akshtsaklani7]

Tried 26.2. Same error.

[Exactol]

Can you verify the integrity of the game files?

[maxdup]

So... this is awkward but as far as I can tell, you can't launch CSGO by its executable anymore. Unless I'm missing an alternative, it must be launched through steam C:\Program Files (x86)\Steam\steam.exe -applaunch 730 -game "C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\csgo"

This means NAV, CUBEMAPS and GAME are broken atm

[Exactol]

Closing stale issues, please try the latest prerelease and if the issue is still happening feel free to reopen