Jump to content

JoshF

Moderator
 View Profile  See their activity

  • Posts

    1330

  • Joined

  • Last visited

  • Days Won

    15

 Content Type 

Posts posted by JoshF

    B-Events do not work since Update 1.0.3

    in Other

    Posted

    On 3/15/2024 at 10:08 PM, Philipp20 said:

    Hi, I found a few L Vars that are working. As an example there ist B:AIRLINER_PROFILE_Button. Could you provide L Vars for pressing and pulling the kobs (HDG, ALT, SPD, VS)?

    thanks

    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

    A320Neo

    in General Discussion

    Posted

    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 🙂

    • Like 2

    Engines seem underpowered

    in Systems

    Posted

    9 hours ago, SkySurfer87 said:

    I can confirm same issue here. Throttles are broken in latest update. My reversers are messed up as well. Using honeycomb bravo. Number two reverse lever only closes halfway when selecting reversers off. 
     

    Tom

    How is your Bravo set up? I'm using one and haven't seen this

    Unable to contact support

    in General Discussion

    Posted

    On 10/27/2023 at 7:47 PM, Swervr1 said:

    I am trying to change my email address in the store, but the support contact form returns an error saying try again later all the time.

    I have successfully changed the email within this forum. Could the request be dealt with here or forwarded to support?

     

    Regards

    Mervyn Edwards

    Hi, is this still an issue?

    Empty place for pilot and pax

    in Suggestions

    Posted

    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.

    A310 Fuel Usage, actual compared to predicted

    in Systems

    Posted

    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. 

    Can't turn the Ignition Selector

    in Systems

    Posted

    8 hours ago, exergon said:

    Hi Josh, I do, using the Honeycomb Bravo. Had this idea alreday, tried to map this, but couldn't find what has been the right set up for the ignition selector. 

     

    In that case please try with it unplugged, see if that's causing the issue

    How to create a circle to land approach in the fms

    in Suggestions

    Posted

    2 hours ago, Alexair said:

    Just tried to do the same flight to be sure.

    I got your point now, the Navigraph AIRAC or the A310 (don't know which one is the culprit) is lacking the OSMOS arrival for RWY 10. Thus your decision to build the DME-ARC.

    There is no STAR for RWY 10 at LGTS in the FMS. Would be good to know from inibuild if it's a navigraph issue or the A310.

    Do other default aircraft have STARs for rwy 10?

    • Like 1

    Localizer capture impossible

    in Systems

    Posted

    2 hours ago, alexven1972 said:

    yes, i noticed that. Maybe the logic of the 310 needs LOC GREEN before GS GREEN (my hypotesis). Nevertheless i think that the clear laziness of the FD in transitioning from LOC* to LOC GREEN would have led to the same results, even if i d used VL for LOC capture and then LAND for GS. 🤔😊

    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

    Localizer capture impossible

    in Systems

    Posted

    6 hours ago, alexven1972 said:

    so here is another example of the a310 FD “laziness”. The approach is again Comiso LICB ilsrwy05 (COM VOR transition). This time i wanted to help the FD a little, inserting manually 2 PBD points after COM-D9 in order to allow a smoother final left turn ending in a lower LOC intercept angle. After a WAY TOO LONG LOC* ,parallel to the localizer, at the end it nails the LOC green. This time, the “laziness” of the FD involved also the GS capture: as U can see, the GS diamond passes the midline but the FD does not command the descent until 1 dot below. At this point suddenly it commands a -5 degrees dive 😰In real life all of this could probably have triggered a go around. 🤔 

     

    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...