J20Stronk

Yes I get the pop-up, but I still only get 50 pts out of the 100 and fail the mission. I opened the mission in the editor and checked the win conditions. After 30 seconds I do get awarded the 50 points, and flying into the Sochi trigger zone also awards me the other 50 (I moved and spawned myself over the area at mission start.). But for some reason playing the mission all the way through, coming back to base after successfully flying to Sochi and destroying the targets I still only get 50 points in the debrief and the mission ends in failure. I know that you don't have to destroy anything, just flying into the Sochi trigger should be enough to pass the mission. I even changed the parameters so that you DO need to damage at least one of the parked aircraft, and that worked also, but only when I was testing it in the editor. In the actual mission I still only got 50/100, even after completely wiping out all targets at Sochi. My guess is that for some reason the 50 pts you get in the first 30 seconds are removed later in the mission, and only the SochiDetection pts are kept.

Can't seem to get past mission 3. I get there on time and destroy the Bears and Floggers. Then, I get BRAA call for the Flankers and are told to RTB, but when I land and end the mission, it says I've failed. I do get the Mission Complete pop-up after I am told to RTB on the top right, but again it says I failed on the debrief.

The radar now actually has to update between sweeps and uses trackfiles to predict positions between them. It is less precise in high bar, high volume scan settings. Likewise, the SD-10 will be less precise if you fire in TWS/SAM with a high scan volume/bar setting since it has to wait longer to receive updates. The trackfile may not match the target's position if it performs a sharp maneuver between scan cycles, which wil make the missile also do sharp turns as it flies to the target.

Only JF-17s on the same Net and AWACS should appear in the GROUP page. JF-17 is not Link16 capable; Link16 aircraft appearing in GROUP and donating D/L info was incorrect behavior that was fixed last patch.

1. The WMD-7 has a range of about 20nm to 22nm at best. You must be in AG master mode to enter Area / Point Track. Provided you are within 20nm and in AG mode, the TGP should at least stabilize in Area Track. If you want to go into Point Track, but the pod instead switches to Area Track, it could be that you need to add or increase the deadzone on your slew stick. 2. You need to turn on CLDP on the AAP.

I'm referring to the course line. In other aircraft the course line extends indefinitely from one end to the other and intersects the TACAN beacon at the input heading (which we can change in the TCN preset page, I know). It is always visible on the HSD, even if the TCN marker is not visible. In the JF-17 the course line is always this tiny little bar that is always the same size no matter the HSD scale. It gets cut off when it reaches the TCN marker and won't render if the marker isn't also visible on the HSD. It is virtually useless for navigation and even then, to make matters worse, for some reason it is affected by INS drift (seriously, why?)

Is this in-flight or on the ramp? If it's on the ground with the canopy open, then most likely your pilot is overheating. Pilot temperature is modeled, so if the mission takes place in a very hot environment (>~35°C), your pilot will overhear and black out.

@L0op8ack Speaking of which, the TACAN symbology on the HSD doesn't scale with the HSD's Zoom setting. It will always be displayed at the same size if you set the scale to 240 nm or 9 nm.

I think L0op said the WMD7 clears zoom, TV/IR setting and PT. Track as intended since it switches video sources and resets the lens.

Different launch rails. The rails for the SD-10/PL-12 are PF-12s. C-701 and PL-5 use smaller P-9W rails. The dual pylon, AFAIK only uses PF-12s. Not sure if there is a dual rail P-9W. This may also be why we can't mount SD-10, PL-5 or C-701 on the inner stations; it is unknown if the inner pylon can mount the rails on them.

The Advisory Panel will trip random failures after a short while when you push the Advisory Panel Light BIT button. No systems are actually malfunctioning, and anywhere from 1 to 5 failure will trip all of which will be random. The "failures" will last anywhere from 1 second to up to 10 seconds, after which they automatically go away. The same will happen if you push the BIT in flight. AFAIK the BIT only turns on all lights to ensure they are working for as long as the button is held. The warnings that are tripped appear to be random and last for a random amount of time, and there is no indication that it is actually running a second BIT for system fauilure detection. A similar issue also occurs if you sit in a parked, cold and dark aircraft for too long before starting it up. The Advisory Panel will show erroneous failures, and will continue to trip other random failures as you start the plane up. Most of the time, it won't even show failures that normally trip on start, like ECS OFF or CABIN PRES. Some failures may disappear as you start the plane, while others will remain there for the duration of the flight. Again no actual systems have malfunctioned, the debriefing screen will show that the plane is all right.

You can ask the Ground Crew to input the coords. for you before you start up . Comms Menu > F8 Ground Crew > F6 Update INS Coordinates > F1 Get Coordinates I always do that if I need to get up quickly.

OK, thanks for the clarification. Again, even if you hold S3 to designate up until release, LGBs will not drop, and only LGBs. Other bombs work just fine in DTOS.

Thing is though, even with GC alignment and HNS on, drift will begin to occur even as you taxi out to the runway. I've tested by spawning a jet already on the runway and swithing to the airport WPT. Doing gentle left end right turns on the tarmac is enough to misalign the INS, I even managed to get a couple hundred meters of drift by doing nothing except swerving the plane around on the runway. HNS didn't help restore the drift, so that is definitelynot working correctly. and switching to AG gave the actual correct position of the WPT which is incorrect (it should give me the "drifted" position instead) The Navigation systems are broken, it drifts WAY too quickly with even the gentlest of maneuver and HNS doesn't help restore the drift or at least slow it down. This issues havebeen reported before but have never been fixed.

