Search the Community

I'm playing in sandbox and want to send Bob to ike,is 3 synchronous orbit relays and 1 in sol orbit enough to always get signal? (I will use the biggest antenna)

I'm completely new to KSP and currently trying to set up a CommNet. Is it necessary for the relay antenna on a communication satellite to point at Kerbin? Also, do you need two (relay) antennae, one on each side? (the 1st one aligned to Kerbin, the 2nd one to e.g. a probe)

Stock Antenna Balance Uses ModuleManager to adjust the range, power usage and other attributes of the stock antennas and how they function with the new CommNet that was added in KSP 1.2. This makes it much more important to use a mix of direct and relay antennas to communicate with Kerbin's Deep Space Network (DSN). License GPL 3.0 Links: SpaceDock / GitHub (downloads & source) Source code: https://github.com/WuphonsReach/KSP-StockAntennaBalance Current effects: Direct-connection antennas are changed so that you usually can't reach back from Jool/Eeloo without relying on a relay network. Stock antennas now have better defined niches. Relay antennas are now equivalent in power (or stronger) then DSN antennas on Kerbin's surface. This makes it possible to disable the extra ground stations on Kerbin's surface in the difficulty options. The drawback is that relay antennas also consume a lot more power when transmitting data and should not be used on science-gathering probes / spacecraft. Relay antennas are also heavier and more expensive and some have constant power draw. The optional contracts will give you guidelines on how much battery capacity you need to operate through Kerbin's shadow. Full details are available at GitHub, including sample network links. Installation: Because this is all done through ModuleManager patches and no new models or assets are included, it doesn't matter where you put the contents of the .zip file as long as it's under GameData/ somewhere. This also means that as long as ModuleManager and ContractConfigurer support the newest KSP versions, then this addon will probably work okay as well. You must have ModuleManager installed (or from GitHub releases), this comes with a lot of other addons, so I'm not including it. Installation of ContractConfigurer is optional, but provides in-game contracts for building out your CommNet. Download one of the releases from GitHub. Extract the .zip file into a folder under your GameData/ directory. Upgraders should delete the old folder before installing the new version. There are no settings that get shared across releases and this prevents problems in case I rename one of the configuration files. Effect on existing games: May cause loss of probe / craft control due to changed CommNet ranges. May cause power issues due to the constant power demand of the relay antennas. Science gathering spacecraft may be unable to send data back home if they only have relay antennas installed (and not enough battery capacity or power generation ability to process and transmit the data). Removal is easy as long as you have not used any of the antennas which were added by this mod, removing this addon's folder under GameData/ will revert your antennas to the stock capabilities. Recommended KSP difficulty settings: These are available in the "Settings / Difficulty Options / Advanced" menu and can be changed at any time in a career save. I'm running with the following values in my current career save: DSN Modifier set to between 0.02 and 0.10 Turn off "Enable Extra Groundstations" Occlusion Modifier, Vac = 1.02 Occlusion Modifirer, Atm = 0.98 If you don't adjust these values, you'll find that the DSN ground stations are often going to take priority over those relay satellites that you lovingly placed into KEO orbits. Change log: https://github.com/WuphonsReach/KSP-StockAntennaBalance/blob/master/CHANGES.md ModuleManager Patches included for these mods: DMagic Orbital Science (Soil Moisture sensor and SIGINT experiments) SXT Continued (Comm DTS-R4, Komm 16)

Greetings everyone! I recently started to built larger communication infrastructures supporting massive explorations towards Duna and Eve. Now I've seen a video by Scott Manley talking about sunsynchonous orbits and was wondering if those mechanics might help in optimizing communication networks. So, is it possible to have 2 different satellites orbiting both Duna and Ike, Eve and Gilly so that the planetary satellites keep a sunsynchonous orbit with their respective moons as the "sun"? Same goes for the moons. Espescially in case of Duna and Ike, who are tidally locked where I could have permanent outposts on their surface both facing each other.

