Falout 3 Is Too Buggy and full of bad coding, and no one feels responsible

This topic is locked from further discussion.

Avatar image for traber1228
traber1228

25

Forum Posts

0

Wiki Points

0

Followers

Reviews: 0

User Lists: 0

#1 traber1228
Member since 2008 • 25 Posts

I repeatedly get a crash at the birthday party at age 10. I contacted bethesda with the following info. Their responce will follow the DXDiag info. I would appreciate any help or responce..

------------------
System Information
------------------
Time of this report: 12/30/2008, 05:30:38
Machine name: TOM2-PC
Operating System: Windows VistaTM Home Premium (6.0, Build 6001) Service Pack 1 (6001.vistasp1_gdr.080917-1612)
Language: English (Regional Setting: English)
System Manufacturer: Gateway
System Model: GT5694
BIOS: Default System BIOS
Processor: AMD Phenom(tm) 9100e Quad-Core Processor (4 CPUs), ~1.8GHz
Memory: 3838MB RAM
Page File: 1814MB used, 7685MB available
Windows Dir: C:Windows
DirectX Version: DirectX 10
DX Setup Parameters: Not found
DxDiag Version: 6.00.6001.18000 32bit Unicode

------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Sound Tab 2: No problems found.
Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)

---------------
Display Devices
---------------
Card name: ATI Radeon HD 3200 Graphics
Manufacturer: ATI Technologies Inc.
Chip type: ATI Radeon HD 3200 Graphics (0x9610)
DAC type: Internal DAC(400MHz)
Device Key: EnumPCIVEN_1002&DEV_9610&SUBSYS_014E1025&REV_00
Display Memory: 1917 MB
Dedicated Memory: 253 MB
Shared Memory: 1663 MB
Current Mode: 1024 x 768 (32 bit) (60Hz)
Monitor: Generic Non-PnP Monitor
Driver Name: atidxx32,atidxx64.dll,atiumdag,atiumdva,atiumd64.dll,atiumd6a.cap,atitmm64.dll
Driver Version: 7.15.0010.0163 (English)
DDI Version: 10
Driver Attributes: Final Retail
Driver Date/**** 12/1/2008 14:35:27, 2340352 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B71EE2-D550-11CF-E371-4421A1C2CA35}
Vendor ID: 0x1002
Device ID: 0x9610
SubSys ID: 0x014E1025
Revision ID: 0x0000
Revision ID: 0x0000
Video Accel: ModeMPEG2_A ModeMPEG2_C
Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled

_____________________________

Here is a copy of the E-Mail communication.;;

I disagree with your recommendation that this is not enough of a machine to run Fallout 3. I feel the software is buggy and attention needs to be given to corrected coding. In fact I do meet the minimum requirements established by your company.

As I stated before my machine is as follows:

Time of this report: 12/30/2008, 05:30:38

Machine name: TOM2-PC

Operating System: Windows VistaTM Home Premium (6.0, Build 6001) Service Pack 1 (6001.vistasp1_gdr.080917-1612)

Language: English (Regional Setting: English) System Manufacturer: Gateway

System Model: GT5694

BIOS: Default System BIOS

Processor: AMD Phenom(tm) 9100e Quad-Core Processor (4 CPUs), ~1.8GHz

Memory: 3838MB RAM

Page File: 1814MB used, 7685MB available

Card name: ATI Radeon HD 3200 Graphics

Manufacturer: ATI Technologies Inc.

Chip type: ATI Radeon HD 3200 Graphics (0x9610)

DAC type: Internal DAC(400MHz)

Device Key: EnumPCIVEN_1002&DEV_9610&SUBSYS_014E1025&REV_00

Display Memory: 1917 MB

Dedicated Memory: 253 MB

Shared Memory: 1663 MB

*The processor is a 1.8 Gig but you fail to realize that a quad core 1.80 GHz Performs at 4.59 GHz

*The ATI HD3200 is built on the same video card chipset as the ATI HD3400, therefore I see no difference

I am badly disappointed in the solution which seems to be to drop the ball after the release of the product and be so quick to lay it back on a hardware issue.

If you can assist me any further by going back to the drawing board please contact me further..

Thank you

________________________________________________________

-----Original Message-----

From: bethsoft.tech@aqinc.com [mailto:bethsoft.tech@aqinc.com]

Sent: Friday, January 02, 2009 1:33 PM

To:

Subject: In response to your question about Fallout 3, your customer number is 400084777

Hello,

Your 1.8 Ghz processor is below requirements for Fallout 3.

Fallout 3 for PC requires the following:

Minimum System Requirements:

* Windows XP/Vista

* 1GB System RAM (XP)/ 2GB System RAM (Vista)

* 2.4 Ghz Intel Pentium 4 or equivalent processor

* Direct X 9.0c compliant video card with 256MB RAM (NVIDIA 6800 or better/ATI X850 or better)

Recommended System Requirements:

* Intel Core 2 Duo processor

* 2 GB System RAM

* NvidiaDirect X 9.0c compliant video card with 512MB RAM (NVIDIA 8800 series, ATI 3800 series)

In addition, some content requires access to Games for Windows LIVE, including the PC Fallout 3 Achievements. More info on Games for Windows LIVE is available online at www.gamesforwindows.com/live/

Below is a list of the supported video card chipsets for the PC version of Fallout 3:

* NVIDIA GeForce 200 series

* NVIDIA Geforce 9800 series

* NVIDIA Geforce 9600 series

* NVIDIA Geforce 8800 series

* NVIDIA Geforce 8600 series

* NVIDIA Geforce 8500 series

* NVIDIA Geforce 8400 series

* NVIDIA Geforce 7900 series

* NVIDIA Geforce 7800 series

* NVIDIA Geforce 7600 series

* NVIDIA Geforce 7300 series

* NVIDIA GeForce 6800 series

* ATI HD 4800 series

* ATI HD 4600 series

* ATI HD 3800 series

* ATI HD 3600 series

* ATI HD 3400 series

* ATI HD 2900 series

* ATI HD 2600 series

* ATI HD 2400 series

* ATI X1900 series

* ATI X1800 series

* ATI X1600 series

* ATI X1300 series

* ATI X850 series

Unfortunately, your system does not meet the minimum system requirements for the program to function properly.

Your customer number is xxxxxxxxxx

Please refer to case #:: xxxxxxxxx if you have any further questions.

If you need further assistance, you can also reach us online at http://support.bethsoft.com/ or our technical support staff at (410)-568-3685. Please include all previous replies when/if responding to this message.

Best Regards,

John S. at Bethesda Softworks Technical Support support04@bethsoft.com

-----------------------

-----Original Message-----

From: bethsoft.tech@aqinc.com [mailto:bethsoft.tech@aqinc.com]

Sent: Monday, December 29, 2008 5:10 PM

Subject: In response to your question about Fallout 3, your customer number is xxxxxxx

Hello,

Please use the steps below to record and send us the information about the current installation of DirectX on the computer. We need this detailed information in order to assist in troubleshooting the issue at hand. No personal information is contained in the report.

Windows 95/98/ME/2000/XP

- Click Start, then Run, and type in DXDIAG, then click the OK button.

- Once the DirectX Diagnostic Tool appears, click on the Save All Information button at the bottom.

- When asked to where to save the file to, click on the drop-down box next to Save in and select Desktop.

- In File Name box towards the bottom, then name DxDiag.txt should appear.

Leave this as is and click on the OK button.

- Click the Exit button to exit the DirectX Diagnostic Tool.

- On the Desktop, there should be a file name DxDiag or DxDiag.txt. If there is no file with this name, please repeat the steps above and make sure to save the file to the Desktop.

- Open this email up and click the reply button.

- Type in your response to any additional questions or information that was requested into the body of the email.

- Click the Attachment button and add the DxDiag.txt from the Desktop.

- Once the attachment has been added, click the Send button to send us this information We will reply to you shortly.

Windows Vista

If you are using the Vista desktop:

- Click on the Windows icon located by default in the lower left-hand corner of the screen.

- In the "Start Search" field, type in DxDiag.

- Press Enter. This will start the DxDiag utility.

- Once the DirectX Diagnostic Tool appears, click on the Save All Information button at the bottom.

- When asked to where to save the file to, click on the drop-down box next to Save in and select Desktop.

- In File Name box towards the bottom, then name DxDiag.txt should appear.

Leave this as is and click on the OK button.

- Click the Exit button to exit the DirectX Diagnostic Tool.

- On the Desktop, there should be a file name DxDiag or DxDiag.txt. If there is no file with this name, please repeat the steps above and make sure to save the file to the Desktop.

- Open this email up and click the reply button.

- Type in your response to any additional questions or information that was requested into the body of the email.

- Click the Attachment button and add the DxDiag.txt from the Desktop.

- Once the attachment has been added, click the Send button to send us this information We will reply to you shortly.

If you are using the ****c desktop:

- Click on the Windows icon located by default in the lower left-hand corner of the screen.

- Choose "Run"

- In the Run box, type in DxDiag

- Press Enter. This will start the DxDiag utility.

- Once the DirectX Diagnostic Tool appears, click on the Save All Information button at the bottom.

- When asked to where to save the file to, click on the drop-down box next to Save in and select Desktop.

- In File Name box towards the bottom, then name DxDiag.txt should appear.

Leave this as is and click on the OK button.

- Click the Exit button to exit the DirectX Diagnostic Tool.

- On the Desktop, there should be a file name DxDiag or DxDiag.txt. If there is no file with this name, please repeat the steps above and make sure to save the file to the Desktop.

- Open this email up and click the reply button.

- Type in your response to any additional questions or information that was requested into the body of the email.

- Click the Attachment button and add the DxDiag.txt from the Desktop.

- Once the attachment has been added, click the Send button to send us this information We will reply to you shortly.

Your customer number is xxxxxxxxx

Please refer to case #:: xxxxxxxxxx if you have any further questions.

If you need further assistance, you can also reach us online at http://support.bethsoft.com/ or our technical support staff at (410)-568-3685. Please include all previous replies when/if responding to this message.

Best Regards,

Dan W. at Bethesda Softworks Technical Support support04@bethsoft.com

-----------------------

Fallour crashes at the age 10 point in the game.. right after the point the boy says "Aw man you got a pipboy." This is also the same place that the game crashes on my other machine running a ATI X700 Vid card. All droppes back to the desktop leaving a black window over part of the desktop, with a locked up machine except for the taskmanager. Its disapointing to have spent the money on such a piece of messed up software that is so buggy it wont get past 1st base..

Any help from your end????

To: bethsoft.tech

OS::Windows Vista

ComputerManufacturer::

ComputerModel::

Processor::Xeon(PIII)

ProcessorSpeed::2.3 Ghz

RAM::4096

VideoManufacturer::ATI

VideoModel::Radeon HD 3200

3DCardManufacturer::

3DCardModel::

AudioManufacturer::Realtek

AudioModel::

CDROM::Optiarc AD 7203s

CDROMSpeed::16X

DVD::Optiarc AD 7203s

Modem::

Joystick::

Date::12/28/2008

Time::8:17:53 AM

SessionId::080305081228070178243238

strDesc::Fallour crashes at the age 10 point in the game.. right after the point the boy says "Aw man you got a pipboy." This is also the same place that the game crashes on my other machine running a ATI X700 Vid card. All droppes back to the desktop leaving a black window over part of the desktop, with a locked up machine except for the taskmanager. Its disapointing to have spent the money on such a piece of messed up software that is so buggy it wont get past 1st base..

Any help from your end????

Country::USA

-----------Attachments-------------

file://hvglobalv/Attachments/Inbound/400204237_1.txt%3C/file>

To: bethsoft.tech

Avatar image for flclempire
flclempire

4914

Forum Posts

0

Wiki Points

0

Followers

Reviews: 30

User Lists: 0

#2 flclempire
Member since 2004 • 4914 Posts
tl;dr version please :D And I'm serious :| I doubt anyone will try to find the meat of this post.
Avatar image for eddy96_1
eddy96_1

1388

Forum Posts

0

Wiki Points

0

Followers

Reviews: 2

User Lists: 0

#3 eddy96_1
Member since 2003 • 1388 Posts

have u got the latest ati drivers? even get the latest direct x drivers aswell the x700 isnt supported so it cant run on that system

ati vista 32 8.12 drivers

http://game.amd.com/us-en/drivers_catalyst.aspx?p=vista32/common-vista32

make sure u click on the first download link

direct x

http://www.microsoft.com/downloads/details.aspx?familyid=2da43d38-db71-4c1b-bc6a-9b6652cd92a3&displaylang=en

download those and see what happens

Avatar image for overratedgames
overratedgames

124

Forum Posts

0

Wiki Points

0

Followers

Reviews: 0

User Lists: 0

#4 overratedgames
Member since 2008 • 124 Posts

its because you are trying to run this game with a freaking intergrated chipset dude.

buy a damn video card

Avatar image for couly
couly

6285

Forum Posts

0

Wiki Points

0

Followers

Reviews: 18

User Lists: 0

#5 couly
Member since 2004 • 6285 Posts
yeah it's the game's fault that your system is terrible. You seem to be a kid so my advice is buy a 360 and leave the PC to the big boys.
Avatar image for Hellboard
Hellboard

2429

Forum Posts

0

Wiki Points

0

Followers

Reviews: 86

User Lists: 0

#6 Hellboard
Member since 2008 • 2429 Posts
ehmm not me, call Bethesda, and they confirm that you pc cant run it!
Avatar image for nevereathim
nevereathim

2161

Forum Posts

0

Wiki Points

0

Followers

Reviews: 2

User Lists: 0

#7 nevereathim
Member since 2006 • 2161 Posts
If you're really 10, then you shouldn't even have fallout 3
Avatar image for Treflis
Treflis

13757

Forum Posts

0

Wiki Points

0

Followers

Reviews: 0

User Lists: 0

#8 Treflis
Member since 2004 • 13757 Posts
If you're really 10, then you shouldn't even have fallout 3nevereathim
I concur.
Avatar image for Sordidus
Sordidus

2036

Forum Posts

0

Wiki Points

0

Followers

Reviews: 0

User Lists: 0

#9 Sordidus
Member since 2008 • 2036 Posts

yeah it's the game's fault that your system is terrible. You seem to be a kid so my advice is buy a 360 and leave the PC to the big boys.couly

Well, with my system, since I'm outside the Vault the game keeps crashing lol but my brother have the game on his crap laptop and it runs just fine:evil:From what I've played that game doesn't seem very good though.

Avatar image for Qixote
Qixote

10843

Forum Posts

0

Wiki Points

0

Followers

Reviews: 4

User Lists: 0

#10 Qixote
Member since 2002 • 10843 Posts
Does the original post even have any programming experience for video games to claim the coding is bad? Did you look at the source code? Really, you can't go around making these claims based on your own experience with the game.
Avatar image for Cdscottie
Cdscottie

1872

Forum Posts

0

Wiki Points

0

Followers

Reviews: 3

User Lists: 0

#11 Cdscottie
Member since 2004 • 1872 Posts
An ATI HD3200? Good luck running it with that my friend. And seriously, why is it when a person has an issue with the game due to being under the required hardware specs that the game is all of a sudden "Coded badly and buggy"?
Avatar image for ColdfireTrilogy
ColdfireTrilogy

4911

Forum Posts

0

Wiki Points

0

Followers

Reviews: 11

User Lists: 0

#12 ColdfireTrilogy
Member since 2005 • 4911 Posts

"The processor is a 1.8 Gig but you fail to realize that a quad core 1.80 GHz Performs at 4.59 GHz"

Sorry man it doesnt work that way at all, maybe you should have done a little more research in the CPU department.

Avatar image for DanielDust
DanielDust

15402

Forum Posts

0

Wiki Points

0

Followers

Reviews: 0

User Lists: 0

#13 DanielDust
Member since 2007 • 15402 Posts

"The processor is a 1.8 Gig but you fail to realize that a quad core 1.80 GHz Performs at 4.59 GHz"

Sorry man it doesnt work that way at all, maybe you should have done a little more research in the CPU department.

ColdfireTrilogy
Too much system requirements lab for some people, if i recall correctly that's what it says to most quad cores, it performs as a 4.6 ghz single core.
Avatar image for johan1986
johan1986

4764

Forum Posts

0

Wiki Points

0

Followers

Reviews: 1

User Lists: 0

#14 johan1986
Member since 2003 • 4764 Posts
remember that games for windows live can also cause problems
Avatar image for Poshkidney
Poshkidney

3803

Forum Posts

0

Wiki Points

0

Followers

Reviews: 7

User Lists: 0

#15 Poshkidney
Member since 2006 • 3803 Posts

i think they could have done betterwith getting rid of the bugs and properly improve the structure and if you think oblivion was buggy.

But this might be a bug that no one else has gotten but your using an ATI card and its really is better with an nvidia. Quiet the fanboy in me. but in the manual it does say they made it for 8 series cards and on my computer it runs quite well my computers not the best but it is good even if i'm still using a 939 processor 2 gigs of ram and an 8800gt the the most powerful out of them but it from what i paid for it is giving brilliant quality.

Avatar image for death1505921
death1505921

5260

Forum Posts

0

Wiki Points

0

Followers

Reviews: 1

User Lists: 0

#16 death1505921
Member since 2004 • 5260 Posts
So because YOUR system can't run it, their game is full of bugs? And how can you make the assumtion it's "Too buggy and full of bad coding" after you have experienced one crash? I've played and completely fallout and done the vast majority of the side quests flawlessly. Yet to have a single crash.
Avatar image for adrake4183
adrake4183

668

Forum Posts

0

Wiki Points

0

Followers

Reviews: 0

User Lists: 0

#17 adrake4183
Member since 2006 • 668 Posts
This is the sad thing about pc gaming. Specs aren't clear,. A 1.8 quad is not the same as a 2.4 dual cpu even though it seems like it should be. They support a 2900 and 3400 series chip but not a 3200 series. I understand the posters frustration. On the other hand if you have a marginal system you know you are taking a risk buying a fairly demanding game like fallout 3. Its not bethedsa's fault because they did warn you on the box albeit in small hard to understand print. And the poster says no one feels responsible when he surely is at least partly if not mostly to blame. We really need a better system to determine game stability for a given system.