So we have to manually drop LGBs ourselves and use the AUTO steering cues to give us a rough guide? It's intended behavior then? That's the thing, even when in parameters and holding S3 to designate and flying with the cues, LGBs still will not drop. All other bomb types will release once RC crosses FPM and TTR is 0. Hitting S3 again removes the cues but does not return the DTOS designate symbology, and no LGBs are released.

AUTO release mode does not release automatically when using laser-guided bombs. When the Release Cue moves down the Bomb Fall Line, pressing S3 Weapon Release will drop the bomb immediately, rather than waiting until the Release Cue overlaps the FPM and TTR is 0. To duplicate: -Load any LGB (GBU-12/16/10) -Release > AUTO -Designate using any sensor (TGP is obviously preferred, but occurs with any SPI designation) -Wait for RC to go down BFL and HUD TTR timer to countdown. -Hold Weapon Release. Bomb will immediately drop instead of prepping for release @ RC-FPM overlap/T-0 *This ONLY happens when using LGBs in AUTO, regardless if using TGP or other sensors to mark SPI. *Other unguided bombs release like normal when using AUTO with all sensors marking SPIs. *Holding S3 before RC starts falling/TTR countdown, LGB will not drop even if RC overlaps FPM. *Also related; LGBs cannot be dropped in DTOS. They ignore launch when S3 is held after designation and RC crosses FPM. If S3 is tapped after designation in DTOS, AUTO release cues disappear as if bomb is relased, except it does not.*

So I was rummaging around the MFD .lua files trying to change the color of the text and background of the displays I noticed that there are some .luas for pod pages. I managed to find what I believe is the .lua for the LD-10's seeker view, similar to the HARM seeker view in the F-18c when used in TOO mode. Can the LD-10 be used like the HARM in this way? Can we see what the missile sees, select and Hand-Off the LD-10 to a specific emitter? Is this coming later in EA, or was this added by mistake? I also found .luas for IRST camera (not TGP) and HMD rendering in the HUD folder. So, Two Weeks™? ;)

Before the patch I was testing these in Active Pause to simulate what these would be like if they were SALH and had the AFM/Spinning Rocket oscillation. In my testing @ a range of 4.8nm, 300kts release, 6000 ft high only 1 out of 9 BRMs missed hitting the 8 BTR-80s I set up. They were actually quite accurate, since all they had to do was fly directly down to the target. They weren't constantly trying to place themselves between the target and myself since I was stationary; that is ultimately what made them suck before. The Vikhr scheme over-exaggerated the AFM oscillation, which is supposed to be there, just not at the magnitude we were experiencing it at.

Some more TGP issues I found: * On cold starts if you start the engine, load DTC with pod equipped, turn on CLDP and immediately turn on TGP, the BIT/alignment on the TGP is skipped. Pushing any MFD OSB on the TGP page or cycling CLDP off/on BEFORE you turn it on will start BIT correctly. * When entered point track and target is lost due to aircraft or terrain masking, TGT RNG and Relative Velocity disappears from HUD. It should show range and velocity to selected waypoint, since that automatically becomes SPI when TGP is masked. *When in point track and you use the zoom in / out axis (the "smooth" one controlled by the T6 axis keybind or + and - keys, not S2 fwd/aft.), point track will be "lost". TGP will still follow target if it were still in point track, but bounding box disappears and you cannot slew TGP anymore unless S2 depress to unlock or T5 depress to re-lock in PT or A track. (Area track has neither of the two issues above, but aircraft or terrain mask does not reset SPI to WP. using T6 or +/- zoom does not break slewing in area track.) *Time to impact is way off. WMD auto-lases for an average 10-20 seconds longer after impact (though I think I recall someone saying this was intentional. Still, it'd be nice to have an actuall TTI counter for dropped ordinance separate from lase time.)

Modern MBTs are stil OHK from the rear and 1-2 on average from the sides. Very reasonable, considering a blown track or dead engine essentially renders the thing useless IRL. And those spots are generally less armored than the front.

According to DIS, the real SD-10 has a 100 second battery, then ED changed it to 80 to match the 120C. That change was unwarranted since ED does not have the documentation that proved it was 80, Deka does. Mostl likely the CCM change was an adjustment made to better reflect the new guidance laws. It should be much harder to notch and spoof with chaff than before, and it should no longer do the "notch wobble".

Yes, it's in the newest hotfix from today Tiger. Gloria; CCM was lowered from 0.15 to 0.08 fi_search was increased to 1.05 from 0.175 supersonic_A_coeff_skew was increased to 0.25 from 0.1 And battery life was increased to 100 from 80

YOOOOOO!!!!! THEY'RE FINALLY SALH ROCKETS YEEEEEEEHHH!!!!!!!!!!!! :cheer3nc::cheer3nc::beer::beer::drunk::drunk::v::v::drink::drink::prop::prop: also on a slightly unrelated side note SD-10 got it's 100 second battery life again and got a serious boost in CCM resistance. D.I.S. IS THE BEST :beer:

You can add the new lights and button textures to any own cockpit livery. Just copy the textures over and amend the description.lua with the ones from "JF-17 Better Lights"

Yep. display materials.lua changes thankfully pass IC and the advisory lights and MFD/UFCP buttons are just a cockpit livery.