I went to check to see what more can be done but that Fatal error keeps coming back.

I guess there is not much else that can be done.

Hi Cray,

 

What you have to look for is another AFCAD that might be trumping out the defaults rendition of KSFO.  Did you put the KSFO scenery into the Addon Scenery folder?  If so, there could still be a .bgl in their that is trumping out the default.  In my commercial AI program (MyTrafficX), there is a scenery folder in the MyTrafficX folder that has been activated in the Scenery Library.  This scenery folder contains AFCAD for many airports in the world so that the AI in this program can land and take off.  So, if MyTrafficX were located at the top of the Scenery Library, it would trump out all of the airports installed below it unless the person went into the MyTrafficX folder and deleted that airport.  I owned UT2 but decided to go with MyTrafficX so not sure if this is the case with UT2 too.  That's why I brought it up. 

 

Sorry I cannot take care of your problems uploading pictures.  You can only continue to try uploading.  I use OZx Image Hosting - http://fsfiles.org/flightsimshotsv2/.  It's freeware unless you want to give them a donation managed by FlightSim.com.  One good thing about using that site is that there are no restrictions on size like there is here in AVSIM.  You just upload the photo there and it will provide a link (BBCode) that you copy then paste into your post here.

 

You might also look in your Addon Scenery folder for a scenery.dat file and delete it. 

 

Best regards,

Jim

Jim,

 

I don't know what an AFCAD is and how to trouble shoot something like that. I will probably just delete the KSFO addon altogether from my computer even though it is disabled in FSX.   I will just take the dollar loss since I can't use it anyway because of the poor frame rates. I am content with the default airport.  I still can't fix the Fatal Error issue.

Cray

So, removing or deleting the KSFO addon fixed the problem?  If you have an addon scenery in your addon folder, problems like yours could occur.  This is why I set up a KSFO folder, then, under that I set up a Scenery folder.  I then place the KSFO files into the Scenery folder then go to the Scenery Library and connect the KSFO folder.  This way I can put the KSFO or any addon scenery on any HDD and I can move the scenery up and down in the Scenery Library without any problems. 

 

What is the fatal error issue?  I thought you had fixed this problem.  Didn't you rename your fsx.cfg and restart FSX and let fsx rebuild?  It will not harm any of your programs other than you might have to place the UT2 entry in the Main section of the Fsx.cfg.  Other than that, your aircraft and all of your scenery you simply have to trust again and the entries will go into the Trust section of the new Fsx.cfg.  You will also have to enter highmemfix=1 in the Graphics section of the Fsx.cfg too but that's it.  You will have a whole new fresh FSX that you can begin tweaking again because something went amiss with your current fsx.cfg.

 

Your solution if you do not want to do the above is to completely uninstall/reinstall FSX (and I would recommend a clean install of Windows too).  An excellent guide for uninstalling FSX (if you are not reinstalling Windows) is here - http://support.precisionmanuals.com/KB/a87/how-to-uninstall-and-reinstall-fsx.aspx.

 

Jim

Jim,

Thanks for the help but this is all over my head.  I am not a software person at all.  I thought I had the fatal error fixed but it came back 15 minutes later, unlike the first time it would show up about 5 minutes after starting FSX.  I may have to give up flight simulating.

 

Cray

Jim,

 

See my post #28 regarding the re-install issue I had.

Cray

Jim,

 

I deleted the the KSFO but was unable to check FSX because the fatal error is back after a few minutes.

 

Cray

I was able to get back into FSX and check KSFO runway after deleting the add on from my file,  but the grass is still on the runway in the default.  I could not go further because the fatal error came back.  It comes back again about 3 minutes after getting in FSX.

Jim,

 

I went into the the scenery library in FSX and deleted the KSFO addon also.  I quickly checked the runway before the fatal error showed up the grass is now gone.

Cray

Jim,

 

I went ahead and copied the original FSX.CFG file (just in case) and retitled the original FSX.CFG file to FSX.orig.  I booted up FSX and it did what you said, but I lost all my add on airline liveries, for which I had many,  and UT2 was not showing up.  Also,  the screen was stretched full screen, stretching all the scenery and aircraft and was unable to minimize it where I had about 1 inch on each side of the screen. I brought back the original file and replaced the FSX.orig file.   I did check again for the grass covering part of Runway 28L and it was still there covering a small portion of the runway.  I was hoping perhaps it would go away.  I tried searching for what would cause that in FSX airport default.  I wonder if it had to do with the airport add on after I disabled it?

 

 

See my post #28 regarding the re-install issue I had.

The screen was stretched full screen because the Fsx.cfg is being rebuilt and it comes up with a default resolution.  Once you get on the startup page and click on Settings/Customize, you can change the resolution.  Rebuilding your FSX.cfg is like reinstalling FSX but it is the only file that is modified during the rebuild process.  We are trying to investigate possible causes for your fatal errors.  If it doesn't fix the problem, then you can simply go back and rename the fsx.orig back to fsx.cfg and we are back to square one again.  But, if it does work, then there was an issue with your Fsx.cfg and you will know what caused the problem.

 

Glad you were able to get rid of the KSFO anomalies!!

 

Best regards,

Jim

Your problem only occurs with the PMDG747-8.  What about the PMDG747 as that has to be installed too?  It may be a registration problem. 

 

The API.dll crash indicates something is taking up a lot of resources and you are nearing getting an out-of-memory error message.  If the product is having a hard time verifying registration, that might be the issue.  It could also be a problem with any repaints you might have added to the product.  Sometimes it is best to simply uninstall the both the 747 and the 747-8 and try reinstalling again (after running fsx at least once after everything is uninstalled).

 

Best regards,

Jim

Jim,

Thank you for all the help.  I found out the fatal error is also happening to Level D 767,not just the 747.   I had the PMDG 747-400 and 8 and Level D 767 for about 2 years now without the fatal error problems.  It just came up suddenly last week.  I have not added any liveries for several months.  The last add on was the GSX Ground services about a week before the fatal errors started.  But the fatal errors did not start right then.  I did manage two flights with QW 757 a week before the fatal errors started.  The fatal errors do start up now even if I don't use GSX ground services.  At first I thought that GSX may be causing the fatal errors.  I sure wish there was a "Geek Squad" for FSX that can have remote access to fix problems.

 

Attached is a better screenshot of the error area.

 

Cray

screen shot

Here is the latest fatal error:

Hi Cray,

Yes, the same faulting module is causing your crash and the Exception Code 005, Memory_Access_Violation is still showing up.  There is no known fix.  The api.dll manages memory and other functions for a software program.  The PMDG747 and the LevelD 767 use more resources to run in FSX as they are more detailed.  Don't know what else to say other than maybe you should upgrade your computer? Evidently your system is not capable of running fsx detailed addons.

 

Best regards,

Jim

 

Did you install the Heap Limitation fix?  It will give your system more memory to breathe.

Jim,

 

I did install the Heap limitiation a few days ago, and upgrading my computer is out of the question.  It is strange after three years of simulating this fatal error suddenly shows up even when I had the 747 an 767 for two years without problems.  I guess my flight simulating days are over.  I will just need to get use to that fact.   Thank you for the help you did provide me.  I will miss flght simulation greatly.

 

Sincerely,
Cray

Jim,

 

When you mentioned "upgrading my computer", did you mean purchase a new computer?  That I cannot do.  I checked my computers memory and I have 6.00 GB of space with 5.74 available.  I still don't understand why I would be short on memory when using the 767 or 747 when I had been using them for 2 years now.  I guess as you stated, it is not a fixable problem for whatever it is.

 

Sincerely,
Cay