MARLAN_

It's new, nice to see updates to the super carrier. I wonder what other undocumented radio comm was added

Maybe the contacts should be "normalized" such that they are appropriately displayed inside or outside of the AZ/EL scan volume for their range. I haven't looked into how it works IRL, this is just a logical assumption based on the fact the entire point of the scan volume box is to quickly indicate to the pilot if the contact is inside their vertical scan volume.

Per title. Seems to be isolated to just the Moskva although I didn't extensively test every single ship or anything. Edit: No track/launch indications, you do get search indication. SAN6.trk

I'm not seeing any issues

What are the other mods in the file doing? I'm just confused and not sure if I should continue using the mod or not per your suggestion but there are still other files present, do they still help performance?

It may be helpful here to add that a neutral coalition also returns a "hostile" NCTR print in the F-18, I wouldn't be surprised if it's a shared system with the F-16.

AGM-84D loses alignment when another weapon is selected (not deselecting weapon) I would have guessed it would work similar to JDAM or the SLAM/SLAM-ER in that you only lose alignment if you specifically deselect the weapon as opposed to changing weapons. I don't have evidence to provide for this if there already exists evidence that states the Harpoon should lose alignment if any other weapon is selected, this is just based on an assumption that it should work like the JDAM or other SLAM/SLAM-ER. A84DLoseAlignment.trk

It would be nice if we could export DDI's/HUD for use in Tacview or something like that (without requiring every client to need to record their screen/exported views), having a virtual "tape" would be immensely helpful for debriefs.

For your SA: In the F/A-18C we have in DCS, we should have a solid "A" on the ATTK page to indicate HPRF Active (Husky) and then change to a flashing "A" to indicate MPRF Active (PItbull) - currently in DCS we are receiving only a solid A (Note that it is not a requirement to go from HPRF to MPRF, depending on target aspect you can go directly to MPRF). (DCS F18 HUD is correct as is, assuming it is indicating active (HPRF or MPRF), the HUD does not differentiate between HPRF/MPRF only if it is active.) If ED doesn't have evidence for this I can indicate a page/index number for it, it's either in the FRM or 742 (as well as the other book) Also, does that mean HPRF active is implemented in DCS? We only lack the indications? Great news if that's the case, the indications I guess wouldn't be too hard to add.

The implementation in DCS is currently incorrect, it prevents you from designating until some arbitrary lower range. IRL you should be able to designate a track file immediately once it is created. In DCS this means a track file with radar contribution since the capability of the Hornet to designate offboard track files doesn't exist in DCS yet. Normally you can detect a fighter around 48nm in DCS but cannot designate until 44nm (also missing probability of detection, IRL there would be some chance to detect sooner or later, the lack of probability of detection removes the point of a lot of meld mechanics) In your video the contact is slightly below you which now also adds the unrealistic look down penalty which is why you don't detect until about 32nm (hard to see the exact numbers on my phone) and can't designate until about 28nm. IRL the look-down penalty should be much much less drastic, e.g. if normally you detect a threat at 48nm (based on DCS) co-alt, you should be able to see them at 500ft (hot, over land) at around ~42nm (if they were over water the look down would be negligible)

Haven't been able to find time plus a buddy to test in a short track yet, but over the longer flights I've done, ACLS has consistently only worked for the first aircraft who calls inbound, and none of the others. In my last test (was a full flight, so not a short track) the dash 2 landed first, but only the dash 1 received ACLS indication (since they called inbound first I assume) While I don't have a short track, could the official testers please investigate this bug, ACLS is quite literally unusable in multiplayer because of it.

I'm sure many have heard the annoying alarms constantly when you're flying on speed as every time you adjust the throttle it alarms. HOME FUEL should not be alarmed when: - Refueling Probe is extended (correct in DCS) - Weight on wheels (correct in DCS) - Landing Gear in DOWN position (incorrect in DCS) - Within 5 seconds of changing the HOME FUEL waypoint (I don't know, I didn't test this) Evidence: See FRM, Ctrl+F "HOME FUEL" HomeFuelLdgGearDown.trk

Use a controller (human preferably, or just spam "bogey dope" calls to the AI) to get range, shoot on timeline, continue normally. "Darkstar, Colt 11, strobes 360." "Colt 11, strobe range 35, 35 thousand, hostile." "Colt 11, fox 3."

XX SL should also be displayed after the 5 second LOST cue is indicated.

Any plans for in the future for AI to execute out maneuvers (skates/aborts)? Especially vs. active missiles like the AMRAAM it would be more effective and realistic to kinetically defeat missiles rather than trying to evade them. AI could use a timeline the same as real pilots which would work nicely with an AI decision tree. At specific ranges they would skate/abort regardless of RWR indication, high skill AI may be better at recognizing they aren't targeted and can press the timeline, lower skill AI may be worse at recognizing they were targeted and press when they shouldn't have and then execute their current evasion tactics.

Just set them back to the defaults and press SET again, no? You normally wouldn't want your weapon sets changed once set, so I'm not aware of any way to do this besides just setting them again. Or you can cycle the generators to give the jet the "slap" (but this will reset everything)

Could we mod DCS to remove those textures maybe? Or set the LODs to a very small range? I should look into this next time I'm home

Yellow light is too large and extends out of the box, red/green lights are fine.

It sets the altimeter using QFF not QNH, the closer you are to sea level, and the closer weather settings are to ISA the smaller the error will be. Try setting different temperatures and pressure settings in the mission editor (in addition to using higher altitude bases) and there will be a discrepancy. See here: https://forum.dcs.world/topic/305660-dcs-qnh-appears-to-be-qff/#comment-5046915

DCS automatically sets the altimeter incorrectly so you need to adjust it anyway.

To be fair, as far as I know, metal (like vehicles) shouldn't be matching the terrain even if the vehicle is "cold", ambient temperature would heat up the metal faster than the earth, and vice versa when night falls, there would be a temporary transitionary period where the metal is the same temperature as the earth. Currently in DCS, "cold" vehicles are nearly invisible to IR.

I assume when it said that at a merge the one-circle fighter will minimize turning room, it actually meant minimize turn radius? It's always beneficial for a fighter to take advantage of turning room (when possible) regardless of whether it prefers angles/energy fighting in that particular match up.

Maybe one day we'll get all three: Commit, Lock, and TUMA (target under missile attack) lines, the TUMA line would be especially useful.

Nevermind, I am wrong, I found an answer in one of the documents, the current DCS implementation is correct. Sorry! I feel dumb now

Looking through many schematics and other JDAM sources, nothing indicates anywhere that STEP/RELEASE should do anything other than change between priority stations and not missions, which requires the user to select. I'll double check with my F18 friend when I can, but he's been busy so it might be a bit.