Flight Simulator X Deluxe issues...Please help!

[mcramer6]

Hello all, recently i loaded flight simulator x deluxe onto my computer and it works great except every time i go to do a mission and click "go to briefing". A box pops up and says a fatal error has occured. It is really annoying. I have reinstalled the game and i have even added service packs one and two.

[xabzxjaffx]

Hi i was wondering if you sorted the issue and if so how? as im having problams installing the game as half way through installation an error message 1305 comes up....it be a possible link???

[mimo2005]

Originally Posted by xabzxjaffx

Hi i was wondering if you sorted the issue and if so how? as im having problams installing the game as half way through installation an error message 1305 comes up....it be a possible link???

http://support.microsoft.com/kb/873281

Could be a scratched cd?

[scilento]

hi all, I too having the same error message as " mcramer6" is having, anyone know whats up... Everything else works fine...

[xabzxjaffx]

Hi There

I was wondering if anyone knew if the FSX Deluxe Edition was compitable with Windows Vista as ive tried it with several Computers and half way through loading an Erorr 1301 message comes up and the Intallation is Aborted, and i cant seem to rectify the matter no matter what i try.

[Mike1H]

Hi Folks, Have a read of this it might give you a clue.

http://msdn.microsoft.com/en-us/libr...35(VS.85).aspx

[Sven2157]

Originally Posted by mimo2005

http://support.microsoft.com/kb/873281

Could be a scratched cd?

FSX does not require the CD to be in the drive when the game launches.

Give me a couple minutes guys and I will look into this for you...


Sven2157

[Sven2157]

Originally Posted by xabzxjaffx

Hi There

I was wondering if anyone knew if the FSX Deluxe Edition was compitable with Windows Vista as ive tried it with several Computers and half way through loading an Erorr 1301 message comes up and the Intallation is Aborted, and i cant seem to rectify the matter no matter what i try.

Microsoft Flight Simulator X (or 10), was deisgned SOLELY for Vista, at the beginning. People complained, so the ACES team delayed the release date to make it compatible with XP.

Have you already installed it? Is the "loading" when you try and launch the game or setup.exe?

[Sven2157]

Originally Posted by mcramer6

Hello all, recently i loaded flight simulator x deluxe onto my computer and it works great except every time i go to do a mission and click "go to briefing". A box pops up and says a fatal error has occured. It is really annoying. I have reinstalled the game and i have even added service packs one and two.

Originally Posted by xabzxjaffx

Hi i was wondering if you sorted the issue and if so how? as im having problams installing the game as half way through installation an error message 1305 comes up....it be a possible link???

Originally Posted by scilento

hi all, I too having the same error message as " mcramer6" is having, anyone know whats up... Everything else works fine...

Try this:

1. - Right-Click your Dektop..?..Choose "New"..>.."Folder". Call it whatever you like!

2. - Insert your DVD into your Drive. When the Autorun comes up cancel it.

3.- Double click Computer/My computer. When the Windows Explorer window comes up, navigate to your DVD Drive. Click ONCE on the drive letter to "Highlight" it and display the contents of the disk in the Right Window Pane.

4. - Click ONCE on ANY folder or file in the right window pane, Hit "CTRL+'A'" to select ALL. Now Copy ALL These files to the New Folder.

5. - Repeat steps 2 - 4 for the second disk. If the COPY procedure asks about duplicate files, choose "OVERWRITE EXISTING FILE".

6. - Now, go into that folder and locate the "Setup.exe"/"Setup" icon.

7. - Righ-Click this and choose "Run as Adminstrator" (Vista) and "Run As..." in XP. (When the "Run As..." window opens choose the administrator account.)

It sounds to me as if the program is running into security issues with certain files. This will also solve any "SCRATCHED" disk issues, as it will read straight from your hard drive. If there are any scratches on the disk, preventing the reading of the file, then you will be notified when you try copy from the disks to the folder.

