Open Yanis-Sauve opened 3 years ago
Great idea, was pondering this since the beginning, but figured would involve a lot of buy in from FEs to change asr files; now there's some momentum, I think this is great to not have doubled up tags and targets on ground screens, tower screens etc.
proposed solution at 1ba6383
Add the following to .asr files that you want Situ to display on
PLUGIN:VATCANSitu:DisplayTypeName:IFR
If you open a twr asr file, seems to not show the PPS, because they were changed to MOVETO 0 0 to implement Vatcansitu on IFR asr displays
You have to switch your radar to NARDS to have the PPS for VFR displays. Only the CSiT must be MOVETO 0 0 for IFR
Will work on a NARDS style display for the tower asrs at some point
(label changed to enhancement)
As discussed, how about having Situ display CJSs on a "VFR" display type, so CANscope would not be needed anymore?
For IFR, Situ will draw CJSs, targets and tags. For VFR, Situ will draw CJSs, Euroscope will draw NARDS targets and tags.
3ebe1e7
Add the following to your VFR screens and the CJS should now draw for targets. More work to come on a full NARDS tags symbology and toolbar
PLUGIN:VATCANSitu:DisplayTypeName:VFR
We need a way to keep Situ from drawing to VFR type displays.
How about having the plug-in create display types so we can control this easily.
I'd propose creating at least one named "IFR", which would be used to allow Situ to draw to, after changing the "DisplayTypeName" variable in our .asr files. Ideally, lets create two types "IFR" and "VFR", that way we can explicitly keep Situ from drawing to a TWR view, for example.