Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
Collapse
Just Flight Community Forum
  1. Home
  2. Just Flight
  3. MSFS Products
  4. 146 Professional
  5. TOD/VNAV cCalculation only correct for next, acitve waypoint

TOD/VNAV cCalculation only correct for next, acitve waypoint

Scheduled Pinned Locked Moved 146 Professional
4 Posts 3 Posters 349 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • C Offline
    C Offline
    Chrjs
    wrote on last edited by
    #1

    HI,
    overall a great update. I noticed a problem with the VNAV/TOD calculation of the UNS. It only calculates the descent rate and TOD of the next, currently active waypoint in your flightplan. Within the menu you can chose another waypoint for the calculation (for example another, later waypoint on the STAR for your descent calculation), this waypoint is even displayed as the current calculated descent, but the calculation is actually for the next (here invisible) next active waypoint. The calculation just restarts when you have overflown this next waypoint in line messing up your initial descent. I'm sure a fix shouldn't be too hard. Kind regards
    chris

    MarkM 1 Reply Last reply
    2
    • C Chrjs

      HI,
      overall a great update. I noticed a problem with the VNAV/TOD calculation of the UNS. It only calculates the descent rate and TOD of the next, currently active waypoint in your flightplan. Within the menu you can chose another waypoint for the calculation (for example another, later waypoint on the STAR for your descent calculation), this waypoint is even displayed as the current calculated descent, but the calculation is actually for the next (here invisible) next active waypoint. The calculation just restarts when you have overflown this next waypoint in line messing up your initial descent. I'm sure a fix shouldn't be too hard. Kind regards
      chris

      MarkM Offline
      MarkM Offline
      Mark
      JF Staff
      wrote on last edited by
      #2

      @Chrjs Thank you for reporting this. We have passed this onto the UNS-1 development team.

      Mark - Just Flight

      Just Flight Development Assistant

      1 Reply Last reply
      0
      • F Offline
        F Offline
        falcon71
        wrote on last edited by
        #3

        I have just encountered the same issue.
        I flew to EINN via the TIPUR 2D arrival. I manually set the VNAV to waypoint to GILOG. However, the distance calculation was still to TIPUR and the altitude calculation was to 6000ft:
        before TIPUR
        Passing TIPUR, the calculations were now correct to GILOG:
        after TIPUR

        1 Reply Last reply
        0
        • F Offline
          F Offline
          falcon71
          wrote on last edited by
          #4

          I tried it again with the latest update and I can confirm, that v0.2.1 fixed this issue. Thank you!

          1 Reply Last reply
          2
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • Users