Jump to content

JoshF

Moderator
  • Posts

    1330
  • Joined

  • Last visited

  • Days Won

    15

Everything posted by JoshF

  1. Sure, Speed: - pull: L:INI_FCU_SELECTED_SPEED_BUTTON - push: L:INI_FCU_MANAGED_SPEED_BUTTON Alt: - pull: L:INI_ALTITUDE_PULL_COMMAND - push: L:INI_ALTITUDE_PUSH_COMMAND Heading: - pull: L:INI_FCU_SELECTED_HEADING_BUTTON - push: L:INI_FCU_SYNC_HEADING_BUTTON V/S: - pull: L:AP9_BUTTON
  2. @B320Max8 hi, is this still an issue?
  3. @Philipp20 @aviator64 Hi, can I ask which B Events are you trying to use that are now not working? I can provide you with the relevant L Vars instead 🙂
  4. JoshF

    A320Neo

    Thanks both! Going by what Jorg said yesterday it will indeed not make a beta flighting; but its not long now until SU15 full release where we can all enjoy the neo V2 🙂
  5. Additionally all here please confirm which axis binding you're using in the sim? Regular Throttle Axis, or Throttle Axis (0-100%)?
  6. How is your Bravo set up? I'm using one and haven't seen this
  7. Hi all, thanks for bringing this to our attention, it should be resolved now
  8. Hi all, we've had reports this should be fixed in SU12 and A310 V 1.1.9, please try again and let us know
  9. Hi all, we have reports that the uplink via Simbrief/ACARS issue has been fixed with SU12 and V 1.1.9 of the A310, please try it again and let us know
  10. Hi, we have this logged internally but for now, this is not something we can fix as the default pilot and passenger models do not disappear in the default aircraft either. Once this changes in the core of the sim, it should automatically apply to the Taifun too.
  11. Hi folks, thanks for getting in touch. This kind of thing is quite nuanced to balance as we're dealing with a myriad of variables here; Simbrief's data and calculations, our data and calculations; winds in the sim maybe not matching the predicted as closely as expected; cost indexes; procedural approaches adding more burn; the A310's notoriously problematic VNAV (IRL). The data we have provided for the profile is the same as that in our manual, which is what we use for our calculations in the sim. Having just performed a flight, I landed with 800 kg less than planned on Simbrief; however this is including what appeared to be several wind shifts at cruise in the sim, and following the full procedural approach to the ILS, which is not factored into Simbrief's calculations.
  12. In that case please try with it unplugged, see if that's causing the issue
  13. Hi Markus, do you have any flight control hardware? Throttle, yoke etc?
  14. Hi! There should be no compatibility issues
  15. Thanks Haseen, I'll take a look as soon as possible
  16. Okay might be a navdata issue then, thanks we'll escalate it as required
  17. Do other default aircraft have STARs for rwy 10?
  18. Hi Haseen, In order to to properly diagnose this, I need the following: A screenshot of your FMS (with constraints inserted) Your full route, including weights and cost index A screenshot of your FCU
  19. Hi, as Alexair says, the A310 can fly DME-ARCs as part of a navdata approach despite the ND showing a straight line (a real life quirk of the A310)
  20. Yes it probably would in that case if you armed it at the same time as you did LAND there, as the intercept angle was too sharp. Please try again with a shallower approach angle
  21. Hi, if you're trying to do an APU assisted start, you need to use the IGN modes (A or B), not CONT RELIGHT
  22. Hi Tomás, you can edit your PROF speeds on either the MODE or TACT MODE page
  23. A few things to try Push LAND later. Use V/L first to establish fully on the localiser when the diamond is +/- 1 dot. You need to be LOC captured before it will descend on the G/S. It looks like in the video that the FDs don't command nose down until the G/S diamond is one below; but if you watch your FMAs at the same time, you can see that it actually descends when LOC* transitions to LOC.
×
×
  • Create New...