I'm away on business for a couple of weeks so I can't test this out on my PC but I've been thinking of a mission outline that relies on proper usage of Commnet. Let's say I have: a rover on Ike with a Communotron 16 (Ike surface facing away from Duna, but in LoS of Ike relay), a 2 satellite highly elliptical relay with HG-5 around Ike (no LoS to Kerbin but LoS to Duna relay) , and a 3 satellite equatorial relay with RA-15 or RA-100 around Duna (LoS to Ike relay and Kerbin) Does the default Commnet allow the rover on Ike to be controlled on the surface, with the signal bouncing from Kerbin-->Duna relay-->Ike relay-->Ike rover? Or do I need to have a relay in Ike orbit capable of reaching Kerbin? Here's what I quickly threw together to illustrate my question: On a side note, would Remotetech allow this connection (signal from point A to B to C and then finally to D, or even further to E), given the appropriate omni and dish antennae?

Hi Guys I started with KSP 1.5 with only 1 Ground Station. And my Probe just lost Connection on his way to Mun. It has enough Antenna Power To put my problem in a larger scale: How can i archive a permanent Connection from Jool (or any Planet, doesnt really matter) if my only ground Station is on the other side of Kerbin? Do i really have to build a Relay satellite around Kerbin with power of same power as the Tracking Station on LVL 3 (158 Gm). Seems a bit overkill to me Just two pictures for comprehension: https://imgur.com/a/eyWjItU Thx for your help

Caveat: I admit that it is entirely possible that I was being too cute for my own good. I've launched my first fleet for Duna, and it includes a ship with a stack of HECS cores each with as battery, a pair of OX-4L solar panels, and an RA-2, with decouplers to separate them. The plan is to arrive at Duna with plenty of delta V, park myself in nice wide orbit, say 4-5 Mm, pop off the first relay. And this is where I've hit a rough patch. What sequence of maneuvers will put me back in the same orbit, but X degrees ahead(or behind) the first relay?

Now I got the understanding that with commnet, one can control an unmanned probe if the command module/probe core have "probe control point". However, the next sticking point is: Suppose Vessel A, B, C are not connected to KSC. Vessel A is a Lander Can Mk2 (aside from MEM and Mk1-3, it also have Probe Control point), with 1 Pilot and 1 Kerbalnaut. vessel B has an advanced probe core and a Cabin, containing a non pilot kerbalnaut Vessel C is an unmanned probe. Based on my understanding, A can control C, and B can also control C, right? If B cannot, would (B') where the kerbalnaut is a pilot allow (B') to control C? EDIT: Thank you. so in my case, Vessel B' will suffice.

Hi everyone, I've picked up KSP again recently and am trying to build a comm network local to Kerbin. For context: I'm playing on pretty hard settings, and I only have a ground comm station at the KSC itself, not anywhere else on the planet. This pretty much means that I need a comm network local to Kerbin itself. I'm at the point in the tech tree where I only have the 5M relay antennas. For various reasons it would be really nice to be able to launch and control probes around Kerbin (and due to settings I don't have probe control unless I have a comm-link). In case it's relevant I'm using the Kerbal Engineer plugin (automatic suicide burn and Δv calculations FTW!) and the latest KSP available for download. My plan was a three-relay-sat constellation at 2.15Mm altitude (so a 2.75Mm orbital radius). Since the three comsats will form a equilateral triangle, that means by the law of sines the side length between any two comsats will be 2.75Mm * sin(3π/2) / sin(π/6) = 4.76Mm. This was based on the understanding that since the 5M relay antennas have a comm rating of 5M, that means the maximum distance two relays can talk with each other is √(5e6 * 5e6) = 5Mm. Since 4.76Mm < 5Mm, they should be in (low-signal-strength) contact with each other. However, I've placed two of the three relay sats (launching 2 at a time, for redundancy) and despite being almost exactly 4.76Mm apart from each other, there's no comm link. They can both talk with the ground station just fine, but not with each other --- the "network" and "vessel link" views don't show a link, nor can I control the one with an occluded link to the KSC. What am I misunderstanding? Thanks! - ethereal

