TaxiService

Hey, thanks for showing. Based on my tests and log analysis, it seems something is going wrong on your side related to combination of KK, JNSQ and unknown third-party mod(s). Near the beginning of your log, JNSQ ground stations are added with proper data, included human-readable names, like my own game does. But near the end of your log, JNSQ ground stations were erroneous with non-sense names like "AirBaseS00A_transmitter_mast_0" instead of "Airbase S00A" plus invalid CelestialBody errors. I dont see any obvious mod in your mod list that may cause mod conflict and I can't replicate the data issue on my side. Do you have any idea how it could happen on your side?

Hi, it was static charge accumlated in my "dying" graphic card and my PC is fine now after I de-charged it. I keep it at low-power setting to be sure it is really static charge, not actual dying. According to your log, KK ground stations below were added by KerbalKonstructs(?) On my side, I enabled the KK setting of additional ground stations but it doesn't seem to add any of the additional stations and I saw only stock stations. Can you show how to trigger the addition, please? Thanks

It should be able to see a stock antenna part fine, like this antenna (and power generation) requirement satisfied below. The additional functions, included frequency segregation, from CNC do not change this stock contact in any way. Any chance your antenna part is not stock? Reskinned or mod antennas may be not recognizable to the stock contract.

Hi dave1904, Thanks for the GameData folder. Per discussed, I am trying to replicate the issue on your folder and save on my side. I added more preventative checks based on what I found so far, hopefully to prevent this issue from happening again. Hi, can you give the name of this contract pack mod? If I remember right, there is no contract pack specifically for CNC.

Thanks, I confirmed none of CommNet frequency values is blank in your save, and saw no obvious conflict with your other mods. As such, I added new more preventative checks related to the error. Please replace your CNC copy with CommNetConstellation_5Jan2022. You will still need CommNetManager mod. Do let me know if no more spam is generated for you. Thanks!

Hi, I will take a look at your save. Can you check that your drive link is set to public access? It is returning access denied message and access request when I click your link. Thanks

