Jannik Vogel (1432304) Posted July 10, 2023 Report Share Posted July 10, 2023 Hello, is it possible to implement a color for uncontrolled VFR flights (neither tracked nor on contact) without using the FIC_Position=1 setting? I currently do not know how to achieve this in my setup. In the end, all uncontrolled VFR traffic should be displayed in this color which differs from the color of unconcerned tracks. Link to comment Share on other sites More sharing options...
Juha Holopainen Posted July 11, 2023 Report Share Posted July 11, 2023 Why not just use the setting? Link to comment Share on other sites More sharing options...
Jannik Vogel (1432304) Posted July 17, 2023 Author Report Share Posted July 17, 2023 Because VFR is considered concerned in this case (at least it seems to be like that). I would like VFR to be treated similar to an informed flight in this case. It should be in VFR color regardless of the state (except it is assumed). 1 Link to comment Share on other sites More sharing options...
Juha Holopainen Posted July 18, 2023 Report Share Posted July 18, 2023 I'm not sure I understand the issue. When enabled, the FIC_Position setting makes the plugin use the "VFR" color instead of the "Unconcerned" color for all aircraft that are both uncontrolled and untracked. It does nothing to change anything else. Link to comment Share on other sites More sharing options...
Jannik Vogel (1432304) Posted July 19, 2023 Author Report Share Posted July 19, 2023 Ok, then there seems to be something wrong in the color logic. When enabling the FIC setting, the labels and history dots of uncontrolled and untracked VFR flights are in "redundant" color (the magenta color in my screenshot). The track symbol however is in "VFR" color (the brown/cappuccino color). I would expect the label and history dots to be colored in "VFR" color, too. Possibly a bug? Link to comment Share on other sites More sharing options...
Juha Holopainen Posted July 19, 2023 Report Share Posted July 19, 2023 This may be a bug I've already fixed in development code. The color for these tracks is "VFR" in the default version, but "Redundant" in the COOPANS version. Some time ago I noticed that not all the track components were referring to the correct color based on the selected version. In the next version the "VFR" color will be used in both setups. 2 Link to comment Share on other sites More sharing options...
Jannik Vogel (1432304) Posted July 20, 2023 Author Report Share Posted July 20, 2023 Thanks Juha! That will solve my issue Link to comment Share on other sites More sharing options...
Jannik Vogel (1432304) Posted October 14, 2023 Author Report Share Posted October 14, 2023 Hi Juha, following up on this: If FIC_Position is on, VFR tracks are no longer subject to any filter of any kind (neither Squawk, Altitude, etc.). Is this intended? If so: Could we get a possibility to color VFR tracks but not change anything in their behaviour besides the coloring? I would like to rebuild the behaviour of the german iCAS system which is coloring VFR tracks in a non prominent but (in difference to unconcerned color) still easily visible color. Thanks for considering! Jannik Link to comment Share on other sites More sharing options...
Juha Holopainen Posted October 15, 2023 Report Share Posted October 15, 2023 On FIC positions, whether untracked uncontrolled aircraft are affected by filters or not is controlled by the "System_FIC_Position_Free_Filtered" setting. 1 Link to comment Share on other sites More sharing options...
Jannik Vogel (1432304) Posted October 15, 2023 Author Report Share Posted October 15, 2023 (edited) The settings seems to be not existing in the documentation excel. Edited October 15, 2023 by Jannik Vogel (1432304) Link to comment Share on other sites More sharing options...
Juha Holopainen Posted October 16, 2023 Report Share Posted October 16, 2023 That setting was introduced in version 2.5b4 Link to comment Share on other sites More sharing options...
Jannik Vogel (1432304) Posted October 17, 2023 Author Report Share Posted October 17, 2023 Indeed, we were using an old Version of the documentation. Sorry for that! Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now