Runtime Error

[llamedos]

Every time i do a specific flight i receive a runtime error.

Is there a fix for this, could it be caused by an addon? is it FSX or is it my PC?

I had a look at the Microsoft website but did not understand it.

[Wingo]

I had a quick look through that article, and by the sounds of it it may be a bug within FSX. Which version are you running, RTM, SP1 or Acceleration? If you have RTM (The FSX straight out of the box before SP1 was released) then i would suggest installing SP1 from fsinsider.com to try and remedy the problem. If you have SP1, wait for the SP2 download to come out and give it a go. Also, maybe wait for Nick. He may be able to shed more light on this.

[llamedos]

Thanks for the reply Wingo,

[NickN]

Install this package and try your flight again

http://www.microsoft.com/downloads/deta ... laylang=en

[llamedos]

Thanks Nick,

[llamedos]

I installed the package, same error in the same location.

[NickN]

The first order of business with that error is to make sure the C++ runtime library update is installed, as you did yesterday. If the error still persists then the issue is caused by illegal C code which is usually tied to a 3rd party AI flight plan, model or scenery element.

Your next step is to use only default aircraft for testing the flight and eliminate any/all 3rd party add-on scenery from the FSX scenery data base. Remove any add on AI flight plans so they are not scanned by the sim when it is booted. You will need to revert your install to a pure default environment and retest the flight. Once the error is gone, start adding things back in one at a time until the error appears. When it does, the last add-on installed/enabled is the culprit.

The error can be caused by an add-on plane, its flight plan .bgl or ground scenery additions.

Do not assume because an add-on is located 500 miles away in the scenery, or, because you are not booting a 3rd party aircraft for flight or use it in traffic it will not be the problem. Make sure to remove all add-ons in order to eliminate them as the reason. Unlike FS9 all SimObjects (aircraft, boats, cars, traffic files etc) are scanned when the sim is booted so you must make sure there are no 3rd party planes or traffic files in the sim before it is booted even if you are not using them to test.


EDIT: This does not mean FSX is not the issue and you may have come across an area in FSX which has an error in its default scenery. If after you have removed any/all 3rd party add-ons, and, the problem still persits but only shows in a single area flight path then it is possible it could be a code issue with FSX but usually the error is tied to something installed.

Also, make sure no aircraft add-on has replaced/added any gauges which may have replaced defaults because they are C based code too.

[llamedos]

I archived all the files with traffic.bgl in the name. This appears to have fixed the problem.

I think i will buy a payware traffic addon.

Thanks Nick.  ;)

[NickN]

Right now not many payware packages are not worth the hub-bub. I use WoAI, PAI, GA Traffic and a few others. All freeware and it takes a big chunk of time to get everything together and working so all the gates are full around the world.

The best automatic schedule maker with the most accurate gate assignment is Ultimate Traffic X but their flight models have performance and other issues. That one is the way to go in order to have the ability to easily customize the entire world with traffic and you can replace/reassign better aircraft to the UT schedules

The situation with many older FS9 models (including UT) and FSX SP2 not allowing textures to show is hitting even the payware people because not many of them are FSX compliant other than flight plans.

That will change over time. However, the thing that makes 3rd party traffic more frame rate friendly in FSX is not the models, its the lack of the gate call in the aircraft.cfg file.

You see, people assume the FSX models are what cause the default AI to exert such a high toll on frames but it is not the default models its the fact that ANY compliant aircraft in FSX should have code in the aircraft.cfg file which addresses gate/jetway animations. The toll in performance comes from the sim calculating all the AI gates at the airports 120NM around the aircraft.

So you see, once payware offerings are finally brought up to FSX specs they wont be much better on frames than the default aircraft unless the payware maker leaves out the code which is needed for jetway animations, etc.