Jump to content

Recommended Posts

Posted

See trackfile. At 08:03:52 ingame-time, PGM is at 3, at 08:04:03, in a low G turn, it jumps back up to 4. Is this logically? If so, why?

PGMdecreaseLowGturn.trk

  • Like 2
DCS Wishlist: 2K11 Krug SA-4 Ganef SAM, VR-TrackIR icons next to player names in score-chart

PvP: 100+ manual player-kills with Stingers on a well known dynamic campaign server - 100+ VTOL FARP landings & 125+ hours AV-8B, F-14 crew, royal dutch airforce F-16C - PvP campaigns since 2013

DCS server-admins: please adhere to a common sense gaming industry policy as most server admins throughout the industry do. (After all there's enough hostility on the internet already which really doesn't help anyone. Thanks.)

Dell Visor VR headset, Ryzen 5 5600 (6C/12T), RTX 4060 - basic DCS-community rule-of-thumb: Don't believe bad things that a PvP pilot claims about another PvP pilot without having analyzed the existing evidence

Posted

The fast and clean track is appreciated but remember not everyone has DLC terrains which will limit your audience.

  • At 0:30 the major-minor axes of the threat zone are 86nm x 6.7nm
  • 0:45 83x7.4nm
  • 1:00 78x13nm
  • 1:08 86x4.0nm
  • 1:22 19x92nm
  • 1:35 21x5.4nm
  • 2:28 9.1 11nm
  • 2:41 20x3.3nm
  • 2:54 5.1x15nm
  • 3:35 8.8x6.9nm
  • 3:49 12x1.8nm 3
  • 4:01 3.6x9.9 5
  • 4:02 3.5x9.7 4

I feel that <1 second PGM 5 at 4:01 factored into the rolling average causing the 55555354 PGM history. The update frequency is pretty low. I'd expect the HTS/HARM combo to devote more resources to refine the location of the boxed threat instead of once every ~15s. I'm also surprised to see the longitudinal axis not the largest distance so regularly. The uncertainty is not growing strictly smaller. I'd be interested to see of an AxB vs T graph to see how the area changed over time.

 

  • Like 2
Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...