Greetings! I've finally worked on building my first CommNet, but I find myself a bit confused after reading https://wiki.kerbalspaceprogram.com/wiki/CommNet and doing some searching here on the forums. Here is my situation: Level 2 Tracking Center 4 Satellites orbiting Kerbin at an altitude of ~777km (Screenshot:https://i.imgur.com/Po3BR5g.png) Each satellite has 4 antennas. Three RA-2s and one 16-S Two RA-2s from each dish are pointed at sibling satellites. One RA-2 is available for tasking as needed. One 16-S is used for comms with Mission Control My confusion is, the RA-2 has a stated range of 200Mm which, as I understand it means 200,000,000 meters. As a result, my expectation was that this commnet would be good for unmanned missions to Minmus or closer. However, on the CommNet wiki page (specifically the table on top) it states that with a level 2 tracking center and a RA-2 that the range is 10Gm or all the way to Moho (if it is close). I am unclear how it could possibly have that range with the RA-2 only have a max range of 200Mm. Can someone help me understand what I'm missing? Thank you!

Outside of the CustomBarnKit method - is there a way to SET the DSNRange property to adjust the value while in the flight scene / after the save game has loaded? I've only seen CustomBarnKit do this on Game Load to preset the available options for upgrading levels / costs. I'm thinking what I'm after is probably not possible, but wondered what the wisdom of the crowd says? Checking the values for stock - I can see the current DSNRange via the GameVariables.Instance.GetDSNRange(trackingStationLvl) all fine there. Different idea - is it possible to overwrite the GetDSNRange function to perform my own lookup of values based on some custom criteria? While it's not DSNrange, I did notice a curiosity that the returned level int for the GameEvents.OnKSCFacilityUpgraded for the tracking station gives the levels as 0, 0.5, & 1 - pretty much everywhere else uses the range 0,1 & 2. Separate question - is there a nice way to set a DestructibleBuilding to the destroyed state without having to get through the DemolitionFX?

While developing a new feature for my mod Antenna Helper I came across a bug in the CommLink list attached to each vessel. In order to get the "real signal strength" of a vessel I need to multiply the signal strength of each link in the path between this vessel and the DSN. I do it like this : foreach (Vessel v in FlightGlobals.Vessels) { double realSignal = 1d; foreach (CommNet.CommLink link in v.Connection.ControlPath) { realSignal *= link.signalStrength; } } And it works good, most of the time, sometimes the link.signalStrength is off, still in the 0 - 1 range but wrong according to the in-flight display : in flight : it's always accurate at the space center : * when coming from the main menu : accurate most of the time * when coming from the editor or the tracking station : always accurate * when coming from flight : always wrong at the Tracking Station : * first time entering it : accurate most of the time * n+1 time entering it : always wrong At first I believed I was getting the info too early, before the CommNet gets properly initialized, but even with a coroutine that wait 10s before retrieving the signal strength it was still off. For a proper testing I wrote a little plugin that display all the link of all the vessel when a CommNet event is fired (only three exist : OnNetworkInitialized, OnCommStatusChange and OnCommHomeStatusChange), the plugin also display the link when pressing X. You can find it, along with its source, here. (Launch a game, open the console and look for entry starting by "[CommTry]") This save can be helpful, it has three ships, relay_A (signal of : 66%), relay_B (signal of : 36%) and transmitter (connected to relay_B : 69%, combined : 25%). I wanted to bring it to the attention of the forum before writing a proper bug report, I check and it haven't been reported. But @TaxiService made a bug report about incorrect value in the CommNet instance. This may be connect to my issue but not sure : in the CommNet instance, values are always off (and way off, not even in the 0 - 1 range) but in the Vessel.Connection.ControlPath.CommLink they are sometimes valid... @TaxiService your issue still stand, I add a method to test it in my plugin, press Y and it list all the existing links (from CommNet.CommNetNetwork.Instance.CommNet.Links). Pinging @RoverDude, he was assigned @TaxiService issue.

