Jump to content

Recommended Posts

Posted (edited)

I have had a problem since last patch.

I do the start up by the book. Even if I do it with auto-startup. The results are the same.

 

 

My Hornet just wants to go nose up. I am constantly fighting the controls.

 

Also.

 

I can not engage the Autopilot modes Radar Altitude Hold or Baro Altitude hold.

I click the buttons and nothing happens on the UFC, and the aircraft just keeps nosing up.

 

 

If I input controls, I have to wrestle it out of the AP though, so something happens. But no Lights on the UFC to tell me that the alt hold modes are on, and the aircraft keeps climbing so.. something weird going on there.

 

 

The other two modes work fine. HSELL and Attitude Hold.

 

 

I'm getting desperate now so I have tried it about a zillion times.

Both on Carrier and on land. Both on caucasus and Persian gulf.

A hundred start ups, and take off's - all the same.

No difference if I use autostart or not.

 

 

No one else have this problem?

 

 

Edit: Oh! I forgot to mention!

I have noticed, that when I press the take-off trim button, my FCS page says "STABS: 13" Instead of the usual 12? This might be related?

Tried with both clean and loaded jet

Edited by Grodlund

"Your pumping days are over, Megatron!" -Optimus Prime

"This calls for a very special blend of psychology and extreme violence" -Vyvian

Posted

I have that problem in some instand missions but not in a editor started mission where I do the startup myself. Maybe crosscheck the manual startup procedures?

Posted

Checked and double checked.

Done it by the manual, step by step.

Done it by following videos. Step by Step.

Done it by autostart.

 

I will mention that I only play in co-op multiplayer enviroment.

It might behave different in Single Player mode. I will test it

"Your pumping days are over, Megatron!" -Optimus Prime

"This calls for a very special blend of psychology and extreme violence" -Vyvian

Posted

Autopilot Modes are working just fine...

try putting a 1% deadzone on pitch and roll. That helped me a lot.

 

Greetings

-K

Modules: Well... all of 'em

 

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Motherboard: ASUS Maximus VIII Hero | CPU: i7-6700K @ 4.6GHz | RAM: 32GB Corsair Vengance LPX DDR4 | GPU: GTX TITAN X (Maxwell) | SSD1: 256GB NVMe SSD System | SSD2: 250GB Games | HDD 4TB WD Red

Posted

Yeah definitely no issues with autopilot make sure the plane is leveled and trimmed before selecting any of the Alt holds and 1% or 2% dead zone on stick axis..... also on take off give her a few clicks of nose dwn trim if taking off land.... on cv leave it as is

Posted

It's a bug reporr. Because I think it's bugged.

Obviously not many people have this issue. Such is the nature of bugs. Some are widespread. Some are rare. There are bugs related to what hardware setup you have and driver versions etc.

 

If you don't know this, then why are you here?

I think it is bugged because of the reasons I mentioned in the OP.

 

I am doing the startup by the book.

I am doing autostart.

I am doing nothing different than before the patch.

Stabs says 13 instead of 12.

Other AP modes work.

 

I will try setting a deadzone though.

"Your pumping days are over, Megatron!" -Optimus Prime

"This calls for a very special blend of psychology and extreme violence" -Vyvian

Posted

I use half flaps, as instructed.

But for testing purposes, I have tried flaps at both auto and full.

Results are the same.

"Your pumping days are over, Megatron!" -Optimus Prime

"This calls for a very special blend of psychology and extreme violence" -Vyvian

Posted

Going from cold, to start, to taxi, to take off.

No AA or AG engaged

"Your pumping days are over, Megatron!" -Optimus Prime

"This calls for a very special blend of psychology and extreme violence" -Vyvian

Posted

With the UFC it takes about two seconds or so for the colon to show up. Give it Time and it should come on. Getting it to turn off that’s a different problem I’m having. The only way for me to disengage it is by paddle switch or yanking it out of parameters.

[sIGPIC][/sIGPIC]

Posted
Yeah definitely no issues with autopilot make sure the plane is leveled and trimmed before selecting any of the Alt holds and 1% or 2% dead zone on stick axis..... also on take off give her a few clicks of nose dwn trim if taking off land.... on cv leave it as is

 

This worked for me. 1% was enough.

i5 7600K OC 4.4, MSI Z270 Sli plus GTX 1080 OC, 2x16 GB Memory 3000 MHz, Windows 10

Thrustmaster Warthog, VKB pedals TrackIR 5.

Posted

Deadzone set ingame, or in the controller software?

"Your pumping days are over, Megatron!" -Optimus Prime

"This calls for a very special blend of psychology and extreme violence" -Vyvian

Posted

enable the controls display in-game (right ctrl + enter i think) and see if your aircraft is actually pitching up uncommanded or if your controls are doing it for whatever reason

Posted

Thanx.

Will try when I get home

"Your pumping days are over, Megatron!" -Optimus Prime

"This calls for a very special blend of psychology and extreme violence" -Vyvian

Posted

Same issues with BARO mode. Click the button on the UFC, most of the time the colon never appears (very occasionally it does). However the plane does sort of seem to be in an autopilot mode. It usually doesn't hold altitude very well, and will happily gain or lose thousands of feet over time. However the controls are "sticky" like in autopilot, and it'll give you a warning if you pull hard enough to break out of it.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...