I think there has always been a problem launching a mod to debug directly through hl2.exe since mods started being based on the source sdk base instead of hl2/hl2dm. I found a way around it on the wiki, and that is to use steam.exe to -applaunch 215 with the -game as your mod, then manually attach the visual studio debugger to hl2.exe once it starts. Working directory is still set to source sdk base. In the debugging properties, I have command set to "e:\program files\valve\steam\steam.exe", and arguments set to "-applaunch 215 -dev -insecure -game "e:\program files\valve\steam\steamapps\SourceMods\Obsidiandev" -allowdebug %1 %2 %3 %4 %5 %6 %7 %8 %9"
From: "Ben Everett" <[EMAIL PROTECTED]> Reply-To: [email protected] To: <[email protected]> Subject: [hlcoders] Crashing on Debug Date: Wed, 4 Jul 2007 19:07:46 -0500 This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] Steam.exe is crashing whenever I attempt to debug our modification, it's before hl2.exe even launches. I'm launching source sdk base\hl2.exe with the working directory set to source sdk base. Command line arguments are: -dev -windowed -sw -game "c:\games\steam\steamapps\SourceMods\Forsaken" -insecure This is under VS2005, Vista x64. Any suggestions guys? -- _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
_________________________________________________________________ http://liveearth.msn.com _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
