J20Stronk

I've made a .trk file to show what I mean. I had a MiG-21 fly towards me then make a 90 deg. turn right while also dropping it's speed to have it notch my radar. As you can see, my radar enters MEM mode two times: once it dropped for about 3 seconds before it reacquired it and kept a solid lock, but then shortly after it entered MEM mode again. During that second MEM mode period, you can see the TD box jumping backwards ever so slightly as if it was updating target position, even though the TD box was blinking meaning it's still in MEM mode and it supposedly can't find the target. Not only that, the TD box blinked for a solid 32 seconds after the radar entered MEM mode that second time. Also worth mentioning: in the track file I show off 2 more bugs that I have discovered involving Velocity Search. First is the fact that VS mode will show the range to any detected targets on HSD with Datalink on. This is obviously not possible since VS does not measure range at all, only target velocity and bearing. (there were no AWACS in the mission, only me and the MiG) Second is that hits found in VS can transfer over to other radar modes, allowing you to bug them in RWS/TWS at a much greater distance than either of those 2 modes can normally detect and/or track targets. You can see when I switched to TWS, the VS hit was visible and trackable, but when I let the radar sweep over it in TWS without bugging it, the trackfile disappeared. Normally, TWS will find this MiG at 35nm with the variables from this scenario. In the .trk VS picked him up at 55nm, at which point you could S2 Left twice to go to TWS and quickly bugged the target before the radar clears the trackfile. Thank you for your time. JF AA radar bugs.trk

The thing is, even though the radar enters MEM mode, the HUD TD box and trackfile in RDR page will still update the target's position when the beam goes over the it. After the update, the radar will still remain in MEM mode, with TD box flashing. After the 8 seconds, the bugged target will not be dropped from the radar, but only if it's bugged in TWS or SAM. STTs do drop after the timeout.

The Kh-29T is not meant to be used in Low-Light/Nighttime; it has a TV seeker. Also the Kh-29T does not correlate its seeker with the Merkury LLTV Pod, meaning the Kh-29T will not lock on if you use it. You have to use the Shkval.

HUD SPI offset (number with L or R next to it, above DeltaT time to target) reads 0L or 0R when the SPI is vertically centered on the HUD. The HUD SPI Directional Indicator (Diamond with arrow that points to SPI) is also bugged and may suddenly jump to the opposite end of the HUD when approaching 90Deg. offset angle to SPI. (You can see this on timestamps 0:45, 1:30, 1:40 and 1:56 in video) Example video below.

WMD7 external model animation does not match where you are looking at in the POD page. Video example below.

Can confirm, AGM-154 also go M 1.0 when they are about to impact. It is scheme-related behavior, not just an LS-6 thing.

Thank you for addressing the issue! As far as the reduced symbology glow during night mode, all I did was reduce the color_night values in the MFCD_init_COMMON.lua file from 1/2 of the day value to 1/5 of the day value. ie. Color_green_day = {0, 1, 0} Color_green_night = {0, 0.5, 0} to Color_green_day = {0, 1, 0} Color_green_night = {0, 0.2, 0} I tried to keep the white color of the AA RDR symbology, but I didn't since the symbology wouldn't dim when I set it to night mode had I kept it white. You can see that issue in the last screenshot; only green, red and yellow materials dim when set to night. Some materials like White, Blue, Blue_L and others do not.

Are these being worked on, or is it at least planned to improve the render of these screens later in the year?

Some images to show what I mean: DMAP: POD/TVIR/MIL Seeker: Something I forgot to mention in my OP, some symbology and and text, for example the POD or RDR page are also no affected by the DAY/NIGHT switch; they will remain at the same brightness as in DAY mode:

The MFD DAY/NIGHT and BRT/CNT switches do not affect any TV_Render viewports, ie the TGP, TVIR, MIL and DMAP renders. When flipped to NIGHT mode, all of these screen renders retain the same level of brightness as they would during the daytime, which makes these screens extremely overexposed and very hard to see at night especially the DMAP on the HSD. The POD, TVIR and MIL renders are also not affected by the BRT/CNT buttons and they along with the DMAP do not have the screen glow effect when displayed.

Can confirm, even with a blinking TD box on the HUD (meaning radar did not find the target in the sweep at the expected location and it has entered MEM mode), the radar will still magically update itself with the target's true location and heading and will not drop the lock, no matter how long the radar says it "can't find the target". Also happens in SAM and DTT modes. Notching in STT behaves as intended and will drop lock after TD box blinks, and it will also not show the true location of the target while it blinks/target is lost.

Yep, I have encountered this a while back with other weapons as well. ie the LD-10s will have a weird targeting mode or firing amount if I reload DTC from another weapon type. I do know of a workaround: Re-select the weapon using MFCD L3 in your currently selected profile. That will properly reset the profile to the weapon defaults and it will also let you set new options properly.

That countdown timer was moved to the AG Parameters page. It is located on the Right MFD, bottom of the display when you are in AG Master Mode. That page also contains coordinates of the selected SPI or PP target and other parameters for the selected weapon profile.

You need to perform Full GC alignment and enable HNS for GPS/INS to get them to hit reliably. Autostart performs a Partial FAST aligment, which will deteriorate the accuracy of the bombs significantly, even with HNS enabled.

