With the latest update I am getting a constant clicking sound in the cockpit. Has anybody else experience something similar?
4 Likes
Yes and i have no idea what is creating it or whether said sound occurs in RL, although I’m assuming it does.
I love the new EFB. It look so much larger in VR and so is far easier to read.
The not full-brightness lighting is also very welcome and I’ll be particularly impressed if any tweaks i make to the brightness of the displays are retained for the next load/flight.
I wasn’t on the beta, but the performance does appear to have been significantly improved and i think I’ll need to turn up some of my settings.
It’s looking great so far. \o/
I had the opportunity to spend some time in a “real” simulator not long ago and didn’t notice it there. Also, non of the other “study level” A320s have that sound so I assume it is not intended. Anyway, it is driving me nuts…
1 Like
Do you have FSRealistic with FNX320 profile in use?
No, just the Fenix.
Now there’s murphy’s law in action.
I’ve just thought that it might be a switch being repeatedly activated, perhaps by some phantom mapping, so i started to look around the cockpit, just as the bloody noise stopped.
Ah, it’s back again. i’ll see if i can see anything moving when the sound happens. Trust me to be on a night flight 
Edit: the good news is i’ve remembered the dome light, but the bad news is the noise has stopped again. Maybe you could check if anything is moving when you hear the noise?
Just read on their discord that a hotfix for the clicking sound is imminent.
3 Likes
I think this is now a known issue. Folks are discussing it on Discord.
HAHA. Ya beat me to it!
ah sweet. i was starting to wonder if the passengers were making heavy use of the toilets, following a particularly bad in-flight meal. 
1 Like
Funny you are saying that because the first thing I checked when hearing the sounds for the first time was that cockpit door was closed 
1 Like
Can we now do the really basic stuff like save and reload a flight and look foward to purchasing .
How do I open the engine thrust reverser after landing? I kept pressing the F2 button several times to no avail, and the plane could only be pulled away when it slowed down to 60 knots. How to set up or operate?
I might not be overly representative, but I just pull my throttle levers back beyond idle, to a detent for idle reverse and another for max reverse.
The throttle calibration utility on the MCDU will allow you to set these “software” detents and I’ve just gone a step further by getting an insert for my Warthog HOTAS that creates their physical counterparts.
It works like a dream and just like the throttles on the real airbus.
I am using Warthog HOTAS too, to setting it in MCDU or in 2020setting ?
I used the MCDU utility in the aircraft.
I fly in VR, so it doesn’t matter that when the throttle is in IDLE on the aircraft, it sits above the Idle label on the throttle. The main thing is that the detents line up perfectly with the virtual throttle levers
I had a neverending clicking clacking sound in the Flysimware Cessna 414. It was the round turn-knob on the thrust lever somehow jittering and constanly moving the rich and lean lever up and down half a millimeter (barely visible even when fully zoomed in). I don´t know how that lever in a small plane is named I think mixture lever.
But the never-ending clack clack clack clack clack clack was of course audible, because I have that lever mapped to the round turn knob.
But I don´t have any sound problems in the Fenix so I guess that clacking and clicking sound in the Fenix cockpit also comes from a joystick switch or lever that is constantly turning on and off some cockpit element, or moving some switch on and off several times every second caused by joystick jittering and bad joystick null-zones.
These joysticks, no matter how expensive and no matter if 200€ or 500€ are litarally all the same chinese plastic-toy-trash coming from the same factory since 1997, got rebranded every five years, and jitter ghost and nullzone-twitch like crazy on all axis and all turn-knobs … 
so you are not alone with this problem *ggg
And I also found out what to do to get the awesome eighties CFM56 thundering back, the following code lines must be implemented under the “SimVarSounds” section:
</Sound>
<Sound WwiseData="true" WwiseEvent="Engine_CFM56_1_Exterior_Exhaust_Combustion_Rumble" ViewPoint="All" ConeHeading="180" NodeName="Engine_L_SFX" LocalVar="A320_Sound:ENG_1_N1" CancelConeHeadingWhenInside="False">
<Range LowerBound="0.01" UpperBound="300.0" />
<WwiseRTPC LocalVar="A320_Sound:ENG_1_N1" RTPCName="VAR_A320_Sound_ENG_N1"/>
</Sound>
<Sound WwiseData="true" WwiseEvent="Engine_CFM56_2_Exterior_Exhaust_Combustion_Rumble" ViewPoint="All" ConeHeading="180" NodeName="Engine_R_SFX" LocalVar="A320_Sound:ENG_2_N1" CancelConeHeadingWhenInside="False">
<Range LowerBound="0.01" UpperBound="300.0" />
<WwiseRTPC LocalVar="A320_Sound:ENG_2_N1" RTPCName="VAR_A320_Sound_ENG_N1"/>
</Sound>
<Sound WwiseData="true" WwiseEvent="Engine_CFM56_2_Exterior_Exhaust_Running_Loop" ViewPoint="All" ConeHeading="180" NodeName="Engine_R_SFX" LocalVar="A320_Sound:ENG_2_N1" CancelConeHeadingWhenInside="False">
<Range LowerBound="0.01" UpperBound="250.0"/>
<WwiseRTPC LocalVar="A320_Sound:ENG_2_N1" RTPCName="VAR_A320_Sound_ENG_N1" RTPCAttackTime="0.5" RTPCReleaseTime="0.5"/>
</Sound>
<Sound WwiseData="true" WwiseEvent="Engine_CFM56_1_Exterior_Exhaust_Running_Loop" ViewPoint="All" ConeHeading="180" NodeName="Engine_L_SFX" LocalVar="A320_Sound:ENG_1_N1" CancelConeHeadingWhenInside="False">
<Range LowerBound="0.01" UpperBound="250.0"/>
<WwiseRTPC LocalVar="A320_Sound:ENG_1_N1" RTPCName="VAR_A320_Sound_ENG_N1" RTPCAttackTime="0.5" RTPCReleaseTime="0.5"/>
</Sound>
Just in case you fancy getting an insert to make those detents a little more positive, here is the file that i used to buy a couple of them from an online 3d printer. Just rename the file as a .stl file and either get it printed online or print it yourself if you have your own 3d printer.
320detents.txt (980.6 KB)
1 Like
The ATC ATIS bug is indeed a MSFS bug which I’ve seen on multiple aircraft and also reported. There is a thread about it somewhere.
The endless ATIS issue is discussed in a few threads below and is location-specific having to do with the default freq. matching a nearby atis. There are a few suggested “workarounds” in the threads. I use pro-atc/sr now so have msfs atc/atis audio off completely which is my workaround
The illumination changes took me by surprise as well, but I can live with that given the massive amount of improvements in this update (including better fps). I had been flying mostly pmdg 737s but I’m happy to be flying the Fenix again.