Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Flybywire A32NX Stable v 0.7.0 more issues......

Featured Replies

Hello,

          It seems that this version still has more bugs/issues. Last time was that the autopilot didnt work/engage. But was able to function once I removed the livery I was

 using, according to Flybywire website that was a Known issue.......Today just a couple minutes ago...ATC instructed me to climb to 8,000ft after departure. Which I set

 for the autopilot. I took off and started climbing. During the climb I heard like couple of clicks it seem something turn off or disegage. But all seem ok. After a couple of

 minutes I notice that the Autopilot turned off and I had pass 8,000FT so ATC instructed me to descend to 8,000FT but the plane didnt respond/autopilot. The plane kept

 climbing. So I dont know why....Also When I click on the LOC button it doesnt work/engage. Any help is appreciated THANX

Edited by Whisper202

Sounds like user errors, not bugs to me. I fly the FBW every day and the autopilot works fine.

I recommend watching some YT videos (easyjetsimpilot or others) to familiarize yourself with the typical A320 flows.

 

Most of what is said on the Internet may be the same thing they shovel on the regular basis at the local barn.

For my part the autopilot does not follow the flight plan.

12 minutes ago, filou said:

For my part the autopilot does not follow the flight plan.

And... at this point I should probably add the words "of course" here, everything seems to be working for me, except for one scare where my waypoint's all disappeared from  -direct-to, but then reappeared after I went into Flight Plan and then went back.

So far, that's been it.

We are all connected..... To each other, biologically...... To the Earth, chemically...... To the rest of the Universe atomically.
 
Devons rig
Intel Core i5 13600K @ 5.1GHz / G.SKILL Trident Z5 RGB Series Ram 64GB / GIGABYTE GeForce RTX 4070 Ti GAMING OC 12G Graphics Card / Sound Blaster Z / Meta Quest 2 VR Headset / Klipsch® Promedia 2.1 Computer Speakers / ASUS ROG SWIFT PG279Q ‑ 27" IPS LED Monitor ‑ QHD / 1x Samsung SSD 850 EVO 500GB / 2x Samsung SSD 860 EVO 1TB /  1x Samsung - 970 EVO Plus 2TB NVMe /  1x Samsung 980 NVMe 1TB / 2 other regular hd's with up to 10 terabyte capacity / Windows 11 Pro 64-bit / Gigabyte Z790 Aorus Elite AX Motherboard LGA 1700 DDR5
  • Author
1 hour ago, Silicus said:

Sounds like user errors, not bugs to me. I fly the FBW every day and the autopilot works fine.

I recommend watching some YT videos (easyjetsimpilot or others) to familiarize yourself with the typical A320 flows.

 

I will take a look....thanx

 

  • Author
2 hours ago, filou said:

For my part the autopilot does not follow the flight plan.

I.m having same issue

2 hours ago, filou said:

For my part the autopilot does not follow the flight plan.

Why am I not surprised…..

2 hours ago, Silicus said:

I fly the FBW every day and the autopilot works fine

same, recently in the experimental mod only and before in the dev mod. no problems once I sorted that the AP disconnects for floor protection

Phil Leaven

i5 10600KF, 32 GB 3200 RAM, ASUS 4070 12GB EVO, Asus ROG Z490-H, 2 WD Black NVME for each Win11 (500GB) and MSFS (1TB), Rolling Cache 16GB, Photogrammetry always OFF, Live Weather and Live Traffic always ON, Res 2560x1440 on 27"

Flightplan works every time for me (I fly the AC every day). Certain ground rules need to be followed due to the limitations of the Asobo flight planner which is still in use in the STABLE AND DEV versions.

