Jump to content

Burnspot

Members
  • Content Count

    228
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

5 Neutral

About Burnspot

  • Rank
    Member

Contact Methods

  • Website URL
    http://www.burningfiles.com
  • ICQ
    0

Profile Information

  • Gender
    Male
  • Location
    North Carolina
  • Interests
    FJR1300's...

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    Other
  • Virtual Airlines
    No
  1. None that I've noticed except perhaps a slight stutter as the FCOM window opens, but it doesn't impact the flight. That's probably more as a result of my lowly system than anything else though. ;)
  2. I've been using FSCaptain with the NGX for quite awhile now and have had no problems. I don't let it do the loading, but rather "simulate" the loading while I manually set the fuel and payload to the specified amounts in the NGX CDU (these are options in FSCaptain to configure). Seems to work fine doing it's own loading also, but I prefer to manually do it. The passenger counts between the NGX's CDU and FSCaptain won't equal out though...manually loaded or otherwise (as long as the weights are good). I could have something misconfigured in the weight stuff as I'm still a relatively new FSCaptain user, but it hasn't affected anything at all...so long as I have 3 green "ready" signals in FSCaptain when I commit, it's all good. Some minor oddities I've noticed, perhaps due to possible misconfiguration on my part, is that I'll get "busted" on airspeed under 10k when it's around 251kts, plus transition altitude callouts in FSCaptain aren't matching up with what's going on in the NGX...the FO's usually very late on the call....long after I've gone to STD per the NGX's indicated altitude. Those are minor quibbles though; it's been going great otherwise.
  3. Not a pilot, so I'm probably talking out of my a$$ (by not looking it up), but I ran into this yesterday. The descent looked reasonable to me; however, the "No Descent Path..." message appeared while the route itself was not broken. IMHO, I think it comes from a couple of waypoints not having adequate spacing between them for a reasonable descent rate . I got the message after adjusting my route to fit the approach into KRDU for 23L, SBV.FRAZI. I fixed it by looking up the approach in EFB and seeing what waypoint I had deleted. Turns out I had inadvertently deleted a waypoint after the point mentioned in the FMC descent error message. Once I reinserted the waypoint, all returned to normal.
×
×
  • Create New...