TaxiService

Yes, there is now the final beta of CommNet Constellation on top of CommNet Manager. I am waiting for my pull request of a fix to be accepted into CommNet Manager before an official release can be dropped. Looking at the codebase of Signal Delay, only 1 change needed to get on CommNet Manager is from CommNetVessel to CommNetManagerAPI.ModularCommNetVesselComponent and recompile against CommNetManagerAPI

Beta 3 of CommNet Constellation + CommNet Manager I ported this mod to utilize the common CommNet infrastructure, managed by CommNet Manager, instead of own infrastructure. This means other mods running CommNet Manager can work fine with this mod. Also, it will work on your player save as if nothing is changed. Please back up your save first before trying out! Progress Update Fix difficult bug behind NullReferenceException spam when additional ground stations are created. One related change is required in CommNet Manager (pull request) Update CNC App button to display in both Flight and Map Mode Add ability to toggle an individual antenna in VAB, SPH or Flight Requirements CommNet Constellation + Patched CommNet Manager (download) ModuleManager 4.1.4 Request Please let me know on any issue found. I plan to publish several betas with any fix included before releasing to the wide audience officially. Thanks!

Hi, it is not possible to put the CNC button in VAB/SPH because it requires underlying CommNet, which is not run in both scenes. Your suggestion of toggling individual antennas in VAB/SPH is much better. I will make all internal (built-in) antennas of 5k power to be disabled by default and all Direct and Relay antennas enabled by default. Update: Based on few play tests, I decide against disabling internal antennas by default and leave this to players' freedom.

Hi, my apologies for this delayed response. Possibly it is too late for you now but I will add a new setting to change to set all probe core antennas off by default. For the CNC button, it seems a recent KSP change interferes the button displaying. It will be changed to be displayed all the time regardless of flight or map view mode. Hi @stk2008 and @Grimmas, I believe the issue you encountered is related to the nasty ground station bug between CNC and CNM I was trying to resolve until now. You can try a new CNC+CNM build and be sure to download "CommNetConstellation_PatchedCommNetManager.zip" to replace both CNC and CNM. My CNM fix is pending acceptance into CNM codebase.

From the two player reports earlier, I found a nasty bug in the beta of CNC+CNM where few invalid ground stations would be created persistently throughout player session until exit, on top of the valid ground stations. It is possibly the same errors you encountered after installing this beta. JNSQ and KK are merely victims of the bug once I reproduced it in CNC+CNM build. For the stripped-down game, I looked through the log and could not find any clue to explain why the CNC launcher button is not shown in Tracking Station or Flight Map Mode. Any idea you may have?

Hi, if possible, kindly provide the logs you checked. I would like to find out what CNC version you used and whether CommNet Manager is installed. Thanks. Hi, based on your log, CNC 1.5.4 is standalone (have own CommNet infrastructure) and does not utilise CommNet Manager. Having both CNC and CNM on your installation will cause mod conflicts, including NullReference spam. Short time ago, I created a new CNM port of CNC 1.5.7 but it only runs on KSP 1.11 due to 1 important KSP change introduced.

I poked around in JNSQ and KK (without CNC installed) and could not figure out which models are CommNet ground stations. They seem like normal models to place in KK editor mode. Can you help to explain how you set up those KK ground stations? Thanks Edit: Found the KK parameter setting of CommNet ground stations and the facility-type function function of a model.

Based on the codebase (link), each vessel has a sorted list of all valid paths, which is sorted in ascending by path length. Generally, RemoteTech will take the first path from this sorted list as working connection. I saw few code sets using conditions to select a path from the list, not necessarily the shortest path. By the way, I think you should be interested to know that each antenna of a vessel has own process (link) of transmitting science data, based on science packet size, interval and cost. Basically, if you click "Transmit all science" button in Part Action Menu of one antenna with the strongest data properties, RemoteTech will run it based on those antenna data properties. Last time I checked, it had been decided that Kerbalism would eventually implement its own CommNet functionality, phasing out the RemoteTech dependancy.

Hi, RemoteTech pathfinding logic will find the shortest path among all possible paths from a destination to source, even if there is a better but longer link. This problem is complicated by the fact that all links are on same plane regardless of vessel purposes. Also, link power (signal strength) is not considered by RemoteTech which just looks at the distance if I understand your description correctly.

Hi, did you manage to get it work by trying few workarounds discovered by other players? Switch to another save (even fresh save) and back to your save? Quit and re-launch the game? If none is working, please provide the Player.log per log section of guideline.

Indeed, it is very strange. I checked the codes for toolbar button and it didn't have any condition on when you can't click. I will look into this problem and the bug you reported in CNC+CNM later. For your request, you can go into "CNC: Communication" button of probe core and de-select specific antenna(s) in "Antenna Selection" tab to turn off.

