Captain Slow Posted February 18, 2019 Posted February 18, 2019 (edited) Question: Intended behavior or not? Reproducible: 100% Date: 2018-02-18 1940Z Sim version: 2.5.4.27314 Open Beta Mission: Any Steps to reproduce: 1. Set radar to bvr/rws scan 2. Set 1B scan pattern Problem: Indicated vertical coverage altitudes at TDC distance correspond to bar scan centerline. Track: Screenshot only attached Desired solution: coverage altitudes should take into account width of bar. SP/MP: Affects both. System spec: Tested on multiple systems with same result. Controllers: Tested on multiple systems with same result. Edited February 18, 2019 by Captain Slow
Captain Slow Posted February 18, 2019 Author Posted February 18, 2019 (edited) I can confirm the behavior is the same regardless if bar scan pattern setting (see attachment), i.e. bar scan centerlines encapsulated scan volume is displayed as altitude coverage. In the attached pdf: bars: the bar scan setting of radar alt coverage kft: total number of 1000s of feet covered at TDC distance (scan centered around horizon) dist nmi: TDC distance in nautical miles zones: number of encapsulated "scan zones" corresponding to bar count pm coverage kft: half of alt coverage kft pm coverage nmi: same as above but in nmi pm coverage degs: corresponding vertical scan angles around horizon (i.e. 5.95 means +- 5.95 degrees coverage around horizon vertically) degs per zone: calculation of covered degrees per zone (to evaluate if bar width or not is taken into account) degs per par: calculation of covered degrees per zone (to evaluate if bar width or not is taken into account) since degs per zone is relatively constant, but degs per bar is not => only bar centerline is taken into account in the current attack radar page implementationScan angles - Sheet1 (2).pdf Edited February 18, 2019 by Captain Slow
Recommended Posts