You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And if any code needs to changed in Telemachus to use JNSQ or ANY other pack from there,
maybe changes could/should be made to future-proof and make it easier for Telemachus to use different packs from there? (like either a UI or config/settings file for Telemachus to switch between packs, rather than having something that would need to changed, being hard-coded?) vOv
i know there was uncomfirmed comments/discussion made about maybe adding some other popular planet packs to the KM catalog, in the future... vOv
I have a first draft of this up on development. The only maps implemented so far are the Stock/JNSQ Kerbin and Stock Mun. I will get the rest implemented over the next couple of days.
So with @Row-Bear 's latest PR, we have all the bodies for both JNSQ and stock, and we have an extensible way to add more sources as they are available in Kerbal Maps. I see some improvements we can make in the UI to help declutter it a bit, but I think we've met the intent of this ticket, @StoneBlue ?
Actually, here is the specific post in the thread, with the beta link that includes complete JNSQ maps:
https://forum.kerbalspaceprogram.com/index.php?/topic/181688-kerbal-maps-is-back-sort-of/&do=findComment&comment=3756346
And if any code needs to changed in Telemachus to use JNSQ or ANY other pack from there,
maybe changes could/should be made to future-proof and make it easier for Telemachus to use different packs from there? (like either a UI or config/settings file for Telemachus to switch between packs, rather than having something that would need to changed, being hard-coded?) vOv
i know there was uncomfirmed comments/discussion made about maybe adding some other popular planet packs to the KM catalog, in the future... vOv
Originally posted by @StoneBlue in #19 (comment)
The text was updated successfully, but these errors were encountered: