J20Stronk

The P indicator only turns on when you reach 108 knots. That indicates that the FCS takeoff assist is engaged for whatever mode is selected: Auto-Rotate for AA. Pitch stabilization for AG1/2. example .trk file: JF auto to ind.trk

Yep, they baounce needlessly around the laser, no matter the wind condition or ownship maneuvers (or lack thereof). Maybe ED somehow changed something with the guidance API since I don't see any changes to the rocket itself in the .lua file.

It could be that it's too hot or too cold, not hypoxia. Pilot reaction to cabin conditions and temperature is modeled in the JF-17. You should start the engine, seal the pit and turn on ECS ASAP if you are playing a mission where it's really hot or cold.

Technically we already have a "fictional" JF because it's a Block 1 with an AAR probe (which were never mounted on Blk. 1, only Blk. 2). Also, ED added the cheek mount for the F/A-18's LITENING, which they initially claimed was never going to happen since they were modeling a USN/MC Hornet from ca.2006. The US never used cheek mounts for their Hornets, but it's there now. I believe an HMD is not impossible for Deka to add since the JF is definitely capable of using one as integration was planed for blk.1 by Chengdu, but the PAF turned it down since they didn't need it for their JF's strike fighter role. (They want to save as much $ as possible too.) Of course it's up to them to decide to add that in the future, as well as other Blk.2 features like OBOGS, KLJ-7V2 and WMCs software updates. (Maybe even sensible blk.3 stuff, like 360 deg MAWS and a better engine?... :music_whistling:) Edit: As foxwxl stated, the HMD coding is actually complete. You can find the files in your JF-17 install folder. It's been disabled, but Deka can literally just enable it in a couple of minutes on their end.

That's the T/O auto-trim indicator. It turns on when you reach ~108kts down the runway to assist during takeoffs. If FCS is in AA mode, it automatically rotates the plane. Some slight backstick pressure may be needed to help the FCS lift the nose, especially if you're heavy. In AG1/2, auto-rotation is disabled and FCS acts as a dampner and stabilizer to assist in t/o ration. Backstick pressure is needed to take off in this mode.

They track on my end, but they also appear to have a new FM with too much bounce. The new bouncy FM makes it extremely difficult to hit targets when maneuvering away, but its also hard to hit targets when straight and level.

<500kts IAS >500ft AGL N+T fusing, best used in AUTO with an interval of 750 to get the best distance on Runways

Yep, SEA1/2 and GMTI still drop locks.

Yep, looks like it was fixed. Thanks Deka!

I think it's been fixed this update, but if it hasn't you can switch to AA mode, wait for the antenna to come down, then switch back to AG. It should now be pointing where you want it to.

.trk #1 AG Radar Bugs: 1-1. The first trackfile shows various bugs with the AG radar. For starters using the keybinds for antenna elevation up and down will change the number for desired antenna elevation, but the antenna itself will not move to the entered elevation. You must switch to AA radar and then change back to AG radar to gimbal the antenna after setting the elevation. I believe the antenna will move in AG mode if you have antenna elevation bound to an axis, but I have no axis on my HOTAS to test. :( 1-2. This track also shows how upon unlocking a surface target from SSTT (or GMTT/FTT), display range will always reset to 40nm. This will happen also happen when using S2 depress to unlock a target, and will also restore the radar mode to the second-to-last radar mode; ie MAP -> GMTT -> SEA1 Lock -> S2 Depress -> Mode returns to GMTT or MAP and Range to 40nm. If the target unlocks by going out of gimbal range or on it's own due to the notch filter bug (bug I know has been fixed internally.), then mode does not reset but display range does, back to 40nm. 1-3. AG radar contact will briefly display in AA radar modes, and can also be locked onto and engaged if you are quick enough. SD-10s will home onto the surface target unless there is an aircraft nearby, then they'll chase it instead. (<- not shown in .trk) .trk #2 AA datalink contacts and CM-802AKG oddities 2-1. There is a small window of time where a contact will disappear from HSD upon being detected by radar. Though my track does not show the worst case, there are times especially in populated MP or SP missions where an AA contact will not reappear on HSD until the contact has faded entirely from the RDR screen. 2-2.The first half of the track show how contacts locked in STT do not update position on HSD at all, provided that the aforementioned disappearance bug does not occur. They appear static on HSD in the exact same location where first locked in STT. Once unlocked and detected by other means or ownship radar if bug from above does not occur, they will teleport to their new position on HSD. Changes in the target's heading are still repeated on the HSD contact however, even though it is not shown in the track. 2-3. CM-802AKG will not update the SPI on the HUD if you have selected PP mode, nor will it highlight the first RP point on the HUD or HSD. The AKG missile will still follow the selected PP or RP route, but range and target diamond on the HUD will always point to the selected SPI (usually selected waypoint on UFC). Also, the HSD now seems to indicate that the max launch range is 20nm in a similar way as the LS6/GB6, by using a perpendicular line and dotted line to SPI in PP and TOO modes. of course the AKG has much greater range, and you can fire it beyond the indicated 20 limit. I think it's actually showing Min launch range, in which case, wouldn't it be better to have a large blue circle as the indicator for that just like the LS6/GB6? to avoid confusion. 3. Selecting Non-IAM AG weapons remove the waypoint indicator from the HSD. This is probably behavior from the real aircraft, but I figure I should still report it and be wrong than live with it and never have it looked at. The only way to have the selected waypoint/SPI show up on the HSD in AG mode is to have an INS/GPS guided weapon with PP capabilities selected like the C-802AK/G, GB-6 or LS-6 bombs. Selecting any other weapon removes the waypoint/SPI indicator from the HSD, making it difficult to find target location or SPI where AG radar/ TGP is designating. 4. Most lighting knobs still behave like buttons and do not dim lighting. Self explanatory. In the track I show which lighting knobs behave more like on/off switches (Landing Gear, OXY Blink), and others that just do not work (AAP Brightness). Also the Speed-Brake, Drogue-Chute, TE-Flaps and Front Panel Indication (Trim, selected FCS mode, NWS) lighting is way too dim during the day. I believe the intensity is supposed to be controlled by the Day/Night switch and brightness knob on the Warnings and Advisories Panel (which do work, but only for this panel). Thanks for coming to my TED Talk. Keep up the good work Deka! :thumbup: 1 JF AG Radar Bugs.trk 2 JF DL AA detect delay and AKG bugs.trk 4 JF binary light knobs and dim status lights.trk

