Are you opted into the Steam client beta?
Yeah, sorry I should have mentioned that in the report. Opted into the beta and on Linux.
beta for the steam client right? That is different to the game beta's. The reason I ask is that there is a bug fix for this in the Steam client beta that is live right now, so in theory it is fixed.
Yeah - the client beta. I did just pick up an update although there's no notes currently posted on the Steam group. Will try and install one of these again and have a look at what happens.
Great, you may have to reinstall the dependent games (opfor, ep1, et al) to verify the fix, and please say if it doesn't work.
Okay, internet taking a dump so that took a bit longer than usual. Anyway, reinstalled Half-Life to the extra Steam library then tried installing Blue Shift aaand.... nope. Blue Shift is in the default library again.
Same with Episode One, unfortunately.
Right hang on. I appear to be having an issue with the updater. Despite being prompted for an update I just did that whole operation in the May 17th build rather than today's. The client is now just telling me I'm up to date if I check for an update.
Okay, we have a Steam client updating bug right now, so I bet you are flopping across broken and working versions, can you wait a couple of days and then try again :)
Just got the 21st May build and installed OpFor which landed in the right Steam library.
Blue Shift as well. Pencilling this one as fixed.
I've just updated Steam (May 21 2013, 14:24:03 build) - and I am still unable to install both BS and OpFor to non-standard directories
From the beta update log:
My affected games (where I am unable to choose another path):
I've read somewhere that non-standard paths are only allowed for SteamPiped games, which might explain the non-Valve titles.
Though, reading the first post it seems that Half-Life is able to be installed in another path (where mine is not?).
@swordfischer Blue Shift and OpFor are dependent games of Half-Life. This means you can't choose an extra Steam library for them to be installed into, they will always install into the same folder that Half-Life is already installed in (as of the May 21st build) so you're actually seeing the correct behaviour on those.
Strange that you can't select another path for Half-Life though. In fact Serious Sam 3 should be moveable too.
Once ANY hl based game is installed the library location will be locked, you need to remove all the HL games to then get the option to move the install.
@alfred-valve That was my thought too, but I have none of the HL based games installed ( not even Half-Life ).
I am simply unable to install Half-Life in any path besides the default one.
Though I have had Half-Life installed once, but removed it last week because I needed to move the games to another drive.
Does this mean that if you install HL to the default Steam Library folder, then uninstall, and then want to install: it will always be forced default Steam Library folder?
Also to loop back to my previous comment, none of the games are installed.
] app_config_print 70 "UserConfig" { "name" "Half-Life" "GameID" "70" "betakey" "Beta" "Language" "english" }
Today I was able to install as intended. (This goes for all my mentioned games). Fixed for me too :)
I have a dedicated hard drive for games with the Steam library
/media/games/Steam/Linux/. Half-Life and Half-Life 2 are installed there so the full path is/media/games/Steam/Linux/SteamApps/common/Half-Life{ 2}/.If I install Blue Shift or Opposing Force, they are installed to
/home/joe/.local/share/Steam/SteamApps/common/Half-Life/{gearbox,opfor}/and Episode One and Two to/home/joe/.local/share/Steam/SteamApps/common/Half-Life 2/{episodic,ep2}/regardless of the fact that their parent games are on another filesystem.This means that those games don't launch, since they share binaries with their parent games. Symlinking works, though.