Hi, your KSP.log is fine. It has this line "[ERR 14:34:35.160] [CommNet Constellation] Error: CNCCommNetScenario - Conflict with third-party CommNet mod(s)! Please remove this or other mod(s)" and I suspect it may be a new bug in the beta of CNC+CNM. Can you remove CNC1.5.7+CNM and install the official CNC 1.5.7 (linky)? I looked at your other mods and they should not have any CommNet feature. Thanks

Hi, your log seems to say CommNetConstellation (CNC) was uninstalled and there aren't any CNC log printed in your last play. Can you upload a different log, Player.log per log section of guideline, please? Just to be sure, KK is Kerbal Konstructs? The NullRefs errors are likely due to incomplete information of KK ground stations and I need to take a look at their configs. The other bug of blank ground station name in the signal strength list is fixed.

Correct, the statement is actually interactive depending on the checkbox. It will be "Planets and moons will not block a signal" if it is ticked. Otherwise, it will be "Planets and moons will block a signal". Thanks for the logs. According to the logs, RemoteTech version in your KSP 1.9 is 1.9.10 for KSP 1.11. The errors are because of KSP 1.11 interface changes that not in KSP 1.9 You will need to use RemoteTech 1.9.6 for KSP 1.9 (linky)

In this case, please provide Player.log, per log guidelines for investigation. KSP being 1.9 far from 1.11 could mean anything and I request for this log to analyse. Thanks!

Beta 2 of CommNet Constellation + CommNet Manager I ported this mod to utilize the common CommNet infrastructure, managed by CommNet Manager, instead of own infrastructure. This means other mods running CommNet Manager can work fine with this mod. Also, it will work on your player save as if nothing is changed. Please back up your save first before trying out! Progress Update Recompiled for KSP 1.11.1 No performance issue found from profiling No gameplay issue or bug found so far Requirements CommNet Constellation (download) CommNet Manager 1.1.0 ModuleManager 4.1.4 Request Please let me know on any issue found. I plan to publish several betas with any fix included before releasing to the wide audience officially. Thanks!

The antennas deactivated by HBNT won't activate automatically unless WAKE is scheduled in future to activate the antennas again. Do note WAKE will only target the antennas deactivated by HBNT. If you try WAKE the antenna that you manually deactivate, it won't be activated. I am not sure if you are aware of the THLD function. THLD will put the vessel in special power mode where the antennas will automatically deactivate if vessel battery falls too low, and activate if vessel battery is charged enough. Hi, please provide Player.log, per log guidelines for investigation. RT interface of signal delay and flight computer button is not in your screenshot. RT 1.9.9 and 1.9.10 are for KSP 1.11 due to the new morning sun wrap button. Sure, a new similar setting for time wrap stop on reconnection will be added in Misc section of RT options. I need some time to implement it.

Thanks for your interesting results. The issue is how deployable ground parts operate. The deloyable control station is treated as CommNetVessel instead of the deployable comm dish. My preliminary investigation indicates it would need a lot of code work to just make the comm dish as CommNetVessel. The justification for this is very weak, given the narrow scope of deployable ground parts.

Yes, CNC should see an additional CNConstellationAntennaModule and shows the second "CNC: Setup" or similar button in Part Action menu. You can experiment it. It should not make your player save irreverible.

Hi, can you switch to the control station and see if the 400km omni range is present and the connection status is green? The picture below shows this.

Beta 1 of CommNet Constellation + CommNet Manager I ported this mod to utilize the common CommNet infrastructure, managed by CommNet Manager, instead of own infrastructure. This means other mods running CommNet Manager can work fine with this mod. Also, it will work on your player save as if nothing is changed. Please back up your save first before trying out! Requirements CommNet Constellation 1.5.7 CommNet Manager 1.1.0 ModuleManager 4.1.4 Beta Link Linky Request Please let me know on any issue found. I plan to publish several betas with any fix included before releasing to the wide audience offically. Thanks!

Hi, please provide your Player.log for further investigation, per Logs instructions in the guidelines.

Hi, please provide your Player.log for further investigation, per Logs instructions in the guidelines

RemoteTech 1.9.10 for KSP 1.11 released This release is a standard fix for KSP 1.11. What are fixed/changed: Add multiple protections against the construction mode Add cargo support for small RemoteTech antennas Update support for renamed part of HG-5 High Gain Antenna Complete changelog is below: If you find any bug, please report them on our github (as it is hard to keep track of bugs here). Feedback is also welcome for the next release, here or on this post. We are in the RT 2.x branch development and continue to support the RT 1.x branch.

Hi, I invite you to read one tutorial on communication range. From what you described, it may be range issue. By default, the range model is: a link is only possible if the distance between two vessels is less than the smaller of the two antennas’ ranges.