March 9, 20215 yr Hi, sorry if this topic has already been posted, I really didn't find anything similar. Since always, when I start a flight from the sleeve with the dark and cold plane. After all the routine procedure and I reach the assigned runway, when I take off, the plane turns into an uncontrolled machine in the first 1000 feet of elevation. Sometimes it takes a sharp turn to the right or left and is very difficult to control. Almost on the verge of losing control and crashing. After approximately 1000 feet, you can resume steering and apply autopilot. But when I start the flight directly from a runway, the takeoff is smooth without any problems. I use the A320 Neo by Flybywire. The same thing happens to me with the MSFS weather or with the REX Weather Force. Any suggestion. Eduardo Lee (MROC)
March 10, 20215 yr The only experience close to your description is sometimes the sim can forget your control setup (doesn't explain you weather problem) before I take off I've learned to check all axis controls (normal part of any checklist) as if you were checking for being operational. That will or can wake up the program and remember your control setup. That has caught me numerous times and I think some planes are more susceptible than others. Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz (8 cores) Hyper on, Evga RTX 3060 12 Gig, 32 GB ram, Windows 11, P3D v6, and MSFS 2020 and a couple of SSD's
March 10, 20215 yr Author @jimcarrel Thanks for your reply. Please can you give me more detail about what you mean by learned to check all axis controls. I do not wanna Miss a Thing Thks Eduardo Lee (MROC)
March 10, 20215 yr I've noticed that a cold and dark startup makes the Cessna Longitude default to a NAV1 tracking when the autopilot is engaged. A regular end-of-runway startup makes the Longitude default to an FMS (or GPS) tracking when the autopilot is engaged. Maybe that peculiarity applies to your situation as well. Processor: Intel i9-13900KF 5.8GHz 24-Core, Graphics Processor: Nvidia RTX 4090 24GB GDDR6, System Memory: 64GB High Performance DDR5 SDRAM 5600MHz, Operating System: Windows 11 Home Edition, Motherboard: Gigabyte Z790 Aorus Elite AX, LGA 1700, CPU Cooling: Corsair H100i Elite 240mm Liquid Cooling, RGB and LCD Display, Chassis Fans: Corsair Low Decibel, Addressable RGB Fans, Power Supply: Corsair HX1000i Fully Modular Ultra-Low-Noise Platinum ATX 1000 Watt, Primary Storage: 2TB Samsung Gen 4 NVMe SSD, Secondary Storage: 1TB Samsung Gen 4 NVMe SSD, VR Headset: Meta Quest 2, Primary Display: SONY 4K Bravia 75-inch, 2nd Display: SONY 4K Bravia 43-inch, 3rd Display: Vizio 28-inch, 1920x1080. Controller: Xbox Controller attached to PC via USB.
March 10, 20215 yr 2 hours ago, elee said: @jimcarrel Thanks for your reply. Please can you give me more detail about what you mean by learned to check all axis controls. I do not wanna Miss a Thing Thks Generally, adusting the deadzones of joystick axis(yaw,pitch,roll) to 10% solves the problem. Edited March 10, 20215 yr by kt069 Intel i7-9700K - AMD 7900 XT (VRAM 20GB) - 32 Gb Ram - SSD Drive - Win10 x64 - Samsung 43" 4K TV - Quest 3 VR
March 10, 20215 yr 8 hours ago, elee said: @jimcarrel Thanks for your reply. Please can you give me more detail about what you mean by learned to check all axis controls. I do not wanna Miss a Thing Thks For a real world pilot, it is sometimes a very good idea to check that all flight control surfaces are moving before takeoff. Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz (8 cores) Hyper on, Evga RTX 3060 12 Gig, 32 GB ram, Windows 11, P3D v6, and MSFS 2020 and a couple of SSD's
March 16, 20215 yr Author RESOLVED I have finally found the problem. Something was broken in my personal joystick settings. I have created a totally new one and I have configured the same as I had the previous one and this has been enough for the problem to disappear. Very strange error since the problem only occurred when it started from the boarding gate. There were never any problems if the flight started from the runway. This is life Eduardo Lee (MROC)
Archived
This topic is now archived and is closed to further replies.