TaxiService

Yah, I tested and confirmed CNC 1.5.3 is compatible with KSP 1.8.1. The main difference between KSP 1.8.X and 1.9.X is cosmetic. Please assist to provide output_log.txt for further investigation. This error generally happens on outdated antenna data, like you found out with force-update with the antenna config.

Hi, Parts of this feature were actually implemented in RT2 codebase few months ago. A player would start with non-KCS ground stations at stock locations with Level 0 (no power) to upgrade to Level 3. I think it is good time now to enhance this feature with new 2 MM-patch functions of adding new ground stations and edit the locations, and port whole feature over to CNC.

CommNet Constellation 1.5.3 is out for KSP 1.9.1 Added localization support with initial languages of en-us and zh-cn Added toggling of vessels' orbit lines to colour based on vessel's strongest frequency Fixed critical bug of stock CommNetVessel instances, polluting CNC network of nodes and links Added preventative measure against null antenna range curve due probe core antenna being relay instead of internal Linky

Hi @Zorg and @leatherneck6017, I made a fix to the issue of probe core antenna being set to RELAY instead of INTERNAL. Kindly assist to download the latest develop build and test whether the issue is correctly resolved on your side. Thanks!

Hi, it is not compatible with CommNetManager currently. There was some progress of integrating CNM with CNC in separate code branch but the main challenge is the correct understanding and application of CNM interactions between CNC and KSP CommNet. Hope this clarifies.

Hi, A new release for KSP 1.9.1 is not necessary for now since the current release is working well with KSP 1.9.1. But there will be a next release for KSP 1.9.1, contained a major fix to the critical bug of relay antenna reported recently.

Hi, Yes, the issue you faced is the exact same one Zorg reported and your NRE spam also origins from this issue. According to my analysis, the problem is happening, regardless of the category and vessel type. I am attempting to fix the underlying root cause in CNC's CommNet layer

Hi @Zorg, I think the relay issue you reported is the symptom of a larger CommNet issue of CNC. It does not require BDB mod as I am able to reproduce on KSP and CNC only if the antenna of a probe core is changed to RELAY. This probe core has links to 6 ground stations despite no vessel control. As you can see, there is a duplicate comm node for every comm node, which may explain the control issue. It is a miracle that players and I didn't encounter this issue for so long time until you reported the relay issue. I am trying to fix the duplicate issue to see if it resolves the relay issue. Hi @dtoxic, Each antenna of a satellite can connect to destination (Kerbin in your case) separately. The working connection between the satellite and destination is the strongest antenna connection among the antenna connections. See the table below. Relay antenna frequency Internal antenna frequency Connection to Kerbin 0 0 Both relay and internal (Relay dominates due to larger power) 0 1 Relay 1 0 Internal 1 1 None By the way, it may be possible that the relay antenna is third-party mod and not supported by CNC.

Hi, The CNC mod targets the stock ground stations existing to apply its own changes (for example custom color) via GameData\CommNetConstellation\cnc_settings.cfg. To answer your question, I think you need to find a third-party mod that edits/adds ground stations (with their IDs) in the stock CommNet. If you can find it, then you only need to edit cnc_settings.cfg to target those stations to match the JNSQ stations.

