DSplayer

At least according to the manual, threat-based programs for MAN 2 dispensing are not available yet and it seems to just default back to the MAN 1 program.

Another particularity that I've found when aligning is that if you started your alignment too early after starting your engines (starting before they reach idle RPM), your alignment will kick to the HOLD mode when your engine(s) reach idle RPM. Advice is to wait at least 10 seconds for your engines to reach idle RPM before starting your alignment (this might or might not be accurate to IRL since on the Tomcat you want to avoid having any issues by having the INS ruined by voltage fluctuations iirc). Another issue that others and I have observed that can cause a HOLD condition is rearming while aligning.

Make sure to check the weather conditions in your missions. If the temperature is too high, you're going to hit a wall earlier than normal.

Bug: F-15E radar is unable to reliably track in TWS modes while in Active Pause Can I reproduce it 100%: 100% How to reproduce/description: Step 1: Fly against any aircraft in the F-15E Step 2: Enter Active Pause Step 3: Enter a TWS mode (HDT, 2TWS, 4TWS, etc.) Step 4: Designate a target. Result: The radar will attempt to maintain track but will lose track somehow (refer to video for reference). DCS Version: Open Beta 2.8.6.41363 (Multithreading) Mission File: F-15E Jamming AI Test.miz Track: F-15E TWS losing track in Active Pause.trk Video/Screenshots: Mods: I do not use any mods.

Bug: F-15E radar detecting non-existent jamming on SP mission (even with aircraft without ECM equipped). Can I reproduce it 100%: 100% How to reproduce/description: Step 1: Fly against any aircraft in the F-15E (this includes WW2-era propeller aircraft) Step 2: Enter Active Pause Step 3: Enter a Single Target Track while in Active Pause against the aircraft. Result: The radar will enter HOJ against that target. Exiting STT will momentarily show the target as jamming with a HOJ strobe but will then revert to a normal track. However, a TWS/HDT cannot be maintained. This bug will be reported in a different topic. DCS Version: Open Beta 2.8.6.41363 (Multithreading) Mission File: F-15E Jamming AI Test.miz Track: F-15E Jamming AI Test.trk Video/Screenshots: Mods: I do not use any mods.

If I remember correctly boat switch aft short will quick step between targets.

I will check the V1.2.3 release build I put out since my dev build allowed me to remove the fuel pylons. EDIT: Seems like V1.2.3 still has the fix I implemented so please verify you're using V1.2.3.

I've had this problem and the way I've remedied it was by entering an Auto Acquisition mode like Supersearch or VTS.

Assuming the track is correct (which it probably isn't), you seemingly dropped a bomb severely off target like overflew the target then dropped the bomb. Do you mind redoing this and recording yourself with something like OBS?

A track or video would be helpful btw.

I will have to think about it and talk to Spino and Space about it. On another note, I did just update the mod to V1.1.4 so hopefully that works out without any problems.

Yeah, the lack of probability of detection was what I expected since Quaggles' graph showed a hard number. I was more interested in perhaps how his analysis could translate in terms of maximum detection and STT ranges compared to our new Phase 1 values.

How would something like the APG-68 and APG-73 fair with your analysis compared to the current Phase 1 radar changes?

They just hot patched it out btw.

Btw, the F-15E is in the files as an AI only right now.

Why do the older missiles like the S530F, R-27s, AIM-9 and other IR missiles, R-77, etc. still use the older weapon API compared to other missiles like the AIM-120s and AIM-7s? I know the AIM-54 specifically hasn't been ported to the new API/scheme system because the AIM-54 has features that isn't aren't really possible with the new API iirc but what prevents porting over other SARH missiles like the S530F (which was newly added) and the R-27 family over since the "aa_missile_semi_active" schema is already used by other SARH missiles?

I think the P-3 version he was previously referring to is what we have now as the AIM-9P since our AIM-9P is rear aspect only much like the versions of the 9P prior to the P4.

Screenshot of the radar from the discord: "find the target" (https://discord.com/channels/1071433028045377637/1108849721566576671/1115457202849857706)

Unfortunately, this is basically an ED issue and Deka can't really do anything about it outside of switching schemes.

Fresh from the HB Discord

Thanks for pointing that out! Seems like something messed up when I was zipping it last time but I just reuploaded the mod so it should be fixed now.

Sounds like a good idea. Would probably get a bit monotonous having to program the MPD pages every time you hop in the jet.

V1.5.3 has been released: - AIM-23 Hawk drag increased. - HB weapon loadout limitations added (and the clean pylons for the fuel tanks).

I'm sure you'll be able to modify the description.lua so you can enable the model argument.

From my buddy's testing, it basically just has the same guidance characteristics as the AIM-120 which means it currently has a worse loft and some other weird performance quirks.