Introduced in 1.2, the CommNet feature made communications-satellite constellations relevant in the base game. A relatively easy way to provide pretty good communications coverage is a three-satellite constellation in an equatorial orbit. However, such a constellation does not provide full coverage over the entire surface of a celestial body. But a four-satellite constellation, if placed in a tetrahedral configuration, does! With that in mind: I've compiled a list of orbital parameters for this kind of tetrahedral constellation for every celestial body in the Kerbol system. Legend INC. Inclination ECC. Eccentricity SMA. Semi-Major Axis LAN. Longitude of the Ascending Node LPE. Longitude of Periapsis (a.k.a. Argument of Periapsis) MNA. Mean Anomaly at Epoch EPH. Epoch Moho Satellite 1 INC. 33° ECC. 0.28 SMA. 1812500m LAN. 0° LPE. 270° MNA. 0 EPH. 0 Satellite 2 INC. 33° ECC. 0.28 SMA. 1812500m LAN. 90° LPE. 90° MNA. -1.57078 EPH. 0 Satellite 3 INC. 33° ECC. 0.28 SMA. 1812500m LAN. 180° LPE. 270° MNA. 3.14159 EPH. 0 Satellite 4 INC. 33° ECC. 0.28 SMA. 1812500m LAN. 270° LPE. 90° MNA. 1.57078 EPH. 0 Eve Satellite 1 INC. 33° ECC. 0.28 SMA. 5075000m LAN. 0° LPE. 270° MNA. 0 EPH. 0 Satellite 2 INC. 33° ECC. 0.28 SMA. 5075000m LAN. 90° LPE. 90° MNA. -1.57078 EPH. 0 Satellite 3 INC. 33° ECC. 0.28 SMA. 5075000m LAN. 180° LPE. 270° MNA. 3.14159 EPH. 0 Satellite 4 INC. 33° ECC. 0.28 SMA. 5075000m LAN. 270° LPE. 90° MNA. 1.57078 EPH. 0 Gilly Satellite 1 INC. 33° ECC. 0.28 SMA. 94250m LAN. 0° LPE. 270° MNA. 0 EPH. 0 Satellite 2 INC. 33° ECC. 0.28 SMA. 94250m LAN. 90° LPE. 90° MNA. -1.57078 EPH. 0 Satellite 3 INC. 33° ECC. 0.28 SMA. 94250m LAN. 180° LPE. 270° MNA. 3.14159 EPH. 0 Satellite 4 INC. 33° ECC. 0.28 SMA. 94250m LAN. 270° LPE. 90° MNA. 1.57078 EPH. 0 Kerbin Satellite 1 INC. 33° ECC. 0.28 SMA. 4350000m LAN. 0° LPE. 270° MNA. 0 EPH. 0 Satellite 2 INC. 33° ECC. 0.28 SMA. 4350000m LAN. 90° LPE. 90° MNA. -1.57078 EPH. 0 Satellite 3 INC. 33° ECC. 0.28 SMA. 4350000m LAN. 180° LPE. 270° MNA. 3.14159 EPH. 0 Satellite 4 INC. 33° ECC. 0.28 SMA. 4350000m LAN. 270° LPE. 90° MNA. 1.57078 EPH. 0 Mun Satellite 1 INC. 33° ECC. 0.28 SMA. 1450000m LAN. 0° LPE. 270° MNA. 0 EPH. 0 Satellite 2 INC. 33° ECC. 0.28 SMA. 1450000m LAN. 90° LPE. 90° MNA. -1.57078 EPH. 0 Satellite 3 INC. 33° ECC. 0.28 SMA. 1450000m LAN. 180° LPE. 270° MNA. 3.14159 EPH. 0 Satellite 4 INC. 33° ECC. 0.28 SMA. 1450000m LAN. 270° LPE. 90° MNA. 1.57078 EPH. 0 Minmus Satellite 1 INC. 33° ECC. 0.28 SMA. 435000m LAN. 0° LPE. 270° MNA. 0 EPH. 0 Satellite 2 INC. 33° ECC. 0.28 SMA. 435000m LAN. 90° LPE. 90° MNA. -1.57078 EPH. 0 Satellite 3 INC. 33° ECC. 0.28 SMA. 435000m LAN. 180° LPE. 270° MNA. 3.14159 EPH. 0 Satellite 4 INC. 33° ECC. 0.28 SMA. 435000m LAN. 270° LPE. 90° MNA. 1.57078 EPH. 0 Duna Satellite 1 INC. 33° ECC. 0.28 SMA. 2080000m* LAN. 0° LPE. 270° MNA. 0 EPH. 0 Satellite 2 INC. 33° ECC. 0.28 SMA. 2080000m* LAN. 90° LPE. 90° MNA. -1.57078 EPH. 0 Satellite 3 INC. 33° ECC. 0.28 SMA. 2080000m* LAN. 180° LPE. 270° MNA. 3.14159 EPH. 0 Satellite 4 INC. 33° ECC. 0.28 SMA. 2080000m* LAN. 270° LPE. 90° MNA. 1.57078 EPH. 0 * Note: The correct semi-major axis of 2320000 metres causes satellites to eventually be pulled away by Ike's gravity. The listed SMA corresponds to the highest stable orbit I could find. Ike Satellite 1 INC. 33° ECC. 0.28 SMA. 942500m LAN. 0° LPE. 270° MNA. 0 EPH. 0 Satellite 2 INC. 33° ECC. 0.28 SMA. 942500m LAN. 90° LPE. 90° MNA. -1.57078 EPH. 0 Satellite 3 INC. 33° ECC. 0.28 SMA. 942500m LAN. 180° LPE. 270° MNA. 3.14159 EPH. 0 Satellite 4 INC. 33° ECC. 0.28 SMA. 942500m LAN. 270° LPE. 90° MNA. 1.57078 EPH. 0 Dres Satellite 1 INC. 33° ECC. 0.28 SMA. 1000500m LAN. 0° LPE. 270° MNA. 0 EPH. 0 Satellite 2 INC. 33° ECC. 0.28 SMA. 1000500m LAN. 90° LPE. 90° MNA. -1.57078 EPH. 0 Satellite 3 INC. 33° ECC. 0.28 SMA. 1000500m LAN. 180° LPE. 270° MNA. 3.14159 EPH. 0 Satellite 4 INC. 33° ECC. 0.28 SMA. 1000500m LAN. 270° LPE. 90° MNA. 1.57078 EPH. 0 Jool Satellite 1 INC. 33° ECC. 0.28 SMA. 43500000m LAN. 0° LPE. 270° MNA. 0 EPH. 0 Satellite 2 INC. 33° ECC. 0.28 SMA. 43500000m LAN. 90° LPE. 90° MNA. -1.57078 EPH. 0 Satellite 3 INC. 33° ECC. 0.28 SMA. 43500000m LAN. 180° LPE. 270° MNA. 3.14159 EPH. 0 Satellite 4 INC. 33° ECC. 0.28 SMA. 43500000m LAN. 270° LPE. 90° MNA. 1.57078 EPH. 0 Laythe Satellite 1 INC. 33° ECC. 0.28 SMA. 2909000m* LAN. 0° LPE. 270° MNA. 0 EPH. 0 Satellite 2 INC. 33° ECC. 0.28 SMA. 2909000m* LAN. 90° LPE. 90° MNA. -1.57078 EPH. 0 Satellite 3 INC. 33° ECC. 0.28 SMA. 2909000m* LAN. 180° LPE. 270° MNA. 3.14159 EPH. 0 Satellite 4 INC. 33° ECC. 0.28 SMA. 2909000m* LAN. 270° LPE. 90° MNA. 1.57078 EPH. 0 * Note: As pointed out by boccelounge: given these orbital parameters, the correct SMA of 3625000 metres is outside of Laythe's sphere of influence. The listed SMA is the closest possible value that is still within Laythe's sphere of influence. Vall Satellite 1 INC. 33° ECC. 0.28 SMA. 2175000m LAN. 0° LPE. 270° MNA. 0 EPH. 0 Satellite 2 INC. 33° ECC. 0.28 SMA. 2175000m LAN. 90° LPE. 90° MNA. -1.57078 EPH. 0 Satellite 3 INC. 33° ECC. 0.28 SMA. 2175000m LAN. 180° LPE. 270° MNA. 3.14159 EPH. 0 Satellite 4 INC. 33° ECC. 0.28 SMA. 2175000m LAN. 270° LPE. 90° MNA. 1.57078 EPH. 0 Tylo Satellite 1 INC. 33° ECC. 0.28 SMA. 4350000m LAN. 0° LPE. 270° MNA. 0 EPH. 0 Satellite 2 INC. 33° ECC. 0.28 SMA. 4350000m LAN. 90° LPE. 90° MNA. -1.57078 EPH. 0 Satellite 3 INC. 33° ECC. 0.28 SMA. 4350000m LAN. 180° LPE. 270° MNA. 3.14159 EPH. 0 Satellite 4 INC. 33° ECC. 0.28 SMA. 4350000m LAN. 270° LPE. 90° MNA. 1.57078 EPH. 0 Bop Satellite 1 INC. 33° ECC. 0.28 SMA. 471250m LAN. 0° LPE. 270° MNA. 0 EPH. 0 Satellite 2 INC. 33° ECC. 0.28 SMA. 471250m LAN. 90° LPE. 90° MNA. -1.57078 EPH. 0 Satellite 3 INC. 33° ECC. 0.28 SMA. 471250m LAN. 180° LPE. 270° MNA. 3.14159 EPH. 0 Satellite 4 INC. 33° ECC. 0.28 SMA. 471250m LAN. 270° LPE. 90° MNA. 1.57078 EPH. 0 Pol Satellite 1 INC. 33° ECC. 0.28 SMA. 319000m LAN. 0° LPE. 270° MNA. 0 EPH. 0 Satellite 2 INC. 33° ECC. 0.28 SMA. 319000m LAN. 90° LPE. 90° MNA. -1.57078 EPH. 0 Satellite 3 INC. 33° ECC. 0.28 SMA. 319000m LAN. 180° LPE. 270° MNA. 3.14159 EPH. 0 Satellite 4 INC. 33° ECC. 0.28 SMA. 319000m LAN. 270° LPE. 90° MNA. 1.57078 EPH. 0 Eeloo Satellite 1 INC. 33° ECC. 0.28 SMA. 1522500m LAN. 0° LPE. 270° MNA. 0 EPH. 0 Satellite 2 INC. 33° ECC. 0.28 SMA. 1522500m LAN. 90° LPE. 90° MNA. -1.57078 EPH. 0 Satellite 3 INC. 33° ECC. 0.28 SMA. 1522500m LAN. 180° LPE. 270° MNA. 3.14159 EPH. 0 Satellite 4 INC. 33° ECC. 0.28 SMA. 1522500m LAN. 270° LPE. 90° MNA. 1.57078 EPH. 0 The information in this post is based on John Draim's paper, Three- and Four-Satellite Continuous-Coverage Constellations, and an excellent thread by maltesh. The maths are all his; I only did the number-crunching and table-setting.

