J20Stronk

Does it actually work? Is there extra setup required besides INS alignment and HNS enabled on the UFCP? I always enable HNS to allow INS + GPS, but eventually waypoints, especially noticeable with airports (50-59), end up misaligned after long flights or hard maneuvers. I though the whole point of it was to prevent drift in the Nav computer, resorting to INS as a backup when necessary. (or even correcting INS drift automatically while it's active)

Ah that's a shame. I hope you are all safe, I know things aren't well that side of the world. Still thank you all for the updates. I see HOTAS controls for the HSD were shadow-patched in, thanks for that! If it helps, I think the radar's issue appears to be related to the way it stabilizes. pitching up lowers the antenna, pitching down raises it, and rolling 90 left of right makes the radar attitude-stabilized. You can see this behaviour with a waypoint on the radar screen, it'll jump around on the RDR page as you maneuver the plane.

Can we expect a fix for the radar attitude and altitude calculations today?

That's most likely INS drift. It's quite strong on this plane in particular, even with HNS on. Generally I get an error of 1-2 nm per 30 minutes of flight which again, is quite a lot.

The scan zone elevation appears to be bugged. It's scanning a couple of degrees below what's indicated on the FCR screen. I noticed I can see targets below my indicated minimum scan altitude on the TDC, so best bet is to make sure your minimum scanning altutide is higher than the target altitude

Can confirm. Antenna appears to be scanning a couple of degrees below the supposed center of the indicated scan zone. This only happens with INTC radar modes RWS, TWS, and VS. ACM radar modes work just fine in my testing. SAM and DTT modes seem to dispel this effect, correcting the scan area for as long as you have a target bugged in SAM or TWS/DTT. But it will offset downwards again upon losing lock. Oddly enough, you can see the effect of this in the PL-5's search pattern when you STT lock someone in an INTC radar mode and uncage the seeker. The missile will run its pattern BELOW the target box.

Viper IFF is borked, It even registers your ownship as hostile in the D/L. JF-17 IFF works fine, and so do other aircraft.

From the Changelog thread: I assume that this relates to the stabilization issue? Or is it unrelated?

The FPM looks correct, but the pitch ladder and artificial horizon are definitely offset down a bit. Also I'd like to add that the ADL cross is NOT indicative of the nose position and is offset down as well. For example, if you pitch up to align the ADL with the 10* pitch bar, the F2 view will say 11*. The 'Real' nose position is right below the heading tape and can be found by using the caged PL-5 seeker

1) Go to your DCS install\Mods\aircraft\JF-17\Cockpit\Scripts\MFCD\Indicator 2) In the file 'UP_L1_HSD_SA.lua', find 'local MAX_RWR_CONTACTS = 20'. You can edit the .lua with Notepad or Notepad++ 3) Change the 20 to a higher number like 200. 4) Save and play! This workaround will allow the HSD to show more contacts as the script catches up to delete or update older RWR hits. (It won't actually show 200 RWR hits. And no, it won't break IC or undo the patch changes where the contacts eventually get super fuzzy and unreadable along w/ the FPS drop. This is a temp fix until Deka fixes it officially next patch(es)!

The 802AKG has an altitude limit of 1,500 to 24,750 feet. Descend between those altitudes and try again. If you were between that range, then it may be a bug and you should investigate further and report it.

Description: When in any AA mode (INTC, ACM/DFGT), locking onto a target in TWS, RWS, or VS to enter STT, DTT, or SAM causes the radar antenna to gimbal with respect to the plane's attitude, rather than ground-stabilized like most modern fighter aircraft. In the attached replays, I was able to maintain a lock on the F-15 while beaming him upwards of 80-90 degrees left or right, so long as I kept him within 30 degrees horizontally relative to my plane's current attitude. Details: -Radar antenna becomes attitude stabilized when in STT, SAM or DTT. -Antenna elevation stays at 0 when locked onto somebody, and Ground-Stabilized in the MFCD is set to NOR = Ground stabilized. (I tried pushing the MFCD button for it but nothing changes. Not implemented?) -This occurs both in MP and SP. -This only happens if you lock someone into SAM, STT, or DTT. Otherwise the radar is ground stabilized when you are not locked onto anything. -HSD D/L contacts and antenna info also repeat this behavior, and will show incorrect polar position when locked on. -This applies to both cold and hot starts. To reproduce: Simply lock an enemy in any INTC or ACM mode to enter STT, DTT, or SAM. the antenna will now be attitude-stabilized to the plane rather than ground-stabilized, even if Ground Stabilize MFCD button is NOR. JF AA radar locked gimbal to attitude.trk JF AA radar locked gimbal to attitude 2.trk

The gears and gear bay still use a simple place holder. It's in their known issues thread. Eventually their 3D artist will finish them.

Ok then, the AKG launch is working as intended. However, the LS6 and GB6 still suffer from the reported launch bug, as RDY is crossed out regardless of altitude and speed. Also, the ALIGN bug I described still persists with all A/G smart munitions.

I had this issue only after I re-armed the CM-802AKG. I joined an MP server with a cold and dark JF-17, no weapons were preloaded. I loaded 2 AKGs and the DL pod. Those first 2 I fired and successfully guided them to their PP targets. After landing and rearming another 2 AKGs, those failed to fire. Also I could not cycle between my PP targets with the second pair; I could with the first 2. And the warm-up timer got stuck at 3:00 minute alignment after I turned them off and on again in attempt to try and fix the issue. I have also seen this happen with C-701s, where the cooldown timer stays at 3:00 and does not countdown if shutdown and resatrted after rearming them. EDIT: After playing around with them some more, I found out that the CM-802AKG will not fire above 24,600 ft. RDY is crossed out below the ALIGN window in the SMS page if I go above that altitude, but gets reverts back if I go below said altitude, even if the Alignment is not completed. The frozen alignment issue is still present if I turn the missile off, then back on again, but you can reset it by clearing the stores and manually loading them in the SMS' LOAD page. That will allow the alignment process to run again.

You need to activate jamming with T2 Forward on your HOTAS. Mode 1 activates jamming when an emitter locks onto you Mode 2 constantly jams all emitters detected by the RWR.

So like, are you gonna tell Deka what needs fixing and what broke or not?

I've had similar problems attacking an EWR; Fired a couple of bursts at it, I actually got hits on it (yellow sparks, no dust kicking up from hitting the ground) but no damage dealt. It's strange because the JF has a 23mm gun with, I'm assuming HE/AP mix, uet it can't kill an EWR site, but the Hornet's 20mm HE-I can. Then again, there are a couple of problems with Air Defense units and the JF. Some of them deal with a .dll issue, which only ED can fix. Maybe this is one of them.

Are you using ACT mode? That's what it's supposed to do in ACT mode if no emitters can be found near the SPI.

IIRC, in the D/L video the W/L designation is a hard coded assignment base on which plane is flight lead in the Mission Editor. For example, Enfield 1-1 will always be L, and Enfield 1-2/3/4, will be labeled W, regardless of who is MAST of the D/L connection. The MAST unit of the D/L connection is indicated by the [*] next to the ID in the GROUP page.

Much like other bugs, the CM-802AKG and C-802AK do not function properly in aircraft that are started cold and dark. In a cold start the CM-802AKG fails to guide itself to the target regardless of mode used (DIR, COO, or MAN). Instead it begins to fly to the top left corner of the theater's playable area, for example an AKG missile fired from Kutaisi will turn to heading 292-293 and fly at the altitude it was fired from before de-spawning a few moments later. The MITL POD page shows this same heading and LAT LONG of the missile properly, but no TKJ, no RP#s if fired in MAN on the OSB L1 and L2, and shows 0nm to target. In an airborne or pre-started plane on the ramp or runway, the missile behaves just fine and follows the selected guidance options you set for it. On the other hand, the C-802AK simply does not fire on a cold start plane. Master arm is on, Alignment period completes, and target is set in all modes, but the missile will not come off the rail. Again, the missile fires and guide itself just fine in an airborne or hot-started Thunder. DCS log.txt below PS: Also, it doesn't matter if the missile or DL pod were re-armed, just if the aicraft was started cold or not. PSS: I did wait for the 802AKG to fully align as well. dcs.txt

It is a known issue which ED needs to fix since it's a problem with their AG radar API. For now set your display res to just 512 or 1024 WITHOUT every frame.

Only RP# and PP# seem to work, but they have to be capitalized. WP# doesn't seem to work, regardless of letter case...

Does anyone know how to create waypoints using the F10 view? Red kite mentioned you could use the F10 to create Waypoints, Markpoints, and Pre Planned Strike points and upload them to the DTC before takeoff, but I don't know what to call the markers to turn them into something the plane can use.

If I cold start in a clean plane and equip the WMD7 through rearm, it will not align and gets stuck saying "Time Remaining: 0" when I turn it on. I also noticed that it is not in the stowed position.