Hi, Thanks for uploading your output_log. I notice your log is truncated by the scribd site, leaving the beginning part only available. However, based on this partial log and screenshot, it appears that you installed CNC 1.5.x on your KSP 1.7.3. The version 1.5.x is compiled against KSP 1.8.1 or 1.9, and contains 1 major change (Added new functionality of predetermined ground stations in cnc_settings.cfg). Please rollback your CNC mod to version 1.4 (download from SpaceDock's Changelog tab)) which should work on KSP 1.7.3. Hi @Zorg, Thank you for your confirmation. I will debug the CNC behaviour on the BDB patches and inform you on what I find.

Pplease provide the output_log.txt at C:\Users\YOURUSERNAME\AppData\LocalLow\Squad\Kerbal Space Program. This log contains internal information generated by CNC mod about ground stations. Hi, I tested KSP 1.9 only with CNC 1.5.2 and BDB v1.6.2_hotfix_2, and observed that MOCA probe core has the CNC option of antenna setup in Editor. I can see the probe doesn't connect right out of the box and need to debug this issue first. If it has an antenna part, it connects and uses the 20M antenna as the primary antenna, per expected behaviour. It seems what I see on my side is different from your observations, besides the issue of probe core not connecting out of box. Do you have any idea on which third-box mod is influencing your side?

RemoteTech 1.9.6 for KSP 1.9 released This release is a simple recompilation for KSP 1.9. 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.

CommNet Constellation 1.5.2 is out for KSP 1.9 Recompiled for KSP 1.9 Added support for Near Future Exploration mod Linky

Hi, please provide a screenshot of the frequency dialog with your number input on the pad. In addition, please provide the output_log.txt at C:\Users\YOURUSERNAME\AppData\LocalLow\Squad\Kerbal Space Program.

The patch above won't work as it would be patched last after NFE. Sadly, this patch below would work by CNC patching first before NFE. @PART[*]:HAS[@MODULE[ModuleDataTransmitter]]:FOR[CommNetConstellation] {...} However, the pull request of modifying FOR[CommNetConstellation] to FOR[zzzzCommNetConstellation] was recently submitted by Kerbalism developer to set the CNC patching order to the last, and accepted. With these considered, it is better for me to maintain a separate patch for explicit compatibility between CNC and NFE. Hope this clarifies. ---- Updated patch for your reference

Hi @Nertea, I determined the root cause of the incompatibility between NF Exploration and CNC, which is the patching order of ModuleManager. Currently, CNC patch (cnc_module_MM.cfg) is applied lastly (zzzzCommNetConstellation). However, since NFE patch (NFExplorationAntennaFeedsStock.cfg) will be before CNC patch alphabetically, it will replace all "ModuleDataTransmitter" module with "ModuleDataTransmitterFeedeable" module in all the parts. As such, CNC patch being applied lastly will not work as it won't find any part with "ModuleDataTransmitter" module. I tested the revised CNC patch (two mutual-exclusive part patches on ModuleDataTransmitter) and it seems works. cnc_module_MM.cfg // Add the CNConstellationModule to all parts contained ModuleCommand i.e. the command and probe parts @PART[*]:HAS[@MODULE[ModuleCommand]]:FOR[zzzzCommNetConstellation] { MODULE { name = CNConstellationModule } } // Add the CNConstellationAntennaModule to all parts contained ModuleDataTransmitter i.e. antennas, probe cores and manned cockpits @PART[*]:HAS[@MODULE[ModuleDataTransmitter]]:FOR[zzzzCommNetConstellation]:NEEDS[!NearFutureExploration] { MODULE { name = CNConstellationAntennaModule } } @PART[*]:HAS[@MODULE[ModuleDataTransmitter]]:FOR[NearFutureExploration]:NEEDS[zzzzCommNetConstellation] { MODULE { name = CNConstellationAntennaModule } } // Deployed Experiment Control Station has internal antenna @PART[*]:HAS[@MODULE[ModuleGroundExpControl]]:FOR[zzzzCommNetConstellation] { MODULE { name = CNConstellationModule } MODULE { name = CNConstellationAntennaModule } } //Deployed Sat Dish with huge antenna power //Comment: Too much work to support sat dish that isn't even part of exp control station's commnetvessel //@PART[*]:HAS[@MODULE[ModuleGroundCommsPart]] //{ // MODULE // { // name = CNConstellationAntennaModule // } //} Kindly assist to test and confirm that the CNC patch resolves the issue at your end. Thanks!

Hi Crixomix, 1. Stock CommNet has the setting of requiring connection signal to Mission Control in order to remote-control a vessel. Without signal, the control is full loss if I recall right. 2. I learnt about the new NF Exploration while ago and was surprised when players start to ask me out of blues. I am investigating the compatibility between CNC and NF Exploration. 3. Yes, there is the development of new RT codebase on the top of the stock CommNet but the pace is quite slow due to how Unity Engine handles KSP and CommNet. It is planned that the first iteration will be exactly RT1 functionality and then further enhanced from this point. Hope this clarifies. Hi Javelius, Many thanks for your log. According to your log, CommNetVisualisation is installed on your KSP instead of CommNetConstellation. CommNetVisualisation has only cosmetic change regarding how connections are displayed in Tracking Station and Map View. Please remove CommNetVisualisation and install CommNetConstellation at https://spacedock.info/mod/1309 Thanks.

Hi, Please assist to provide your output_log.txt at C:\Users\YOURUSERNAME\AppData\LocalLow\Squad\Kerbal Space Program Based on your description, the issue may be some of your mods not compatible to CNC mod i.e. no support of CNC for such mod.

Hi Nertea, This mod does not alter or interact with ModuleDataTransmitter in any way. It creates and attaches its own CNConstellationAntennaModule (link 1, link 2) to every vessel part that has ModuleDataTransmitter (i.e. antennas, probe cores and manned cockpits). When iterating over every part interfaced as ICommAntenna (link 3), the mod reads the stock data of ModuleDataTransmitter for its own use. I looked at the ModuleDataTransmitterFeedable codes referred and do not see any possible conflict with my mod. If you would like, I can run with CNC and NFE and debug to see what the problem is. Hope this clarifies.

Hi, Please check your setting of Texture Quality, as shown below. It controls the stock and mod interface quality for performance reason.

RemoteTech 1.9.5 for KSP 1.8.1 released This release contains a large number of bug fixes due to the new Unity engine and KSP 1.8.x. What are fixed/changed: Localization (en-us and zh-cn) (all credits go to tinygrox) Fix issue of wobbling when holding Kill Rotation or Maneuver Node Hide interface of signal delay & control indicator when opening in-flight Action Group Editor Fix issue of ReStock antennas auto-expanding in Editor (HG-5, Comm 16, Comm HG-55 and Comm 88-88) Introduce new flight computer interface of in-flight PID Controller Fix issue of flight computer commands not saved persistently Fix issue of part configuration values being duplicated when saving and loading Fix issue of NullReferenceException when moving deployable science stations between 2 inventories Fix issue of missing science transmission button and information on antennas 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 @David H, Without the output log, I can't help to fix your problem. It is important to find this log because it contains what KSP did in background. The screenshots you provided so far don't really tell what caused. Please look for the log again at C:\Users\%USERNAME%\AppData\LocalLow\Squad\Kerbal space Program\output_log.txt If you manage to find it, use any free upload site like https://pastebin.com/

Hi @David H, Please provide both "RemoteTech_Settings.cfg" of your save and output_log.txt at "C:\Users\YOURUSERNAME\AppData\LocalLow\Squad\Kerbal Space Program" for further investigation. I need to see what your KSP was doing in background.

Hi all, Due to KSP 1.8 and Unity 2019 largely, the amount of bug fixes and changes is quite big. I would like to request for your assistance in playing the beta release (linky) of RemoteTech 1.9.5 and reporting any issue prior to an official 1.9.5 release for KSP 1.8.1. Do make a save backup first before installing this beta release. List of major changes: Localization (en-us and zh-cn) (all credits go to tinygrox) Hide interface of signal delay & control indicator when opening in-flight Action Group Editor Fix issue of ReStock antennas auto-expanding in Editor (HG-5, Comm 16, Comm HG-55 and Comm 88-88) Introduce new Flight Computer interface of in-flight PID Controller Fix issue Flight Computer commands not saved persistently Fix issue of part configuration values duplicated every time saved or loaded Fix issue of NullReferenceException thrown when dragging deployable science stations between 2 inventories) Fix issue of science transmission button and packet information Thanks!

CommNet Constellation 1.5.1 is out for KSP 1.8.1 Ground station changes (e.g. "Jeb's Base" rather than "Kerbin: KSC") can be stored in the CNC setting file for new game saves Fixed issue of all possible control lines shown per vessel in 'All Active Connections' mode Linky