Screens pls. I've been flying this thing almost exclusively since launch, and not once have I seen it mark SAMs through D/L without them emmiting or beimg spotted by AGR

And JF can't see them through D/L unless they (or literally any other thing detected by its radar.) are being constantly tracked by AG radar from another JF, which is almost never. JF has no Threat rings or SAM locations a-la F-16/8.

TF are you talking about? It is impossible to pinpoint radars unless you have the KG-600 and they are on, or you have been prebriefed via F10 spectator view or mission briefing. The JF doesn't have pre-loaded SAM threat rings and locations unlike the F-16/8 which, as stated by others, is because of the lack of DTU for them. Hence they simply have them visible on HSD/SA by default unless specified in the ME. JF doesn't have PB SAM threat rings at all.

Yep :( You gotta keep it off for as long as you are in AG mode with the Radar on. The problem is (I believe) the new static target detection is overwhelming the D/L and HSD with a ton of contacts if there are a lot of vehicles in a mission. Hopefully Deka will fix this as they work on D/L and AG radar improvements, but for now: If you are going to use AG radar, turn off D/L. If you are not going to use AG radar, but are going to use AG mode, Silence radar or put it in STBY before entering AG mode.

The only thing I notice with the GB6 over say, the CBU 97, is that the submunitions tend to be less accurate, or at least it takes maybe 3-5 munitions to score a kill, where as the 97 can kill with 1-3. Also, and I think this may be what you are experiencing, the GB6 submunitions tend to have a smaller "detection" cone than the 97's.

Oh yeah. Still I think the PAF should think about obtaining HMD/HOBS AAMs and updating their B.2s to the WS-13.

I find the JF the easiest plane to AAR second to the F18. M2000 has a super twitchy FCS, F-14 loves to shake and I overcorrect alot, Harrier is a big nope, the Flanker is as twitchy as the F-14 plus the FCS loves doing its own thing and AL-31s tend to spool asymmetrically. F15 and A10 are ok. JF and Hornet are a dream to refuel IMO.

Deka pls. Or at least if some feasible stuff like HMD, OBOGS, and possibly the engine update get backported to B.2/1 :music_whistling:

TACAN symbology on HSD can only be enabled if D/L is off with MFD button R5. You can toggle it on before turning on D/L, and it will show TCN info, even after you turn D/L on. That is because the arrow points to the course heading you should be flying as set in the TACAN page, not the TACAN source itself. You should reference the HSD for bearing info to the TCN station. (Provided you have TCN info enabled on HSD)

They recently added a notch filter simulation for the AA radar so slow and low flying targets will drop lock quickly. Unfortunately Deka mistakenly gave the A/G radar the same mechanic, so it's impossible to maintain a lock unless you are within 10nm from the ship. It's been fixdd internally, just wait for the next patch.

It's Datalink, coupled with the fact that MAP mode now detects ground targets much easier, it overwhelms the HSD with contacts. If you turn off DL before using AG radar, you should be fine.

I rolled back the driver, but I was still having this issue. However I think I found the culprit to be Datalink. When D/L is active, as soon as AG targets and Ships start appearing on my radar and HSD, my game stutters really bad and FPS drops to <1 after a few seconds. (not joking). If I disable D/L, the stutters are gone and FPS is normal when my radar finds ground targets. Disabling GND on HSD does nothing, I have to turn off D/L entirely ofherwise if my radar finds ships or ground vehicles the game slows down to a halt. PS: AG targets detected by the radar will also momentarily show up on the AA radar screen if you switch to AA mode. You can lock them up in AA mode and attack with SD-10, which is pretty funny.

It looks like a bug in the RU translation. It should say WMD-7 TGP.

EXP is not fully implemented. ED needs to implement it, as it is their API, not Deka's.