Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I wanted to suggest possibly implementing a basic filter to ignore grids under a certain size that only contain wheels or provide an equivalent solution. This would greatly improve the readability and functionality of the radar for similar scenarios.
I attempted to implement a solution myself but I don't have any experience with C# and I couldn't so much as load the script in VS without being swarmed by errors. Despite this, I believe it would be relatively straightforward to add such a filter, at least for this specific case. However, I am not sure if it is feasible with the script API and size constraints.
Regarding point of reference overrides, I asked about something similar for the artificial horizons script.
Based on ships being in a configurable range of a master reference instance.
https://steamproxy.net/workshop/filedetails/discussion/1721247350/4358997660743992387/
I don't think this would add any value to the radar script, as when I jump into a fighter to intercept an enemy, I need targeting data relative to the fighter, not the base I am docked to. Otherwise, I'd take off in the wrong direction to intercept, then waste time and fuel turning around.