Wolf0

That is true, and probably the shortest runway (SBRJ) where the A320 operates. Only with a caveat. No ordinary A320 operates there. Only those equiped with the SHARP packages (or similar) that allow for lower speeds due to fuselage modifications. https://www.noticiaslatamsales.com/noticias/january-february-2016/a320neo-sharp-game-changer-brazilian-airlines/ I still recommend Horta for a realistic standard A320 landing at 64500Kg experience 😉

On a more real-life note, there are instances where A320's have landed on Horta's runway (Azores, Portugal), which has 1595m and have managed to stop mid-runway. That is roughly 700m of braking distance for a passenger paying flight. Check here:

Hello. I had the same issue. But I've took the initiative to look at the files and adjust them to the new version (I'm currently using the CFM version, adjust to the IAE using the same logic). On your LINDA folders there are two main folders: LINDA and LINDA-CFG. Enter LINDA->aircrafts->Fenix A320->ident.lua. Here change the contents to: «simfolder="FNX_320_CFM"». Everything should be back to normal. Additionally I've added a new function to use the tiller. This should go inside «user.lua»: function FNX320_Misc_Tiller_Pedal_Disconnect_on() Lvar = "L:S_FC_CAPT_TILLER_PEDAL_DISCONNECT" if ipc.readLvar(Lvar) ~= 1 then ipc.writeLvar(Lvar, 1) ipc.writeLvar(Lvar .. '_Anim', 1) DspShow('PDL_DSC','on') end end function FNX320_Misc_Tiller_Pedal_Disconnect_off() Lvar = "L:S_FC_CAPT_TILLER_PEDAL_DISCONNECT" if ipc.readLvar(Lvar) ~= 0 then ipc.writeLvar(Lvar, 0) ipc.writeLvar(Lvar .. '_Anim', 0) DspShow('PDL_DSC','off') end end function FNX320_Misc_Tiller_Pedal_Disconnect_toggle() Lvar = "L:S_FC_CAPT_TILLER_PEDAL_DISCONNECT" if ipc.readLvar(Lvar) < 1 then FNX320_Misc_Tiller_Pedal_Disconnect_on() else FNX320_Misc_Tiller_Pedal_Disconnect_off() end end Have fun!

It's roughly a keyboard length.

That's the one. The info is partially outdated. The knobs are fully working. The displays are now able to show almost all parameters. I believe that SPEED is still not shown if in selected mode.

Hello. I have a VRInsight Airbus FCU with EFIS fully working with the Fenix A320 thanks to LINDA.

Pull harder... They are not bonded by glue or any slot. The shaft is a polished cilinder and I expected less friction, but they resist a lot initially to the pull. Maybe fit a flat head screwdriver bellow the black caps to help leverage.

They appear to be high quality but they have some compatibility issues: 1) The shape is round and won't fit the mainboard without major adaptations. 2) The contacts are bellow the encoder and the mainboard is expecting a flat base with side contacts 3) There are only 3 contacts, which means the push action will be lost. The original encoders have 5 contacts to allow for two different actions: 2 for the push function and 3 for the rotary function. Overall it appears that they could be used in a contingency scenario with additional workload for the modifications, but the rotary encoders that I ended up choosing are much more compatible (albeit with their own issues) and require less work.

