toilet2000

Can confirm, same thing happened to me when I tested it on release day! If you can post the track file, I'm sure Deka would appreciate! :)

There are several misleading things in your statement. To the contrary, the "East" way is to autopilot absolutely everything. The Soviets were extremely good at designing autopilot and control systems, with most of their aircraft having some sort of autopilot (including approach autopilot as in the MiG-21 and its SAU). The Buran space shuttle basically needed no pilot. Moreover, nobody codes in "binary". Programming in pure "binary" with opcodes would be an exercise in masochism and you can stay on the same abstraction level by working with human readable assembly. The JF-17 was developped in C++ because it is recent. C++ hasn't been around for very long (especially in the aeronautics world) and that's the reason why most military aircraft are programmed in some older less popular programming language. The F-35 was programmed in C++, as it is much newer. Adding an autopilot is no trivial task and, since as you pointed out, a turn autopilot isn't extremely useful in a military jet, was most probably left out due to cost constraints. Moreover, this is the kind of feature that gets added during the lifetime of the aircraft, so I wouldn't be suprised a "fully equipped block 3 or 4" could get advanced autopilot functions, especially if a customer requests it.

The DBS modes are done via Deka's own AG radar implementation, as these are not available in ED's API. Basically, Deka was developping their own AG radar tech (but RBM and DBS), but they were not satisfied with the resulting effects and as such, they used ED's RBM AG radar API for the RBM mode. Now the EXP/DCS mode should not be accessible in the JF-17, but due to a bug they are accessible via HOTAS commands. The resulting images are clearly WIP and not working as they should, as you can see through mountains and way past the maximum range of the radar. Right now, the DBS modes look like a simple top down "IR" view with some added noise and special effects. So yeah, TL;DR Deka have said that DBS/SAR is not available in ED's API.

If I'm not mistaken, this has been fixed (next OB) according to: https://forums.eagle.ru/showpost.php?p=4131877&postcount=2 It seems like they computed the elevation using only half of the antenna beam width, so elevation coverage should be double what it is currently.

This is only true because: 1. Most DCS players have no idea of the capabilities of surface radars. 2. Most current day ops revolve around low intensity conflict with lots of civilians around. Those scenarios makes little use of all the capabilities of surface radars (such as an extremely large scan zone). There's a reason why AG radars are added to every single attack aircraft out there, including helicopters (think Apache Longbow) and surveillance aircrafts (E-8 JSTARS, Global Hawk etc).

When using the CM-802AKG in the MITL terminal phase, the slew control does not automatically revert to center when letting go the slew button. This seems to affect the "button" slew control, but I couldn't test it against an "axis" slew. This seems to be a bug, as in the demo video, the slew always revert to center, see: I included a track. Steps to reproduce: 1. Fire CM-802AKG 2. Wait for MITL terminal phase 3. Slew the seeker with TDC buttons (not axis) Thanks! JF-17_cm_802akg_slew_bug.trk

The quick manual has a usage guide for LD-10s. Basically, there are 3 modes: 1. Active: similar to HARM Pre-Brief mode, goes to your SPI and look for radar emission close to you SPI. 2. Passive: also known as maddog, starts seeking the highest intensity radar. 3. Self-Protect: starts seeking the emitter currently locking you. You're probably in SP with no emitter locking you, so that's why they won't go off. Try one of the other modes.

Can confirm this is an issue. See attached track. Same kind of issue as with the TPOD. JF-17_cm_802akg_bug.trk

Yep it’s definitely a bug. The luminosity of each symbol adds up to the other, so it gets brighter the more contacts there is. It should stay the same luminosity.

I think I've seen "rp#" and "pp#" for RP (30-39) and PP (40-49) points. I would guess "wp#" for waypoints (1-29), but I'm not entirely sure. EDIT: corrections: 1-29 are for waypoints, 30-33 are for RP, 34-39 are for PP, 40 is SPI, 41-49 are for mark point, 50-59 are for airports

The strobing screen when using a TPOD or TV/IR missile and A2G radar is in the known bugs for the JF-17. I can't say I've seen a performance difference when using the A2G radar in my experience.

Great! Thank you! I was a bit straight to the point in my bug report, but great job on the JF-17, it's a blast!

