J20Stronk

Firstly, designating using the TDC in EXP/DBS doesn't work yet. It always assumes the radar is in RBM mode and will designate a completely different area than what you see in EXP. Also the TDC sensitivity does not scale correctly in EXP, it's too sensitive and moves way faster than in MAP, making it difficult to select a specific point. Second, the way the radar renders the DBS image and doppler mask is completely wrong. When you designate a point way off-boresight from the aircraft's heading and switch to EXP, the image will set the antenna's heading as the "up" reference, when in reality it should still be using the aircraft's heading as "up". This is incorrect; only the area within 10° left or right from the aircraft's nose should be masked, and the aircraft heading should always be "up".This is why we always get that 20° cone mask in EXP no matter or offset heading to the target. Thirdly, the AG radar will always magically detect ground vehicles and display their exact positions on the HSD with datalink even in MAP mode. Really only GMTI and SEA1/2 should be the only modes that display contacts on the HSD, since these modes are the only ones capable of detecting moving vehicles and ships. One more thing, using S2 Left to enter EXP just brings up a blank radar scope, nothing is shown.

The EXP modes still need a lot of work to be fully functional. Firstly, designating using the TDC in EXP/DBS doesn't work yet. It always assumes the radar is in RBM mode and will designate a completely different area than what you see in EXP. Also the TDC sensitivity does not scale correctly in EXP, it's too sensitive and moves way faster than in MAP, making it difficult to select a specific point. Second, the way the radar renders the DBS image and doppler mask is completely wrong. When you designate a point way off-boresight from the aircraft's heading and switch to EXP, the image will set the antenna's heading as the "up" reference, when in reality it should still be using the aircraft's heading as "up". This is why we always get that 20° cone mask in EXP no matter or offset heading to the target. This is incorrect; only the area within 10° left or right from the aircraft's nose should be masked, and the aircraft heading should always be "up". Thirdly, the AG radar will always magically detect ground vehicles and display their exact positions on the HSD with datalink even in MAP mode. Really only GMTI and SEA1/2 should be the only modes that display contacts on the HSD, since these modes are the only ones capable of detecting moving vehicles and ships. One more thing, using S2 Left to enter EXP just brings up a blank radar scope, nothing is shown.

I saw that. Unfortunate it doesn't use ADF, even if it's redundant. And yes, I know HNS does absolutely nothing rn. Hopefully once it's in we won't have yo update the INS everytime we fly for a couple of miles/minutes; the NAV system will do it for us.

You won't need to fix the INS yourself since the NAV computer will do so using GPS. But yes, I would like to see DSG FIX so that you can use the radar to fix it in missions that do not have SATNAV enabled. (Or TCN, if it can.) Also, I hope ADF navigation gets implemented as well. You can tune to stations using the radio panel and you will get Morse Code response, but no symbology is presented on HUD/HSD yet.

I'm really tired of seeing my SD-10 shots go for the first chaff released after getting notched 2nm away from hitting the bandit. Nevermind the fact that at that distance the biggest return would be the relatively giant aircraft directly infront of the missile. Chaffing and beaming would be nigh ineffective at the close distances shown in the OP images. (Also the fact that the chaff was well out of the seeker's FOV, yet it still somehow saw and began tracking it)

You are correct in that this should do absolutely nothing. It does not actually use the radar to give AZ and RNG differences to a known waypoint. Rather it uses the differece between "Combat" SPI and "NAV' SPI to fix drift, which is not how "drift fix by radar" works irl. (Look up Redkite's F-14 INS fix video to see how the concept of using radar to fix drift would work in the JF-17) In the JF-17's current state, systems that are used for employing weapons are 100% accurate. They have a "magic" INS that always displays correct position info regardless of the plane's actual INS. You can see this for yorself by flying perpendicular to a waypoint for a couple of minutes, then turn towards it to center the WPT on the HUD and switching to AG MM. The SPI will shift to the "Combat SPI", which is always in the correct geographical position. Couple the fact that INS drift only affects NAV mode and Combat-related sensors like AG-radar are always accurate, this lets you use the sensor's SPI as a fix point. Once the Navigation systems are finished, if you do not have HNS enabled or have no satellite link available in the mission, both NAV and Combat SPIs will correlate with each other and will drift naturally (INS/GPS weapons should suffer accuracy penalties from bad coordinates given by the drifted computer). INS fixing using position update will need to be done regularly, and like you said WPT 40 would not help at all since it is what the computer interprets as an already "correct" point. If HNS is available then the mission computer will update itself using the GPS at regular intervals, preventing drift. You should not need to fix drift once HNS is implemented. tl;dr The JF-17 has a simple INS drift that only affects NAV mode and not AG mode. You can use AG mode SPIs to fix NAV mode SPIs because they are different things in the current implementation. (Should be changed in the September update) Also HNS does not work at all.

Yes they did. Sometimes the seeker will lock onto a flare before firing if the target dumps a lot of them. Also, If you fire a PL-5 without getting tone in the direction that the enemy is flying, there is a chance the missile will detect the bandit's exhaust and home in on its own. Mind you, the seeker has an extremely small detection FOV.

