search

PapaJoesSoup / BDArmory

Gun turrets and other weapon systems for KSP
114 stars 57 forks source link

Radar data receiver user interface #715

Open meltingSnowdrift opened 5 years ago

meltingSnowdrift commented 5 years ago
ISSUE TYPE
KSP and BDA Version
KSP 1.7.2
BDA 1.3.1
OS / ENVIRONMENT

Windows 10

SUMMARY

The radar user interface treats radar data receivers in unhelpful and presumably unintended ways. When no radar is active on a vessel with a radar data receiver and the receiver is activated, the radar user interface shows an unchangeable display range of 1km. Testing suggests that no contacts are actually displayed at all even if they are within 1km of the vessel with the receiver and detected by the radar providing the data.

When there is a radar active on the receiving vessel, display range is constrained by that radar.

STEPS TO REPRODUCE

Make a vessel with a weapon manager, a radar data receiver, and no radars. Make another vessel capable of acting as a source of datalinked radar data. Launch both and place them near each other, along with something for the radar to detect. Try to use the receiver to get data about the contact.

I understand that radars can affect display range to indicate their maximum range. Keeping it this way would require making an exception for the receiver, which has no detection range of its own. I therefore propose an alternate approach to fixing this: Do not allow radar capabilities to affect display range at all. Instead, display a circle to represent the maximum detection range provided by radars on the current vessel whenever the display range exceeds this maximum detection range. A future more sophisticated version can possibly also do this for vessels providing data over datalink, thereby showing the entire area for which radar data is available.

Gedas-S commented 5 years ago

Probably a duplicate of #646

meltingSnowdrift commented 5 years ago

Oops. I forgot about that one; sorry about that. This one does contain new and more accurate information about how the bug behaves, though. How should information about the problem in its current state be merged into a single thread?

One way would be to close that one and make this one the main thread of the entire issue after verifying whether the APG-63 over datalink works as was stated there. If it is preferable to keep the older thread s the main one, I can copy most of the content of this one to that thread and close this one.

Gedas-S commented 5 years ago

Don't worry about it. Mentioning the issue by number produced a reference on the other one, we'll find both when we get to it.

Neros7 commented 4 years ago

Is the issue fixed for newer versions? Can I use newer versions on KSP 1.7.1 (I need it that "old" for other Mods)? Is there a other way to fix it?