Let me know if this helps...

Sven2157

[Sven2157]

Ok.....

So after researching a bit with Google, I have noticed this is a new problem. It has to do with the installation of the .NET Framework 3.5 Update and Visual Studio; both Express and the FUll version. I have both, the .NET 3.5 Framework and BOTH the Express and Full Visual Studio, on my computer.

I started my FSX, selected a mission, clicked "Go To Briefing", and BAM! "A fatal error occurred."

Now, this is one of the features I LOVE about VIsta. When that window appears there is a little button with a down arrow. Next to it says "View problem details". When you click that it shows the error report.

This is where the beauty of Vista is! In the list look at, approximately, the 5th "Problem signature" down. It is named, "Fault Module Name:". To the right, it shows EXACTLY where the program failed! Mine says, "MFC80.DLL".



Start FSX, select a mision, click the GTB button, when the fatal occurs, click that details button and view the Fault Module. Post is here, or see the link below...

Go here to the Microsoft support page for the Hotfix for your Fault Module, named in the Problem Details.

Actually, let me try this first, and I will let ya'll if it works....

Sven2157

[Sven2157]

Here is some additional information, when you have Visual Studio installed..

"You create a Microsoft Foundation Classes (MFC) application in Microsoft Visual Studio 2005 Service Pack 1 (SP1). The MFC application contains an ActiveX control inside a Tab control. When you run this application, the application may crash. Additionally, you may receive an access violation error message in the HandleInitDialog function in the Dlgcore.cpp file."

The rest of this article can be found here.

Sven2157

[Sven2157]

OK?....

This is pretty lame, I have to call Micro-SQUISH, to get the hotfix!

So I will do that in the next couple minutes. Once I have it, I will try FSX again, and post back.....

Sven2157

[Sven2157]

GOOD NEWS!

First of all, sorry it took so long to get back with everyone on this issue! Now...

IT WORKED!

As I have stated above, I am running Visual Studio 2005 and Visual Studio 2008 Express editions. I too, had the "FATAL ERROR" when trying to go to the briefing of the FSX missions.

This is caused by the .NET Framework 3.5 SP1 Update from Microsoft. Well, what is happening?... Good Question!

The original MFC80.DLL that FSX was built with, contains ActiveX Control features that are "bumping heads" with the newest version of the MFC80.dll. When you click the "Go to Briefing" button in FSX, the MFC80.dll tries to call the .NET Framework ActiveX controls, so you may maneuver through the different tabs for the mission. However, the newest version of the MFC80.DLL is not compatible with the older version. Thus returning a "A fatal error has occurred."

What the hell does ALL that mean? That means look below and get the fix!

Though this is related to .NET Framework 3.5 SP1, it is advised that you leave this installed, and resolve the issue with one of the simple solutions below!

FOR VISUAL STUDIO, ANY EDITION, USERS

Unfortunately you have to call Microsoft, 1-800-Microsoft, to obtain the hotfix for your FATAL. Tell them it is in reference to "Article KB958036". They will email you the fix; it took about 5 minutes for me.

I cannot post the fix here for several reasons: First, the hotfix is PASSWORD protected, so I don't want to break any laws that may be associated with M$ and the fix. Secondly, I use Vista Ultimate SP1, I have 2 versions of Visual Studio on my PC, etc, etc. So our systems may require a different version of the hotfix.

FOR ALL OTHER USERS WITH THE .NET FRAMEWORK 3.5 SP1

You can download the updated version of the Visual C++ Redistributable from HERE. This is in reference to "Article KB961894".

Hope this helps all...

Sven2157

[barrob326]

Originally Posted by Sven2157

GOOD NEWS!

First of all, sorry it took so long to get back with everyone on this issue! Now...

IT WORKED!

As I have stated above, I am running Visual Studio 2005 and Visual Studio 2008 Express editions. I too, had the "FATAL ERROR" when trying to go to the briefing of the FSX missions.

