Menu

#251 GPS/FMS heading in Autopilot Disappears Short Time After Take Off

Verified
nobody
Nav (28)
2011-06-05
2011-01-10
Anonymous
No

Originally created by: grg.gdsr (code.google.com)

*What steps will reproduce the problem?*
1. Start from eg, YBBN with eg, 747-200 or any plane that uses the Route Manager.
2. Set Arrival box in Route Manager to eg, YSSY.
3. Open Auto Pilot window and notice that GPS/FMS is correctly shown.
4. Take off, open Auto Pilot window again click the GPS/FMS radio button and Heading box.
5. After a very short time observing the destination (YSSY), it disappears from the HUD.

*What is the expected output? What do you see instead?.
The expected is for the arrival airport code to continue displaying on the HUD but it is replaced with (TQ). In the Auto Pilot window GPS/FMS is replaced with True Heading.
I thought at first this might be something about how it is meant to behave but it wont arrive accurately at the destination airport.

*Any output in the console (black window)?*

*What version of the product are you using (when using GIT version, please
mention date or Hudson build number)?*
cebif@cebif-desktop:/usr/share/FlightGear$ sh run_fgfs.sh --version
Processing command line arguments
FlightGear version: 2.2.0
Revision: [r0361f136fe5c81576bc426d218f4dec2366ea086]
Build-Id: none
FG_ROOT=/usr/share/FlightGear/install/fgfs/bin/../fgdata/
FG_HOME=/home/cebif/.fgfs
FG_SCENERY=/usr/share/FlightGear/install/fgfs/bin/../fgdata//Scenery:/usr/share/FlightGear/install/fgfs/bin/../fgdata//Scenery/Terrain:/usr/share/FlightGear/install/fgfs/bin/../fgdata//Scenery/Objects:
SimGear version: 2.2.0
PLIB version: 186

*What operating system and graphics card?*
Ubuntu 10.04 64bit.
Nvidia Geforce 7950GT

*Please provide any additional information below or as attachment (Avoid
expiring external links, such as to imageshack/pastebin/...).*

