Hell, at least you can actually start your copy. Mine doesn't ebven make it past the startup screen.

And now I find out that it isn't 7 compatible. I am so not suprised.

Funny thread is funny. :laugh:

I sent a reply to Bethesda recommending them to change the information on their web site and on the Box that the game was not for Windows 7, not too expose themself to FTC filings

And what do you know, I got an reply today:

"Hello,

I do apologize for the confusion, but Fallout New Vegas is indeed compatible with Windows 7. The last response you received was in error........"



Lol, so it was a "support cop out", as susspected.

And they want an new DXDIAG (the third by now), so the never ending story continues

I ran the game fine for almost 50 hours on Windows 7 x64 Service Pack 1 Beta. Some problems, but not related to the game itself, hardware issue on my end.

I seriously would not call a leftover bit of text from FO3 a "support cop out".

The entire section you quoted was likely set as his "signature" in the email program and added to every message. They just forgot to remove it when New Vegas went live.

Lol, I love the part where you "know" where it was set in a email you haven't seen.

And, no it wasn't in his signature. It was in the middle among other instructions.

Ah, my apologies then. The section you quoted in the first post appeared to position it directly above his signature/name/contact information, where this type of boilerplate information is often placed. I didn't realize you were cutting and pasting different sections of the email since you gave no indication of that and used quotes around the entire block.

The guy was probably just so used to saying that about Fallout 3 that he forgot he was providing support for a different game...

I'm running Windows 7 64-bit and i've only experienced a few bugs. Just one or two crashes and ED-E went psycho in Primm. Other than that it works great.

I'm on Win7 64bit as well but i keep getting CTD's quite often, Vault 22 was a nightmare and i had to give up the quest there.

Win7 Pro 64bit here. Can't complete 'For Auld Lang Syne,' which is a gamebreaker. More than half the time I can't even start the launcher, but I think that's a Steam problem, because the event log shows that the game overlay renderer .dll file is causing the crash. I also crash at least once every time I play. So for the idiot who claimed that "all" the bug complaints were from console users? Learn to never generalize. It makes you look dumb.

Of cause you couldn't know that. My bad.

One reason I call it "cop out" is that this has become standard business practise.

First you create a "support forum", this in not for giving support or communicating with the customers though. This is so other customers can help those with problems. Quite much cheaper that way

Then if a customer sends in e-mails for support the replies are "cut and paste" from different templates. Quite often not related to the problem.

"Reinstall the game". Well i wrote that I done that.
"Verify game cashe". Yea, wrote that to.
"Update drivers". Well, look at the DXDIAG and you can see that that is done.
"Send DXDIAG". Whats wrong with the one 2 e-mails down??
"Your operating system is not supported". Sigh.........


So maybee I am just tired of how a lot of companies launches games according to the corporate launch schedule, whenever they are ready or not, then focus on the money-making DLC's and puts support and patches as second priority. Maybee it's just me.