TaxiService

FYI, you can export your installed mods to a shareable .ckan file The error requires BetterBurnTime, CNC and Signal Delay to happen. If I remove BBT, CNC works fine. If I remove Signal Delay, CNC works fine. I am not even sure if I can resolve this combination. You may have to remove BBT.

@bulletrhli Your point 2 is not bug. This is the popup property of blocking everything except the popup area until the popup is dismissed. What are your list of mods? It seems there is an external interference because I see no conflict between Signal Delay and CNC on my side (KSP+CNC+SD only) so far.

I am not sure about the error now. The error I replicated yesterday is happening in KSP Dev build only, and is different from your error. My error is about Signal Delay's FixedUpdate() not CommNetVessel nature. On official KSP release build, both CNC 1.3.2 and Signal Delay 0.2.9 work fine together, as shown below. Can you check again at your end after downloading the latest CNC build (linky)?

Yup, I replicate your issue with Signal Delay. It has own CommNetVessel subclass like CNC mod's own CommNetVessel subclass, causing mod conflict at your side. I added a new generic error message telling mod conflict to the CNC codebase for easier diagnosis. Thanks for reporting this mod conflict.

Hi, On your fresh save, how did you build a vessel with antennas in VAB? I greatly appreciate this if you can give reproducible steps on a fresh save. The error dump you linked said the mod crashed when accessing the global vessel list (presumably with your vessel launched from VAB) from the game when you opened the constellation control panel in Tracking Station.

Hey, if you are trying to make an image button out of DialogGUIButton, here's this way to get it right! DialogGUIImage img = new DialogGUIImage(new Vector2(32f, 32f), Vector2.zero, Color.white, someTexture); DialogGUIHorizontalLayout imageBtnLayout = new DialogGUIHorizontalLayout(true, true, 0f, new RectOffset(1, 1, 1, 1), TextAnchor.MiddleCenter, new DialogGUIBase[]{ img }); //this is secret ingredient DialogGUIButton btn= new DialogGUIButton("", onClick, 34, 34, false, new DialogGUIBase[] { imageBtnLayout }); //DialogGUIButton takes in ui components Edit: In addition, if the vertical scrollbar of DialogGUIScrollList somehow starts in middle, it is because the pivot of the scroll area is 0.5 in both x and y by default (for unknown reason I have yet to determine) You need to first access protected variable scrollRect of DialogGUIScrollList: Use C# Reflection approach Make subclass of DialogGUIScrollList and then update scrollRect variable (preferably after DialogGUI creation)with codes below. this.scrollRect.content.pivot = new Vector2(0, 1); //set scrollbar to top or this.scrollRect.content.pivot = new Vector2(0, 0); //set scrollbar to bottom

Yah, I am aware of this KSP-RO group's CommNet plan because of deteriorating RemoteTech performance. I recently enlisted help of KSP-RO group to do a sanity-check on RemoteTech 2's realistic comm model and to get suggestions/changes. With this model worked out, I should be able to Finish the revision of the comm model paper based on latest feedback. Resume work on RemoteTech 2's comm implementation iteration in a similar manner of RealAntennas. I have the (long) paper if you want to look over while I do the pending implementation work

@JohnTomato @strudo76 Hi, this is because I never got around to recompile RemoteTech codebase for KSP 1.6.1 as the difference is so minor (5 fixes). RT 1.9.1 will work on both 1.6 and 1.6.1.

Only 1 difference is display of all active connections of all vessels. This mod is more like a code resource for modders interested in enhancing CommNet. Hence, I didn't pay much attention to this mod for long time.

@DeltaDizzy @MaximumThrust My apologies for this prolonged response. I am unable to replicate this scenario error on my side. Nevertheless, I suspect the mod scenario data is botched during saving/loading, and add preventive measure against null-scenario error to this mod. This measure will be included into my other mod, CommNet Constellation to be safe. P.S. New version 1.0.4 is released for KSP 1.7.

CommNet Constellation 1.3.2 is out for KSP 1.7 Color Picker can parse your hex color string Fixed issue of CommNet Range Multiplier not affecting Antenna Power New tool to edit individual antennas' frequencies without going into Flight Scene Linky

