What makes it unflyable? I’ve been flying it every day, and don’t notice any issues whatsoever that aren’t caused by me.
2 Likes
Mainly
(1) The way it sometimes completely goes crazy on final approach, it sort of just flips around and then teleports in a random pattern - maybe you don’t get this, but a lot of people do and it is reported on the Fenix discord. You might have been lucky and not had it, it is certainly a low percentage of flights that result in this, but I have had far too many 3+ hours wasted by it doing this at the end that I am not prepared to risk it.
(2) Lack of performance compared to other comparable airliners.
(3) VNAV issues.
I’ve definitely not had #1, although I have had issues where the angle to capture the ILS was too steep so I had to put in another waypoint to reduce that angle. #2 is obviously going to depend on systems, as everybody’s is different, so I can see where that’d be a problem. #3, I believe I’ve had one time, where the plane just wanted to nosedive. I thought it was a conflict with another plane in Community folder, which I removed and haven’t had since, but who knows if that was really the cause. Are there other VNAV issues?
1 Like
The plane exceeds speed limits in step climb because A/T applies too much thrust when initiating a climb. Don’t know how you didn’t notice it when you fly every day. It’s an old bug.
There are also LNAV issues where plane is unable to follow certain teardrop shape approaches/departures.
Below an example showing how FMS plots TEPIC 3A SID from MMEP airport.
It does exceed speed limits, so I manually set the speed to account for that. When you said “unflyable” this is not what I had in mind. I do manually set up those teardrops too.
Who do you manually setup the SID from my example?
Setting speed limit on MCU does not fix the problem. The plane will still exceed this limit.
Can you not fly that SID in heading mode? As for the speed limit, I honestly haven’t noticed it exceed it when I manually set the speed.
I can but it’s not the point. The plane should be able to follow the flight plan entered into FMS. PMDG737 can do it, even A310 can fly this SID. Why Fenix cannot?
I am just replying to your post saying “I don’t notice any issues whatsoever that aren’t caused by me”. These are bugs, not user errors.
1 Like
I agree with you. The Fenix should absolutely be able to perform these without issues. I just disagree that said issues make the plane unflyable. They are rare & minor and can be corrected by the pilot.
They don’t make the plane unflyable per se. But when there are other aircraft that don’t have these issues, the Fenix becomes unflyable in comparison.
Speed has to be often set manually on approach at least 15 miles out, to keep it at a good number for controlled landing.
The developer just posted an update on avsim. He doesn’t mention any release date though. But previously they talked about that it would be definitely before the end of the year.
2 Likes
That’s not true at all. If you fly managed and check that deceleration is normal and you configure as expected, the aircraft will be landing at Vapp without any issue. It’s the way it’s done in real ops…
1 Like
I am not a real pilot so cant comment on that. But in windy conditions I’ve had major challenges slowing down in autopilot. There have been many occasions when I was 10 miles from threshold and still at 210+ KTS, extending flaps and in some cases gear as well just didn’t get the aircraft to Vapp.
For this mystery or riddle here I need the help of a real Airbus pilot 
Because I am too curious if this is a bug or an authentic A320 CEO quirk…
Well I have noticed that as soon as I open the flight plan page on the MCDU → all icons on the copilot navigation panel disappear. (PLAN page setting on the rose.)
The airplane icon in the middle, all VOR all waypoints etc. simply vanish like I was in the middle of the Bermuda triangle:
Even if I create a completed short flight plan with SID and STAR to test the copilot navigation panel, it still does not show up:
As soon as I press “insert temporary flight plan” which changes from yellow to green line the flight plan shows up on both displays.
Is this correct authentic Airbus behaviour or a bug I should notify to Fenix?
I didn’t know DCDU is working. How do you use it? Where do you send this re-direction request to?
Of course the Fenix is pure perfection everything* in the Fenix is fully functional (* minus the tire pressure and brake temp circuit breaker) 
First you need a Hoppie ACARS code for the Fenix launcher app. Without a Hoppie code the menu for DCDU will not shop up in the MCDU.
Let´s assume you have entered some nice Hoppie code…
Here are the steps:
The DCDU is the Discord chat of the Fenix 
The speedbrake is your friend in this scenario. What I do is exit Managed Mode & bring speed down to 250 knots prior to reaching 10k feet. If necessary, I deploy speedbrakes. Then I’ll fly at 250 knots until I approach a 220 knot speed constraint. I dial the speed down to 215 knots (for safe flap deployment), and again, use speedbrakes if necessary, which it often is. Once I get down to 215 knots and deploy flaps 1, I can switch back to managed speed mode, and it usually does fine. If at any time it appears that it won’t reduce speed in time, I deploy speedbrakes again. Each approach is different, so sometimes it’s necessary, and sometimes it isn’t, but you should never miss a speed constraint or fail to slow down to VApp.
Just got this email from FSiPanel. For those who haven’t come across this, it’s a very good tool for practicing landings etc, albeit it isn’t cheap. Here’s a link: https://www.fsipanel.com/
Here’s the email, which announces a state saving capability for the Fenix:
3 Likes
Thanks for this information! 