September 14, 201015 yr I need some major help here, Suddenly nearly all of my aircraft weighs like a ton of bricks, including all my default aircraft. It as if someone flipped a switch in FS9 and everything is 2x heavier. Even the default Jetranger won't take off.I cannot takeoff or maintain altitude on my Realair C172, the plane stalls at 70 to 75kts straight and level which is well within the green range. It's the same for almost all my other small piston-driven aircraft. The Default 737 stalls at ~185kts KIAS with flaps 15. Only my PT TU-154 and my PMDG MD-11 works OK....I think. (Not sure about the Airsimmer)Everything is in default. default ISA weather @ sea level, the planes' aircraft.cfg and .air files are in order and not overweight. I did not install anything major in the last few months, only some AI traffic. Please help!
September 14, 201015 yr Hi,Try reloading the default flight (Cessna at SeaTac) - it's in the Other category. Then try a takeoff.Hope this helps, Tom Gibson CalClassic Propliner Page
September 14, 201015 yr Author lol many thanks, it worked! I never knew the default flight file could have an effect on default flight dynamics.
September 14, 201015 yr Hello. As a first step, I would suggest this; I assume you still have the original download of the Realair C172 available or can download it again if necessary. If so, you could temporarily rename the aircraft configuration file and the airfile in the FS9 aircraft folder/ RealAirC172 folder and replace them with the corresponding files from your freshly opened zip. Start up FS9 and start a new flight to test if the problem still occurs. If it does reoccur shut down FS9 and reboot your computer ( to dump and stored variables etc. ) after restarting your computer and FS9 load the default flight which should be the stock C172 and 34R at KSEA. If you have changed the default flight to some other aircraft and location reselect the c172 and KSEA 34R and reassign it as the default flight and exit FS9. Restart FS9 and you should see the default C172 in the aircraft selection window and KSEA listed as the starting airport. Click in fly now and try a flight to test. If all goes well then the what had happened is that a stored or saved flight and the aircraft involved is storing its variables data and causing them to be used in other aircraft. Note that several payware aircraft recommend that you load the stock C172 first to clear these variables first so as to allow their new set of variables to load properly. If all goes well then try another aircraft such as the default 737 if that flies well also, then problem solved.If these steps do not fix the problem then it is safe to say it is something a little more complex and more work will need to be done. You may also wish to post your system specs, especially your OS.I hope this helps you remedy your problem or at least gets you headed towards that goal.Best regards,Mel
September 14, 201015 yr Commercial Member lol many thanks, it worked! I never knew the default flight file could have an effect on default flight dynamics.It can have a massive effect. Let's say your last flight was using a 767 (anyone's). You encountered icing while flying and accumulated 7,000lbs of ice before landing. Upon landing and parking you saved the flight. The ice buildup is now stored in that flight. If you then set that as your default flight so that the next time FS loads it's the selected flight... the aircraft is initialized with 7,000lbs of ice on it. If you then switch to an aircraft that weights 7,000lbs fully loaded on it's own... you've in fact just doubled it's weight because of the ice.This is just one of the things that can go wrong if the default flight isn't the very first thing FS loads when it starts up. Developers have been stating for years to always, always load FS with the default flight before creating a flight or loading another flight. Ed Wilson Mindstar AviationMy Playland - I69
September 15, 201015 yr Author It can have a massive effect. Let's say your last flight was using a 767 (anyone's). You encountered icing while flying and accumulated 7,000lbs of ice before landing. Upon landing and parking you saved the flight. The ice buildup is now stored in that flight. If you then set that as your default flight so that the next time FS loads it's the selected flight... the aircraft is initialized with 7,000lbs of ice on it. If you then switch to an aircraft that weights 7,000lbs fully loaded on it's own... you've in fact just doubled it's weight because of the ice.This is just one of the things that can go wrong if the default flight isn't the very first thing FS loads when it starts up. Developers have been stating for years to always, always load FS with the default flight before creating a flight or loading another flight.What I think happened was that I recently created my own custom default flight in order to create a realistic overcast effect. (i.e. Several layers of overcast at 9000ft-12000ft and 1/3 mile viz below 10000ft.) I placed my default Cessna at an airfield that is 7000ft high and saved it. This is probably above the freezing level and therefore in an icing zone.
Create an account or sign in to comment