[1.7] CommNet Visualisation v1.0.4 [17 April 2019]

[TaxiService]

What is this?

A lightweight interface add-on for CommNet of Kerbal Space Program.

What does it do?

This add-on adds RemoteTech's MultiPath mode to the CommNet visualisation of connections. This mode is to display all working connections of every vessel in the game.

Just click the 'Network' button in Tracking Station or Map View to change the visualisation mode of CommNet.

Why?

• Useful mode without installing CommNet Constellation (also have same mode)
• Useful resource for other modders to look and add other CommNet modes

Mods required

Nope. It is a DLL file.

License

GNU GENERAL PUBLIC LICENSE, Version 3

DOWNLOAD

Github

SpaceDock

Edited April 17, 2019 by TaxiService

[Alewx]

Wait what, why the new name? Or is this seperate from CommNet Constellations?

[HebaruSan]

36 minutes ago, TaxiService said:

• Useful mode without CommNet Constellation

Would it work to install both at once, or should we mark them as conflicting in CKAN?

[Rocket In My Pocket]

Love it, exactly what I wanted when I first saw constellations. Many thanks for making this lightweight version!

My Commnet makes so much more sense visually now.

[TaxiService]

11 hours ago, Alewx said:

Wait what, why the new name? Or is this seperate from CommNet Constellations?

Yup, separate mod.

11 hours ago, HebaruSan said:

Would it work to install both at once, or should we mark them as conflicting in CKAN?

My bad, I forgot to add this exclusion. I will reply on the github ckan pull request.

[flart]

Localization is forgotten   

Also it breaks the stock CommNet type names Localization

[TaxiService]

11 hours ago, flart said:

Localization is forgotten   

Also it breaks the stock CommNet type names Localization

I am unable to preserve the localisation. Each text comes out as an entire word and I can't see which part of this text to split to change the mode name. In end, I give English texts across the modes consistently.

[flart]

8 hours ago, TaxiService said:

I am unable to preserve the localisation. Each text comes out as an entire word and I can't see which part of this text to split to change the mode name. In end, I give English texts across the modes consistently.

 

Spoiler

I don't understand what you are saying

 

would it be working?

public enum CustomDisplayMode
        {
            [Description("#CommNetVisualisation_None")]
            None,
            [Description("#CommNetVisualisation_First_Hop")]
            FirstHop,
            [Description("#CommNetVisualisation_Working_Connection")]
            Path,
            [Description("#CommNetVisualisation_Vessel_Links")]
            VesselLinks,
            [Description("#CommNetVisualisation_Network")]
            Network,
            [Description("#CommNetVisualisation_All_Working_Connections")]
            MultiPaths
        }

 

 

 

 

 

 

[TaxiService]

15 hours ago, flart said:

I don't understand what you are saying

would it be working?

public enum CustomDisplayMode
        {
            [Description("#CommNetVisualisation_None")]
            None,
            [Description("#CommNetVisualisation_First_Hop")]
            FirstHop,
            [Description("#CommNetVisualisation_Working_Connection")]
            Path,
            [Description("#CommNetVisualisation_Vessel_Links")]
            VesselLinks,
            [Description("#CommNetVisualisation_Network")]
            Network,
            [Description("#CommNetVisualisation_All_Working_Connections")]
            MultiPaths
        }

Not exactly. It would look like below

[Description("#lang_tag_12345")]
None,

where the corresponding tag is in KSP's language file. 'Path' and 'MultiPaths' are new names I gave myself.

By the way, I am able to restore some of the localisation after poking more around but I can't do anything with the mode names without translating them. I will push a new version soon.

[flart]

v1.0.1

all mode-names ("None", etc) still are unlocalized

https://www.dropbox.com/s/4klbh3jwpz9b2ba/screenshot91_cr.png?dl=0

4 hours ago, TaxiService said:

I can't do anything with the mode names without translating them.

Yes, I'm talking about usual translation in /localization/en-us.cfg, etc. Other languages will be commited by users.

Edited January 12, 2018 by flart

[TaxiService]

On 1/13/2018 at 1:43 AM, flart said:

v1.0.1

all mode-names ("None", etc) still are unlocalized

https://www.dropbox.com/s/4klbh3jwpz9b2ba/screenshot91_cr.png?dl=0

Yes, I'm talking about usual translation in /localization/en-us.cfg, etc. Other languages will be commited by users.

I added and tested the localization of 9 languages (initial English to be translated later) for the two mode-name phrases. It looks working. You can help to translate the two phrases to Russian if you desire. I am posting in the central Localization thread to ask for assistance on other languages.

Spoiler

Localization
{
    en-us
    {
        #autoLOC_CommNetVisualisation_ModePath = Working Connection
        #autoLOC_CommNetVisualisation_ModeMultiPaths = All Working Connections
    }
    ru
    {
        #autoLOC_CommNetVisualisation_ModePath = Working Connection
        #autoLOC_CommNetVisualisation_ModeMultiPaths = All Working Connections
    }
    es-es
    {
        #autoLOC_CommNetVisualisation_ModePath = Working Connection
        #autoLOC_CommNetVisualisation_ModeMultiPaths = All Working Connections
    }
    zh-cn
    {
        #autoLOC_CommNetVisualisation_ModePath = Working Connection
        #autoLOC_CommNetVisualisation_ModeMultiPaths = All Working Connections
    }
    de
    {
        #autoLOC_CommNetVisualisation_ModePath = Working Connection
        #autoLOC_CommNetVisualisation_ModeMultiPaths = All Working Connections
    }
    ja
    {
        #autoLOC_CommNetVisualisation_ModePath = Working Connection
        #autoLOC_CommNetVisualisation_ModeMultiPaths = All Working Connections
    }
    fr
    {
        #autoLOC_CommNetVisualisation_ModePath = Working Connection
        #autoLOC_CommNetVisualisation_ModeMultiPaths = All Working Connections
    }
    }
    it
    {
        #autoLOC_CommNetVisualisation_ModePath = Working Connection
        #autoLOC_CommNetVisualisation_ModeMultiPaths = All Working Connections
    }
    pt
    {
        #autoLOC_CommNetVisualisation_ModePath = Working Connection
        #autoLOC_CommNetVisualisation_ModeMultiPaths = All Working Connections
    }
}

 

