daid
Request - Science Rings Labelled
Add some sort of label to each of the raw data science rings. Inline with the rings, and the same color as the ring it's labelling.
We were talking about it in discord today. understanding what they mean makes it much easier to interpret too.
- Green : Biological
- Red : Electrical
- Blue : Gravitational
That information is in the science db. Maybe hinting that info would work? It could be in the tutorial or maby a tiny button. I am not sure how readable it would be to put those labels directly on the rings. Especially if they are colored. They could also overlap with callsigns.
I've seen some forks put a legend on screen in one of the open areas, which feels like a decent solution.
Or we could put it in the F1 menu.
Then as the tutorial happens and the person is in science, the tutorial makes them press F1 to see the tooltip and the RGB meaning?
Mentioning it more thoroughly throughout the Science tutorials would also help- the system is already quite detailed and already reacts to gameplay systems, so the tutorial could explicitly incorporate things like "a moving gravity signature with a matching moving bio signature could be an indicator of a warping ship", stuff like that.
Oh! What if there is a little legend widget like this, but instead of just showing scores (in this screenshot is it perhaps showing the score at the ship's current heading? not sure), it shows you the bearing of the strongest peak in each channel (maybe RMS'd like an audio VU, to account for noisy signals like Electrical, as well normal movement). The channel name labels 'Electrical' etc. would be smaller and secondary instead of being the primary text, simply labelling what that number is telling you:
In this way, it both self-explains the sensors signals and provides a nice little hint to Science about 'maybe look at this thing' for each channel, and dovetails well with ideas for other, more advanced sensor analysis stations where deeper follow up can happen, as well as of course the normal "let's get closer so I can see it on the scope and scan it".
Implementation wise it would be the fastest to just integrate that component and rework to our branch.
@Jadael do you know which fork that component is?
It came up in discussion in Discord https://discord.com/channels/206597597455056898/468130064513368064/1382751929108533289 as "The LARP fork"
Actually your small version is very nice and I would think adding a time versus value graph on it would also allow a person to understand what happens when the jump and such. That would give an opportunity for science to learn the Sensor station #2417 as they work on science.