IM A CAREER PILOT IN MSFS! | Microsoft Flight Simulator 2020

[@verbjimtim6869]

Hellz yeah, ready to see the climb and concurring of Neofly again

[@chillainous]

Excited to get back in to it!

[@llamavert]

🔥🔥

[@tonyhorn2954]

Some notes for you. At 4:43 you refer to Flight level 15. NO. Below the transition altitude (10,000 feet in Australia) altitude is ONLY in feet. Above 11,000 (Flight level 110) altitude is only measured in flight level. At the end you mentioned the hard landing and how "it didn't matter" In this case it did not. But if you are flying a sensitive cargo mission (higher XP) You will fail the mission if the landing is greater than 200 feet per minute. Hotas "phantom" inputs. The X56 does not generate "phantom inputs" What causes that is if YOU have mapped two functions to the same switch. Your fault, not the HOTAS. Finally, the XP in Neofly. You get XP for a successful mission. You get bonus XP for good flight practices (taxi > 30 kts, strobe on while engine is running, landing > 200 FPM) and you get XP based on how long the flight is. One line you skipped over was the XP multiplier. You can do qualification flights that give you a number of stars based on the hardness of your landing. 2 or three stars give you an XP multiplier (higher multipliers for higher levels of aircraft) which is a big bonus for your XP. You also need to complete a qualification flight to one star level in order to fly a more complex (two engine piston is the category B) aircraft in Neofly.

[@chillainous]

I'm a High IFR pilot, I'm used to saying FL(insert altitude) and it was an honest slip, I even corrected myself IMMEDIATELY after saying it. While I also appreciate your explanation of the Neofly systems, I am aware of how Neofly works, I have an older profile I have been on since July last year. Qualified AECBD. Also used to fly NF3 missions with my Dad a few years ago. As for the HOTAS, your comments are extremely rude. I continuously checked my bindings, and in even messed around with the sensitivity sliders, to create larger deadzones to stop it from happening. It only slightly helped. Once I plugged it in to a USB3 port (which is kind of ridiculous since it's a 2.0 device), it stopped ghosting. I like to think I have a high tolerance of people, but saying it's "my fault" is completely untrue. I've worked around peripherals for a long time, and understand when something is my fault, when it is mechanical, or when it is software. At the end of the day, I am doing KZbin, not to be the most realistic I can be, but for the ENTERTAINMENT of others.

[@tonyhorn2954]

I fly with the X56 and NEVER have had a "ghosting" problem. Switches turning off things they are not supposed to is defs a double mapping system and has nothing to do with the X56. And I use the X56 for everything from ultralights to the 747. That's not being rude. That's a fact.

[@chillainous]

Regardless, quite a few other people had the problem, and guided me to plug direct to USB3 It has been much better since.