[maculator]

Does this mod cost performance?

[Warezcrawler]

32 minutes ago, maculator said:

Does this mod cost performance?

Does not look like it is running on each update of the game, so it seem quite light weight.

[maculator]

thank you. Always afraid of hidden fps eaters^^

[maculator]

Does "working" mean they're just working or the're actually connected?

there are only two things to translate if I'm right:

working connection

and all working connections

so I guess it does refer to "active connections" and "all connections"?

If yes it would be "Aktive Verbindungen" and "Alle Verbindungen" in german.

[TaxiService]

As in actually connected that you control the vessel.

If this meaning is right to you, I will add your German translation to the localization file.

[maculator]

So the first one refers to the actual connection on the active vessel? Then It's singular "Aktive Verbindung".

[TaxiService]

15 hours ago, maculator said:

So the first one refers to the actual connection on the active vessel? Then It's singular "Aktive Verbindung".

Yup, and I think I misunderstand your second one. "all working connections" is what you will see all active connections on all vessels in Map View/Tracking Station. Unused connections will be hidden.

[maculator]

I noticed that. After lunch I'll play anyways and then I'll check what's the best way of translating it

 

Edit, Got it:

Aktive Verbindung

Alle aktiven Verbindungen

 

 

Edit Edit:

Did you by any chance alter the strength of the connection lines? I mean the visuals. They're looking pretty thin for me. Wish they were a bit bigger. 

 

This is what I mean:

Spoiler

 

Edited March 18, 2018 by maculator

[TaxiService]

Thanks, I added your translation to the codebase.

Spoiler

Did you by any chance alter the strength of the connection lines? I mean the visuals. They're looking pretty thin for me. Wish they were a bit bigger. 

I didn't touch the default line thickness. I thought it was too thin too but I let it slide to see how it works out eventually. One change in KSP 1.4.x is this thicker line when zooming out enough.

[cakepie]

I was going to take a shot at translating JA, but due to the ambiguity English wording (thanks @maculator for seeking clarification above) I thought it might be a good idea to suggest that the English be changed to something clearer and less ambiguous first -- to prevent future translation errors, as well as for players' ease of understanding.

The two strings are "working connections" and "all working connections".
If I'm not mistaken, the mod behavior is:
1) show only the path through which a control connection is established from Kerbin ground stations to the current vessel
2) same as above, but for all vessels
So the intended meaning is "active"/"in-use" connections.
However, "working" can be easily misinterpreted to mean "functioning properly" (has line of sight, electrical power, no malfunction, etc.)

Besides maculator's German, it looks like the Russian translation is also correct, whereas @Nils277's German and @fitiales's Spanish might be incorrect.
For what it's worth, I also misunderstood the meaning at first, before I grabbed to mod to try it for myself.

Is there any difference between stock KSP's "path" display mode v.s. this mod's "working connections" display? (Looks the same to me, but maybe I missed something?) If not, is there some other reason not to use the term "path"?

Also, with "connection" it isn't immediately obvious whether we're talking about an intermediate connection between two vessels/relays ("hop"/"Link") or the full "path" between vessel and Kerbin.

I'd suggest that "Active vessel path"/"Current vessel path" and "All paths"/"All vessel paths" would be the most accurate labels to use.

For reference, stock KSP uses:

		#autoLOC_6003083 = None
		#autoLOC_6003084 = First Hop
		#autoLOC_6003085 = Path
		#autoLOC_6003086 = Vessel Links
		#autoLOC_6003087 = Network

 

[flart]

10 hours ago, cakepie said:

"Active vessel path"/"Current vessel path" and  "All paths"/"All vessel paths"

Taxi was saying:

Quote

Path is ambiguous. Vessel can have one or more paths to Mission Control but Path doesn't show which of these paths is the active control. Can you picture if I say Paths? Players may think it is like Network.

So I borrow the word from RemoteTech mod, Working Connection, to show this path is active control. So All Working Connections show all active controls of all vessels. So it is better.

 

Active Connection and All Active Connection are more accurate labels, for my taste, but it is English native speakers decision

 

Edited March 24, 2018 by flart

[cakepie]

@flart "Control path" or "Connected path" then, if the concern is over which of multiple paths is actually in use.

[TaxiService]

@flart @cakepie Yup, lot of ambiguity in English language words. This Active word is certainly better than Working. The localisation file is updated, except for 3 translated phrases. They will be eventually corrected later.

Thanks!

[cakepie]

6 hours ago, TaxiService said:

except for 3 translated phrases.

Russian and German by maculator are already correct, I think.

Edit: pr#3 adds JA and merges language tag fixes by Nils277

Edited March 24, 2018 by cakepie
PR