Isaiah53six

fair enough but it still stands true that "just because everyone is doing it" makes whatever "it" is, correct or incorrect.

exactly right

neofly

You don't know this. What if Microsoft doesn't believe the xbox was intended just for casual gamers? That would mean they would develop the Xbox to run eveything the PC runs, including a study level sim regardless of platform.

I've had trouble just getting minecraft to download and install in one go through the windows store. Not that this will eliminate CTD's in coming updates but highly recommend the steam version of the flight sim as well.

I have experienced this glitch too but only when using Nvidia driver updates newer than 466.77. Apparently it's been around for some time now since early last year. Not sure why Nvidia still hasn't at least addressed the problem or fixed it.

all this discussion over the CPU, but I wouldn't run MSFS with less than 16gb ram. Windows by itself loves its memory.

I found the buttom system doesn't work the way I would want it to but with an actual throttle, you should be able to get reverse thrust working correctly for a two engine jet using throttle1 and throttle 2 axis (0 - 100%) in the throttle settings. Make sure the Reverse Axis box is not selected. Center your throttle first which would be zero thrust on the z axis, so when the throttle drops below the center, the engines go into reverse thrust and turn off when you move the throttle back to center. ( I am using a joystick throttle combo system though (thrustmaster hotas flight stick). I would assume just add more throttles axis ( 0 - 100%) in settings (3, 4 etc) to add more engines even if you were only using one actual throttle system.

Been enjoying Neofly for many months...great to travel around the world with a sense of purpose.

possible keybinding interference or overlap? what peripherals/controllers plugged in?

yes, I was having throttle control start and stop during flight using the icon plane. I have the saitek throttle quadrant and a thrustmaster joystick plugged in. maybe a conflict somewhere? although they both seem to work fine in the 172 skyhawk