Jump to content

Problems with the 172's after UPDATE 1.10.7.0


Recommended Posts

It is NOT the sensitivity of the joystick. I can tweek that. I have flown the 172 without problems prior to the newest update 1.10.7.0

 

Even if I use the keyboard the problem seems that the plane will not take off any thing less than 80 Knots. Yes I am trimmed properly.

 

How can I fix this or is there a fix for this ? It is upsetting because I bought the premium deluxe and a computer just for the 172 steam gauges.

Link to comment
Share on other sites

  • Replies 50
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

Bit of a long shot.. but could the payload have changed for some reason?

 

Regards

Steve

Intel I9-13900K - Gigabyte Z790 Aorus Elite AX - 64Gb DDR5 5600Mhz - Asus RTX4090 ROG STRIX 24GB

3x 43” Panasonic 4k TVs - Corsair RMx 1200W PSU - 2 x 2TB M.2,  2 x 4TB SATA III and 1 x 4TB M.2 SSDs.

Pico 4  VR Headset - Honeycomb Alpha Yoke - Honeycomb Bravo Throttle Unit

Thrustmaster TPR Rudder Pedals - Saitek Throttles

Link to comment
Share on other sites

I just tested it myself. I was doing 97 down the runway, still would not take off, usually 55 is my sweet spot. Sigh.....................
Windows 10 Pro, 32 gigs DDR4 RAM, Nvidia GForce RTX 3070, Intel I7 10700 running at 3.8, with Noctua NH-L9x65, Premium Low-Profile CPU Cooler-HP Reverb G2 for Virtual Reality
Link to comment
Share on other sites

Just done a couple of tests here too.. only I didn’t have any problems. I tried both 172’s with default payload and full of fuel. Didn’t make any difference.. I could still take off at less that 60 knots

 

Regards

Steve

Intel I9-13900K - Gigabyte Z790 Aorus Elite AX - 64Gb DDR5 5600Mhz - Asus RTX4090 ROG STRIX 24GB

3x 43” Panasonic 4k TVs - Corsair RMx 1200W PSU - 2 x 2TB M.2,  2 x 4TB SATA III and 1 x 4TB M.2 SSDs.

Pico 4  VR Headset - Honeycomb Alpha Yoke - Honeycomb Bravo Throttle Unit

Thrustmaster TPR Rudder Pedals - Saitek Throttles

Link to comment
Share on other sites

Tested another flight, weight was just 2 pilots, 48%. Full flaps got me off the ground and then nosed dived down.
Windows 10 Pro, 32 gigs DDR4 RAM, Nvidia GForce RTX 3070, Intel I7 10700 running at 3.8, with Noctua NH-L9x65, Premium Low-Profile CPU Cooler-HP Reverb G2 for Virtual Reality
Link to comment
Share on other sites

David, did your trim somehow get set nose down. I just recreated what happened to you with nose down trim.

 

Not sure, trim is something I usually don't mess with, however, I will look at it (just not sure where to loook??)

Windows 10 Pro, 32 gigs DDR4 RAM, Nvidia GForce RTX 3070, Intel I7 10700 running at 3.8, with Noctua NH-L9x65, Premium Low-Profile CPU Cooler-HP Reverb G2 for Virtual Reality
Link to comment
Share on other sites

Found the trim, thought that might have been the problem, the button the joystick had changed (was a view button I used all the time pre-update), was changed to nose trim.

 

However, did not change anything in flying, had to use full flaps, got a few feet off of the ground before stalling and plowing into the trees

Windows 10 Pro, 32 gigs DDR4 RAM, Nvidia GForce RTX 3070, Intel I7 10700 running at 3.8, with Noctua NH-L9x65, Premium Low-Profile CPU Cooler-HP Reverb G2 for Virtual Reality
Link to comment
Share on other sites

It worries me that it only affects some people.

 

That is a worry for me as well.

 

Tried adjusting my joystick config, did not help, could not get above 5 degrees up.

 

