Re: MountAppFileSystem() failed: ... Bad launch configuration
Posted by MeatStick on
Tue Dec 21st 2004 at 3:59am
37 posts
4 snarkmarks
Registered:
Dec 6th 2004
Location: USA
MountAppFileSystem() failed: SteamMountAppFilesystem(0x12e0f4) failed with error 4: Bad launch configuration
I just updated the entire suite, reset game configs, Refreshed SDK contents, ran HL2, HL2DM and CS and then exited, then ran Hammer and tried to run the map I've been working on for so long and ... GGGGGAAAAAAAAHHHHHH WTF! Anyone run into this after updating and figured out the fix yet? Everything is set to HL2DM for the game config. I notice that Hammer now uses (and REFUSES to use anything else!) environment variables for the paths to the various folders. I tried to manually put the absolute paths in there, like I had before, and it just resets to using the variables, though those variables should resolve to the exact same place, however I assume Steam has taken care of creating those variables for me. If that's not the case perhaps this is the issue. If so, can I just slap together an environment variable using the absolute path up to and including the user ID. For instance, it has $SteamUserDir\half-life 2 deathmatch. Should I go create a variable that makes $SteamUserDir = D:\Games\Steam\SteamApps\MyUserID\ ?
I did a search on goog for this error and the closest (in ENGLISH) that I came across seemed to be a bunch of jerk-offs that don't actually own the game but instead are doing something "else". Well, I'm staring at my HL2 box right now wanting to smash someones face in.
Re: MountAppFileSystem() failed: ... Bad launch configuration
Posted by Baddog on
Tue Dec 21st 2004 at 5:02am
79 posts
8 snarkmarks
Registered:
Dec 6th 2004
Location: Portland,Oregon USA
All I can tell u is that I had the same problem so I backed up my map and reinstalled the sdk.
Re: MountAppFileSystem() failed: ... Bad launch configuration
Posted by Leperous on
Tue Dec 21st 2004 at 10:13pm
Posted
2004-12-21 10:13pm
Leperous
Creator of SnarkPit!
member
3382 posts
1635 snarkmarks
Registered:
Aug 21st 2001
Occupation: Lazy student
Location: UK
I had this problem too a while ago, unfortunately reinstalling the SDK was the only way to fix it :sad: If you do and it still doesn't work, try deleting the GCFs and the directory yourself manually.