Here’s the link to the full site with the Table of Contents so you can search it all:
http://www.a320dp.com/A320_DP/menu.html
4 Likes
This was a HUGE help thank you thank you!!
2 Likes
I’m using FBW dev latest version, I got power issue, power shutdown after a few minutes start. Is this bug?
1 Like
No, not normally.
This is usually caused by a conflict with another mod. (could be mod, sometimes livery, not very often with scenery)
Remove any mods from your community folder and give it a try!
2 Likes
I think conflict with salty mod
1 Like
I think it’s best to have one aircraft improvement mod at any given time.
2 Likes
I keep mostly all my addons in a separate folder.
I use a symbolic link in my community folder for mods I am going to use in that session.
The only things in my community folder is the A320mod, a tree fix mod, the hide toolbar mod, and the Navdata, all of which I use every time I sim.
1 Like
I experiment this this week end. When manipulate tablet.
For now I’ve got serious lag when manipulating FMC / Flight Plan.
A good site as well for A320 this includes the flow.
Latest Dev version of FWB did not calculate distance at FLN tab in MCDU. Here is test vid:
From begining - 19:05: Dev version standalone, without any mod else in Community Folder.
20:00 - 40:37: Stable version standalone, without anything else in Community Folder.
After 40:37, I tested both of dev version and stable version with all mods that I currently have.
From what I’m seeing from your video, the distance is shown in the F-PLN page. I can see the DEST to VVND35L, is showing the Time, and DIST with the distance number. As you fly it’s also changing to a lower value which suggests you’re getting close to the destination. 1:28:36 you start with 345 nm, then after you take off at 1:29:14 it reduces to 343 nm which is closer to your destination. I don’t see any distance issue here, unless you’re trying to point something different than what I’m seeing.
Also, you’re still using an outdated A32NX installer. They’ve updated the installer a while back to the new version, so you might not be getting the correct build version as well. I may be wrong, but what I do know is that you’re using an outdated installer that may or may not download the correct A32NX build.
1 Like
Stable version reduce distance, dev version did not reduce distance. Sorry, “calculate” have made you misunderstand.
Okay, I’ve checked Fly By Wire discord, and distance remaining updating is known issue of latest build. Maybe I should back to stable version.
Is that something that’s more important to you than everything else?
Cause I could not determine when to decend if the distance remaining not update 
I just follow my ATC.. it works generally 80% of the time… I go with my gut feeling if that’s not the case using my ND. If I’m too high and too late. I just do a corcscrew maneuver to keep descending while I stay at the same place when rejoin the path when I’m at the right altitude.
I want to free roam, so that I don’t use IFR, just go to simbrief make a plan, input to mcdu and flight, descend and landing manually by hand.
Then all the more reason not to use FPLN isn’t it? Completely visual, means your TOD is based on your visual and gut feeling. You don’t need simbrief if you want to free roam, right? Just spawn at a departure gate, and take off and see where it takes you.
I did not reach to level flight by raw data yet 
I noticed that same “not updating the miles or distance to destination” error in the F-PLN page as the simulator followed the flight plan also–I believe it was either yesterday (2/8) or the day before.
Having run the FlyByWire Installer just prior to loading the flight plan into my current MSFS session (which I do every time I run MSFS), I realized that that wasn’t going to work. So, I killed the simulator and ran the FlyByWire Installer again. In both instances, the installer installed an updated version of the “Custom FBW” version. After that most recent installation of the “Custom FBW” version, the distance to my destination was decrementing as it had always done in the past. I chalked it up to a version-specific issue that had escaped their QA, had been caught and corrected immediately–something I expect to happen when using pre-beta versions of any software.
As an aside…
Yesterday afternoon while not using any of the usual MSFS applications or in an MSFS session, I noticed my entire PC performance had slowed to a crawl–as in taking 30-45 seconds to move from one browser tab to another. I started poking around and finally found in the Task Manager that my Memory column was pegged at ~100% and highlighted in the color RED! When I sorted the Memory column by size (large-to-small) I found the culprit was the FlyByWire Installer application; which wasn’t even running, or so I thought. I highlighted it and killed it with the End Task button in the Task Manager and everything in my system returned to normal. I then restarted the FlyByWire Installer and exited it after it had updated the Custom FBW–everything appeared normal (using ~0-2%, 21.5 MB of system memory).
To me this is all just Livin’ La Vida Loca on the bleeding edge of technology…
2 Likes