It's just the debugger deciding to tell you about every single C++ exception that gets thrown in Steam.dll. I don't know how to turn it off, but we have adjusted some things in steam.dll to gretly reduce the volume of the spammage in the next release.
Taylor -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeffrey "botman" Broome Sent: Monday, January 03, 2005 6:46 AM To: [email protected] Subject: [hlcoders] First-chance exception spam in Visual Studio Output window... I was creating some Wiki documentation over the weekend and I wanted to start building a MOD from scratch so that I would have exact wording on Dialog boxes and whatnots. So, anywho, after deleting MyMod directory and deleting SteamApps\SourceMods\botman folder, and using "Reset Game Configurations" to flush everything from Steam. I "Create a Mod" in the "C:\MyMod" directory and name the mod "botman". I open up Game_SDK.sln in Visual Studio .NET 2003, change to the "Release SDK", build the solution, it copies the client.dll and server.dll to the Mods "bin" directory. I start things up from the Steam "Play games" dialog by double-clicking on my MOD name. Everything runs fine, I start the vehicles map, shoot my gun a few times, then quit. Then I switch to the "Debug SDK" solution, delete the client.dll and server.dll files from my Mod's "bin" directory, build the solution and the debug .dll files show up fine. I set the Debugger properties on the "hl" project to: Command: c:\program [EMAIL PROTECTED] 2\hl2.exe Command Arguments: -dev -game "c:\program files\valve\steam\steamapps\SourceMods\botman" -allowdebug ...right click on "hl" in the Solution Explorer and do "Debug->Start new instance". Everything starts up fine, but I get (literally) thousands of exception messages... Microsoft C++ exception: common::CErrorCodeException It's been a few weeks since I ran a Mod in the debugger, but I don't seem to remember getting all that before, but I did remember somebody posting a message to this list about a month ago saying they were getting LOTS of "exception" messages, and I replied that you can turn off some of the exceptions using "Debug->Exceptions" in Visual Studio .NET 200, but you can only turn off stuff that Visual Studio recognizes (like stack overflow, illegal instruction, or array bounds exceeded, etc). common::CErrorCodeException is something being raised by the engine and isn't something I can turn off. I did notice that if I create a server plugin for a Valve game (like CS:S or HL2DM), I get a few common:CErrorCodeException messages when starting up, but I don't get the 1000's of message that I get when I start my own MOD. So, to make a long post even longer, does everybody get 1000's of these execption messages in the Visual Studio Output window when running their MOD in the debugger, or do I just have something not set up right? P.S. I did try adding "-steam" to the "Command Arguments" before starting the debugger, but that doesn't seem to make a difference, I still get the same behavior. -- Jeffrey "botman" Broome _______________________________________________ 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