What plane should I try next (similar to the 172?? Tried the 152, same results.

Windows 10 Pro, 32 gigs DDR4 RAM, Nvidia GForce RTX 3070, Intel I7 10700 running at 3.8, with Noctua NH-L9x65, Premium Low-Profile CPU Cooler-HP Reverb G2 for Virtual Reality
Link to comment
Share on other sites

My 172 does not do this, so I think your control device is setting full down trim.

Try this. First Unplug your joystick from USB. Reboot your computer. Plug the joystick back into USB. Go into Windows 10 and calibrate the joystck. Then start MSFS and see if that fixed it.

If you have it, even better, after you unplug the device, before reboot, run CCleaner to clear out your cache.

Edited by plainsman
I7-9700K, RTX-2070, Asus Strix Z-390-H MB, 32gb G Skill 3000 CL15, Corsair Obsidian 750D case, WD Black 1tb M.2, Crucial CT500MX SSD, Seasonic Prime 750W Titanium PSU
Link to comment
Share on other sites

My 172 does not do this, so I think your control device is setting full down trim.

Try this. First Unplug your joystick from USB. Reboot your computer. Plug the joystick back into USB. Go into Windows 10 and calibrate the joystck. Then start MSFS and see if that fixed it.

If you have it, even better, after you unplug the device, before reboot, run CCleaner to clear out your cache.

 

Just tried that, no difference. Funnny thing is, I loaded up another plane, and it works like it should (no autopilot, lol), no, the autopilot was not on

 

Is there a way to rest the config for the 172, delete something (??) then have it reloaded. Might lose some custom settings, but right now I am trying everything.

Windows 10 Pro, 32 gigs DDR4 RAM, Nvidia GForce RTX 3070, Intel I7 10700 running at 3.8, with Noctua NH-L9x65, Premium Low-Profile CPU Cooler-HP Reverb G2 for Virtual Reality
Link to comment
Share on other sites

The patch#5 Hotfix is available to download now, it updates the sim to version 1.10.8.0. Edited by tiger1962

Tim Wright "The older I get, the better I was..."

Xbox Series X, Asus Prime H510M-K, Intel Core i5-11400F 4.40GHz, 16Gb DDR4 3200, 2TB WD Black NVME SSD, 1TB Samsung SATA SSD

NVidia RTX3060 Ti 8Gb, Logitech Flight Yoke System, CH Pro Pedals, Acer K272HL 27", Windows 11 Home x64

Link to comment
Share on other sites

The patch#5 Hotfix is available to download now, it updates the sim to version 1.10.8.0.

 

Cheers Tim :)

 

Regards

Steve

Intel I9-13900K - Gigabyte Z790 Aorus Elite AX - 64Gb DDR5 5600Mhz - Asus RTX4090 ROG STRIX 24GB

3x 43” Panasonic 4k TVs - Corsair RMx 1200W PSU - 2 x 2TB M.2,  2 x 4TB SATA III and 1 x 4TB M.2 SSDs.

Pico 4  VR Headset - Honeycomb Alpha Yoke - Honeycomb Bravo Throttle Unit

Thrustmaster TPR Rudder Pedals - Saitek Throttles

Link to comment
Share on other sites

Did nothing

You could go into the Flight sim directory and delete the 172 and then go back to the content manager and download it again.

 

I just tried this on the Pitts and it worked for me.

i7-10700K, ASUS Prime Z490-P motherboard, 32 gig, GTX 1080 Ti, 1TB M2 drive, Thrustmaster T16000M, Logitech Rudder Pedals , xbox controller.
Link to comment
Share on other sites

KFMZ to 0F4. Crossing the Platte River, then landing at Loup City and Parked after successful landing.

My 172 flies very nicely??

Two pilots and a 55 pound cargo.

172Platte.jpg

Loup1.jpg

Loup2.jpg

I7-9700K, RTX-2070, Asus Strix Z-390-H MB, 32gb G Skill 3000 CL15, Corsair Obsidian 750D case, WD Black 1tb M.2, Crucial CT500MX SSD, Seasonic Prime 750W Titanium PSU
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.

Announcements


×
×
  • Create New...