-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection Diagnostics #31
Comments
Transferring my post from the forum thread as per Starstrider42's request, slightly expanded and hopefully better explained: One of the major causes of help requests stems from the fact that people get no connection but don't know why, often involving Active Vessel as a target somewhere in the network. Typical example: A player controlling a probe/sat currently above the Mün - intended as a relay for crafts in the Mün's shadow - can see a connection to their main network around Kerbin, because those satellites have AV as a target. As far as I know there is no way to see why the connection is made (is it targeted? inside a cone? due to active vessel?). Once he switches to the vessel behind the Mün - which would now need that relay to connect to KSC - he get's no connection and doesn't know why. He's not told "Active Vessel set, but no line of sight", "Out of range" or anything else along those lines. All this information could be in a tooltip on the map (if plugins can create/override tool tips for objects on the map) or drawn as text next to either the satellites or their connection lines (with a new button in the lower-right corner to toggle this display). As a more minimal and less intrusive alternative would be color-coding the relay-satellite-icons (and/or the connecting lines). Preferably with a key drawn at the side to explain what it all means. Just for further illustration, a coloring/linestyle example: Related to that, it would be quite helpful in diagnosing issues if we had access to lists of what something is set to connect to. Basically a list of targets for a satellite. One way would obviously be a tool tip (again), but this could also be done visually by drawing lines - possibly labelled with the target name, as it might be way out of sight - to the set targets (possibly with the colors and/or line types from above). Obviously you'd need a way to select which target-list to show. The easiest would probably just to show them for whatever the map is centered on (if it's active, would obviously need another toggle in the bottom right). |
Hi. Lurker here. |
Color-coded network would need a huge legend. For an active path I would prefer tooltips (alternate resource panel style) with uplink and downlink target name, antenna name and max range for every sat in the path, plus leg distance markers (like ap/pe ones). For managing satellites without switching to them there is a button with sat icon in map view already, but almost every time I try to use it I get infinite zoom out or Kerbin texture as a skybox bugs. |
Yes, this could become problematic. But do keep in mind that what I wrote is basically an exhaustive list, mainly for illustration purposes. In practice you'd have one part of the legend for colors and one for line-types, so no more than 10 entries. A tooltip would make for a cleaner screen, but would also remove the overview aspect. You can only ever see the status of one satellite at a time. Real problems usually just arise with large-ish networks, where you have to figure out where on the way to your craft the signal breaks down. It's hard to mouse-over the right satellites when there's like 10 candidates for what may or may not be the shortest route. If you don't have a connection there's obviously not gonna be a nice green line, pointing out the sats you need to check. In the end it's mainly about having tools to diagnose this situation at all though. So it's better to have something working soon-ish rather than something more visually appealing much later ;) I also thought about the whole thing some more and noticed that I didn't even mention in the line-shape/color-coding parts, that every possible connection obviously concerns two satellites. Those potentially have asymmetric settings, like a relay for Duna will likely use a cone (or active vessel), but the receivers over there might target the relay directly (or also use a Kerbin-cone). Obviously it's not trivial how to show that. Using lines becomes difficult there for another reason, because any satellite with a cone might have multiple targets. It would be rather problematic to decide which lines to draw... Only the one that have something targeting back? So yea, I get that using lines has it's problems :)
Yea I had kind of forgotten that you can use the target-selection-ui for that, just ignore the last paragraph... Usually, the feature does work for me though. |
Display is toggled by clicking on the signal delay field in the Time Wrap display. Connection is cached internally, and the last cached route is checked for quality. Limitation: because no RT2 information is retained between scene changes, diagnostics are only available for the active vessel, and only if the connection goes down while the vessel is active.
Original issue at Cilph/RemoteTech2#215.
Cilph wrote:
The text was updated successfully, but these errors were encountered: