MalevolentNinja

@Nertea What a great mod, thanks for taking the time to create and share this with the community. I had a thought... would it be feasible and have you considered expanding the effects from this mod to re-entry?

Thanks Nansuchao, for pointing me in the right direction. But just to clear things up a bit, that version you linked is pretty old, and won't work for newer installs of KSP. There are two "official" branches of Kopernicus that I am aware of. There's the "Main" or "Stable" branch and the "Bleeding Edge" branch. This issue with blocked solar panels happens if you have the Main branch version of Kopernicus installed, but seems to be fixed in the Bleeding Edge branch. I haven't done a bunch of testing, just a quick solar panel test. So the BE branch may brake something else, it's kind of in the name Thanks to everyone who responded for your help! Main / Stable branch: https://github.com/Kopernicus/Kopernicus/releases Bleeding Edge branch: https://github.com/R-T-B/Kopernicus/releases IN CKAN, select the Parallax mod, then select the versions tab and the 1.0.1 version. Beyond Home is not compatible with the latest Parallax version at this time.

I'm not. From my original post:

@Gameslinx Is there an easy way to remove the binary star system in Beyond Home and revert to standard Kerbol? I'd like to play with the rest of your changes, but the blocked solar panels is stopping me.

I've searched and didn't find anyone mentioning blocked solar panels in this thread. Which makes me think I am doing something wrong? I am aware I can manually set which star the panels track (via Kopernicus) but that seems like a lot to micro-manage if you have more than a few flights in progress. Is there a way to avoid having to manually change this as the "front" star changes? Minimal install of BH on KSP 1.11.1, installed via CKAN Beyond Home 1.52 EVE 1.11.2.1 Kopernicus release 34 (not BE) Modular FlightIntegrator 1.2.9.0 Module Manager 4.1.4 Parallax 1.0.1 Scatterer 0.0723

Yep, that's what happens when I add a third. I see now what you're saying. Nice find

I was able to replicate @Poodmund's issue with the 1.0.7.3 beta, but I'm not sure I agree with what's causing it. With RangeModifier=2.25 I get this The ship in the editor and the ship in-flight are the same vessel. Strangely, it shows the wrong value for the current vessel's power, but it shows the correct value for the in-flight ship. HG-5 = 5M 5M * 2.25 RangeModifier = 11.25M Two HG-5 total vessel power = 11.25M*2^0.75 = 18.92M

Nice find! 5 places... I looked at the code and couldn't find one. This is why I'm not a programmer Thanks for taking the time to look into this!

Yeah that's what got me in trouble when I said the other mod was doing the same thing, so I started testing with more obscure values

(This is a Sandbox save, so DSN is at level 3. You can see this in the mod, the asterisks are on DSN Level 3) I'm not sure what you mean "Max Range is correct". Here's what I see when I follow my steps. Since the vessel only has one relay antenna, the vessel's antenna power rating is the same as the antenna - 2G * 1.84 And since we are trying to determine max range between two vessels with the same antenna power rating, the max range happens to be the same as the vessel's antenna power rating. MaxRange = SQRT ( Vessel1 * Vessel2 ) This page explains it better than I can: https://wiki.kerbalspaceprogram.com/wiki/CommNet

Sure, here you go. https://www.dropbox.com/sh/d2hogssqlnya7vo/AADw9gHABwhrUjFgUxSnf4Aia?dl=0 Extract to a fresh install of KSP 1.9.1 Open 'Test CommSat' in VAB Open Antenna Helper Select Relay Select Pick A Target Select In Flight Ships Select 'RA-2 In Orbit' - this is the same ship, just cheated into orbit The Range Modifier in this save is set to 1.84. Both Power and Range should be 3.68G (2G * 1.84) Antenna Helper shows 6.77G (2G * 1.84 * 1.84) No rush! Oh and I don't say it enough, thanks for all you do for this community

Yes, I reverted back to the CKAN version for testing since the quick build didn't fix the issue.

I don't know if this helps at all... With range modifier settings of < 1 it seems to work fine. I've only spot checked a couple settings, but they worked. Here's range modifier 0.64 (2G * 0.64 = 1.28G): With range modifier settings > 1 it seems to multiply antenna power by range modifier twice. Here's range modifier 2.48 (2G * 2.48 * 2.48 = 12.3G): You can see CommNet Antennas Info is showing the correct values in the tooltip.

Will do, I'm grabbing a fresh copy now. Edit: New install of KSP 1.9.1 with BG and MH Installed Antenna Helper with dependencies from CKAN Created new save file with range modifier of 1.90 Tested with RA-2. It should be 2G * 1.9 = 3.8G but Antenna helper shows 7.22G which is 2G * 1.9 * 1.9 So I was able to reproduce the issue. I did make a mistake about the other mod having the same issue (sorry!), but I verified again that Antenna Helper does show the wrong info. Replaced mod with build downloaded from dropbox loaded the save Antenna Helper shows range of 2G, which is the RA-2 without factoring in the range modifier So no luck @linuxgurugamer

