DSplayer

Notso did say there appears to be a bug with the ground handling that makes takeoffs and landings rather squirrely (hopefully I'm not reading his message out of context):

Since this isn't an official implementation, the way you should do it is to load the pylon it is on as a weapon that is supported in the A/G LOAD page. So, for example, you load pylons 2 and 8 as Mk 83 LDGP bombs and then use CDIP to fire them.

I would say the F-15E had no direct impact on the F-4E release with what Cobra reflecting that HB wanted to put more features into the EA release F-4E and it wasn’t directly affected by the F-15E’s release. Indirectly? Maybe.

I will say that while the documents might be declassified, they are generally not publicly available and getting a hold of the documents is a pain in itself. It's also good to note that a good amount of DCS' missile characteristics are estimates since it is pretty hard to get the aforementioned documentation regarding this type of stuff. Also, the Isp doesn't change in the way it does like you think within the files. With my limited knowledge (feel free to correct me here JNelson), the way the difference in lower and higher altitude performance is achieved in DCS is via the nozzle_exit_area parameter along with some other potential stuff. So if you were to reduce or enlarge that value, a larger performance delta would appear. Currently with the current AIM-54 simulation with the older schema/API, it doesn't really need any change and sticking with it's current parameters seem to do the job quite well. In the case of missiles like the SD-10 or AIM-120 which use the newer API/schema, the nozzle_exit_area parameter does have a pretty good influence on higher altitude performance. Imo, the current AIM-54 simulation in DCS is the best that we can get with the extremely limited information available.

Yep those are one of the only weapons that sort of work.

You can fire them via CDIP and the method described in the original post but you will not be able to track targets.

Allows for the EXTREMELY limited usage of weapons that will be officially added in the future and weapons that will be not added in the future to the F-15E Strike Eagle. Excellent mod in my opinion to make screenshots in DCS. To be honest, I was pretty bored and I wanted to mess around and make screenshots with weapons not yet available to the Strike Eagle. To use these weapons (in an extremely limited capacity and outside of screenshots), I would suggest loading them into the PACS as already working GBUs like the GBU-12 and using CDIP. **Breaks IC** Mod Link: https://www.digitalcombatsimulator.com/en/files/3331830/ Changelog: V1.0.0 - Initial Release V1.0.1 - Updated for new official weapon additions (JDAM now actually works) and to be compatible with latest OB version. Note: GBU-31(V)3B does show up visually and does work with this mod unlike the current OB version 2.9.1.48111.

Bug: The F-15E Auto Acquisition Modes that are supposed to use Medium PRF (Super Search, Vertical Scan, Boresight) all use High PRF instead. Can I reproduce it 100%: 100% How to reproduce/description: Step 1: Enter an Auto Acquisition mode that is supposed to use Medium PRF. Step 2: Lock up a target. Result: The radar will lock up the target but it will indicate it is in a High PRF mode. DCS Version: Open Beta 2.8.6.41363 (Multithreading) Mission File: F-15E Auto Acq Test.miz Track: F-15E Auto Acq Modes HPRF not MPRF.trk Video/Screenshots: (Guns Auto Acq mode is not shown in this video or in the track but it does also use HPRF and not MPRF). Page from the manual that gives a general description of the Auto Acquisition Modes and how all of them, with the exception of Long Range Boresight, use MPRF. Mods: I did not use any mods during these tests.

That screenshot is from the "An Outsider’s View Of The Phoenix/AWG-9 Weapon System" thesis paper. While I trust the document, it was written utilizing publicly available sources at the time (such as OSINT publishes like Janes) and mixing them in with actual specifications with the intention of being vague. This document was actually one of the documents used to create the original AIM-54 motor simulation before it was changed last year. I do have a copy of that document but I will say it will not help you in trying to get a clearer picture of the AIM-54's motor section.

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?