Strange fluctuations after getting into wake turbulence

[Cytarabine]

Not sure if this is a bug or it was some form of damage from over stressing the airframe but after pulling behind a Mirage 2000 in BFM and destroying it with guns (and not as far as I could tell hitting any debris) my F-15E continued to oscillate like it was still in the wake turbulence no matter what control inputs I made.

I've included a track file of the incident (including my horrendous BFM skills).

Anyone noticed anything similar?

 

Edit: To save having to watch the whole track it is right at the end in the last minute or so.

wEIRD.trk

Edited June 28, 2023 by Cytarabine

[matze140]

I had the same behaviour everytime i pull too much Gs. In F2 view, you see the horizontal and vertical stabs osszilating a bit even if there are no control inputs. 
 

Maybe a sort of damage model, but it is not described anywhere. 

[T-B0NE]

I watched your track and there were afew instances of rapid over G from what I've found the rocking motion is from over G damage to the airframe the F15E isn't fly by wire and won't restrict AOA thus G loading is instant if you pull back to fast on the stick at high speeds.

In real life aerodynamic forces are acting upon the control surfaces making quick jolts to the control stick very hard to do but with a simulator Hotas there is no such limitation and worse no flight computer between the controls and flight surfaces to correct for the error like in the F-16 or F/A-18.

so ultimately overly rapid inputs can cause structural damage to the aircraft it causes simulated damage to the wingtips of the F15E I think that's why after a few abrupt over G maneuvers the airframe starts to rock slowly side to side in level flight they have also simulated the damage model for this as seen in the pictures below. 

Otherwise, I do see what you mean about the rudders oscillating like crazy I'm not sure as to why this specific thing is happening. 

I may not be 100% correct here but it may have something to do with the damaged wing and the Aileron/Rudder Interconnect (ARI) and the Yaw Channel CAS. 

the F15 series has a system in place to assist pilots who forget or hesitate to use rudder inputs during maneuvers I'm not 100% sure but I think after the damage the YAW CAS was in some way chasing its own tail trying to compensate for the wing dip from the damaged wings and the yaw it was producing but it was overcompensating and thus causing the oscillation if that makes sense.

from what I've read online is that the F-15 has strong positive dihedral effect, which produces strong roll in the direction of yaw at all flight conditions at higher speed the wingtip dip from side to side would be exacerbated take into account the left engine failure adding even more yaw and it's likely the Aileron/Rudder Interconnect (ARI) was freaking out the Yaw CAS just a theory would be awesome to see if this was the actual issue.

 

Edit: out of interest I replayed the track took control of the F15 after the oscillation it looks like the left engines feed tank ran dry of fuel explaining why it stopped, I reduced both throttles to idle and used the YAW CAS switch just above the throttle to reset it a few times it worked, and the rudder oscillation stopped completely it looks like it may have been possibly a few factors leading to the CAS freaking or maybe a series of factors like wing overstress/damage and engine failure thus asymmetric thrust also the added possibility of hitting the mirages wake side on too but overall looks like the CAS was going crazy hahaha.

Edited July 1, 2023 by T-B0NE