I will test now. And I need to confess something... I made a mistake. I am very sorry for the confusion. The mod "CommNet Antenna Info" does not have the same problem. That mod shows the correct antenna power ratings with different range modifier settings. My mistake was because I had a leftover MM patch in place that doubled antenna power. Sorry! That said, Antenna Helper is definitely showing the wrong info, as I described above.

I'd be happy to help out any way I can

The VAB/SPH part tooltip does not show the effect of the range modifier setting. See @Poodmund's bugtracker from 2 years ago https://bugs.kerbalspaceprogram.com/issues/19996

I'm no programmer, but what if KSP is giving you the correct antenna power, with the range modifier already factored in, and then you are multiplying it by the modifier again? Edit: Oops, @Poodmund already said that

Hello @flart There seems to be a bug. I tested this in KSP v1.9.1, CommNet Antennas Info v2.4.1 with Antenna Helper being the only other mod installed. Steps to reproduce: Set advanced options range modifier to 2. An RA-2 (default antenna power of 2G) shows an Antenna power of 8G. It should be 2G * 2 = 4G. It seems your mod is taking the range modifier, raising it to a power of 2 and using that as the multiplier for antenna power. I've tested this in game as well - there are more details are in the Antenna Helper mod thread, which has the same problem. Edit: Please disregard all of this. I made a mistake. I am very sorry for the confusion. The mod shows the correct antenna power ratings with different range modifier settings. My mistake was because I had a leftover MM patch in place that doubled antenna power. Sorry!

The CommNet Antennas Info mod acts similar to Antenna Helper. It shows an RA-2 (default antenna power of 2g) with a range modifier of 2 to have an antenna power of 8g. Which I bring up just to point out that the two mods agree, which made me question my sanity So I retested in stock KSP 1.9.1. Here we have two probes, each with an RA-2. And the range modifier is set to 2.25. I propose this math is correct: VesselAntennaPower = RA-2 * RangeModifier = 2,000,000,000 * 2.25 = 4.5G MaxRange = SQRT ( 4.5 * 4.5 ) = 4.5Gm Here's the in game test: I lose the link between the two probes at exactly 4.5Gm. Edit: The other mod 'CommNet Antennas Info' works correctly, my bad.

Nice, I'll check that out!

Also, just be aware, KSP does not show the effect of the range modifier setting in the part tooltip in the VAB. An RA-2 still shows an antenna power of 2G with the setting changed to 2. But it does work in flight.

@linuxgurugamer I agree with @Poodmund - I've done some testing in game also. I started with a stock install of KSP and changed the game setting for range modifier to 2. I cheated a couple sats into orbit, each with one RA-2 relay antenna (antenna power of 2 Gm). I get a very faint link at 4 Gm, but lose connection any farther out. So it seems to me, the range modifier setting is a straight multiplication of the antenna power. The text that appears when you hover over the setting would indicate this also. Since the formula is range = sqrt ( Vessel1AntennaPower * Vessel2AntennaPower), the range will be doubled just by doubling the antenna power.

Howdy @linuxgurugamer There seems to be a bug in this mod. Tested on KSP 1.9.1, AntennaHelper 1.0.7.2, no other mods installed (aside from required dependencies). Steps to reproduce - create a ship with RA-2 relay antenna (antenna power rating of 2 Gm). Target is the same ship. Antenna Helper Mod shows the correct range. Then use the game settings to increase the range modifier to 2.0 Antenna Helper shows antenna power increased by factor of 4. If you change the range modifier setting to 3, Antenna Helper increases range by a factor of 9. It seems the mod is taking the range modifier setting, raising it to a power of 2 and using that as a multiplier. I looked at the source code, but I'm not good enough with C#, I couldn't find the problem. It seems to be in AHUtil.cs? Sorry. Thanks for all you do!

I think there might be a bug with "Time to Manoeuvre Burn" in the Orbital section. From what I can see in the source code (NodeTimeToHalfBurn.cs), it's supposed to be ManoeuvreProcessor.UniversalTime - ManoeuvreProcessor.HalfBurnTime - Planetarium.GetUniversalTime(). It's always close, but it's never quite exact. In this example screen, the m.node is in 103.8s. The burn time is 51.3s. 103.8 - 51.3/2 = 78.2s Kerbal Engineer shows 76.3s Kerbal Engineer Redux v1.1.7.1, KSP v1.8.1, modded. But from what I've seen this happens with no other mods installed.