Recently starting new career saves using CommNet, and found out that no antenna is consuming any EC when i'ts idle. It was a bit strange because I could still control probes and activate various parts at no cost at all. As this is the case for both relay and direct antennas, relay antennas which can handle signals from various sources has no disadvantage of the feature, making direct antenna somewhat less attractive. How about add a module that forces base EC consumption whenever an antenna is deployed? And set those values differently for their target range, actual communication range, type? Then You'll have to spend a lot more time in VAB editor wondering whether the EC generation on current vessel can handle these antennas or not, and direct antennas will be attractive option for more situations.

What does multihopping mean, exactly? I've seen it on some command pods, and even searched it up on what it means, but nothing really explained to me what it is. So I decided to go here, the forums, to ask this very question. So what does multihopping mean?

I've been using CommNet for a while, and love it. I have just managed to find myself in a particular situation I want answers to in my science game. In it, I'm still waiting for transfer windows thanks to kerbal alarm clock, so I'm sticking to Kerbin system-based operations. My rather primitive and outdated relay system contains two relay sats, exactly the same including layout, with four of the antennas directly superior to the Communitron 16, except they're pointing opposite directions. This is obviously because they're supposed to be on opposite sides of Kerbin(And yes I do have newer antennas.) Anayway, I did not align the orbits perfectly so they shifted very close to each other, so any vessel can hit up both at once. In Map view, I noticed one of my ships had a very strong(green) connection to probe A but a weak(red) connection to probe B. They have since moved on but I still want to know: Is the weak connection because the antennas were pointing away from the target? Does signal strength relate to the angle of an antenna relative to the connection direction? Thanks in advance. --GKSP

