TaxiService

Hi, it is available on CKAN, about 1 hour after the official release. Please verify that your ckan has KSP version of 1.10.xxxxx ticked in the "Compatible KSP Versions" setting.

RemoteTech 1.9.7 for KSP 1.10 released This release is an update for KSP 1.10 Shared Hozrion. What are fixed/changed: Support for NearFuture Exploration (min 1.0.7) Support for 2 new probe core parts of KSP 1.10 Support for Universal Storage 2 You can set and save the target of a dish antenna in VAB or SPH prior to a launch 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 @Shizen, Thanks for your feedback. Please see the updated sheet and my comments below. 1. The Ax-5 and the F-DA are so similar there does not need to be 2 of them. [TaxiService] AX-5 is demoted and made an attractive entry-level dish. 2. The D-2 Spot and the RA-00-2 are also too similar. Only one is needed. [TaxiService] D-2 is made an attractive entry-level dish for ksync orbit 3. The RA-X2 at first glance seems overly powerful considering its massive angle and low relative power cost. Also i don't think you need such a large antenna angle considering the range is the nearest moon. It would be nice if the spread sheet showed mass of parts as it would make it easier to assess the trade offs. Overall this part isnt needed. [TaxiService] I think this is my mistake in the first place. Given RA-X2 is the biggest phased antenna (a keyboard) and there is only two other dishes for Duna, RA-X2 is made a good choice for moderate power with awesome angle at higher power cost 4. D-50 isnt necessary. There are 6 antenna that reach ksync range and this one doesnt fit any special role that would make you choose it over the other 5. [TaxiService] D-50 is moved to Minus orbit and has a decent moderate power 5. RA-0-8 isnt necessary, its bigger than the RA-100 and uses more power but provides less range, not worth it. [TaxiService] RA-0-8 is made an attractive choice (lower power and higher dish angle) over RA-100 Thanks

Hi, apologies for this late response. May I have your output_log.txt for further investigation, please? I analyzed the KSP behaviour of adding a large assembly to a craft, and it seems the assembly is created or removed, as if it is in launch loading screen. Although your KSP is hanging up when creating the assembly of large part count (I tested as many as 171 parts) in 1 go, I am not convinced that this is why it took some minutes and generates huge log chucks.

CommNet Constellation 1.5.5 is out for KSP 1.10 Recomplied for KSP 1.10 Linky

Yes, this is why your issue occurred with this setting. A new update is committed to CNC to be aware of this setting when initializing extra ground stations or not. Hi, There is no plan for signal delay. It is fully compatible with NFE mod. It is not compatible with Commnet Antennas Consumption.

Hi, I identified the potential culprit - CommNet option of enabling ground stations in the KSP settings. I forgot about this setting when implementing the recent-introduced functionality of custom ground stations. Does it happen to be disabled on your side?

Hi, thanks so much. Based on your log, it is likely a third-party CommNet mod modifying KSP's CommNet functionality so I implemented additional protection against NullReferenceException spam in CNC mod. Feel free to try out the latest CNC build.

Hi, thanks for your logs. I can't find any information that explains why the nullreferenceexception occurs when switching to Tracking Station or Flight scene. If you would like to help further, please download this debug-enabled build and re-trigger the nullreferenceexception on your side. This special build will print out in output_log.txt where the exception happened within the suspected code area. Thanks.

Hi, thanks for the installation information. RealSolarSystem removed most of stock ground stations, resulting in CNC unable to add new ground stations. Can you try out the new dev build contained the fix? With it, I can see "Marsya Base" ground station added. By the way, "RSS_CommNet_Stations.cfg" seems to work in CNC though the names are empty Can you help to provide the output_log.txt for further investigation? This log is telling either CNC setting not available or missing station information.

Hi, I would like to take a look at your RSS patch on my side. Which mods do I need to install, beside CNC and RSS? Thanks.

CommNet Constellation 1.5.4 is out for KSP 1.9.1 New functionality and interface for customizing and/or adding ground stations Warning: All existing ground stations, except for Kerbal Space Center, will be Tech Level 0 (DSN power 0) and require Funds to upgrade to Tech Level 3 (DSN power 80G). Warning: Default list of customized ground stations in cnc_settings.cfg will be only loaded in new games Newer vessels will be on top when sorting by launch time Linky

Hi, up to version 1.5.3, the ground stations shown were locked to the stock ground stations only. You can try out the latest dev build with the new customization functionality for ground stations, or wait for the upcoming release 1.5.4. You should be able to patch the default ground station list in cnc_settings.cfg there.

Hi, the "probe control point" function is belonged to stock CommNet that is disabled by RT. The only visual remote control feature of RemoteTech is the RC-25 Remote Guidance Unit part and its part info. Anything about remote control (eg remote pilot and probe control point) is belonged to disabled CommNet.

