LJQCN101

You actually can, by setting all channels of COMP and EFCS failure.

I can assure you that it's really an Easter Egg, not a joke. :joystick:

Today we also decided to let you participate in our secret program, the JF-17 High Alpha Research Vehicle (HARV), which features thrust vectoring. Here's the way to activate such a function: 1. Include the text "JF17_TVC" in mission description (situations). So that it can be used in multiplayer if mission designers allow it. 2. On the FCS panel, switch FLT Test 1 and FLT Test 2 to ON, then push the FCS REC button. Lateral stick and rudder command will be combined and sent to directional (yaw) TVC channel. Use them in conjunction to maximize yaw rate. At any time you can turn off the roll-yaw augmentation at the FCS panel to resume direct control over the aileron, rudder and directional TVC channel. Longitudinal channels (including FBW and TVC) can not be turned off. The TVC control law will gradually kick-in below 300 knots, and will be disabled when main landing gear WOW. (Note that there's no nozzle animations done for the external model, just pure physics and flight control.) Enjoy your investigation, and don't forget to carry some smokers! NOTES: As one can tell right now the lateral and directional stability is very low above 27deg AOA, especially in transient wing rock region between 35-45 deg AOA. With single engine TVC there's no roll control at high AOA, so it's done by inducing sideslip to create rolling moment. In the TVC control law, the directional (yaw) channel uses roll-rate and sideslip feedback to provide artificial stability and dampening of wing rock. The longitudinal (pitch) channel achieves consistent pitch rate control, without being too sensitive. But still, do not create too much of yaw-rate onset when reversing turn direction, or the actuators can be saturated. Better to build up yaw-rate gradually and smoothly. References: [1] VISTA/F-16 Multi-Axis Thrust Vectoring (MATV) control law design and evaluation [2] NASA TM104232, Research Flight-Control System Development for the F-18 High Alpha Research Vehicle [3] NASA TM4772, An Overview of the NASA F-18 High Alpha Research Vehicle Inspirations: Update: Doing all the above procedure while leaving FLT TEST 2 at OFF will enable a line by line coded F18 longitudinal control law (OFP v10.1), which I implemented at around 2015 as an EFM practice, and just copy pasted the code to be another Easter egg. The reference document was NASA TM 107601. Be aware that the F18 FCS does not fit into the aerodynamics of JF-17 very well and you can tell by the oscillations at medium speeds. TVC will not be enabled in this mode.

Thanks. I'm looking into the fade-in function.

Warning priority issue, fixed.

Nothing changed to dogfighting capabilities. Here's a test from a user at the F-16 forum: https://forums.eagle.ru/showpost.php?p=4145616&postcount=163

That's actually a great opportunity. So there will be another example for our SME from missile bureau to compare how well Fluent performs against their wind tunnel data. We're very looking forward to this.

Looks like it's in today's hotfix.

With a now fully working ground effect, your touchdown speed should be lower. And yes the dampening effect has been taken into consideration.

Only good with that level of fuel. Fuel level has huge impact on TWR and STR in an JF-17.

Hopefully in the next hotfix.

There's some weapons that could break the pylons at 5G, but I've never seen any break at 4G before. Can you reproduce this one and make a short track?

You can check damage to FCS and control surfaces in the FCS page. For landing gears, you'll get constant voice warnings when over-speed, and indication lights on the LG panel when not fully retracted.

This will not affect anything under FCS G limit.

No it won’t happen under G limit.

Did your stores failed or the wings ripped off?

996 (or even 007) mode on.

Oh and the pilot will shake his hands / behave like crazy when he feels too cold or too hot.

It won't burn down everything, but eventually the aircraft will be less responsive.

You can get FCS failure by overheating the FCS computer, or battle damage to sensors on the nose / computers around the cockpit, hydraulics failures, electric or mechanic damage on the control surface links (of roll/yaw CAS).

No it won't anymore. You can try setting random failures on all channels of DFCS and EFCS. It's a lot more unforgiving (less static stability) than the flanker.

The FCS will automatically enter direct link mode if 4 channels DFCS and 2 channels EFCS all failed. Before that the FCS will also automatically enter EFCS if 3 channels DFCS fails. If 3 channels DFCS and 2 channels EFCS fails, you're then on single channel DFCS. (All implemented.) EFCS is designed for landing purpose only and will limit maximum pitch rate to 12.8 deg/s. It doesn't have G or AOA feedback so you'll still able to over-G the aircraft at high speeds.

I see. I'll also check the flaps.

Also just a note, despite the known bug, the JF-17 is capable of 40+ deg/s instantaneous pitch rate as you quickly increases AOA in its flight envelope, but it does not necessarily means it has the same turn rate, since your actual flight path barely changes with such a rapid AOA buildup. Not sure how Tacview measures turn rate, but if it just computes the rate of heading change then it could be wrong. It's only correct by measuring the g-load you pull in a horizontal turn and use formula to compute turn rate. This is also how an EM-chart is drawn.

The out-of-the-envelop performance at high speeds are being looked at ATM and hopefully fixed in the next update, while EFCS law is also corrected which only allows 12.8deg/s maximum pitch-rate and it's actually designed to be a landing law.