This problem was not actually fixed, the HUD SPI marker still points to the True Coordinates and not the INS/Drifted Coordinates in AG Master Mode. Likewise the WMD-7 and other sensors will still point to the True Coordinates if slaved to a waypoint and will not drift over time. Unguided bombs in AUTO mode will still drop on the True Coords and the waypoint/SPI will also not drift. INS weapons are affected by drift from the recent changes, however their HUD SPI marker will not visually drift when using them in TOO Mode.

Will you guys be finishing up the AGR in the near future then? I do have a list of bugs and of things to tweak that I've noticed: - S2 left to enter EXP modes does not render anything on the AGR screen. - TDC slew sensitivity in EXP modes is much higher than in MAP modes - TDC designation in EXP is misaligned; it designates as if it were still in the full scale MAP image instead of the EXP'd zone - GMTI and SEA1/2 modes drop lock very easily; most likely I assume A/A Radar notch speed gates are just copied over to A/G Radar. - EXP/DBS image is very grainy/low res compared to F-18, despite having a more modern and similar sized radar. (might be accurate? idk) - No SPI on AGR. Unsure if real one has a SPI on AGR. TDC is used as SPI stand-in but slight, accidental movements when TDC is depressed makes it no longer move with designated point; makes it hard to make out designated point in MAP/EXP. Appreciated the hard work guys!

... If we could get BRMs and other rockets on the inner stations on chistmas day... haha, jk... Unless...

3D external model is located in: <DCS Install>/CoreMods/ChinaAssetPack/Shapes/JF17 Cockpit models are in: <DCS Install>/Mods/Aircraft/Cockpit/Shape

This bug is also present if you jettison bombs and other weapons/equipment attached to the pylon it self. Missiles jett. off the rail and are properly deleted from SMS

That's why I asked for it. There's a lot of cool unused weapons including the PL-8B & C and the C-802A, the early version of the 802AK.

Do you guys have any plans to add more weapons and equipment to the JF-17, both new and existing in DCS? There are apparently some weapons that the JF-17 has IRL that we don't in DCS, such as: LT-2 500kg LGB (Basically a Chinese KAB-500L) and KG300G SPJ (More variety) LT-3 500kg Laser/INS bomb between WMD-7 and SD-10. (Laser JDAM!) Wingless, low-caliber variants of the LS-6 with secondary laser guidance (L/JDAM SDBs!!!!!!) CM-102 ARM missile (between GB-6 and LT-3) CM-400AKG AShM (400km-range Anti-Ship missile) And if you somehow get your hands on info for it, the ASELPOD I would've included the H-2 and H-4 TV guided SOWs, but besides a baseless Wikipedia claiming it can mount it without proof and the fact that it is a Pakistani weapon which you guys do not have easy access for, I do not think they will be added ever. Other weapons which we already have but I would like to see expanded on (Unless available info says otherwise): - Cluster munitions and High-Drag bombs on inner stations. - HE/Frag variant of the Type-90 unguided and BRM-1 90mm rockets. - M151 HE/Frag Rockets and LAU-3 19-round Pod for the western rockets. - Inner station rockets (pls) - C-701T on Inner stations? (Seems relatively smokeless and it was in those stations when the module first came out a year ago. Unsure if the PF-9 launch rail can be mounted on the inner station, however.) - C-703, basically the radar guided variant of the C-701T meant for small boats. - Different ammo types for the Gsh-23, like the MiG-21bis. AG-belt with API-T, AA-belt with AP/HE mix, and a general belt with Tracers Please consider these additions. If no further updates to weapons and payload are planned, then it is understandable. Disappointing, but understandable.

Well, I hope that ARM Pod Page .lua will get used eventually

So, is there anything in the way of targeting a specific emitter or type of emitter? These seem hit or miss when you lob them at long range radars with SHORADs as they seem to favor the SHORADs even if the more powerful long range radars are scanning or painting. I don't know if the real thing has some sort of accurate targeting mode for it like the F-18 HARM display or F-16 HAS page, but I imagine IRL the JF-17 doesn't just leave it up to chance when it comes to performing the important role of S/D-EAD

Is there any way to tell the LD-10 to prioritize certain emitters or emitter types? As it is right now, they seem to favor SHORAD and Search Radars, even when the SPI (if using ACT mode) is much closer to your intended, active emitter. Sometimes they will even engage different emitters than the one that has you locked if you are using SP mode. ie. it'll engage the Tunguska 1/2 a mile away from the SA-8 that is actively painting and firing at me. Other times in PAS, they will literally do 180°s and hit your friendly Hawk sites and other SHORADs than where you sent it. Is there some mode or prep settings you guys have yet to implement that will let us target specific emitters in the future, or is this thing just a Hail Mary, pray-it-hits-what-you-want type of weapon?

Finally someone else noticed. This has been an issue since the release of the module, but I kept hoping that a glaring issue such as this would be fixed without me needing to report it. Also, the HUD Offset angle only applies relative to the Y axis of the plane, meaning if you were to go abeam 90 and bank so that the belly of the aircraft is pointing at the target, the indication would read 0L or 0R. As you return wings level while keeping the same heading, the HUD indication would then increase up to the correct off angle.