Question

AlecRazec

Newbie
Joined
Sep 26, 2005
Messages
96
Reaction score
0
This thread could belong in about 8 different forums, Steam Help, Tech Help, GMod, HL2, but I thought it would be wise to send it here.

I'm having a bit of trouble getting my Gmod to work. With the new update, whenever I try to open Gmod, it gets to 'Preparing to open Half-Life 2' and then promptly Windows XP tells me that 'We're sorry, HL2 is having problems and needs to close.'

No window pops up or anything like that. I figured I may have corrupted so sort of file or something, so I plan to reinstall it. But I have NO idea how to do that with the new steam interface. Should I just go into my Steam->userid->ectect->gmod folder and delete the content in there and then install fresh or is the 'Nuke local Content' button staring me in my blind face?

Edit: Or I could be off. This problem applies to all Half-Life 2 related programs. This seems to have happend after a glitch in DoD I just didn't notice. Admin, feel free to move the thread to where ever approriate.
So the problem now stems from a bug in DoD. I was in Avalanche, climbing up the ladder in the cathedral, and all of a sudden the screen went black. No sound, no vision, nothing. Just black. I alt-tab out to see if it's the computer trying to start a program on it's own, nothing. Try to reenter. Still black. So I ctrl-alt-del and terminate the program. And now I get the error mentioned above, before it even boots up the program, 'We're sorry, Half-Life 2 has encountered an error and needs to close."

Do I need to delete my HL2 content and reinstall now, or is the whole thing FUBAR'd?
 
A program is never completely FUBAR'D. While I myself am not sure how to totally unistall the program including reg edit files (except maybe uninstalling then running Crap Cleaner to get rid of reg files not in use) which it seems may be necessary saying it's stemming through all of Steam.
 
Create a desktop shortcut. Right click, click properties. Go to the target line, it should be something like <directory> -applaction 220 <directory again> Change the 220 to 240... that should fix it, at least for now.
~
Aelphais
 
Back
Top