Menu
▾
▴
#154 After aircraft crash at airport then start aircraft in air: no scenery rendered and altitude uncontrolled..
Fixed
nobody
None
2011-06-05
2010-08-17
Anonymous
No
Originally created by: grg.gdsr (code.google.com)
What steps will reproduce the problem?
1. Crash the airplane at KGLS. (might be at other airports too)
2. Go to Location, "Position Aircraft (in air)
3. Check airport; KGLS, Runway; default, Distance; 10nm, Altitude; 3000ft, Airspeed; 270kt, leave other boxes blank.
5. In Autopilot, Route Manager, delete KGLS in departure box, Arrival; KGLS.
6. Click Activate.
7. Press key F11, click True Heading, Heading Control. Leave others unselected.
8. Close Autopilot Settings.
9. Click OK in Location (in air).
What is the expected output?
The expected is to see scenery from cockpit veiw position. Also I don't know if this comes under another bug but altitude should be controllable with the mouse.
What do you see instead?
No scenery but water. Also the altitude starts slowly increasing and cannot be controlled.
What version of the product are you using?
FlightGear 2.0.0-2
On what operating system?
Ubuntu 10.04
Please provide any additional information below.
I don't know if this is relevant but as I was about to touchdown on the runway (before crashing at KGLS), it appeared like low cloud was near the runway but it was an illusion it was really no scenery, not even any water and I could see scenery elsewhere in the distance. This caused me to think I needed to go still lower but was in reallity near the ground; the reason why I crashed in first place.
I was flying with a A320-House but probably reproducible with other aircraft.
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: grg.gdsr (code.google.com)
It looks like this is not reproducible. It might only happen rearly. I tried it again in a 787 and a A380-House.
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: zakalawe@mac.com
(No comment was entered for this change.)
Status: Testing
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: gijsrooy
We cannot test this currently (due to bug #204), but I don't remember seeing this behaviour before. Even grg.gdsr considers it as not reproducible, so maybe it was just a once-in-a-lifetime problem...
Related
Tickets:
#204View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
Likely fixed by the NaN fixes. Need a new report otherwise.
Status: Fixed
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
(No comment was entered for this change.)
Status: Temp
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
(No comment was entered for this change.)
Status: Fixed