Hey guys, can you help me? Since the introduction of Commnet in KSP 1.2 I am looking for a mod that lets me say to a probe: "Do this action (for example Retro-burn) in 30 minutes". This is because I often have the problem that I can't circularize my orbit because I am not connected to KSC because the planet is in my way. Are there any mods that let me do this?

I don't know if it's something I'm doing wrong, but my relay satellites don't seem to be working. Despite having a sat halfway between Minmus and Mun, my Minmus probe refuses to connect to anything except Kerbin itself. The probe in question:

So I was thinking about this the other day, and realized one simple thing: for crewed craft that intend to return to kerbin, there is no point to maintaining a commnet(or kerbnet if u call it that) link to the KSC. So I was thinking about a perfect option for that, which is to limit the visibility in map mode without a link. I would say that one will not be able to see beyond their current soi that they are in or beyond 1m meters, whichever is closer(this is so people could not see everything when they are in kerbol orbit). Another thing for this limited map is that the orbits will only show the same amount as the lvl 1 tracking station aka no patched conics or encounters. If this is implemented, then players will be more enticed to build a relay network, making the game more fun. Also, if there is a mod for this that works in 1.3 that you know of please point to it. thank you, 322997am

I'm trying to send probes to Eve, and am having trouble being able to communicate with my landing probe once I separate from the stage that got me to Eve orbit. The stage that remains in Eve orbit has 2 RA-2 Relay Antennas, and my Kerbin DSN Ground station has bee upgraded to L3. I obviously want to have control over my probes during re-entry, so a big dish is out of the question, but when using a Communotron 16, or even the probe core (a Probodobodyne OKTO), as soon as I separate from the stage that has my relay antennas, I loose all control over the probe. I was expecting that the probe core, either via its internal antenna, or the Communotron 16, would relay via my stage and its RA-2's back to Kerbin, but no. The only antenna that give me any kind of connection is a DTS-M1, and that shows as communicating directly back to Kerbin, rather than through the relay. A DTS-M1 is not going to survive Eve re-entry. I don't think its a range issue, as I loose control of my landing probe as soon as I separate, I have extended antennas, and even tried re-orienting the stage with relays just in case the stage body was occluding the signal from my probe to the relay antenna, but no luck. The KSpedia show a table that gives ranges for different combinations of antennas - Class 0 (Probes) unto class 5, as well as the different upgrade levels of the Kerbin Ground Station, but I can't see in the parts guide what class a particular antenna would be. I am using KSP 1.21.1604 on Mac. Any thoughts/suggestions? Thanks Paul