Hello again. I've now completely solved my problem with the defective encoders by replacing them with compatible new ones. This post is aiming to point any other user with the same problem to a possible solution which was the one I found. First of all, for reference, the installed rotary encoders on my VRInsight MCP Combo II - Airbus FCU were ALPS ENCODER part number EC11E15204A3. These are rated for an operating life of 15.000 cycles, which is the root of the problem. VRInsight chose low end encoders for the hardware, with a very low expected life. On my hardware, with low-moderate use they lasted 4/5 years without problems and after that electronic noise started creeping in and they became progressively useless. These encoders have 5 signal carrying pins. 2 on upper half (for the push button action) and 3 on the bottom (for the left/right/left fast/right fast action). Additionally there are 2 latches on the sides which are there just for stability. Overall there are 7 metal pieces contacting (and soldered to) the mainboard (5 pins + 2 latches) which must be de-soldered (by hot air or a very tiny soldering iron tip). I draw your attention to performing this de-soldering step with care, as the mainboard tracks where the pins connect are brittle and if the button is still connected one risks lifting a track together with the button (this is not a deal-breaker, but will involve soldering a tiny electric wire between the encoder contact and the mainboard track origin (been there, done that two times.....). The replacement encoders that I was able to order are also from "ALPS ENCODER" (which, as far as I understand are no longer in active production). I was able to get them via a electronic store supplier which still had stock. I chose the part number EC11K1524406, and ordered them via this store: https://lcsc.com/search?q=EC11K1524406 The reason why I've chosen this model is simple: they are almost identical to the original ones (5 electronic contacts and same base size and orientation plastic pin), but they offer 100.000 operating life cycles! Nearly 10x as long as the original ones. They do come with some minor disadvantages: 1) They lack the side latches to the mainboard, so they stay connected only by the 5 tiny electric signal pins. This is not enough to prevent the encoders from dethatching from the board when the user pulls the black plastic caps for a new disassembly, or even for regular use. I've circumvented this issue by creating two solder bridges from the old mainboard landing plates for the latches to the sides of the rotary encoder. It looks terrible but helps securing the encoders to the board. 2) The new encoder has a shaft slightly wider at the base. This will prevent the metal front panel of the VRInsight device to be fully screwed to the back cover. The round holes drilled at the factory where the encoders protrude will scrap the sides of the new ones. This is circumvented by using a power drill to widen the holes by a small bit. This looks scary at first but actually is really easy. The holes are already made, so the drill will self-center. And the metal is not terribly stiff, so it is easily drilled. The good news is that I now have a working device ready for a lifetime with "minimal" effort, and the new encoders add a very nice rotating quality feel to the unit. I hope someday will benefit from this information someday. Pedro

Would really like to see this addressed! It's always a struggle keeping the aircraft on centerline after a significant crosswind landing. The rudder should be much more powerful on the ground at high speed regimes.

Thank you for your help @BIGSKY. I'll be posting an order soon!

Hello all. This post is a minor hijack but I need advice on a subject and maybe someone here has gone through this very same problem. I have a MCP Combo II - Airbus FCU which is starting to show it's age. The rotary encoders are full of noise (electronic) and are mostly useless now. I have opened the unit multiple times and sprayed contact cleaner on the encoders but the improvement is residual and it fades out quickly. I've decided that I'll have to de-solder the original encoders and apply new ones. Which brings me to my question: which ones should I buy (that will hopefully last longer) and from which vendor? Thanks in advance. Pedro Carvalho

I can confirm. On my desktop the clean install via the geforce experience program hang with a black screen just after the uninstalling old driver bit. I had to reset the PC manually and was able to boot to a basic desktop. While there I've downloaded the official NVidia standalone installer and it was able to install the new driver, albeit with some drama since it appeared to be hanging midway in for almost one minute! This was on a 2080Ti.

Tuning an atis is not convenient... It's how it's don irl but it only works if you know the correct nearby frequencies. Plus it adds workload. Looking at the grass where there isn't any atis nearby isn't a solution either, nor a windsock where there is none. Those are real-world alternatives. The red text bar allowed cross-check with the instruments, flying with the radio off and debugging new software for parameters as altitude and meteo readings. It was a nice thing to have and should have been present in MSFS. If the user wanted he could have the information displayed, otherwise it could be left off for the purists... It was convinient and we need tools since we're in a simulated environment!

That's as real as it gets. It just sucks if you are aiming for a dirt strip hidden from infrastructure. And we can explore those now. Preferably without 10+ kts tailwind on final.