Always put your SID and STAR in the "box" before departure. Note that the Stable and Dev versions use the Asobo implementation of the flightplanner. As a result you CANNOT OUTRIGHT DELETE THE STAR once entered. YOU MAY CHANGE IT on the fly if you need to do so if you are assigned a different runway or approach. HOWEVER, be very mindful of the starting waypoint of the STAR (This is where the flyback bug comes in). to get around this Put the aircraft in manual heading mode temporarily. Then Change the runway and Approach as needed in the "box". After doing this, Either direct to the start of the new approach or whatever waypoint in the approach you desire. Put the aircraft back to managed mode (Make sure the line on the Nav Display is solid and not dotted by pulling "up arrow" on the heading knob) and you're set. If you know what your doing you should be able to quickly double check the new flight plan by putting the ND in PLAN MODE and reviewing the waypoints to ensure you have no weirdness or discontinuities in the flight plan.

Experimental i believe no longer has the flyback bug but i don't mess with the experimental version because its missing a few features so i cant speak for it.

A couple important things i need to Add

As @DAD mentioned. If you get the Aircraft into an Alpha floor situation .. the Autopilot WILL DISENGAGE and you will not be able to re engage it until the aircraft is out of the Alpha Floor flight envelope. Autothrottle will still be engaged ( As far as i can recall so please be mindful of this) 

I always plan my flights using Simbrief  and the flight is always started cold and Dark at the gates.

Also.. If anyone ever installed the stable version from the marketplace ( I didn't) Iv'e read that it must be uninstalled using the content manager (You cant just remove it from the community folder).  If you have only ever used FBW's standalone installer then you can add remove the A320nx folder at will.

Users must also be mindful that they are using a post Service update 5 livery as issues or CTD's may occur if you are using a NON UPDATED livery.

 

Edited by Maxis

AMD Ryzen 9800X3D/ Asus ROG Strix B650E F Gaming WiFi / Asrock Taichi 9070XT / 32GB G.Skill Trident Z5 Neo DDR5 6000 / 2x ADATA XPG 8200 Pro NVME / Arctic Liquid Freezer II 280 / Seasonic Vertex 1000w PSU / Lian Li LanCool II Mesh Performance / Asus VG34VQL3A / Topping E70 Velvet DAC & L70 Amp /Sennheiser HD660s2

Thrustmaster Boeing Yoke + TCA Sidestick + TFRP Rudders

16 minutes ago, DAD said:

same, recently in the experimental mod only and before in the dev mod. no problems once I sorted that the AP disconnects for floor protection

Ditto here

-B

3 flights each day over the past weekend in the FBW A320, not one issue with any... you need to look elsewhere for your issues.

Edited by Car147

AMD Ryzen 7 5800x3d, MSI X570 Pro, 32 gb DDR4 3600 ram, Gigabyte 6800 16gb GPU, 1x 2tb Samsung  NvMe , 1x 2tb Sabrent NvME, 1x Crucial 4tb Nvme M2 Drive

35 minutes ago, swiesma said:

Why am I not surprised…..

Why am I not surprised…..

I haven't had any issues with the auto pilot.

14 hours ago, HiFlyer said:

And... at this point I should probably add the words "of course" here,

 

 

OFF course it doesn't 🙂

No issues here with 0.7.0 stable.

Edited by MrFuzzy

7800X3D | 2x32 GB DDR5-6000 CL32 | RTX 5080 | Alienware OLED 34" | 1 Gbps fiber 

The first iteration of LNAV is available in "Experimental" if anyone wants to try it out. Version 0.70 is fine as long as you do not use the ASOBO flight planner, SimBrief or manual entry only.

AMD Ryzen 7 3700X 4.2 32 gig ram, Nvidia RTX3060 12 gig, Intel 760 SSD M2 NVMe 512 gig, M2NVMe 1Tbt (OS) M2NVMe 2Tbt (MSFS) Crucial MX500 SSD (Backup OS). VR Oculus Quest 2 Windows 11 25H2 

YouTube:- https://www.youtube.com/channel/UC96wsF3D_h5GzNNJnuDH3WQ   2k+ Videos & Streams

BATC and FSFO FB Group:- https://www.facebook.com/groups/1571953959750565 Flight Sim First Officer (FSFOv6) and SoFly Beta Tester

Reality Is For People Who Can't Handle Simulation!

 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.