Hi @dave1904, Your error log is saying at least 1 frequency on one of your comm vessels is blank i.e. "Frequency = " instead of expected "Frequency = <number>". Can you check your certain save file for this pattern below, and put back your frequency, say default 0? MODULE { name = CNConstellationAntennaModule isEnabled = True Frequency = 1 // HERE should be non-blank OptionalName = InUse = True CosAngle = -1 stagingEnabled = True EVENTS { } ACTIONS { } UPGRADESAPPLIED { } }

Beta 4 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 Allow an arbitrary number of upgrades for ground stations in cnc_settings.cfg Fix bug of valid connection displayed in wrong constellation colour Recompiled against KSP 1.12.2 Important: Development and bug fixing is on hold due to my dying graphic card and global chip shortage. Requirements CommNet Constellation + Patched CommNet Manager (download) ModuleManager 4.2.1 Request Please let me know on any issue found. There can be one remaining beta before releasing to the wide audience officially. Thanks!

Hi all, sorry for my prolonged absence. My graphic card is dying since last August, and the integrated GPU in my 2015 Intel CPU is not great. I am not able to find a reasonable graphic card replacement in light of the on-going global chip shortage. Basically, I had to pause my mod development and fixing on hold for the time being. Over this weekend, I will re-compile first against KSP 1.12.2, check if it starts with no error, and release a next official version. I will take look at new bug reports and queries at a later point. Thanks

Hi @panarchist, Thanks for the ping. Hi all, sorry for my prolonged absence. My graphic card is dying since last August, and the integrated GPU in my 2015 Intel CPU is not great. I am not able to find a reasonable graphic card replacement in light of the on-going global chip shortage. Basically, I had to pause my mod development and fixing on hold for the time being. But what I can do over this weekend is to re-compile, check if it starts with no error, and release another beta of CNC+CommNet Manager for latest KSP 1.12.2. Also, do let me know if you would like another official CNC release without CommNet Manager i.e. 1.5.8 after last official version 1.5.7. Thanks

Thanks, I fixed this bug. You can try out the latest build of CNC+CNM.

Do share the antenna setup of those Kerbin satellites. I want to know what makes them different from the Mun ones. Thanks!

Thanks for the screenshots. I replicated your exact scenario on my side. I think these 3 relays actually have direct-relay (purple) or relay-relay (purple) connections between each other but are shown as wrong colour (pink) instead of purple. I need more tests on this to be sure before I fix this. Thanks

From what I tested on direct and relay antennas, I think you are right on color. On full strength, it will show the chosen color but towards 1 strength bar, the redness will be shown. This is the behaviour of stock CommNet This image shows on the outer comm ring, low-strength (more redness) direct connections between all 4 vessels, each with 1 direct antenna of 500k and 1 relay antenna of 5M on green-color channel "Two". If this is not correct, I need more details so that I can replicate on my side. I took a look at the codebase of RealAntennas and it indeed replaces the commnet system with its own by deleting all stock ground stations and creating new stations. This is not something I would like to do because CNC is intended to enhance the stock commnet system.

Hi, I verified it is working on the latest release. With 1 Comm-16 activated, the max range is 2.5Mm. With all 4 Comm-16 activated, the max range is 10Mm. Part Action Menu could need connection statistics like this. I will look into this later. Sorry, RemoteTech and CommNet are incompatible and Remote Pilot cannot be turned on. But you can add 1-Kerbal remote command to a probe core, say RC-001S Remote Guidance Unit, in RemoteTech_Squad_Probes.cfg. It will give your parent craft with at least 1 kerbal inside to remotely control.

Hi, yes, your understanding is correct. A relay will forward the signal from 1 frequency to another frequency. It is actually not governed by CNC so it is nice bonus feature. Yes, those stock stations are forcingly inserted by CommNet when the extra station setting is ticked. I cannot prevent this because it was hardcoded in CommNet behaviour. You will have to tick off this setting. I tested 3 vessels with direct antennas only and they don't make contact with each other, apart from connecting to KSC. Can you double-check if you have any other CommNet mod installed?

Ah um, I can't do anything with this. They are loaded by the game as default. But you can tick off the option of enabling additional ground stations in the stock CommNet setting. It may work with your custom config. Do let me know if it works.

RemoteTech 1.9.12 for KSP 1.12.1 released This release is a recompilation for KSP 1.12.1. What are fixed/changed: Recompiled for KSP 1.12.1 Fixed the misposition of the signal delay interface due to the new alarm button 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, did this happen during the startup loading? You can ignore it as it is harmless. It won't happen after the main menu.

Hi all, I recompiled for KSP 1.12.1 and it is working fine. However, CommNet Manager yet does not accept my pull request of required changes. You can update to the latest CNC+CNM build for KSP 1.12.1.

RemoteTech 1.9.11 for KSP 1.11.2 released This release is a standard update for KSP 1.11.2. What are fixed/changed: Add a new misc option of stopping time wrap when a connection is found Buff RA-15 and RA-100 antennas to be more comparable with Communotron HG-55 and CommTech-1 respectively Add support for a new version of HG-20 antenna in ReStockPlus KSP 1.11 update 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.

I think changes are needed in DefaultActionGroups for this behaviour of ModuleAnimateGeneric. It is not possible to get this mod to work with RemoteTech.

Hi, this MM patch in Antennas_in_Custom03.cfg below is as far as I can go. RemoteTech converts ModuleDeployableAntenna to ModuleAnimateGeneric in all the antennas. But for unknown reason, KSP doesn't localize ModuleAnimateGeneric's localization code to "toggle" when DefaultActionGroups hooks up a new antenna in VAB/SPH.

Hi, I took a look at the codebase and decided small changes would be sufficient to make the upgrade count arbitrary instead of hard-coded 3, provided that a player expands UpgradeableGroundStationCosts and UpgradeableGroundStationPowers in cnc_settings.cfg You can try out the latest CNC+CNM build though I see some hint that underlying CommNet may take up to 3 power levels. Do let me know if you are able to upgrade beyond the 3 upgrade count.

Hi, I am wrong. Two more changes are required to work, on top of the first change. A pull request is submitted to Signal Delay repository.