This is caused by the .NET Framework 3.5 SP1 Update from Microsoft. Well, what is happening?... Good Question!

The original MFC80.DLL that FSX was built with, contains ActiveX Control features that are "bumping heads" with the newest version of the MFC80.dll. When you click the "Go to Briefing" button in FSX, the MFC80.dll tries to call the .NET Framework ActiveX controls, so you may maneuver through the different tabs for the mission. However, the newest version of the MFC80.DLL is not compatible with the older version. Thus returning a "A fatal error has occurred."

What the hell does ALL that mean? That means look below and get the fix!

Though this is related to .NET Framework 3.5 SP1, it is advised that you leave this installed, and resolve the issue with one of the simple solutions below!

FOR VISUAL STUDIO, ANY EDITION, USERS

Unfortunately you have to call Microsoft, 1-800-Microsoft, to obtain the hotfix for your FATAL. Tell them it is in reference to "Article KB958036". They will email you the fix; it took about 5 minutes for me.

I cannot post the fix here for several reasons: First, the hotfix is PASSWORD protected, so I don't want to break any laws that may be associated with M$ and the fix. Secondly, I use Vista Ultimate SP1, I have 2 versions of Visual Studio on my PC, etc, etc. So our systems may require a different version of the hotfix.

FOR ALL OTHER USERS WITH THE .NET FRAMEWORK 3.5 SP1

You can download the updated version of the Visual C++ Redistributable from HERE. This is in reference to "Article KB961894".

Hope this helps all...

Sven2157

Thank You this is exactly what is happening to me, and I have been beating my head against the wall about it. Microsoft is running me in circles as well even with the KB you reference above. Would it be possible to get you Case # so I can point them at that?

[5NIPER_WOLF]

Dang, Sven, excellent work, seriously, I was thinking a corrupted install.... while I made my own hotfix for my version of the game (that worked) this looks awesome, I am bookmarking this.

[patmrotch]

I tried all of this multiple ways. Still getting the Fatal Error when I hit GTB. I'm starting to loose my patients, going on the 6th install. Here's the error I'm getting.

Problem signature:
Problem Event Name: APPCRASH
Application Name: fsx.exe
Application Version: 10.0.61637.0
Application Timestamp: 46fadb14
Fault Module Name: MFC80.DLL
Fault Module Version: 8.0.50727.922
Fault Module Timestamp: 46ca5b7f
Exception Code: c0000005
Exception Offset: 0004c0d3
OS Version: 6.0.6002.2.2.0.256.1
Locale ID: 1033

Additional information about the problem:
LCID: 1033

Read our privacy statement:
http://go.microsoft.com/fwlink/?link...3&clcid=0x0409

[barrob326]

Originally Posted by patmrotch

I tried all of this multiple ways. Still getting the Fatal Error when I hit GTB. I'm starting to loose my patients, going on the 6th install. Here's the error I'm getting.

Problem signature:
Problem Event Name: APPCRASH
Application Name: fsx.exe
Application Version: 10.0.61637.0
Application Timestamp: 46fadb14
Fault Module Name: MFC80.DLL
Fault Module Version: 8.0.50727.922
Fault Module Timestamp: 46ca5b7f
Exception Code: c0000005
Exception Offset: 0004c0d3
OS Version: 6.0.6002.2.2.0.256.1
Locale ID: 1033

Additional information about the problem:
LCID: 1033

Read our privacy statement:
http://go.microsoft.com/fwlink/?link...3&clcid=0x0409

I was not having the exact same problem as you but my problem was caused after I did the FS install. It seems FS is using some controls that when updated by new installs are no longer compatible. If you have .NET 2008 or SQL Server 2008 installed (or any other newer MS app) then that could be causing your problem. I had to uninstall .NET and SQL 2008 to make mine work. I went to SQL 2005 and that solved everything. I am really considering using VM's for some of this stuff to keep my core install clean so I dont have these issues.