ExNusquam

I don't know if this has been reported already, so posting it here for tracking. If there are two clients spawned in on Elevator 2 (the 2 first spots that are taken when spawning), the deck crew will be unable to taxi them unless one aircraft releases their slot and respawns. Observed behavior is: -Both clients spawn, salute once and proceed through startup. -After selecting salute a second time, both aircraft will receive the message "Awaiting Requested Crew Member", which will not clear. The Deck Crew highlight will appear over the yellow shirt in front of the aircraft, however he will not direct the aircraft. -If one client changes slots, the other will immediately receive taxi instructions from the yellow shirt. No track available due to lengthy/large multiplayer mission, however behavior has been observed before:

I absolutely agree, and would happily accept some compromises for the sake of compatibility with other modules. However, we have excellent sources for how it should work for the Hornet - hence why I'm reporting it. I'd like bombs that at least something predictable (like go high-order with reasonable settings applied).

I note that this got moved out of the Hornet forum (put there for specific avionics refs for the Hornet) - is there a status on this (reported, WAD, under investigation?)

Writing up a series of conditions that document the FMU-139 is not functioning correctly, and the avionics interfaces within the F/A-18C do not match expected behavior. Tracks are attached for all conditions. Source for all of this is here: https://www.fighterpilotpodcast.com/post/understanding-the-fmu-139-and-its-employment-options - Source description "This unclassified article was originally penned in 2008 for inclusion into a classified Navy tactics periodical. Various grammatical changes have been made to change the tense of the text from what was expected to happen in 2008 to what is now known over a decade later." This is a fantastic source that is unclassified, publicly released, and includes avionics depictions that is contemporaneous to our F/A-18C. Condition 1: A/C Loaded with 1xLGB and 1xJDAM, each with an FMU-139 set to 10s ARM Delay and INST Function time Expected Behavior: Both weapons should have either EFUZ w/INST/DLY1 as options, ARM function should give options for either 5.5s or 10s. Alternate: MFUZ Option with OFF/TAIL options. ARM function should give 6s/7s/10s/14s/20s options Observed behavior: JDAM shows EFUZ w/INST/DLY1 as options, ARM function is not usable, JPF Page/Function was incorrectly available (Showing 14s Arm Time), however the weapon honored the 10s arm time (went High-Order after 12s TOF). Dud cues honored 10s time set on loadout page. LGB incorrectly displayed EFUZ w/INST/DLY1/DLY2 options, no Arm Function. Condition 2: A/C Loaded with 1xLGB and 1xJDAM, each with an FMU-139 set to 14s ARM Delay and 10ms Function time Expected Behavior: Both weapons should have MFUZ (EFUZ not valid for arm times >10s) with OFF/TAIL, Arm function should give 6s/7s/10s/14s/20s options. Weapon should execute 10ms delay on function. Weapon should go High-Order with specified function time with TAIL boxed. Alternate: if EFUZ must be used, weapon should go High-Order at specified function with DLY1, and on contact with INST selected. Observed behavior: JDAM incorrectly shows EFUZ w/INST/DLY1, ARM function not usable, JPF Page/Function was incorrectly available (Showing 14s Arm time). Weapon went High-Order with INST selected (not correct for this Arm Time selection) but duded with DLY1 boxed. Condition 3: JDAM with FMU-139 10s Arm Delay and INST Function Time, DSU-33 Expected Behavior: EFUZ Option with INST and VT1 as options. INST should function on contact and VT1 should function as airburst. Alternate: MFUZ with OFF/TAIL options. Airburst always functions. Observed Behavior: EFUZ option incorrectly shows VT1/INST/DLY1. Arm Function is not usable. VT1 results in weapon dud (incorrect), INST executes airburst (incorrect), DLY1 duds weapon. Condition 4: JDAM with FMU-139 14s/INST Plugged Extended TOF Expected Behavior: With EFUZ option (FFCS Mode), JDAM should have TOF limit of either 60s or 240s. With MFUZ (FZU Mode) JDAM should have unlimited TOF. Observed Behavior: JDAM fails to go high-order for TOF of 139s. Need further testing to verify what actual TOF limit is (but it's clearly not one of the expected ones) Condition_1.trk Condition_2.trk Condition_3.trk Condition_4.trk

Per title. Selecting the HUD Attitude Selector Switch to "STBY" should remove the Velocity Vector, display a fixed "W" for the waterline, and HUD attitude information should match the Standby Attitude Indicator. The DDI ADI page correctly matches the attitude information provided by the Standby Attitude Indicator, even with a variety of attitude excursions. standby INS bug.trk

Agreed - this would be very helpful.