What are the rules around daisy chaining unmanned probes in Commnet for both science and control? This is my experience: I'm decided to setup a ring of simple unmanned relays in a solar orbit identical to Kerbin's. So for example for 3 relays, you'd see in Kerbin orbit: relay, relay, Kerbin, relay (forming a perfect square). So I went ahead by building a standard probe around the Probodobodyne OKTO, HG-5 High Gain Antenna and RA-2 Relay Antenna. I added batteries and solar panels and off I went launching several of them into Kerbol orbit. The two first probes were easy enough. They are both roughly 8Gm away from KSP and made direct CommNet connection with KSP. I hit a roadblock however at the 3rd probe, which was around 16Gm from KSP but 8Gm from the probe 1. Probe 1 has the HG antenna deployed, the batteries were charged yet refused to relay to KSP. Instead I'm stuck with probe 3 with direction connection to KSP with 1% strength! The table at http://wiki.kerbalspaceprogram.com/wiki/CommNet only gives distances for direct connections so I'm in the dark. What rule have I neglected? Thanks! EDIT: I'm in science mode and KSP is full lvl 3. Range for the relay is 22Gm to ksp.

Currently the only means to transmit science is from a vessel to the KSC-but what if you could transmit it from vessel to vessel? I see two main uses for this-if a vessel had a relay antenna and an RGU on it (a probe control point, manned or not), other craft could transmit to that vessel (storing the experiments in the RGU) even when it is in the comm shadow of whatever body it is orbiting, to be (automatically or manually) forwarded to the KSC when the relay comes back into contact. This would be very useful for landed craft with geostationary satellites that frequently lose connection, even more so when they are on large bodies. This is especially so in the case of gas giant atmodiver probes, since they can't wait for the planet to orient itself favourably so their relay has LOS during the transmission window. The other would be when a kerbal is on EVA. If an EVA kerbal had a tiny, short-range antenna built into their spacesuit that treated all antennas within physics range as relay antennas and could transmit science to them (esp. EVA reports) for relaying back (though the direct transmission mentioned above could only be done after transferring the data to a vessel), draining EC from the relaying vessel as normal (this is why the range should be <2.4km) to prevent exploitation. This would allow the transmission of science without having to walk back to a vessel every time and sift through the potentially hundreds of science reports stored in it to pick out the ones you collected while on EVA to transmit. I'm guessing this in't covered by the "common suggestions" this time? if it is, please berate me .

