All Discussions > Tools & Servers > Source SDK General Discussion > Topic Details
Serge Spartan 28 Oct, 2012 @ 10:01am
error windows "hammer it stop working"
I close hammer and it stop working.

probleme in windows

Signature du problème :
Nom d’événement de problème: BEX
Nom de l’application: hammer.exe
Version de l’application: 0.0.0.0
Horodatage de l’application: 503fea35
Nom du module par défaut: StackHash_0a9e
Version du module par défaut: 0.0.0.0
Horodateur du module par défaut: 00000000
Décalage de l’exception: 00000000
Code de l’exception: c0000005
Données d’exception: 00000008
Version du système: 6.1.7601.2.1.0.256.48
Identificateur de paramètres régionaux: 1036
Information supplémentaire n° 1: 0a9e
Information supplémentaire n° 2: 0a9e372d3b4ad19135b953a78882e789
Information supplémentaire n° 3: 0a9e
Information supplémentaire n° 4: 0a9e372d3b4ad19135b953a78882e789

Lire notre déclaration de confidentialité en ligne :
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x040c

Si la déclaration de confidentialité en ligne n’est pas disponible, lisez la version hors connexion :
C:\Windows\system32\fr-FR\erofflps.txt
_______________________________________________________________________

Quand je ferme hammer ca me dit que hammer a cesse de fonctionner detail si-dessus.
Last edited by Serge Spartan; 28 Oct, 2012 @ 10:01am
< >
Showing 1-3 of 3 comments
aceta120 13 Apr, 2013 @ 5:53pm 
Compiling can be a bit tricky with the "Run Map" option, one thing I did to solve it was NOT running VS (setting it to 'NO') in the run map tools. Also, using VBCT, which is recommended on the SDK pages themselves, still not running VIS there either, it helps compile much faster.

The main reason for this is because compiling can take so long, Windows would like to believe that the program is just not responding, if you leave it, it may still complete the compile, clicking/windowing out will most likely sit you in an eternal compile screen though.
#1
JuJu 14 Apr, 2013 @ 9:51pm 
\
We have just made a topic on GitHub. You may of heard of this site, but the source of it actually came from the word of Valve - asking us to post all bug reports there.

We just posted this: https://github.com/ValveSoftware/Source-1-Games/issues/287 Which informed them of why source sdk is not working in as detailed a way possible.

Please, please, please reply to the topic to keep it bumped up to the top, and type all your (positive, well spelt and gramatically correct) feedback there - so that they are more likely to read it.

Dont be afraid to make your own topics too - signing up on that site is simple - and seeing as valve said about it https://support.steampowered.com/kb_article.php?ref=7388-QPFN-2491, its definatly worth a shot.

Posting things like this is bound to be best:
problem >
how you caused the problem >
what its stopping you from doing >
how you think they could fix it >
how much you really like them and hope they read this >

God speed words.
#11

JuJu Just now
We are trying to get some attention. Be polite don't ♥♥♥♥ off and just ask for a fix.
#2
JuJu 16 Apr, 2013 @ 10:10pm 

Hi ?,
We're going to fix the SDK. We've no intention of discontinuing it.
We should have most of the problems related to SteamPipe fixed in the next week or so.
Please bear with us.
Thanks for your patience,
?

This is a real response. We all just need to be patient. But at least we have a response.
I am so happy that a request can still be heard.
Thank you so much everyone. A special thank you to Jack181
#3
< >
Showing 1-3 of 3 comments
Per page: 1530 50

All Discussions > Tools & Servers > Source SDK General Discussion > Topic Details
Date Posted: 28 Oct, 2012 @ 10:01am
Posts: 3
Start a New Discussion

Discussions Rules and Guidelines