Hi there,

This update to stable version 0.10.1 contains some minor fixes to our previous stable release.

 

•     [ATSU] Hoppie Telex with \n now can be received
•     [EFB] Fixed SimBridge failing to connect if remote setting is enabled then disabled
•     [EFB] Optimized/fixed strobe handling in aircraft presets
•     [EIS] Added > character to the font
•     [FLIGHTMODEL/FUEL] Update of fuel system (center tank transfer and crossfeed)
•     [FMGC] No vapp addition without wind entry
•     [FMS] Improved robustness of ILS selection
•     [FMS] TO SPEEDS TOO LOW uses FQI fuel quantity after engine start to avoid spurious warnings
•     [LIGHTS] Fixed trim decal emissive and floods
•     [ND] Fix ROSE VOR/LS conditions and ILS course
•     [SIM] fix(sim): only show nav radio tip once

Happy Flying!

Note: Throttle calibration is now required.
Guide: https://docs.flybywiresim.com/throttle/

---

Download using our installer: https://api.flybywiresim.com/installer

Our installation guide: https://docs.flybywiresim.com/installation/
SimBridge Guides: https://docs.flybywiresim.com/simbridge/
Support Guide: https://docs.flybywiresim.com/support/
Known Issues and Workarounds: https://docs.flybywiresim.com/reported-issues/

Note: Not Available on MSFS Marketplace.

 

Perhaps a redundant question, but is VNAV included in this version?

16 minutes ago, hvw said:

Perhaps a redundant question, but is VNAV included in this version?

As of yet no.

One thing I can do in the Fenix is set a fix ring, and then create a waypoint where the ring intersects with my flight paths. I can do the first in the FBW, but not the intersect.

This something that is on the roadmap?

12 minutes ago, BrammyH said:

One thing I can do in the Fenix is set a fix ring, and then create a waypoint where the ring intersects with my flight paths. I can do the first in the FBW, but not the intersect.

This something that is on the roadmap?

Sadly intercept waypoints are not yet implemented in the FMS. However, like most features, it's planned.

Edited June 26, 20232 yr by Lucky38i

2 minutes ago, Lucky38i said:

Sadly intercept waypoints are not yet implemented in the FMS. You can however set radials and radii around a given Fix. Read the docs for more info https://docs.flybywiresim.com/pilots-corner/advanced-guides/flight-planning/fixinfo/#examples-of-fix-info-intercept-waypoints

Thanks,. yeah. That is what I am doing now. I can't remember if there is an FMS update in the works or not.

2 minutes ago, BrammyH said:

Thanks,. yeah. That is what I am doing now. I can't remember if there is an FMS update in the works or not.

Sorry I misread your post. Yes all feature sets of the Honeywell H3 (I think we have a slight update) are planned. As-well as the rest of the aircraft and it's abilities and oddities.

1 hour ago, Watsi said:

Note: Throttle calibration is now required.

Can I ask, what will this bring?  Right now I use one profile for the 4 planes I fly and I am super happy with it and never need to visit the controls dialogue.  The only reason I would care to change this is the lose the annoying fact of acceleration during taxi requiring braking.  Will this change this?  And what happens if I don't do the "required" calibration?

Thanks!

I’m looking forward to their own A320N model. 

2 minutes ago, Noel said:

Right now I use one profile for the 4 planes I fly and I am super happy with it and never need to visit the controls dialogue

How are you hitting the detents on the A320 without calibrating it? I am amazed you can get by with 4 different planes on one profile. I need separate profiles for the each A320s and the PMDG.

3 minutes ago, Noel said:

Can I ask, what will this bring?  Right now I use one profile for the 4 planes I fly and I am super happy with it and never need to visit the controls dialogue.

The only reason I would care to change this is the lose the annoying fact of acceleration during taxi requiring braking.  Will this change this?  And what happens if I don't do the "required" calibration?

Thanks!

FBW uses it's own calibration page within the EFB, see here, So you won't need to visit the controls dialogue, that's specific to MSFS.

Just to note, the Leap engine will taxi up to 30kts even at idle. The standard practice is to let it accelerate to 16 knots or so then brake down to 5-10, rinse and repeat. Though that practice varies.

If you don't calibrate then the throttle will function improperly or not at all.

1 hour ago, hvw said:

Perhaps a redundant question, but is VNAV included in this version?

Just use the Experimental branch. 

46 minutes ago, BrammyH said:

How are you hitting the detents on the A320 without calibrating it? I am amazed you can get by with 4 different planes on one profile. I need separate profiles for the each A320s and the PMDG.

I simply look at the graphics and move throttle/flaps/speed brake accordingly.  I use PMDG/A320NX/AS CRJ700 and on rare occasion Longitude.

30 minutes ago, Lucky38i said:

FBW uses it's own calibration page within the EFB, see here, So you won't need to visit the controls dialogue, that's specific to MSFS.

Just to note, the Leap engine will taxi up to 30kts even at idle. The standard practice is to let it accelerate to 16 knots or so then brake down to 5-10, rinse and repeat. Though that practice varies.

If you don't calibrate then the throttle will function improperly or not at all.

Ok sounds like its calibration routine will not mess w/ the MSFS default use, great, so I will run the FBW installer to update.  Thanks for that Lucky.

Yes, I've learned about this bizarre aspect of the NX.  It would be equivalent to having a car that needs to have its brakes applied to stop it from accelerating at idle.  Hard to fathom that was actually allowed to persist in the final design.  I've assigned L/R brake axis to one axis on my TM Boeing Pendulum Yoke but it's finicky to get set correctly.  My other choice is to just start one engine until close to the runway threshold.  

 

22 minutes ago, Farlis said:

Just use the Experimental branch

It's on the DEV branch now as well.