First off, you should remove "applaunch 220" from your command line parameters. Secondly, have the working directory set to the HL2 directory. After that, see if you are still getting the same crash. Let Alfred know if you have the tier0_s.dll problems/crashes after that.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gnolfo Sent: Thursday, September 29, 2005 10:35 PM To: [email protected] Subject: Re: [hlcoders] Tier0_s.dll error when debugging Source Mods ( was: Last update has broken Mod shaders and is causing crashes ) This is a multi-part message in MIME format. -- [ Picked text/plain from multipart/alternative ] I was playing around with this just today, and got it mostly working and have isolated the problem to some areas: First off, this is all with VS 2003 and the SDK "Source Only" codebase, here's my launch options: -steam -applaunch 220 -dev -allowdebug -windowed -game "my\mod\path" If i add +map "mymap" to that, I get the tier0_s.dll error. However if I omit that it works, and then if I load the same map ingame it works just fine. NOTE: I recently changed my code from the "Modify HL2 MP" SDK option to the "source code only" one, mainly so I could branch it in perforce per the instructions on your wiki. The Steam/Source update last week broke this for that codebase as well, and I found that removing the +map arg fixed it. Another problem I'm having now is between debug and release builds. I've checked all the project settings a zillion times, even looking through the files in notepad, and can't seem to find any differences to make this this happen, but I cannot launch the debugger in the solution's debug config. It pops up with a null pointer error. Here's the call stack: > FileSystem_Steam.dll!0d0ee66f() ntdll.dll!77f56dc0() tier0.dll!0086105a() vstdlib.dll!008a407e() tier0.dll!008664b5() tier0.dll!0086105a() tier0.dll!008637d1() launcher.dll!10005ae1() launcher.dll!1000709b() launcher.dll!1000713b() launcher.dll!10007ff9() launcher.dll!100057f8() ntdll.dll!77f8cf62() I guess maybe the current steam build doesn't allow debug builds to run at all? Another issue I came across that be related. Here's what I've got for my executable path in VS: Steam\SteamApps\~username\half-life 2 deathmatch\hl2.exe And my working directory: Steam\SteamApps\~username\half-life 2 Note that the exe is in deathmath and the working directory isn't. That's the only combination I could find to make it run in the debugger (and again only on the release build). Any other combination and I get an error message saying it failed to load the launcher dll. This might have been something I screwed up when I switched codebases. There were a few differences between them, but nothing that would seem to affect other dll's from loading correctly. Before I made the codebase switch (and was working from the HL2MP stuff) I used to have my executable and working paths both pointing to the regular haf-life 2 directory. I hope that helped. If you need more info about my project settings and the like, or if I'm be doing wrong, please let me know :) -Matt ----- Original Message ----- From: Alfred Reynolds To: [email protected] Sent: Thursday, September 29, 2005 3:56 PM Subject: [hlcoders] Tier0_s.dll error when debugging Source Mods ( was: Last update has broken Mod shaders and is causing crashes ) Is anyone still experiencing this error? And just to double check, who is successfully debugging their mod under steam right now (and if so with what launch options)? - Alfred -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ben Everett Sent: Monday, September 26, 2005 9:31 AM To: [email protected] Subject: RE: [hlcoders] Last update has broken Mod shaders and is causing crashes Still not working, same crashes with the error as stated before. The problem seems to be with the DLL tier0_s.dll. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Krenz Sent: Sunday, September 25, 2005 11:03 PM To: [email protected] Subject: Re: [hlcoders] Last update has broken Mod shaders and is causing crashes Control Panel -> System -> Advanced tab -> Environment Variables button -> look for "sourcesdk" in the list of System Variables. This was also after I ran the SourceSDK from the Play Games window in Steam and chose "Refresh SDK Content". If that doesn't work, try the following: "c:\program files\steam\steam.exe" -applaunch 220 -dev -allowdebug -game "<your mod's directory ie c:\mod\mod>" Then I suppose you can try attaching your debugger to it. Ben Everett wrote: > Hmm... I'm still unable to get my mod to work when being launched from VS. > Same errors as before. I've tried using all of the tips you guys have left > but nothing as of yet. The sourcesdk env variable you are referring to, is > this in VS or Windows? Could you provide a example key-value pair? > > And any word on Valve as to a REAL solution? It's kind of disturbing that > they haven't responded to any of our issues (I know that I at least check my > work e-mail on the weekends). > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders -- _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