Our squadron has been using this for a while, it's a great little program:

1 Week Bump. Can we get a status/tag on this?

Entering TWS Auto will remove ability to control antenna elevation. To replicate: 1. STT on contact 2. Enter TWS via PB10(Automatically selects TWS AUTO) 3. Observe no antenna elevation control 4. Select RWS via PB5 5. Observe antenna elevation control not regained in RWS. Track attached. antenna_elevation_bug.trk

Resurrecting this thread, per standard aircraft characteristics for the AGM-84A, a declassified document from 1974, Harpoon should cruise at 50-200' before executing it's terminal maneuver. http://www.alternatewars.com/SAC/AGM-84A_Harpoon_SAC_-_August_1974.pdf

Check OS Elevation. You're looking below the target, when terrain elevation is ~700M.

There is a minor error in the hook bypass switch logic. If the switch is in Carrier, and the hook is down, the switch will not be held in Field. However, if the switch is in Field, and the hook is lowered, the switch is not released to Carrier. If the hook is ever down the bypass switch should no longer be held in Field. Track attached. bypass_bug.trk

If dropped below minimum altitude, the Harpoon will self-destruct after ~25 seconds, despite successfully transitioning to cruise flight. This appears to only occur if the HARM stabilizes fairly low altitude (<300'). If employed such that it stabilizes at a higher altitude (but still below cruise altitude) the missile will level off and transit to the target as planned. I'm not aware of any documentation for a Harpoon self-destructing before it reaches programmed destruct range. Track attached. HPD Self-Destruct.trk

Per title. AIM-9X seeker will not move up or down from the aircraft waterline. Azimuth slew appears acceptable. Track attached. AIM-9X Bug.trk

You can currently adjust the scan center using the AZ/EL format, so this functionality now "exists" but still needs to be copied over to the ATK RDR format.

Check the A-10 employment videos here - these are the "real world" techniques, including Strafing, Bombing, Rockets, Safe Escape Maneuvers and low-altitude jinks. https://www.youtube.com/user/476vFG

One of the nice additions would be Doppler shift for moving objects so that you can't easily drop a designation on them. Some basic info the impacts of target motion:

Don't forget IRL you can cycle between the HSI, SA and EW pages using the HOTAS. The HUD+SA page should give you enough quick info, and the EW page is no more than 2 presses of the castle switch away.

Notso nailed it WRT the inclusion of additional terminal seekers. The push for newer weapon systems is in flexibility and multiple terminal options, not necessarily improving accuracy. And there is additional challenges IRL in terms of generating quality coordinates. It's not as simple as "use this sensor" as there may be various restrictions including range, squint and graze. I honestly think the "arcade" accuracy of DCS is probably producing realistic results, which is that someone in mission planning did the work and you can accurately employ the weapon. You could include things involving the constellation (flex power, etc.) but that's so far beyond scope it really shouldn't be included.

Not really an accurate picture of JDAM accuracy... The JDAM 13m horizontal CEP includes an allowance for 7.2m of Target Location Error (TLE). JDAM guidance accuracy/INS-error account for the remainder. The weapons are really, really accurate, especially if you have high-quality coordinates. DCS at present doesn't include coordinate generation errors from A/C targeting pods, so we should be seeing JDAM inaccuracies on the lower end of the spectrum. Modern GPS weapons are used for a variety of reasons beyond the "launch and leave" capability. The ability to determine a wide array of terminal conditions including impact velocity, angle and azimuth. This makes it the weapon of choice where the targeteers need specific effects on a target. Things like cave entrances, targets with possible overhead obstructions, etc. can't be reliably targeted with an LGB. And target penetration for hard targets is generally iffy with a PW-II class weapon.

Those T/W numbers are probably extremely generous about the installed thrust. The engine thrust number is derived from static test stand numbers. Installed thrust is often significantly lower owing to intake effects (which may vary across the airspeed range). I can absolutely assure you the Hornet does not have an actual T/W >1.0

https://en.wikipedia.org/wiki/Range_gate_pull-off

NineLine, I've submitted two separate bugs that are feeding into this issue, in separate threads, with tracks. https://forums.eagle.ru/showthread.php?t=270993 https://forums.eagle.ru/showthread.php?t=270992

Re #1. Make sure you're updating the AGE setting from the data sublevel. With AIM-120 selected it defaults to 4 seconds, which means that at anything more than a 140/2B sweep the targets will age out. 16+ will work for larger scan volumes. The other 2 are just how the Radar works (other bugs non-withstanding.)

The SLAM is actually about 2 feet longer than the anti-ship Harpoon, and anecdotally has a stupid nose high attitude during cruise.