Discussion

  • Anonymous

    Anonymous - 2011-01-11

    Originally posted by: bre... (code.google.com)@gmail.com

    Could be related to route manager, GPS or HUD itself.

    Labels: Nav
    Cc: zakalawe

     
  • Anonymous

    Anonymous - 2011-01-27

    Originally posted by: bre... (code.google.com)@gmail.com

    Caused by a general issue with the last waypoint. For airport/runway waypoints the distance isn't checked (different to other waypoint types). The destination airport waypoint is considered done whenever the course deviates by more than 90 degrees - even if it is still far away.
    This fixes the issue for me with destination/airport waypoints:
    http://www.gitorious.org/~thorsten/fg/thorstens-flightgear/commit/a859beb0c669b07ee47aff59568150cb9db07272

    Not sure though, if the distance check was intentionally omitted.
    => James, please review. Haven't applied the patch to any official branch yet.

    Status: Triaged

     
  • Anonymous

    Anonymous - 2011-01-30

    Originally posted by: bre... (code.google.com)@gmail.com

    Fixed in "next".
    @grg.gdsr: if possible, please test if you can still reproduce the problem now.

    Status: Testing

     
  • Anonymous

    Anonymous - 2011-02-05

    Originally posted by: grg.gdsr (code.google.com)

    Yes I can still reproduce it. I updated the version yesterday; 05/02/11. One thing I noticed. Updating from last known version to properly compile all the apps, to the latest where atlas wont compile; I am left with the same user interface as last known fully compile, on first page of fgrun; FlightGear Launch Control 1.5.2. Is this now the standard or did the update not go right?
    My version info:
    cebif@cebif-desktop:/usr/share/FlightGear$ sh run_fgfs.sh --version
    Processing command line arguments
    FlightGear version: 2.2.0
    Revision: [r353cba6fcb07258d1481a31b7cd5035abe00d425]
    Build-Id: none
    FG_ROOT=/usr/share/FlightGear/install/fgfs/bin/../fgdata/
    FG_HOME=/home/cebif/.fgfs
    FG_SCENERY=/usr/share/FlightGear/install/fgfs/bin/../fgdata//Scenery:/usr/share/FlightGear/install/fgfs/bin/../fgdata//Scenery/Terrain:/usr/share/FlightGear/install/fgfs/bin/../fgdata//Scenery/Objects:
    SimGear version: 2.2.0
    PLIB version: 186

     
  • Anonymous

    Anonymous - 2011-02-05

    Originally posted by: bre... (code.google.com)@gmail.com

    grg.gdsr: The revision your using ([r353cba6fcb07258d1481a31b7cd5035abe00d425]) is from January 17th - so too old and doesn't contain the fix yet. You need to check your installation:
    Either you didn't "git pull" the latest sources for the "flightgear" repository, or compiling "fgfs" failed, or you're just executing a wrong (old) binary.

     
  • Anonymous

    Anonymous - 2011-02-05

    Originally posted by: grg.gdsr (code.google.com)

    I used this command to update:
    sh download_and_compile.sh ALL UPDATE -j 2

    I also got some errors:
    /usr/share/FlightGear/install/simgear/lib/libsgmodel.a(SGPagedLOD.o):(.rodata._ZTVN7simgear10SGPagedLODE[vtable for simgear::SGPagedLOD]+0x110): undefined reference to `osg::PagedLOD::removeExpiredChildren(double, int, std::vector<osg::ref_ptr<osg::Node>, std::allocator<osg::ref_ptr<osg::Node> > >&)'
    /usr/share/FlightGear/install/simgear/lib/libsgmodel.a(SGPagedLOD.o):(.rodata._ZTVN7simgear10SGPagedLODE[vtable for simgear::SGPagedLOD]+0x118): undefined reference to `osg::PagedLOD::releaseGLObjectsOnExpiredChildren(double, int)'
    collect2: ld returned 1 exit status
    make[2]: *** [fgrun] Error 1
    make[2]: Leaving directory `/usr/share/FlightGear/fgrun/fgrun/src'
    make[1]: *** [install] Error 2
    make[1]: Leaving directory `/usr/share/FlightGear/fgrun/fgrun/src'
    make: *** [install-recursive] Error 1
    /usr/share/FlightGear

    There might have been other errors also. Will I have to delete some or all of my present installation or source code to make it download and compile properly?
    I might try just downloading and compile run_fgfs first.

     
  • Anonymous

    Anonymous - 2011-02-05

    Originally posted by: grg.gdsr (code.google.com)

    I don't know how to make it update. I have deleted the fgfs, fgrun and atlas folders then tried to update every app in the order given on:
    http://wiki.flightgear.org/index.php/Scripted_Compilation_on_Linux_Debian/Ubuntu
    Updating most of the files individually at a time except for; FGFS, FGRUN and ATLAS that I tried to update together but still have the older version shown when I do the "sh run_fgfs.sh --version" command. So I am at a loss of what to do and how to test with the latest.

     
  • Anonymous

    Anonymous - 2011-02-06

    Originally posted by: bre... (code.google.com)@gmail.com

    In case you used the "Download_and_compile.sh" script, you may go back to the wiki and download a new revision of this script. Remove your OpenSceneGraph directory, then run the new version of "Download_and_compile.sh" again.
    (The old version of the script downloaded the latest OSG development sources, which are currently not compatible - causing the fgfs build to fail).

     
  • Anonymous

    Anonymous - 2011-02-06

    Originally posted by: grg.gdsr (code.google.com)

    I did that. I deleted the OSG folder. I replaced the script from the link on the page but it did not make a difference. I looked inside the script and it said version 1.1, the same as before.

     
  • Anonymous

    Anonymous - 2011-02-06

    Originally posted by: bre... (code.google.com)@gmail.com

    "1.1" is still the old script. "1.2" is the current script. Where did you find the link - in the wiki? All links should be updated to the new location...
    That's the new link:
    http://www.gitorious.org/fg/fgmeta/blobs/raw/master/download_and_compile.sh

     
  • Anonymous

    Anonymous - 2011-02-06

    Originally posted by: grg.gdsr (code.google.com)

    Even with the correct download_and_compile script 1.2, it wont compile properly. I noticed errors such as recursive error in fgfs and fgrun. Also errors like no compile rule. I deleted those folders but got a similar result and of course although the program runs, it still has this bug. I don't want to wipe everything from my FlightGear folder to download/compile everything again because of the meager and expensive download caps with ISP's where I live. So I am sorry someone else will have to test this.

     
  • Anonymous

    Anonymous - 2011-03-02

    Originally posted by: grg.gdsr (code.google.com)

    I tested with Revision: [r12f694f06d9f2ffabb66959bb3f055074cee9473]. The bug is no longer reproducible.

     
  • Anonymous

    Anonymous - 2011-03-03

    Originally posted by: bre... (code.google.com)@gmail.com

    (No comment was entered for this change.)

    Status: Verified

     
  • Anonymous

    Anonymous - 2011-06-05

    Originally posted by: bre... (code.google.com)@gmail.com

    (No comment was entered for this change.)

    Status: Temp

     
  • Anonymous

    Anonymous - 2011-06-05

    Originally posted by: bre... (code.google.com)@gmail.com

    (No comment was entered for this change.)

    Status: Verified

     

Log in to post a comment.

MongoDB Logo MongoDB