Even if it was a bugged response, the variables don't magically set themselves to 3MHz and 0MB. Something is putting those values into the variables.

I still believe there is a correlation, but we'll just have to wait for an official patch I guess. Thanks, GStaff, for looking into this for us, though. We all really appreciate the feedback.

My video memory says 0 and after installing the newest Ati Rage driver my performance issues are gone.

It wouldn't surprise me if everyones video memory said 0. Have we seen anyone who has a > 0 value?

The readout is just a log, true, but it is most assuredly displaying incorrect information. That incorrect information has to come from somewhere.

Further, why would there be a log entry for information that isn't even used? Clearly that particular information was deemed to be important enough to display in the initialization log.

It might not directly have anything to do with anything, but it's damn suspicious.

I believe someone on the first page of this thread said his was.. I'm taking his word for it.

I really think this still needs to be looked at. For the record, the 3mhz you guys are seeing is probably a round up or down of your cpu clock speed.

I've got a 4.0ghz machine and it says I have a 4mhz CPU, and no VRam. I've got the horrible texture issues as well.

http://cloud.steampowered.com/ugc/542907314995073448/C9F1856DBD772C82EC3AEA63DC425149A857697E/

http://cloud.steampowered.com/ugc/542907314994988903/49AFF3EFBCD10893F04E1072EA02631A8354A81B/

I've got dozens of screenshots, all showing very poor texture quality and texture pop-ins.

i7-860@4.0ghz
8gb ram
gtx 480

Hmm well, I have come across another texture problem

http://steamcommunity.com/id/eGOSquishyeg/screenshot/594698710699034227

I've only been encountering this when Catalyst AI is Disabled, however when it is Enabled, I get like 1 Frame Per Minute. Anyone know how to fix this WITHOUT turning on Catalyst AI?

Same problem. Turn off Catalyst AI - get texture artifacts, turn on - slideshow.

That's a typo, it should read 3 Ghz. Again, this readout isn't used by the code and doesn't affect performance. The teams at id and Bethesda remain focused on issues you're experiencing, but I wouldn't worry about this readout.