Hi Cray,

 

Actually you shouldn't.  It looks like HP threw all kinds of "trash-ware" on your system to make sure a lot of their programs were running every time you start up Windows.  I see nothing in those two pages of startup programs that should prohibit access to the Internet or that should stop you from running your system.  All of these startup programs are destroying your computer by taking up unnecessary resources.  Carbonite is a backup program that constantly backups changed files and folders to the Internet.  A major resource hog.  It's something that could be run maybe once or twice a week when you are doing nothing.  McAfee Security starts up so it can constantly be looking for updates and maybe it's also tracking what you're doing.  PictureMove by HP is constantly being loaded so when you want to move a pictures (I'm guessing here), you can. The hpwuSchd is something that loads every time I guess to make sure it checks to update your schedule.  You have McAfee, Norton, and a program called VProtect watching your system and browsing.  I see you have hpwuSchd checked twice and AOL Service too.  Anyway, most startup programs are not needed.  I have all of mine disabled except I have a desktop program from Bing that downloads a new background theme every day when I first turn on my computer.  Here's more info on the Startup Program issues - http://www.howtogeek.com/74523/how-to-disable-startup-programs-in-windows/.

 

Best regards,

Jim

Jim,

 

After two weeks of tweeking and adjustments, plus I disabled about 5 items in the start up programs,  i am going to do a test flight today with QW 757 from New York to San Francisco.  If the fatal error does show up,  I guess i will need to default FSX and start over, even if I lose all the liveries.  I will just start from scratch.  Thanks for all your help on this issue.

 

Sincerely,

Cray

Good luck Cray. 

 

Best regards,

Jim

Jim,

 

I was able to successfully fly from KJFK to KSFO without a fatal error. There was on point over Utah that it did freeze, but I just waited.  That is nothing new.  In the past when it freezes and i clicked the frozen FSX screen, it would turn a transparent grey and the hour glass would show.  I would sometimes have to wait about 5 minutes, but I did not do that this time in case it caused a fatal error.   I will next test the 767 and 747 when I have the time.  I don't get to flight simulate as much as I would like.

 

I am having problems with KFSO.  When I was over the San Francisco bay area, the frame rates would start to go bad and when I was on final approach for KSFO, it was terrible as though I was using a very taxing add on airport.  I almost crashed landed because of it.   I was using the default airport.  Usually it is smooth.  Also, I am having problems the airport itself.  Grass is on the runways again on 28L and 28R.  I had the Mesh setting set at 76.  Also, the terminal building details is really bad and some blue transparent color shows at the bottom and you can see the other side of the terminal. I adjusted the settings and even set the default scenery settings without luck.  I also completely deleted the Flightbeam KSFO addon I had from the scenery library and restarted FSX, but that did not help either .  Do you have any Idea what the problem may be?   When I was trying to adjust the settings at the end of the flight, the fatal error came on. 

 

Sincerely,

Cray

Here is another view of KSFO.  This Mesh setting is at the FSX default 38.  In order to clear the runway of grass, it has to be set at 152.  but it does not fix the terminal issue of that blue transparency and lack of detail on terminal B.

 

 

Grass is on the runways again on 28L and 28R.

 

You must have another mesh installed, like FS Genesis or FS Global.  Maybe another AFCAD (some AI Programs add AFCAD so their AI aircraft can take off and land properly).  If you have the default FSX being rendered, it will not do this. 

 

The transparent buildings may be due to fsx having issues rendering because of lack of sufficient resources.  If the textures are not showing then something is corrupt in your installation.

 

Best regards,

Jim

Jim,

 

That is what is so puzzling.  It is the FSX default airport that is a mess.  I don't have FS Genesis or GS Global.  I have had UT2 for 2 years now without this problem.  I wonder if that add on airport I had anything to do with this and somehow corrupted the default airport, even it is completely deleted from FSX?

 

Sincerely,
Cray

Jim,

 

That is what is so puzzling.  It is the FSX default airport that is a mess.  I don't have FS Genesis or GS Global.  I have had UT2 for 2 years now without this problem.  I wonder if that add on airport I had anything to do with this and somehow corrupted the default airport, even it is completely deleted from FSX?

 

Sincerely,

Cray

Hi Cray,

 

That would be impossible.  FlightBeam scenery/textures are located in one folder for KSFO.  Even if you didn't delete FlightBeam's KSFO and just disabled it, it would not affect the default KSFO scenery.  UT2 is the only suspect I can see now as that was installed AFTER the default.

 

For your virtual memory (Page File) settings, do you have "system managed size" for all drives that you have fsx and fsx addons installed on?  If you are not familiar on how to check your virtual memory/page file, click on the Start button and in the search box type virtual memory then look up in the menu and click on How to Change Virtual Memory Settings.

 

Best regards,

Jim

Jim,

 

I checked the Windows 7 help program page on changing virtual memory but change it from what to what?  It is a bit confusing.

 

Do you know if SceneryConfigEDitorinstaller1.1.0.exe might fix the problem?  I don't know if it for the type of problem I have.

 

Sincerely,

Cray

 

 

I checked the Windows 7 help program page on changing virtual memory but change it from what to what? It is a bit confusing.

 

Okay.  If you haven't gone there that's good as the default is system managed size for all drives.  Some people set their min/max page files and that can sometimes cause problems if not done correctly.  I just wanted to make sure you had it on and it was set to system managed size.

 

The SceneryConfigEditor only manages your scenery.cfg (the working one).  If it finds errors it will tell you and offer to fix the problem.  It does not look for duplicate airports you might have installed on your system.  There's another program that looks for duplicate AFCAD's at airports called Airport Scanner - http://www.fsdeveloper.com/forum/showthread.php?t=229564.

 

I am shocked you have not found a solution yet.  If this doesn't work then I strongly suggest completely uninstalling and reinstalling FSX - http://support.precisionmanuals.com/KB/a87/how-to-uninstall-and-reinstall-fsx.aspx.

 

Best regards,

Jim

Jim,

 

It is becoming overwhelming with all the problems I am coming across. It seems to be one problem after another.  The latest is that all the default airports have terrible frame rates as though they are taxing fps add-on airports.  After a month of trouble shooting,  I guess the only thing to do is to re-install, even though I will lose so many add on accessories.  I think for now I will just quit flight simulating and perhaps if I feel up to it in the future I may try and re-install.  The only main problem is trying to get back all my costly add-ons.  it will take weeks alone trying to get everything back to the way it was before all these problems took effect, let alone all the various fixes and tweeking I had to do over those two years.  I do appreciate all the help you did provide.  It is unfortunate I could not get my FSX problems resolved.  I will miss flight simulating and did very much enjoy it, but that's just the way it goes.

 

Sincerely,
Cray

Hi Cray,

 

Sorry to see you go.  You have a lot of "bloatware" installed on your system and it is all taking up valuable resources that could be used for flight simming.  I think your only solution is to reinstall Windows and then FSX.  You won't have the bloatware but you'll be able to use FSX.  Wish I could help you further but I'm totally at the end of any additional suggestions.

 

Best regards,

Jim

Jim,

 

For the past two weeks I have been doing some test flights after 3 months hiatus from flight simulating.  I flew QW757 on some 1 or 2 hour domestic routes and the Level-D 767 from Seattle to Paris without any fatal errors after 11 hour flight. (I was certain the fatal error would crop up for such a long flight)  It would freeze up for perhaps on two occasions for a few minutes while en-route on all the flights (And I was holding my breath that the Fatal Error would not Pop up) but fortunately, the flight would resume, as long as I did not click on the screen or try anything else.  I dis-installed some of the airport add-ons as well.  So far, so good.   I still have not tested the PMDG 747 yet where the original fatal errors started.  The 767 at that time also had fatal errors, but not this time.   The last fatal error happened last week was when I was trying an airport add on demo flight with my 767 and when I was departing the gate, the fatal error showed up.  But fortunately no other type of fatal errors has occurred so far.  The only problem, but not really a big deal is that the frame rates are poor on the default airports where I dis-installed the add-on airports when before I had the add ons those default airports were fine.  It is as though the add-ons contaminated the default airports somehow. Really strange.  I also noticed that 777 is finally out, but unfortunately that aircraft on my computer is out of the question because based on the system requirements, it would be a frame rate killer on my computer.  I will be just grateful when I test the 747, and get good results without any fatal errors.  

 

 

 

 

Cray

 

 

The only problem, but not really a big deal is that the frame rates are poor on the default airports where I dis-installed the add-on airports when before I had the add ons those default airports were fine. It is as though the add-ons contaminated the default airports somehow. Really strange. I also noticed that 777 is finally out, but unfortunately that aircraft on my computer is out of the question because based on the system requirements, it would be a frame rate killer on my computer. I will be just grateful when I test the 747, and get good results without any fatal errors.

 

Glad to hear things are going better for you Cray.  Even with my powerful system I run into glitches here and there so don't expect perfection.  As I have stated several times in other posts, you install FSX, run it with the default settings, and you have extremely high fps.  Same goes after one installs Acceleration or SP2.  Great fps!  Then, you install addons and "tweak" your fsx.cfg and display drivers for your video card and suddenly the fps start to drop.  So, with most addons (not all), suspect your tweaking.  Tweaking works for many but not for all as all systems and expectations are different.  That's why I shy away from tweaking.  If you have a decent system, I don't think you are going to get much more out of it with a tweak.  I wish there was a "holy grail" tweak that works perfectly for everyone but computers do not work that way.

 

You really do not need to uninstall any airport addons as disabling them in the Scenery Library will prevent them from loading.

 

When you install the PMDG 747, check out the PMDG Setup in the FMC Menu.  They have options for getting better fps.  Those might work better for you but you'll have less eye-candy.  You might think about getting an computer upgrade soon as I heard PMDG will be releasing the upgraded version of the 747 soon.  The 777 is absolutely stunning but it's no fun if you cannot run it with all the eye-candy.

 

Thanks for the update.  Sounds like progress is being made! 

 

Best regards,

Jim