Alright, so I've encountered several bugs while playing in MP. 1. After a successful rearm (if no stores were installed) and DTC update, the WMD-7 targeting pod is stuck on "aligning" with a remaining timer at 0, without being able to uncage it (be it on the ground or in the air). The linked track is doing the alignment on the ground, but the same thing happens in the air. 2. The datalink contacts appear as enemy even though they are friendly. 3. RWR contacts are not updated with respect to INS data, so moving the aircraft arounds makes the contact appear at "false" position until an update. I think the same thing happens with the radar (although I'm not entirely sure). This is similar to what was happening before with the F-16 SAM mode, see: https://forums.eagle.ru/showthread.php?t=250827 See track (too large for the forums): https://1drv.ms/u/s!AoHepwqBQ7C3grUSzKCCjUi8SyatUQ?e=w9LSXv The track is a bit long, but the targeting pod issue happens at the beginning. The datalink contact issue appears right before the end, where I unfortunately shoot down a friendly because of that.

@kaoqumba Do you happen to know if DBS is implemented or not? I know back in August DIS said they still had issues with it and it might not make it into EA in Sept, but because of the delay, I thought there might still be a chance that it made it. Thanks!

No it's not. VS is a velocity search only-mode, which gives a azimuth and closure-rate radar picture. This is similar to the PD Search mode of the F-14's AWG-9. It should get it a some point, and yes it gives better "range" due to not having to compute the actual range of the target. As for SAM: I think the closest we have in the Hornet is the LTWS or TWS, but someone more knowledgeable might correct me. SIL vs normal: Silent cuts radar emission, so you won't get any returns.

That info dates back to the 26th of August, DBS could be in. I know back then they had still issues with DBS working correctly (but they had an implementation) and didn’t think they could make it in in time for early access (back when they sound they were aiming for September for release). We’re now closing in on December, so DBS could very well be in.

The notch filter is about the speed difference from ground relative to you. Anything flying below 100 kts even going straight toward you is going to be filtered out. The Notch filter is there to remove Doppler returns from the ground, whereas the Doppler "filter" (really not a filter) is just the absence of Doppler effect due to an object moving at your own speed. Anything flying at +/- 100 kts relative to the speed of the ground for you (either via moving perpendicularly from your direction or by simply moving slowly in your direction relative to the ground) isn't going to appear on the F-14's radar (with the Notch filter on). EDIT: Just to be more clear, you will never be able to see a heli flying less than 100 kts ground speed if your Notch filter is on, which is definitely something that will happen often for a heli (flying less than 100 kts GS).

AFAIK, it is possible to input an image of the target in the weapon's system and it will try and match what it sees with what is saved in its memory. The issue is that the weapon is not Datalink capable and from what I've read, it is done on the ground and not in the air. A TGP image of the target would not suffice. This would not really be feasible in DCS. Note: this is not official info in any form, but simply what I gathered reading online on that topic. Feel free to correct me.

A radar view of a Belgian F-16 seems to show the SAM scan pattern as it is in DCS currently. It is clearly not the same version as our F-16, but at least it gives the possibility that DCS' current SAM scan pattern might be true to life. At 0:40, you can see the "locked" target, with the radar staying for a time on the target (the inverted T at the bottom), then scanning around and so on, just like in DCS currently.

So... Are we still getting that MAWS and defensive systems video? :)

Great post Beamscanner! I'm curious if the tracking algorithms of radars use only a motion model like you seem to imply. Considering the Hornet's radar is capable of NCTR, I would assume some kind of appearance model (based off of the return waveform or the likes) could be use to enhance tracking and discriminate between closely spaced and maneuvering targets.

One of the use of that is something that I found to want to be able to do often: Whenever a target goes defensive and notch the target, it is often possible to still see it on the TCS (especially in narrow FOV) if below 40-50 nm. It still tracks the target with TCS but no radar track is available. Switching the radar to Pulse mode and slaving it to the TCS should therefore permit reacquisition of the target. So even outside of a jamming environment, this option would be quite useful.

The Kiowa Warrior does have a laser designator that can designate for other LSS/T and laser guided weapons (LGBs and Mav E's) IIRC.

https://forums.eagle.ru/showthread.php?t=250863 Already reported.

Thanks Santi! @NineLine I added a track (as short as I could make it) to the original post!