J20Stronk

It's definitely laggy, LCOS in particular is extremely sluggish compared to the Flankers, Hornet and Eagle. Even the Tomcat's boomer-ass radar has a better Lead-compute gunsight than the, "most modern aircraft in DCS". Sure SS-LC are "better" but they still lag a bit and could use some tightening, not to mention the rendering bug. And ACM modes are pretty bugged rn: Tomcat has a fully working VS ACM mode with correct bar and degree count, and AFAICT Hornet does too. We got the super slow 30-bar, 3 degree scan. S2 depress doesn't work properly since the radar will immediately reacquire the target you just unlocked. Using BRST and HACQ always sends the antenna elevation to the top so you have to wait for it to come back down to start scanning the correct area. All these bugs and oversights unnecessarily handicap the JF-17 in a dogfight. It'd be a hell of a lot more dangerous if these issues were resolved.

Deka need to start prioritizing Gunsight and ACM radar improvements. The new FM kinda makes it a decent BFM plane, even if the gun itself is cruddy. The biggest issue isn't even the gun imo, but rather the incredibly laggy gunsight and buggy ACM modes.

YSK #2: the Su-25's S-25L rocket spins and is SALH btw

That's why it wasn't firing, there's a new keybind for the designator. Thing is, how does this work on the real jet? Because it doesn't look like it's tied to a HOTAS function on the aircraft, it's just a separate keybind in the SENSORS tab.

Trust me when I say that range is not the issue we have with them. :smilewink:

Codes are separate. When LSS is off, you're using the "designator code". When you push R3 to enter LSS, you are now using the Search code. You can edit by pushing R4 like with LSS off.

The best solution while waiting for lazED to rework their spaghetti guidance code and add SALH spinning rockets would be to just give it the L-MAV scheme. Just remove it's lofting autopilot (this is possible), nobody cares if the rocket spin or not. In fact, the rocket won't spin with the current scheme if EFUZ is set to SAFE, it just flies straight. (Which is also unrealistic since the rocket would spin regardless and yet, you can't tell it's not spinning from the cockpit.) With L-MAV scheme buddy-lasing will be possible, the rocket won't react to the way we fly after we fire it since it won't have to constantly put itself between us and the target, and most importantly this "bug" introduced 2 patches ago would most likely disappear since it no longer rides around a laser beam. No more of this, "fly straight to get a 50% chance of hitting and a higher chance of dying or shoot maneuver, and miss 100% of the time."

YSAK, the whole swerving / guidance bug only seems to happen if you are in F1 view If you switch to any other view, for example F6 and spectate the rocket, it'll actually fly nice and straight down to the target. This is guaranteed to hit so long as you do not fly too violently after launching the rocket.

It's the Pneumatic-Hydraulic test switch. It doesn't do anything right now. I think it's supposed to trip the "Low Hyd." and "P. Low" sensors and warnings

All modes are kinda crap right now since there is something wrong with each of them regarding antenna speed and search patterns. For now if you want to do WVR fighting, i'd say Boresight Acquisition is the best mode.

SAM has 2 submodes that control its Scan Width and Bar count. ASM, the default mode, automatically sets the SW and Bar based on range to the target. When HPT is beyond 20nm, SW is +-30 degrees, 2 bar scan. Within 20nm, SW is +-15 degrees with a 4 bar scan. NAM lets you control SW and Bar count manually.

Looks like the HSD/AG radar issue described by hi41000 has been fixed! I no longer drop into the single digits with both D/L and AG radar on at the same time in MP anymore! Well job, good done!

Dang, what was your fuel state when you began the trek back? At gross weight, fully fueled and no externals it has a TWR of 0.97 so a zoom climb to 30k is believable, even with the extra weight and drag of the pod and pylons since you'd still have well over 1.0 TWR But only 1700lbs burned while supercruising at 1.4? That may need some tweaking.