So, I set up a (relatively) geosynchronous comm ring around Kerbin, as I disabled the other ground stations for communication. My problem is that I am getting a strangely weak comm signal. All three satellites are exactly the same, they have two HG-5 High Gain Antennas, and I have a tier two Tracking Station. I am relatively early game and do not have access to any better antennas. The satellite directly connected has a 100 percent connection. The one connected to it, roughly on the other third, has only a 17 percent connection. The third one hasn't been set up yet. Don't know what else to add. Some pictures: If this is an intended feature, which it probably is as I read more into it, what workarounds are there? Especially considering I disabled the other ground stations.

Hi, i'm having some maths problems. Can anyone explain my error. I've ended up with relay stations with 32 HG-5 High Gains. (Based on maths, but i guess if this is wrong then that is too). Using the wiki I think the power of each relay is: (5*10^9)*32^0.75=6.73*10^10 As all relays are identical that gives a maximum link range of 6.73*10^10. Using the signal strength formula at a range of 2.20*10^10, i get a effeciency of: 1-((2.20*10^10)/(6.73*10^10))=0.67 0.67*0.67*(3-2*0.67)=0.75 (=75%) So, if I want a seperation of 2.20*10^10 in an equilaterl triangle arrangement I need an orbital radius of: (2.20*10^10)*(sqrt(3)/3))=1.27*10^10. I now have three such relays at a Kerbol Orbit of 1.27*10^10, yet not only are they not at 75% power, they are not linking at all. My initial hunch is that some of the measurements are from sun centre and some are from sun surface, but that only affects the third significant figure and smaller, reducing effeciency to 74%, not 0%. What is wrong with my maths (not just the aesthetic choice for the 32 antennae) Thanks in advance, RBS.

What is this? A gameplay add-on for Kerbal Space Program. The purpose is to transform the CommNet network of the single type into multiple constellations of different types. Why? Three reasons: * In our real-life universe, we have satellite constellations of GPS, GLONASS and Galileo talking to their own members. So why can't CommNet have such feature? * Every vessel in the whole network is talking to everyone within its root range model. * This mod is a testbed and prototype for one feature proposal of constellations in the RemoteTech project. (I am a member of the current RemoteTech team) Mods required * Module Manager License GNU GENERAL PUBLIC LICENSE, Version 3 Current status * Radio frequency for every CommNetVessel instance [completed] * A simple interface to assign a radio frequency [0, 32767] (short-type) to a specific eligible vessel [completed] * All vessels within the constellation of each radio frequency are connecting to each other (default frequency of 0 is public) [completed] * Frequency-associated color of vessel icons in KSP's mapview mode [completed] * Piggyback onto most of KSP's CommNet components and develop a layer onto CommNet for an eventual integration into RemoteTech codebase [completed with on-going refinement effort] * A control-panel interface to manage a number of constellations and satellites [completed] Links Download the releases List of CommNet classes RemoteTech's feature requests on constellation Release thread What can you help? Post some information about CommNet workings. I reckon that having such information available to public will help me or a third-party developer to speed up the development of a CommNet-based mod