Jump to content

enyak

Members
  • Content Count

    16
  • Joined

  • Last visited

About enyak

  • Rank
    Junior Member
  1. 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.
  2. Can a mod please move this into the bug forum? Or should I just recreate the thread?
  3. 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.
  4. Please give it to us NOW! :D It would be really fantastic to have robust support for more than 8 players.
  5. 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
  6. 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.
  7. 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.
  8. 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.
  9. > - 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/
  10. Looking forward to the new campaign! If at all possible I would love a ground/airbase campaign (F-16, A-10, AV8B, Mirage?) using the new DCE framework possibly.
  11. Original bug is fixed! I am sorry, I managed to break it again though. I think that's a different problem:
  12. I am getting a problem setting up certain MP flight combinations (on @stable). Like this:
  13. Any updates on the campaign? I would love to game away on some new DCE. :)
  14. The new flexibility for MP flights looks great! Can't wait to try it out this weekend.
  15. 11.05.09 version is excellent, especially multiplayer mission construction seems to be much more robust now. Thanks for the great work!
×
×
  • Create New...