From my experience, the JF now retains energy much better in mid to high AoA than before. You no longer lose 100 +kts in gentle turns at mil power. The RD-93 now cranks out more thrust in MIL power and sucks in more fuel when you're going really fast (while also putting out even more thrust, ya know, like a real turbojet should) Basically, it's now putting out the expected power and retaining energy like an aircraft with a TWR of > 0.70 should (that's how much TWR it has when at full t/o weight, back then it fel like a TWR of 0.4-0.5) If set up with 2 PL-5 and 50% fuel, you have the same TWR as an F-16C fully loaded and clean, and you can definitely feel it. It practically dances when you're light, and no longer feel like a fully loaded A-10C when weighed down.

IDK man. I'm gonna trust in Deka that they did some new tests or got new info on the missile. I did run a couple straight line tests though: It ultimately behaves mostly the same as before. The SD-10 does have a stronger booster stage than the 120, plus the extra sustain stage which is supposed to activate later in the loft. Once that gets added, it should be even stronger. (If Deka were to give us an SD-10A) The cut in battery life did hurt it's max range, but it's still the same missile as before kinetics wise (at least in a straight line, it may be different when chasing and maneuvering)

Could you guys for the time being just make it behave like a Laser Maverick? Is it possible to make it so it flies right into laser without the Maverick autopilot and loft? If so, the pros. of the L-MAV scheme outweigh the cons. IMO Pros: - This swerving bug would be fixed. - Ability to buddy-lase - Launcher-ship maneuvers no longer affect guidance of rocket. - Easier to attack multiple targets via buddy lase and BRM pods with different laser codes. Cons: - Rocket won't spin - BRM may be too accurate. Since spin behavior is not present, less likely to oversteer away from target. - If MAV AP/loft cannot be removed, missile may be too slow to reach tgt before battery dies at decent range (4.0nm - 4.5nm); obvs. too advanced behavior for low cost SALH rocket.

It still beats the AMRAAM By about 5nm. Before it would beat it by about 10nm since it would continue to fly 20 seconds longer before the battery ran out and fell fell from the sky. The biggest "nerf" is definitely the battery life reduction; it now lasts as lon as an AMRAAM. Drag and Thrust are still pretty good and competitive.

Battery life, 1st rocket stage thrust and detection cone were reduced. Supersonic lift, aerodynamic multipliers and 2nd rocket stage thrust were increased. Overall, it's more in line with the current AIM 120C, its drag is more believable. It's performance should be better once dual impulse motors are a thing with the missile API.

Distance to WP is "ground distance", not true distance. In AG mode if it is used as SPI, the HUD will show "true distance" to WP as, "RNG xx.x". HSD and the WP info on the lower part of the HUD will still show "ground distance"

I think he means that the pod returns to Area Track moments before impact, not just the laser shorting too early.

My mistake, it's supposed to go to STT. It currently does not

Got a couple bugs to report on the AA radar Velocity Search (VS) mode. 1. No matter how fast or slow you and the target are closing on each other, it is impossible to lock and enter VS-STT in AA radar Velocity Search mode. In the manual, it says you can bug targets in VS and enter VS-STT. TDC depress on a VS hit currently does nothing. 2. The radar in Velocity Search can detect large targets beyond 80nm, but they will not show on the VS radar screen unless they are within 80nm. You can test this by setting up a large target like a Tu-22 closing fast @ 120nm with a friendly AWACS. The radar will detect it easily, as indicated by the Datalink SA (no bottom bar on HSD contact.), but the target will not be displayed on VS radar scope until he is <=80nm. It is assumed range is irrelevant in VS mode as no processing power is used to calculate range (hence the detection range bonus of VS), so this behavior does not seem correct. 3. The radar will store VS hits for some time in memory even if you switch radar modes with S2 left. This means you can use VS to find targets potentially 80nm or beyond, quickly switch to TWS using S2 left and bug the target at an extended detection range than TWS or RWS. Again, the radar is not calculating range in VS and should not be able to determine their distance using it. More importantly VS MEM hits should not transfer to RWS hits or TWS trackfiles. I have found a similar issue with ground units detected by the AG radar GMTI and SEA1/2 modes, where the hits stored in AG radar MEM will transfer to AA radar modes if you switch to INTC mode. ^You can then actually lock and engage ground targets using the AA radar with SD-10 :lol:

Praise DEKA! :thumbup: :pilotfly:

Both, I hope. Cause if #1 is intended behaviour then AVIC Chengdu is smoking some serious doobies

Jesus that Buk missile isn't a missile at all. It's a frickin' school bus. As soon as the motor burns out, it bleeds almost 50% of its speed in just 5 seconds (~850 kts). There is no way the real missile is that crappy.