Reposted from NearFuture Tech thread for more exposure Hi all, With NF Exploration 1.0.7 supporting RemoteTech, I am requesting your assistance to look over the proposed RemoteTech configs (dev build) for all the NFE antennas. The main issue is there are so many NFE antennas that I can't unilaterally push RT-NFE configs without your feedback on how these antennas should be supported by RemoteTech. Please take a look at the spreadsheet of NFE antenna properties (yellow color). Spreadsheet link Thanks!

Hi @Tokamak, Actually, RemoteTech Remote Command function precedes CommNet Remote Pilot function (earlier than KSP 1.0), and has nothing to do with Remote Pilot requirements such as pilot kerbal. To quality as a command center, a vessel must have enough space for minimum 6 kerbals of any skill, an antenna and a RC-L01 part (red arrow in pic below). You can see I decouple the little RCS probe and fly it around the remote command. Hope this clarifies.

Hi all, With NF Exploration 1.0.7 supporting RemoteTech, I am requesting your assistance to look over the proposed RemoteTech configs (dev build) for all the NFE antennas. The main issue is there are so many NFE antennas that I can't unilaterally push RT-NFE configs without your feedback on how these antennas should be supported by RemoteTech. Please take a look at the spreadsheet of NFE antenna properties (yellow color). Spreadsheet link Thanks!

Hi, each antenna has own button "Transmit all science" that will transmit all science experiments stored in all science parts, based on its science packet details. If you click "Transmit" button on the experiment popup, KSP will randomly pick any working antenna to transmit, which is obviously sub-optimal. However, the science packet information on all the antennas, included the orange giant one, is more or less same, and not really diversified. So you will face the same transmission bandwidth on all the antennas.

Sorry, you are correct. You will need to visit each unloaded vessel in flight so that KSP can update and save that vessel with missing part modules, include CNC ones. Hi, RemoteTech is not compatible with CNC so you can only choose either CNC (improved CommNet) or RemoteTech (higher player control and difficulty)

This command center requires RC-L01 part and minimum 6 Kerbals to work, as shown below.

Hi @DY_ZBX, I found this little-known interface that allows the antenna targeting in Map View or Tracking Station. This is why the target window disappears when switching to Map View. Please use this inteface instead.

Hey, thanks a lot for demonstrating the bug. I found the root cause but fixing it turns out to be more complicated than I thought. I am trying to fix it.

Yes, this is the stock probe core but you need to be aware that RemoteTech adds internal antenna of 3 km range to all probe cores for short range comm. Hi, I tested the antenna target window at my side without any issue. The info window only disappears when mouse cursor is hovering on No Target or Active Vessel entries. Do you have any reproduction steps to trigger your issue?

Hi, my apology for delayed response. Please provide output_log.txt at C:\Users\%USERNAME%\AppData\LocalLow\Squad\Kerbal space Program Your problem description indicates a massive mod-version difference on KSP version between since the version 1.4 is for KSP 1.7.x. Making Less History disables 2 ground stations (Dessert and Larkes), causing NRE spam when CNC tried to read those stations. As per dtoxic recommended, I pushed the fix yesterday to exclude any disabled ground station. Many thanks for your impression details. You can try the latest build with the new interface of upgrading a ground station. Briefly, when you start a new game, all ground stations are at Tech Level 0, except for KSC which starts at Tech Level 1 and is upgraded via KSC scene. Through the new interface, it costs Funds to upgrade a ground station (except for KSC): Tech Level 0 - 0 DNS power Tech Level 1 - 3.1M DNS power and Funds 100,000 to upgrade from 0 to 1 Tech Level 2 - 20M DNS power and Funds 300,000 to upgrade from 1 to 2 Tech Level 3 - 60M DNS power and Funds 900,000 to upgrade from 2 to 3 UpgradeableGroundStationCosts, UpgradeableGroundStationPowers and default ground-station list are configurable in the CNC setting file. For some of your questions, I do not touch the altitude of a ground station and it seems like meters from sea level. I keep the tech level to max 3 in alignment with KSC's tracking station levels (1 to 3). Hope this clarifies.

Hi, I pinpointed to the mod conflict to the CommNetVessel class. SignalDelay implemented own CommNetVessel subclass, SignalDelayVesselModule, but CNC has own CommNetVessel subclass, CNCCommNetVessel. Due to the way KSP's CommNet runs, only 1 class of CommNetVessel can be allowed at a time, resulting in all vessels having SignalDelayVesselModule in the reporter's play session. This causes problems on CNC side as it can't find CNCCommNetVessel in a vessel. Unfortunately, there is no easy resolution to the 1-class problem.