RemoteTech 1.9.2 for KSP 1.7 released This release is a standard maintenance. What are fixed/changed: Recompiled for KSP 1.7 Support for Restock and RestockPlus 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.

Sorry but what you see in your fifth picture is stock CommNet's remote pilot feature. This is what RemoteTech remote command feature looks like. Also, RemoteTech does not have any support patch for USI parts. Anyone or us will need to provide such patch for the USI parts.

Oops, someone already beat you to this. Linky

Here you go. Enjoy!

My bad, I misread your first question. There isn't any way to edit the frequency of each antenna from Tracking Scene or another flight scene. However, if you are brave, you can edit Frequency under CNConstellationAntennaModule block of your vessel in your save file (persistent.sfs)

Oh, thanks for clarification. I need to read his post again and think about it. Yes, you can change the frequency of each antenna to the tracking station's frequency. As shown in this picture below, right click the desired antenna and open up the antenna setup. For your second question, how about adding the Mun and Minmus frequencies to the KSC's frequency list? Your moon networks will directly connect to KCS if they have sufficient antenna power.

I doubt these new antennas are compatible with RT unless MM patch is provided (sample for LackLuster Labs antennas). I replied in the kOS thread. Basically, it is configured this way since Jan 2015.

My bad, thanks for finding this issue. It is fixed in the develop branch now. I am sorry but I will not migrate this mod to a realistic comm model. I am working on the new RemoteTech codebase's comm model, loosely based on our real-world reality. As of now, this mod is complementary to the stock CommNet's current difficulty level.

Enjoy latest develop build!

@Shadriss So sorry, I was looking at the other antenna with the similar name. There are two antennas with similar names: HG-5 HGA (Relay) and Comm HG-55 (Direct). In your initial post, you referred to HG-5 HGA. In this case, the maximum range between your moon probe and relay sat (4 HG-5 HGA) is sqrt(15G*14.14M) = 460.5Mm. So your relay sat should definitely work as expected, as shown on my side below. It seems the root cause on your side is somewhere else. But please correct me if you see any other wrong details taken into my account. Can I have your log for further investigation, please?

Your sat with 4 HGs has more than enough radio power to connect with Minmus probe. But the problem is both vessels' antennas (HG-5) are Direct Type. Direct Antennas can't connect to each other and can only connect to Relay Antennas. Your sat with 4 HG-5 is not Relay. Direct to Direct = Not allowed Direct to Relay = Allowed Relay to Direct = Allowed This is the stock behaviour.

Based on my gameplay sandbox test, I found the root cause in your explanation - Direct Antenna doesn't connect to Direct Antenna, per stock behaviour. It can only connect to Relay Antenna (ground stations are classified as Relay Antenna by stock cfg). The stock formula for max range is square root of antenna one's power multiplied by antenna two's power. For example, two HG-5 antennas has 15G max range. So the combined power of the sat with 4 HG-5 is 42.43G (best antenna power * (total power / best power) ^ (sum(expo*power)/total power)). The maximum range between Minmus probe and relay sat is sqrt(15*42.43) = 25.227G. Clearly, it has more than enough range to connect but you can see that the stock behaviour is not allowing this. If I put up another sat with 4 RA-15 each with same 15G power, the moon probe can connect to this relay sat. So yah, KSPedia never mentioned the distinction between Direct and Relay Type. It never uses our real-life concept where two antennas with sufficient power can connect regardless of KSP's "relay or direct thingy".

From my understanding of this stock behaviour, direct antenna can only either connect to ground station or relay antenna but not direct to direct. Relay antenna can connect to direct, relay or ground station. Speaking of which, I just realize HG-5 on your relay sats is Direct, meaning Comm 16 can't even connect to your "relay" sats. Can you check this? Never mind, it is Relay type. I need sleep now.

I am able to replicate this error in 1.6.x if I click Filter by Cross-Section Profile. It doesn't happen in 1.5.x It seems the issue is local to Editor only. It is resolved by exiting and reentering Editor. Time to update the RT ancient parts if I can figure out what is missing :-/ Sure, open RemoteTech_Settings.cfg in your save folder and toggle the first variable RemoteTechEnabled to False. Most of RT interfaces and processes will be shut down .