DSplayer

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.

I already started a discussion about this topic on the HB Discord but I decided to post it here as well so others can also see it better and potentially add to the discussion. Link to Discord discussion thread on the HB Discord: https://discord.com/channels/1071433028045377637/1108578943168159785 Our current DCS F-14 LANTIRN pod has a pretty blocky imagery and during the development of the RAZBAM F-15E's LANTIRN pod they had something occur with the blocky naturesimilar but they recently posted how they changed/fixed their pod's anti-aliasing so it isn't blocky (while retaining the same resolution if I remember correctly). I was wondering if our current F-14 LANTIRN's blockiness is correct or not since it seems a bit too blocky. What was pointed out to me by Naquaii on Discord was that what I have gathered with my limited research is not really concrete evidence to prove that our current blocky EXP mode isn't incorrect and that the current implementation of the LANTIRN was coded from the information they had to the best of their knowledge. RAZBAM's LANTIRN change: RAZBAM Discord message regarding their implementation of the EXP mode quality on the F-15E's LANTIRN: https://discord.com/channels/536389125276827660/544231925263630336/1106486611757252659 Images from the 2004 Fighter Fling video: https://imgur.com/a/N1eSN Fighter Flint 1995 with developmental LANTIRN footage:

The new patch is out with the PL-12 equipped with the new scheme. Hopefully, it performs a bit better than the SD-10.

Make sure you have the desired weapon selected.

Turns out Spudknocker was given the wrong build or recorded on the wrong build.

There is no (perceivable or visible) difference between the aerodynamic and engine modeling for the AIM-120 API and the SD-10 API as the majority of the differences are purely seeker based (and those seeker changes seem to be in the backend). Technically it would be easy to convert over from the SD-10 to the newer AMRAAM API for personal testing but I am currently unable to at the moment. The last time I attempted to do that, there were some unforeseen abnormalities when using the modified SD-10 but that was months ago. EDIT: I've actually decided to port it over myself now and it seems to perform pretty well with my 5 mins of testing. I'll post it here so you guys can give it a check. Most of the values should be the same as the normal SD-10 with some variables rearranged so I could manage them a bit easier when comparing with the AIM-120C-5. This zip file should be OVGME ready. It's for your root DCS installation folder. SD-10 New AIM-120 API May 2023 DSplayer.zip EDIT 2: Ok one of my buddies decided to test this out and it does appear that there is probably something that is required from the JF-17's so that the INS works correctly and I am unable to change anything so it works properly. At the moment it appears to just fly straight after losing lock and doesn't feel like it has an INS. Feel free to test it out more however.

Slight update on the update status of the mod. I'm planning on updating this mod after the next OB patch comes out just in case something gets changed like last time. We're pretty close to the monthly OB patch so it would save me some effort if I just wait it out. Also hopefully I will have an updated drag model for the Hawk missile in this upcoming patch so it doesn't reach Mach 5 on the deck.