The manufacturer and airline company probably can because they won’t spend/invest millions for something that doesn’t do anything.
It does not matter if the pilot can feel it. If you want a realistic simulation you have to simulate every aspect that sharklets have on the airplane.
Where was it implied that Sharklets don’t “do anything” in RL?
Hi Guys, new to the fenix here. I want to do some a pilot’s life ops with the fenix trio and i was wondering which of the us carriers use the aux fuel tanks which we dont have yet. Most delta a321 flights are 1600 nm at most, while the AAL flights go way beyond 2000 nm. I like to do coast to coast flights and American has these in spades. But do i need the extra tanks for these flights?
Hi everyone and as a newcomer here I’d like to seek your expert opinions on something I just can’t seem to find the answer to - if I’m even asking the question correctly that is.
So, yesterday I took up the Headwind A330 & was struck by the large amount of other aircraft traffic showed in the Nav Display of the PFD. I never see the quantity (had to be a dozen or more) such as that in the Fenix whether it be the A319/320 or 321.
I simply don’t know if I’m doing something wrong in my plane setup or if the Fenix just doesn’t show that much traffic in its’ Nav Display.
I set my TCAS to ta/ra, switch to On not Auto, and the last one to All as opposed to above or below etc.
As I say, it may just be ignorance on my part but I’d really appreciate you seasoned veterans guidance on this please and thank you.
Cheers
Rick
One possible cause may be your settings: ALL will only show traffic ±2700ft, while ABV/BLW will show traffic ±9900ft.
Additionally, according to the FENIX Discord there seems to be a 20NM limit in the FENIX, meaning traffic outside of that range won’t be displayed regardless of the settings. No timeline for a fix according to Aamir (one week ago).
Brilliant answer thank you I’ll try the above/below although I’m pretty sure All is a better option.
Cheers for your help.
It’s normal to switch to BLW when cruise FL is reached. This will be ready to give you advanced warning of traffic potentially in the way in the case you need to make a sudden emergency descent, eg. due to decompression or fire etc.
Winwings EFIS is now available for pre-order. Web site says that it’s ETA>45days. I certainly hope so I waited five months for the FCU.
While on the subject of TCAS, when do you turn it on? At pushback or when taking the runway for takeoff? Even the checklists I’ve seen online seem to be contradictory.
It’s usually a part of before take-off flow.
TA/ RA on when ready to take off. RA doesn’t work below 900ft anyway and I don’t think it being on risks any harm to ground crew (unlike weather radar).
First time I hear this. Most A320 pilots I watched switched to TA/RA before entering runway together with the weather radar.
Yes I meant ready to take off
2.2.0.403
"A new update is now available via the Fenix Installer, this has a couple of optimisations that nets us a bit of high-priority CPU time, we hope that this may help some affected with the oscillations free up a bit of headroom and therefore alleviate the issue, let us know if it helps please! Additionally, some fixes to GPS data, and for those flying in the US - switching STARs should now be a bit easier
Finally, FLX has learned how to behave itself a little better, so improvements all over the airplane really! Enjoy
Avionics and Systems
- Optimised internal scheduling of display rendering
- Added cargo distribution to loadsheet
- Added AOC FREE TEXT
- Added AOC ATIS request via VATSIM and IVAO
- Added new source of GPS ephemeris data - updated NAVSTAR tracking algorithm with more current data, fully prepared for full GNSS constellation (Galileo/Beidou/etc) when the real A320 is able
- Improved internal W&B code to better support sharklets and ACTs
- Improved conditions for auto-tuning ILS
- Fixed approach transition altitude not being based on the entered QNH
- Fixed values like 0.11 being rounded in the RNP field
- Fixed STAR not being reloaded or cleared after changing runway
- Fixed aircraft freezing during rare circumstances when using the ACARS printer
- Fixed S speed being impossibly low at around 45 T gross weight
- Fixed SayIntentions ACARS not connecting if a Hoppie code wasn’t entered
- Fixed CLOSEST AIRPORTS not showing an EFOB
- Fixed “HUNDRED ABOVE” and “MINIMUMS” playing when an MDA/BARO was entered on the ground
- Fixed ACARS client not correctly respecting “invalid login code” responses
- Fixed ALPHA FLOOR engaging on approach when below 100 ft RA
- Fixed SPD LIM not showing with a dual SFCC failure
- Fixed certain speeds showing when they shouldn’t with a dual SFCC failure
- Fixed cross track error not showing on the ground
- Fixed ECP ALL button logic (it shouldn’t “remember” the last selected page)
- Fixed formatting issues of the ATC unit on DCDU
- Fixed FUEL X FEED OPEN light appearing when the valve isn’t fully open
- Fixed tailstrike protection chevron not being amber
- Fixed physical BARO MODE switch becoming out of sync when linked
- Fixed COM3 playing at 100% volume
- Fixed HF2 transmit indicator lighting up when HF1 was active
- Removed MAX FLT TIME limitation on yellow hydraulic low level (HYD RSVR ISOL VALVE INS)
Art and Sound
- Fixed A319 & A321 safety card showing A320
- Fixed flap rods in A319 and A320
- Fixed overhead bin missing polys on high density cabin
- Fixed odd coloured paint on the wing of the A319
- Fixed ATC model not being said correctly in-game (incorrect localisation key)
EFB
- Improved cargo distribution to target an optimal CG
- Improved takeoff performance based on airport elevation
- Fixed EFB being blank on start-up if the previous session was quit with the EFB “sleeping”
Flight and Engine Models
Here we did a bit of work to the FADEC when it comes to FLX computations, some may have noticed a discrepency between the FADEC’s assigned thrust rating and what was actually achieved before - this has now been resolved by a thorough rework of the FADEC, but also it’s associated data sources. Additional to this, as a bonus of giving something a rework - you get to improve certain other aspects too. You may now observe the FADEC rating subtly changing as you roll down the runway during takeoff, this is normal - the FADEC is continously computing the appropriate thrust output and therefore slighty varying EPR/N1 - this is now reflected across the range, but we’re still tweaking the IAEs a little."
Aamir via discord
Lol, you were like one minute faster.
AHA!
This is what I’ve tried to explain weeks/months ago in this thread…whenever I did a US runway change that gives you new routing (i.e. KBOS ROBUC3 arrival, among many others), it was a pain to get everything changed in the flight plan. So it was a “bug”, now fixed. I’ll be trying this tonight.
I have not yet updated this new version, but someone have tried it and told that the MiniCFU does not work after this update. Can anybody confirm that? I would not try because there is no option to revert to older version by Fenix Installer.
Yep, they working on it, it’s broken atm if you use their software
It works. With a STAR that has multiple transitions/routes for different runways (very common in the US), all one has to do is change the runway/approach, and it’ll automatically change your STAR transition fixes. Prior to this update, you had to do lots of FMGC gymnastics, or else have a secondary flight plan with no STAR to make it easier. Excellent!