scoobflight

Change base P3D visual/graphic settings. Change GPU settings. Confirm no unnecessary utilities or programs are running when playing P3D.

And have you tried turning these off?

The sliders adjust how often the gauges refresh. Each system is different, say thanks to IBM for decisions made in the early 80s for that, so each computer had a different sweet spot. If you have adjusted to lowest refresh rates for all gauges you system has another bottleneck that needs to be found. Custom shaders? High settings on P3D? Other custom add-ons?

You are also confirming windows antivirus isn't running?

Have you adjusted the gauge refresh rates using the configuration utility (see manual)?

What settings are you using? What remediation steps have you taken to increase framerates that are outlined in the forum? Details are needed for support to occur.

And be sure to move your yoke/throttle controller fully forward - (note: the above I correct the typo at the end of the first sentance that seems to have made its way into the manual - oops)

have you duplicated the issue? is it possible you knocked the throttle controller? you stated you moved the throttles forward after A/T disconnected?

confirm that you directed the installer, and can find by looking after running the installer, the RC textures in [path to FeelThere directory]\Tower3D Pro\Extensions\Airplanes\Texturepacks also review -

install Real Traffic first then the Real Colors for each airport. right-mouse click the installer and choose 'install as administrator'. when prompted input the unlock keys you were sent in an email by BMTmicro. when prompted direct the installer to the correct Tower!3D folder as outlined in the below linked post -

After the RT and RT installers are downloaded are you running then as administrator and directing them to your Tower install directory?

This is feelThere's official support forum.

Zooming in and please review the below linked thread - https://forum.simflight.com/topic/88087-button-aliasing-issues/

Another solution - https://www.facebook.com/groups/741712162991122/permalink/765750480587290/

Please continue to this discussion in the below linked thread -

Correct, the planes use default P3D lights.

Both ... testing is testing v. other reports of bugs that may be included in the SP due to severity.

It is feelThere policy not to announce on a release date.

Thanks! If more information is needed with let you know.

See - http://www.prepar3d.com/SDK/Mission Creation Kit/FlightFiles.htm

See - And - And - Please continue discussion in the thread that more relates to your issue so there are not duplicate discussions.

the throttle lever on the joystick still needed to be moved to full forward for the same reasons Vic noted.

at this time there have been no duplicate reports of the issue. guess - did you install the plane as admin? the next step will be to uninstall and reinstall the plane (always install as admin) after that you need to provided a FLT file saved JUST PRIOR to when the issue can be reproduced. share that FLT file here. provide EXACT steps on how to reproduce the issue.

if you purchased and downloaded prior to 24 December '19 use your download link to collect the new installer. uninstall the plane. install the new hot-patch edition as administrator. also, a detailed SP is in the works. see -

after engine run-up (about 50%) did you move the your controllers throttle(s) to full forward? this is how the FADEC is modeled. Manual page 63: (note: the above I correct the typo at the end of the first sentance that seems to have made its way into the manual - oops) this procedure is also covered on manual page 73 -