- last post: 01.01.0001 12:00 AM PDT
Posted by: halo3leader
well it's because somewhere along the line a mod got put into the game's file just let the exception run and it should work next time you load it up*facepalm* I don't think you even know what an exception is, do you?
Sorry, pet peeve. As a programmer, I hate it when people don't know what they talk about.
I think you somehow got this confused. Just because Halo happens to launch an exception when you mod (short for "modify") something improperly. And if you modify, say, a .map file improperly in a way that the main executable can't handle, it's only option is to launch an exception. Which can be caused my modding. But "modding" isn't the only reason. Just because you (assumidly) saw this in Halo 1 PC, doesn't mean that's the only way that can happen.
Sorry, I'm being a troll, and I'm not helping out at all. But... pet peeve >_>
Still "let the exception run", that doesn't even make sense... Gah.
EDIT: Yeah, I'm pretty sure that Halo PC might not like a setting on your Nvidia/ATI control panel. Go load that up, and set it to Application Controlled. Or, if possible, only set Application Controlled for halo.exe. That way, you can run all your other games with pimp'd settings, and it'll allow Halo to run properly.
I remember when I tried to turn on Anti-Aliasing for Halo.exe, I'd get the exact same problem as you every time. I turned it off, and it worked. Hope that helps.
[Edited on 12.28.2007 1:55 PM PST]