Well, when MW3 crashed, it would say: "Modern Warfare 2 has stopped responding." and the console said "Modern Warfare 2" as the title.
Hmmm. Well, I didn't see anything from Fallout 3 in New Vegas. Or is there....
As some of you may or may not know, I reverse engineer video games for fun, and not to toot my own horn, but I'm quite good at it.
The first obstacle I had to overcome was unpacking the EXE. 2easy. Launch it, capture it. Done. At first, I thought it was Steam CEG encryption, but it was just some compression packing, and a quite shotty one at that.
Anyway, moving on.
So I was bored last night and I was poking around the code where it adds the shell casings you pick up from your weapon, and I see this:
http://img69.imageshack.us/img69/6197/felloutofmyfallout3exce.png
For those of you who don't know what that is, it's a string related to debugging. What it does, is it sets the exception catcher's output, so if it gets an exception from within this function, it will say something like:
Exception at D:\_Fallout3\Platforms\Common\Code\Fallout Shared\InventoryChanges.cpp Line 3368.
Just thought that was a funny coincidence, considering how much of a failure Falllout New Vegas 1.0 was and the relationship to MW3.
What I also don't understand is why Bethesda stops supporting the game with patches after a year after release. There are so many bugs in New Vegas still, 99% of which are documented on the Fallout New Vegas wiki. Most of them are just scripting errors which could be fixed in a matter of seconds.
And it's not like nobody plays New Vegas anymore, it's one of the most played games on Steam: http://store.steampowered.com/stats/