Jump to content

amyinorbit

Members
  • Posts

    34
  • Joined

  • Last visited

  • Days Won

    1

amyinorbit last won the day on February 10 2021

amyinorbit had the most liked content!

3 Followers

About amyinorbit

  • Birthday 07/31/1993

Contact Methods

  • Website URL
    https://amyparent.com

Profile Information

  • Gender
    Female
  • Location
    Scotland, UK

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

amyinorbit's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Collaborator Rare
  • Week One Done
  • One Month Later
  • One Year In Rare

Recent Badges

21

Reputation

  1. Like Cameron said, what you get with other planes doesn't have much to do with it. The CL650 is a bit more GPU-heavy than the TBM and the Zibo. I had a M1 machine when the CL650 was in beta, and I was seeing frame rates similar to what you reported. The M1 is a best when it comes to CPU workload, but its GPU is a bit weak for the Challenger unfortunately.
  2. Yes, we are discussing the ProLine avionics suite, which is modelled in the HotStart 650. The shortcoming you brought up twice now are not with the simulation, but with the actual, real-life avionics. The aim of this add on is to accurately simulate the real avionics, so the shortcomings will not be fixed if they exist on the real unit.
  3. Like @skiselkovsaid for the other case, thats not a bug; that’s how the ProLine 21 draws course-to-fix legs. Once the plane passes 1,100ft, it will do a right-hand turn to establish on the coded course into D266N.
  4. If it has happened twice, could you please try and get a video of it? Aside from arming APPR much, much too early, I'm not sure what could cause it
  5. I cannot reproduce this even by arming approach. My only other hunch is that you accidentally hit the NAV SRC a button on the DCP, which would have caused the NAV source to switch to LOC
  6. Testing this right now, but my suspicion is that you armed APPR while on the star. If that’s the case, the FMS could have initiated a NAV-NAV transfer, thus setting the autopilot to follow the ILS rather than LNAV.
  7. Hello! Could you try an access https://aeronav.faa.gov/d-tpp/2113/xml_data/d-TPP_Metafile.xml in your browser, and see what it says? From your log it looks like there is a SSL issue when trying to get the charts list from the FAA servers.
  8. Okay folks that’s enough, stay on topic and stop with the ad hominem please.
  9. There’s a whole complex dance that the FMSs have to execute, but in normal ops the conditions are: There is a suitable (read: LOC or ILS) approach procedure linked in the flight plan that the plane is in, or that is coming up down track in your FPL; The plane is within 31nm of the approach airport
  10. Simbrief is pretty hit and miss (and “miss” more than often) when it comes to cruise levels. As Graeme mentioned, these numbers are all in the Ops Reference document that comes with the plane — use it
  11. Things you need to check before the pax will deboardm pax signs are turned off engines are shutdown beacon is off cabin door and main door open
  12. It looks like you shut down the battery master switch before the end of the APU shutdown sequence, causing the APU to go into fault mode. If you open the APU servicing panel (under the number 1 engine), you can press the RESET FAULT button and you should be good to go
  13. This issue is caused by running the APR test while the engines are not running. As mentioned by Bruno, running the test again when the engines are running will fix this
  14. As highlighted by @RP31, Cowl Anti-Ice must be on, and 2 minutes must have elapsed, for the Supplemental Ground Wing Anti ice test to complete.
×
×
  • Create New...