need track replay Trim issue when landing on super carrier

[pixie]

Hi, 

I'm not too sure if it's a bug or if the problem is located between the HOTAS and the chair.

 

Recently it seems I can't get a proper AOA when landing on the carrier.

On my last campaign mission, a correct AOA was impossible to achieve on my last missions (serpent's head 2). As soon as I enter a little trim input, the aircraft is havig a big up'n down woobling. It seems I'm always fighting the FCS and there is no way I can't fly in the E bracket and control my glide rate with the throttle like I did before.

I believed my F18 received some small arms damage in the mission so I tried a Supercarrier preset CASE 3 recovery mission, and it was just the same.

I'm running 2.7 stable

 

Trimming the aircraft has never been a problem before. I used to put the flight vector right in the middle of the E bracket. hook down, anti skid off, <250 knts,  Gear down, flaps down , a little bit of trim to raise the nose and voilà... You all know the drill. But this doesn't work for me anymore and I'm clueless.

 

Has anyone encountered this problem ?  

[Sacarino111]

Hi.

For me it has been like that the entire time, I never got the feeling of the trim, can t tell you why... Let's hope it will change later on.

Saludos.

Saca111

[Stearmandriver]

The plane trims up nicely for me just like it always has.  Only thing I could suggest is, I've seen updates mess up my control bindings before.  You might check out the pitch trim bindings and make sure they haven't been deleted or doubled up somehow. 

[Tusky]

hace 1 hora, pixie dijo:

the aircraft is havig a big up'n down woobling.

 

In the briefing window (accessible by ALT+B), check the value of turbulence. The "wobbling" is typical of turbulence (at low level flying)

[maxTRX]

@pixie  I've seen this once or twice in the last 2 weeks. I couldn't figure out what caused it. Gear and flaps were down, VV started dropping, slowing past 150 kts, I touched the trim and the nose pulled 'cobra'.  I've never seen this before June updates.

[pixie]

2 hours ago, Gripes323 said:

@pixie  I've seen this once or twice in the last 2 weeks. I couldn't figure out what caused it. Gear and flaps were down, VV started dropping, slowing past 150 kts, I touched the trim and the nose pulled 'cobra'.  I've never seen this before June updates.

yes ! this is exactly what happened to me,  a slight trim input of 10ms and the nose pulls up like a "cobra" attempt

hopefuly this will be gone with the very last update, DCS is downloading right now 

 

[Maduce]

Same here. Hornet it is set up in landing config (gear down, flaps to full). Trim super sensitive, hard time keeping it in the E bracket. Also seems that once in the E bracket the Hornet really doesn't want to stay there. This issue just started for me. 

[theIRIEone]

Experienced the same issue here on Sunday, also a few weeks back as well.

Thing is, i can get the plane trimmed after a while despite nose initially shooting for a cobra, but it appears that FCS does not enter PA Mode correctly as the trimmed aircraft does not stay trimmed:
- in PA mode, E-bracket and VV are tied to one another rather rigid, but this is not the case when described bug appears. Rather slow power changes will result in slow drift of e-bracket.

Note that A/P advisory is displayed despite disengaging all A/Ps by the use of paddle switch.

Trackfile is probably too long, but as usual i have an unlisted YT recording of this (problems described from timestamp til landing - ignore bad r/t, was heavily distracted by the bug)

 

[maxTRX]

I've seen the trim sensitivity issue whenever I entered PA mode with auto pilot ATTH active (I haven't experimented with other auto modes).

When I was flying in IFR conditions I used ATTH frequently and sometimes I would drop gear and flaps w/o disengaging ATTH. I didn't expect any issues caused by this. Well, it did cause the trim to misbehave.  Pressing the paddle wouldn't fix it.  I had to raise flaps to exit PA mode then drop them again (I actually cycled both, gear and flaps) and the problem disappeared.

So, for now I always make sure there are no auto pilot modes active before going to landing config. 

Edited July 6, 2021 by Gripes323

[theIRIEone]

1 hour ago, Gripes323 said:

I've seen the trim sensitivity issue whenever I entered PA mode with auto pilot ATTH active (I haven't experiment with other auto modes).

When I was flying in IFR conditions I used ATTH frequently and sometimes I would drop gear and flaps w/o disengaging ATTH. I didn't expect any issues caused by this. Well, it did cause the trim to misbehave.  Pressing the paddle wouldn't fix it.  I had to raise flaps to exit PA mode then drop them again (I actually cycled both, gear and flaps) and the problem disappeared.

So, for now I always make sure there are no auto pilot modes active before going to landing config. 

I'm not using ATTH that much really, but BALT. I don't think it's important what A/P mode is active prior to / the moment of dirtying up, but just that any A/P mode is active.

You can see me cycling gear / flaps in the recording as well, problems didn't disappear this time - meybe i was too fast with the cycling, but i remember being successful the same way during a flight some time earlier (few weeks back).

[Maduce]

Been flying most of the day today and haven't had any issues. I normally use BALT and CPL, but I have been disengaging about 30mi from carrier. Don't know if that had any effect on it. Don't know what I am doing  different now. 

[nighteyes2017]

yes, i experienced this as well. Flying a case 3 carrier approach. trimming to the correct AOA is suddenly very hard. It is suddenly very sensitive. 

[sebihepp]

It seems you have CSS Autopilot on. It is visible on the left DDI as an advisory A/P.

Do you disable the autopilot modes via the paddle switch? If not, this is the problem.

[Svend_Dellepude]

On 8/4/2021 at 5:16 PM, sebihepp said:

It seems you have CSS Autopilot on. It is visible on the left DDI as an advisory A/P.

Do you disable the autopilot modes via the paddle switch? If not, this is the problem.

 

This. ^^^ Users have reported the exact same several times before and pressing the paddle should solve this. If you only uncolonize the autopilot mode, you will only disengage that mode, but not the autopilot.