You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The RA antenna planner, both in the VAB and in Flight, will ignore the set AMWTemp value for Skopos ground stations, and instead use the default antenna noise temp for the ground station tech level. This results in the antenna planner dramatically underestimating achievable connection speed, especially at low tech levels where the default AMWTemp is very high.
Actual in-flight performance appears to be correct, and the Antenna debugger reports the correct AMWTemp.
The origin of this problem is here, where RA for whatever reason fails to identify that Skopos ground stations have a parent body and therefore assumes they are vessel antennas.
The text was updated successfully, but these errors were encountered:
Taking advantage of the new information added to the debugger, we can see that when using the planner, a body is not assigned to the Skopos station, causing this to assign it the default AMWTemp instead of the one specified in config. This failure to assign the parent body in the planner occurs in the VAB and in flight.
Partner issue to mockingbirdnest/Skopos#14 since resolving it may demand changes to both mods
The RA antenna planner, both in the VAB and in Flight, will ignore the set AMWTemp value for Skopos ground stations, and instead use the default antenna noise temp for the ground station tech level. This results in the antenna planner dramatically underestimating achievable connection speed, especially at low tech levels where the default AMWTemp is very high.
Actual in-flight performance appears to be correct, and the Antenna debugger reports the correct AMWTemp.
The origin of this problem is here, where RA for whatever reason fails to identify that Skopos ground stations have a parent body and therefore assumes they are vessel antennas.
The text was updated successfully, but these errors were encountered: