Svend_Dellepude

IIRC that falling leaf stall was corrected in later models of the Hornet. It's also mentioned in the Jetstream documentary.

It's a bug, where CCIP solution seems to be tied to the ground instead of the A/C. So because of the INS drift that was introduced at some point during development, CCIP solution gets screwed with time. There is a lengthy thread about it here:

Old news!

If I'm not mistaken, the last 22% is there to make sure you can reach max G or max AoA with forward trim in the system. Might be wrong on this one, but that was my conclusion when i discovered this.

It might have something to do with some centering functions in the real jet that has not been implemented properly yet. For instance you are able to control the elevation from the AZ/EL page. That would create some problems for an absolute axis where the scan area would either have to jump back to position of the hardware or get added as bias when you exit the AZ/EL. The latter would mean that you would not be able to center you scan area anymore. I have the elevation bound to buttons, I've gotten used to it and don't think much about it anymore.

Delete the shader cache. If that doesn't do it, try a repair. I had the same issue and fixed it, but don't remember which of these that worked for me.

There was a bug once that could get the wing fold handle stuck. Dunno if it was ever fixed, and dunno if that is the case here.

If you have a force sensing stick you can also fiddle with the saturation to make the axis more responsive. It doesn't have to be 1:1. Not so with moving axis though. Personally I never got used to using an extension with the F-16, so i took it of and side mounted my Virpil, which was perfect.

Try a repair to see if that does anything for you. Usually FM changes are mentioned in the changelog, so if there where none mentioned, there probably was no change.

INS is not working correctly. Just stick with GPS when possible. There is already a lengthy thread in here about the issue. search for INS + CCIP.

Speechless!

SIL might keep track memory until timeout, while radar off probably won't. Just guessing.

I didn't look at the mission, but they are probably server restricted.

Yeah, IRL maybe. But INS screws up the bomb fall line which it shouldn't. Another benefit is that you all of a sudden have all your sensors working like they are supposed to. JDAM's will land where you intended, FLIR will point where you intended and so on. So until they fix INS this is a solution. My girlfriend might not like it, but ok. Here is a lengthy thread about the issue:

on the AMPCD select POS/GPS instead of POS/INS if GPS is available. That will fix the problem with the bomb fall line.

There is already a thread about this.

Track TWS elevation 2.trk

Happens if you lost a track in auto, enter bias mode, fiddle with elevation to search and then aquire a new target. The radar will input some elevation on top of what was already applied by the pilot, which makes the radar go too high or too low.

Have a read here:

From time to time here as well. Usually if I've been shot down and the screen goes black, before i respawn.

This thread is nonsense.

g limit in the Hornet is weight dependent and not a "one size fits all". FCS page will show available g at all times. The viper on the other hand is AoA limited in cat 3 but not G limited AFAIK.

Did somebody shoot at you?

Apply some deadzones if you haven't. Or increase the ones applied.