Jump to content

enyak

Members
  • Posts

    22
  • Joined

  • Last visited

  1. I stand corrected, the AN/ALR-69 is older then: https://www.aef.se/Avionik/Artiklar/Motmedel/Nya_hotbilder/RadarWarnStory.pdf Though regardless the 56M still seems like it sounds off with audible RWR PRF chirps as heard in the video posted above. There's what sounds to me like some chirping after the RWR warning tones. https://youtu.be/_KdmzCQxTdY?t=205
  2. It doesn't look to me like the ALR-69 was even available in 1990/91 though. https://man.fas.org/dod-101/sys/ac/equip/an-alr-69.htm https://en.citizendium.org/wiki/ALR-69
  3. enyak

    ALR-56M Tones

    Removed: RWR Handoff Functions PRF Audio. This is more a function of the ALR-69. This would not be correct for the ALR-56M in our Viper based on SME feedback. https://forum.dcs.world/topic/206282-subject-to-change-desired-f-16c-systems-and-payloads/?do=findComment&comment=4988949 I don't understand what exactly got removed. The manual handoff function that allows you to designate the primary threat? Or the RWR tones? Right now the Viper seems to be in Diamond Float handoff mode by default even though the corresponding light is not on. On the PRF tones, they seem to have been in the Viper for quite a while. You can hear them in several 16-under-fire-vids for example clearly in this one from ODS (1991):
  4. enyak

    JDAM Loft

    We've just had the same problem using single-rack GBU-38 lofts at 10nm and 7nm on a 30° Loft from low-altitude NOE. Also had the same problem with a CBU-103. Could this be looked at? Not being able to reliably loft GBUs and CBUs is a tactical disadvantage.
  5. I don't think it's necessary to include VS in order for the Hornet to leave EA but I certainly don't want to see it omitted entirely as it serves a useful function: Detection at range and threat filtering! Even if it wasn't useful I'd like to see a complete representation of the major radar modes in our sim.
  6. Will we get the VS sub-mode (Velocity Search) for the A/A radar, sorting only fast incoming targets by their closing speed? I don't actually know if the Lot 20 has it but I don't see why it wouldn't. Wiki says the APG-65 / 73 is capable for velocity search at least: https://en.wikipedia.org/wiki/AN/APG-65_radar_family
  7. Apparently this is what the range marker looks like in the real thing. The inner target range marker sticks out a far bit and is clearly visible inside the NIRD ring. Additionally the super-imposed half-ring that designates 0nm-target range also leaves a stronger shilouette against the ASE ring. In contrast in DCS the range tick seems to be 2-3 pixels long and is ergonomically difficult to pick up: Ergonomically it doesn't make sense to me that the range marker isn't easier to see in our DCS-F/A-18.
  8. Can a mod please move this into the bug forum? Or should I just recreate the thread?
  9. Apparently this is what it looks like it in the real thing. The inner target range marker sticks out a far bit and is clearly visible inside the ring. Additionally the super-imposed half-ring that designates 0nm-target range also leaves a stronger shilouette against the ASE ring. In contrast in DCS the range tick seems to be 2-3 pixels long and is ergonomically difficult to pick up: Ergonomically it doesn't make sense to me that the range marker isn't easier to see in our DCS-F/A-18.
  10. Please give it to us NOW! :D It would be really fantastic to have robust support for more than 8 players.
  11. I really love DCE but I have a big feature wish! - More robust multi-flight package support for MP (maybe even more than 2 flights?). It already works well enough but sometimes the join steerpoints can be a bit weird / misaligned for completely successful TOT. - Dedicated HOLD Steerpoints with PUSH times for ingress. This too would improve multi-flight package gameplay even more and give better quality TOT
  12. I can't get the catapult working in the SuperCarrier campaign. The groundcrew just stands around doing nothing, I think it's actually misaligned. All campaign settings are default, fresh install, only path.bat modified.
  13. You are absolutely right, I mistakenly switched it around. Let me try again: COM1 / UHF should be AWACS + ATC COM2 / VHF (lower frequencies) should be Package Comms Basically for the Falcon campaign it boils down to: It's necessarry for the package comm to be in the lower VHF frequencies so that global comms can be simultaneously used.
  14. I have a problem with the Comms in the Falcon campaign: - Package Comms should be on UHF / Comm2 - AWACS and ATC on VHF / Comm1 - UHF / Comm2 is currently misconfigured to unattainable frequencies, should be something like [2] = { --radio 2 min = 118, --minimum radio frequency in mHz max = 137, --maxium radio frequency in mHz } Not complaining about the otherwise great work, just what I noticed.
  15. > - Over Persian Gulf : Hornet, Tomcat, Mirage, Falcon, Harrier, Viggen and IRIAF Tomcat. Delighted to see the updates campaigns! But where is the updated Falcon DCE? :) Found it, it's here: https://www.digitalcombatsimulator.com/en/files/3309674/
×
×
  • Create New...