15-04-2006, 07:33 PM
The slew was done before the FSP was started. Basically I had a *.flt file that become incompatable with new scenery I installed because of the
starting location which crashed into a building once the flight was loaded. Basically, I slewed to a different starting location and saved a new
*.flt file. Then using the new *.flt file, I would start up FSP, set up the load, load up the passengers, taxi to the runway, and then take off. In
this most recent event, the error message occurred at about 3500 feet (not 1600 as I originally thought) after takeoff and happened shortly after I
clicked the "NAV" to follow the course.
Note, the new scenery for Oslo (ENGM) has not previously caused any problems with other flights that use that scenery. The only 2 flights that the
error occurred in were ones in which slew was used to set up a new starting position, before FSP is even used.
Last night after this error occurred, I setup a new flight completely from scratch, saved it for future use, and used FSP with no problem.
Another item of note is that these 2 flight plans were originally for use with a different aircraft, but I manually edited them to use a different
aircraft (that I own in FSP). I have done this with other flights and had no problem with FSP.
I know these types of things are hard to debug, but if or when this happens again, what kind of information can I gather that may help to resolve the
issue?
Thanks.
starting location which crashed into a building once the flight was loaded. Basically, I slewed to a different starting location and saved a new
*.flt file. Then using the new *.flt file, I would start up FSP, set up the load, load up the passengers, taxi to the runway, and then take off. In
this most recent event, the error message occurred at about 3500 feet (not 1600 as I originally thought) after takeoff and happened shortly after I
clicked the "NAV" to follow the course.
Note, the new scenery for Oslo (ENGM) has not previously caused any problems with other flights that use that scenery. The only 2 flights that the
error occurred in were ones in which slew was used to set up a new starting position, before FSP is even used.
Last night after this error occurred, I setup a new flight completely from scratch, saved it for future use, and used FSP with no problem.
Another item of note is that these 2 flight plans were originally for use with a different aircraft, but I manually edited them to use a different
aircraft (that I own in FSP). I have done this with other flights and had no problem with FSP.
I know these types of things are hard to debug, but if or when this happens again, what kind of information can I gather that may help to resolve the
issue?
Thanks.