>Designate a landmark using the AG RDR >Go into the position update page on the UFC >Set the waypoint to 40 >fly into the SPI and realign. It helps to bind the UFC button to a rarely used button on your HOTAS, or an easy-to-reach key on your KB.

One thing that is missing and no one's talking about is navigating using ADF mode on the radio panel. You get can get morse code signals if you tune to a station and switch the radio to ADF, but there is no symbology displayed on the HUD or HSD yet.

Speaking of GB-6, thermobaric warhead when?

Slightly off-topic, but entering ACM using S1 FWD also makes it impossible to change SOI, and if the bottom MFD isn't SOI when in ACM, then you cannot change DGFT modes with S2.

Jettison limits are modeled. M 0.8 or 450kts CAS

EXP & DBS1/2 are already in the JF-17 with the correct effects. S2 left switches between modes, or you can use MFD U2 to enter the mode select submenu in the AG RDR page. One thing that is not fully implemented is TDC usage while in EXP modes: you can move it around and designate stuff, but the area you designate is relative to the full RBM image and not to the smaller EXPanded section.

Contacting Ground Crew to perform a repair (COMMS Menu > F8 > F3) clears RWR database when complete, even if Zeroizer switch is set to off. IFF Codes, NAV WPT/FP, SMS, etc are retained. Using DTC update (COMMS Menu > F8 > F5 > F1) does not reapply Database, so a new plane will need to be used. IMO, DTC update should refresh all DTC contents, just to be safe. When DTC updates, all options set by DTC load would be available to reload. It would be up to the player to refresh what is needed; IFF codes, RWR DB/CM invetory, SMS, NAV Flight Plan or just all.

You gus are finishing the Throttle Quadrant, Control Stick/Stick Base, Canopy Control and all the intricacies behind the seat, right? Those are clearly unfinished.

JF-17 has an RCS of 3m^2 in the sim, same as a MiG-21. For comparison, the F-16C is 4m^2, F-15C and F-18C are 5, F-14 is 6. The CEII has the lowest at 1.5. AFAIK stores, aspect and the physical shape and design do not affect RCS in the simulator. These RCS values are entered manually in the .lua entry for each aircraft. As to whether 3m^2 is accurate for the JF-17, I'm not sure. But seeing as this is a slightly upscaled F-7PG the RCS would be higher, perhaps 4m^2 like the Viper. The DSI's probably only help retain the 3m^2.

This, plus dual-rack 250kg-class bombs (82L/SE/AIR/GBU, Mk20, Type-200), and possibly low smoke yield missiles like the C-701s and PL-5. (Maybe single SD-10/LD-10 too?) Oh, and a Centerline C-802AK, plus all bombs.

Considering no one is up in arms about the F-16's radar being able to detect small fighter-sized targets in TWS 80+nm away, no he isn't.

Yep, it's pretty crucial for delivering precise Pre-planned strikes using IAMs (especially since you have no exact range info besides the HSD symbology.), and working with JTAC or as a FAC craft. Of course first they'll have to fix the awfully exaggerated INS drift / lack of proper GPS navigation, since currently the NAV computer will accumulate massive error for flying just a couple nm/minutes.

If you fire an AKG at a target that is a long distance away, ~ 60nm-80nm, once the seeker goes active it will not render the ground around the target area, just the water layer under the level. Zooming in the seeker to NAR FOV may cause the ground to start rendering again, but it will disappear as soon as you zoom out again. Other times zooming in doesn't help at all. If firing AKGs at closer range targets, ~ 20nm-40nm, the ground renders properly. My graphics settings are: Visib. Range = Ultra Preload Radius = 125000 Tree Visib = 90% Clutter = 1500 .trk provided This might be an ED issue, though I have not tested the Hornet SLAMs to see if this issue exists on them. JF 802AKG Ground render bug.trk

Could we finally get AG target info on the lower 1/3rd Right MFD pls? I imagine it would show WPT/SPI info for weapons in TOO/AUTO/DTOS/CCIP mode, and PP TGT info for weapons in PP/COO mode.

When starting the plane cold: loading DTC, turning on CLDP and the WMD-7 pod after engine start will skip it's BIT test and enter STBY mode. If you press any MFCD button on the POD page before turning on CLDP on the AAP, the pod will run the BIT normally. If re-arming to attach a WMD-7, the same thing will happen after updating SMS: >CLDP on >WMD-7 on >BIT will skip and pod enters STBY Once again, pressing any button on the MFCD POD page before "CLDP on" will make the WMD-7 run the BIT. .trk below. JF POD skips BIT.trk

WMD-7 3rd person model does not match the direction you are looking at in the POD display page. If you look right, it looks left. If you look down, it looks up etc. It doesn't look backwards at all, only forward directions. It also does not Cage in 3rd person and continues looking in the direction it was last in. (or the SPI if in SLAVE mode, albeit with the same bugged 3rd person tracking problems when un-caged.)

Unfortunately, the over-exaggerated INS drift makes it innacurate if you're flying long strike missions.

COMMS Menu > F8 Ground Crew > F8 AAR Probe > F2 Remove or in the ME in the very last tab on the right when you highlight a player-controlled JF-17. (Deka pls add an option for probe removal for AI too. It's not possible to do so rn.)