[1.11] RemoteTech v1.9.9 [2020-12-19]

Dunbaratu · September 21, 2018

On 9/20/2018 at 10:25 AM, TaxiService said:

Understood this problem is not always happening, it is okay to provide only output_log.tx first.

The delay window is this one below, plus your vessel in your screenshot.

I still have no specific output_log, but I did notice another problem and they may be related:

When trying to hit the brakes with the mouse button near the altimeter (rather than with the 'b' key), I get the message "Out of power, cannot run [deploy breaks]" when I have *plenty* of electriccharge.

I looked at the RT code on github and it looks as if there's a presumption that all ModuleSPU's will be located inside parts for which part.IsControlSource is true (or higher than "none" since it's not quite a boolean). The test that turns the IsRTPowered flag off is assuming that if isControlSource is not true, the ship is out of power (which isn't really true but may be how RT is disabling some controls internally.) The kOS CPU is not a probe core so it doesn't have the right things to act like one. It appears as if ModuleSPU is assumed to always be inside a proper probe control point of some sort. That may be where all my problems are coming from.

Gordon Dry · September 21, 2018

I helped myself with this:

GameData\zFinal\zzz_RemoteTechAddMissingModuleSPUPassive.cfg

@PART[*]:HAS[@MODULE[ModuleCommand],!MODULE[ModuleRTAntennaPassive],!MODULE[ModuleRTAntenna],!MODULE[ModuleSPUPassive],!MODULE[ModuleSPU],!MODULE[KerbalEVA]]:NEEDS[RemoteTech]
{
    MODULE
	{
		name = ModuleRTAntennaPassive
        TechRequired = start
        OmniRange = 100000

        TRANSMITTER
		{
            PacketInterval = 0.3
            PacketSize = 2
            PacketResourceCost = 15.0
		}
    }
}

@PART[*]:HAS[@MODULE[ModuleCommand],@MODULE[ModuleRTAntennaPassive],!MODULE[ModuleSPU],!MODULE[KerbalEVA]]:NEEDS[RemoteTech]
{
	MODULE
	{
		name = ModuleSPU
        TechRequired = start
	}
}

@PART[*]:HAS[@MODULE[ModuleCommand],@MODULE[ModuleRTAntenna],!MODULE[ModuleSPUPassive],!MODULE[KerbalEVA]]:NEEDS[RemoteTech]
{
	MODULE
	{
		name = ModuleSPUPassive
        TechRequired = start
	}
}

@PART[*]:HAS[!MODULE[ModuleCommand],@MODULE[ModuleRTAntenna],!MODULE[ModuleSPUPassive]]:NEEDS[RemoteTech]
{
	MODULE
	{
		name = ModuleSPUPassive
        TechRequired = start
	}
}

@PART[*]:HAS[@MODULE[ModuleRTAntennaPassive],!MODULE[ModuleSPU]]:NEEDS[RemoteTech]
{
	MODULE
	{
		name = ModuleSPU
        TechRequired = start
	}
}

and also
GameData\zFinal\zzz_AddClassDescriptionsToAntennas.cfg

//Add Class Descriptions to antennas by range.
//Author: Gordon Dry

// stock CommNet
@PART[*]:HAS[@MODULE[ModuleDataTransmitter]:HAS[#antennaPower[<5001],#antennaType[INTERNAL]]]:NEEDS[!RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 1 Antenna INTERNAL.</color> :
}

@PART[*]:HAS[@MODULE[ModuleDataTransmitter]:HAS[#antennaPower[<500000],#antennaType[DIRECT]]]:NEEDS[!RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 1 Antenna DIRECT.</color> :
}

@PART[*]:HAS[@MODULE[ModuleDataTransmitter]:HAS[#antennaPower[<500000],#antennaType[RELAY]]]:NEEDS[!RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 1 Antenna RELAY.</color> :
}

@PART[*]:HAS[@MODULE[ModuleDataTransmitter]:HAS[#antennaPower[>5000],#antennaPower[<200001],#antennaType[INTERNAL]]]:NEEDS[!RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 2 Antenna INTERNAL.</color> :
}

@PART[*]:HAS[@MODULE[ModuleDataTransmitter]:HAS[#antennaPower[>499999],#antennaPower[<2000000001],#antennaType[DIRECT]]]:NEEDS[!RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 2 Antenna DIRECT.</color> :
}

@PART[*]:HAS[@MODULE[ModuleDataTransmitter]:HAS[#antennaPower[>499999],#antennaPower[<2000000001],#antennaType[RELAY]]]:NEEDS[!RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 2 Antenna RELAY.</color> :
}

@PART[*]:HAS[@MODULE[ModuleDataTransmitter]:HAS[#antennaPower[>200000],#antennaPower[<2500001],#antennaType[INTERNAL]]]:NEEDS[!RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 3 Antenna INTERNAL.</color> :
}

@PART[*]:HAS[@MODULE[ModuleDataTransmitter]:HAS[#antennaPower[>2000000000],#antennaPower[<250000000001],#antennaType[DIRECT]]]:NEEDS[!RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 3 Antenna DIRECT.</color> :
}

@PART[*]:HAS[@MODULE[ModuleDataTransmitter]:HAS[#antennaPower[>2000000000],#antennaPower[<250000000001],#antennaType[RELAY]]]:NEEDS[!RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 3 Antenna RELAY.</color> :
}

@PART[*]:HAS[@MODULE[ModuleDataTransmitter]:HAS[#antennaPower[>2500000],#antennaPower[<10000001],#antennaType[INTERNAL]]]:NEEDS[!RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 4 Antenna INTERNAL.</color> :
}

@PART[*]:HAS[@MODULE[ModuleDataTransmitter]:HAS[#antennaPower[>250000000000],#antennaPower[<1000000000001],#antennaType[DIRECT]]]:NEEDS[!RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 4 Antenna DIRECT.</color> :
}

@PART[*]:HAS[@MODULE[ModuleDataTransmitter]:HAS[#antennaPower[>250000000000],#antennaPower[<1000000000001],#antennaType[RELAY]]]:NEEDS[!RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 4 Antenna RELAY.</color> :
}

@PART[*]:HAS[@MODULE[ModuleDataTransmitter]:HAS[#antennaPower[>10000000],#antennaType[INTERNAL]]]:NEEDS[!RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 5 Antenna INTERNAL.</color> :
}

@PART[*]:HAS[@MODULE[ModuleDataTransmitter]:HAS[#antennaPower[>1000000000000],#antennaType[DIRECT]]]:NEEDS[!RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 5 Antenna DIRECT.</color> :
}

@PART[*]:HAS[@MODULE[ModuleDataTransmitter]:HAS[#antennaPower[>1000000000000],#antennaType[RELAY]]]:NEEDS[!RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 5 Antenna RELAY.</color> :
}

//RemoteTech
@PART[*]:HAS[@MODULE[ModuleRTAntennaPassive]:HAS[#OmniRange[<5001]]]:NEEDS[RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 1 RT Antenna PASSIVE.</color> :
}

@PART[*]:HAS[@MODULE[ModuleRTAntenna]:HAS[#Mode1OmniRange[<500000],~DishAngle[]]]:NEEDS[RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 1 RT Antenna OMNI.</color> :
}

@PART[*]:HAS[@MODULE[ModuleRTAntenna]:HAS[#Mode1DishRange[<500000],#DishAngle[>0]]]:NEEDS[RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 1 RT Antenna DISH.</color> :
}

@PART[*]:HAS[@MODULE[ModuleRTAntennaPassive]:HAS[#OmniRange[>5000],#OmniRange[<200001]]]:NEEDS[RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 2 RT Antenna PASSIVE.</color> :
}

@PART[*]:HAS[@MODULE[ModuleRTAntenna]:HAS[#Mode1OmniRange[>499999],#Mode1OmniRange[<2000000001],~DishAngle[]]]:NEEDS[RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 2 RT Antenna OMNI.</color> :
}

@PART[*]:HAS[@MODULE[ModuleRTAntenna]:HAS[#Mode1DishRange[>499999],#Mode1DishRange[<2000000001],#DishAngle[>0]]]:NEEDS[RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 2 RT Antenna DISH.</color> :
}

@PART[*]:HAS[@MODULE[ModuleRTAntennaPassive]:HAS[#OmniRange[>200000],#OmniRange[<2500001]]]:NEEDS[RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 3 RT Antenna PASSIVE.</color> :
}

@PART[*]:HAS[@MODULE[ModuleRTAntenna]:HAS[#Mode1OmniRange[>2000000000],#Mode1OmniRange[<250000000001],~DishAngle[]]]:NEEDS[RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 3 RT Antenna OMNI.</color> :
}

@PART[*]:HAS[@MODULE[ModuleRTAntenna]:HAS[#Mode1DishRange[>2000000000],#Mode1DishRange[<250000000001],#DishAngle[>0]]]:NEEDS[RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 3 RT Antenna DISH.</color> :
}

@PART[*]:HAS[@MODULE[ModuleRTAntennaPassive]:HAS[#OmniRange[>2500000],#OmniRange[<10000001]]]:NEEDS[RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 4 RT Antenna PASSIVE.</color> :
}

@PART[*]:HAS[@MODULE[ModuleRTAntenna]:HAS[#Mode1OmniRange[>250000000000],#Mode1OmniRange[<1000000000001],~DishAngle[]]]:NEEDS[RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 4 RT Antenna OMNI.</color> :
}

@PART[*]:HAS[@MODULE[ModuleRTAntenna]:HAS[#Mode1DishRange[>250000000000],#Mode1DishRange[<1000000000001],#DishAngle[>0]]]:NEEDS[RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 4 RT Antenna DISH.</color> :
}

@PART[*]:HAS[@MODULE[ModuleRTAntennaPassive]:HAS[#OmniRange[>10000000]]]:NEEDS[RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 5 RT Antenna PASSIVE.</color> :
}

@PART[*]:HAS[@MODULE[ModuleRTAntenna]:HAS[#Mode1OmniRange[>1000000000000],~DishAngle[]]]:NEEDS[RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 5 RT Antenna OMNI.</color> :
}

@PART[*]:HAS[@MODULE[ModuleRTAntenna]:HAS[#Mode1DishRange[>1000000000000],#DishAngle[>0]]]:NEEDS[RemoteTech]:FINAL {
	+description ^= :^:<color=orange>Class 5 RT Antenna DISH.</color> :
}

^this also solved the "no connection, no staging" issue for that could happen especially when using non-officially-supported vessels with RT in RSS and with another launchpad than KSC (Kennedy Space Center).

see also

Edited September 23, 2018 by Gordon Dry
Update 9/23

TaxiService · September 23, 2018

On 9/22/2018 at 6:52 AM, Steven Mading said:

I still have no specific output_log, but I did notice another problem and they may be related:

When trying to hit the brakes with the mouse button near the altimeter (rather than with the 'b' key), I get the message "Out of power, cannot run [deploy breaks]" when I have *plenty* of electriccharge.

I looked at the RT code on github and it looks as if there's a presumption that all ModuleSPU's will be located inside parts for which part.IsControlSource is true (or higher than "none" since it's not quite a boolean). The test that turns the IsRTPowered flag off is assuming that if isControlSource is not true, the ship is out of power (which isn't really true but may be how RT is disabling some controls internally.) The kOS CPU is not a probe core so it doesn't have the right things to act like one. It appears as if ModuleSPU is assumed to always be inside a proper probe control point of some sort. That may be where all my problems are coming from.

Yes, you found the root cause. I checked the kOS parts and they do not have any ModuleCommand. The control check will fail and keep IsRTPowered at false. It would explain the strange control inconsistencies in your first post.

I think you need to rework your MM patch to kOS CPU to a correct way.

Dunbaratu · September 25, 2018

On 9/23/2018 at 2:04 AM, TaxiService said:

Yes, you found the root cause. I checked the kOS parts and they do not have any ModuleCommand. The control check will fail and keep IsRTPowered at false. It would explain the strange control inconsistencies in your first post.

I think you need to rework your MM patch to kOS CPU to a correct way.

kOS parts were never intended to be probe cores, so I do not consider adding a ModuleCommand to them to be a "correct way" to fix it.

Would RT be able to handle it if an MM patch added ModuleSPU's to all *crewed* capsules instead of to all kOS cores? That would fix the one case where we originally had a problem that caused me to mess with MM patches in the first place - that case being how RT always pretends there is no connection to a crew-only (no probe core) ship (and therefore kOS won't let people copy files from KSC to the ship because it believed RT when RT claimed there was no connection). Given that any crew capsule should have a ModuleCommand in it, this might be a good way to fix it.

danielboro · September 26, 2018

7 hours ago, Steven Mading said:

kOS parts were never intended to be probe cores, so I do not consider adding a ModuleCommand to them to be a "correct way" to fix it.

Would RT be able to handle it if an MM patch added ModuleSPU's to all *crewed* capsules instead of to all kOS cores? That would fix the one case where we originally had a problem that caused me to mess with MM patches in the first place - that case being how RT always pretends there is no connection to a crew-only (no probe core) ship (and therefore kOS won't let people copy files from KSC to the ship because it believed RT when RT claimed there was no connection). Given that any crew capsule should have a ModuleCommand in it, this might be a good way to fix it.

this problem was do to a bad IF in the code

i believe this was fixed

TaxiService · September 26, 2018

15 hours ago, Steven Mading said:

kOS parts were never intended to be probe cores, so I do not consider adding a ModuleCommand to them to be a "correct way" to fix it.

Would RT be able to handle it if an MM patch added ModuleSPU's to all *crewed* capsules instead of to all kOS cores? That would fix the one case where we originally had a problem that caused me to mess with MM patches in the first place - that case being how RT always pretends there is no connection to a crew-only (no probe core) ship (and therefore kOS won't let people copy files from KSC to the ship because it believed RT when RT claimed there was no connection). Given that any crew capsule should have a ModuleCommand in it, this might be a good way to fix it.

Yah, RT should be able to handle the patched crewed parts as they would be treated as one type of probe cores.

SlavaYaitsam · October 3, 2018

Guys I need help. I built a satellite delivery based on 'Pier' from 'Stockalike Station Parts Redux' with two pilots who have 1 star exp. To the 'Pier' attached two antennas 16-S and HG-5. This unit carries three satellites. Each sat. based on 'HECS' and have antennas 16-S, DTS-M1, HG-5, RA-2. As I understand I can control my sat. remotely from 'Pier', but when sat. decouple nothing happens - No connect. I play with RemoteTech and I've already tried to activate antennas by EVA and target them to the base ship with 'Pier', same result- No connect. What am I doing wrong? My KSP ver. 1.4.5

TaxiService · October 5, 2018

On 10/4/2018 at 2:23 AM, SlavaYaitsam said:

Guys I need help. I built a satellite delivery based on 'Pier' from 'Stockalike Station Parts Redux' with two pilots who have 1 star exp. To the 'Pier' attached two antennas 16-S and HG-5. This unit carries three satellites. Each sat. based on 'HECS' and have antennas 16-S, DTS-M1, HG-5, RA-2. As I understand I can control my sat. remotely from 'Pier', but when sat. decouple nothing happens - No connect. I play with RemoteTech and I've already tried to activate antennas by EVA and target them to the base ship with 'Pier', same result- No connect. What am I doing wrong? My KSP ver. 1.4.5

You were trying to use stock CommNet's remote pilot assistance (1 kerbal)? It is not used in RemoteTech. Remotetech requires the big probe core and 6 kerbals to be a remote control station.

Gordon Dry · October 6, 2018

@TaxiService I just recognized that an action group command is not delayed by the manual delay.

By reading some older posts about RemoteTech I assumed this should work.

Either this issue occures because I use "Action Groups ReExtended" by @linuxgurugamer or the feature was removed?

I found this post:

It seems that just pressing the action group key triggers it immediately, I have to use the AGX UI to delay it ...

Darn ...

TaxiService · October 7, 2018

10 hours ago, Gordon Dry said:

@TaxiService I just recognized that an action group command is not delayed by the manual delay.

By reading some older posts about RemoteTech I assumed this should work.

Either this issue occures because I use "Action Groups ReExtended" by @linuxgurugamer or the feature was removed?

I found this post:

It seems that just pressing the action group key triggers it immediately, I have to use the AGX UI to delay it ...

Darn ...

I have no idea what is going on with Toolbar mod. It is throwing many exceptions in my KSP 1.4.5 and I can't test AGX properly.

One exception:

UnityException: get_dataPath is not allowed to be called from a MonoBehaviour constructor (or instance field initializer), call it in Awake or Start instead. Called from MonoBehaviour 'ToolbarManager' on game object 'ToolbarManager'.
See "Script Serialization" page in the Unity Manual for further details.
  at (wrapper managed-to-native) UnityEngine.Application:get_dataPath ()
  at KSPUtil.get_ApplicationRootPath () [0x00000] in <filename unknown>:0 
  at Toolbar.ToolbarManager..cctor () [0x00000] in <filename unknown>:0 
Rethrow as TypeInitializationException: An exception was thrown by the type initializer for Toolbar.ToolbarManager

Mod list:

Mod DLLs found:
Stock assembly: Assembly-CSharp v0.0.0.0
ModuleManager v3.0.7.0
MiniAVC v1.0.3.2
ClickThroughBlocker v0.1.6.7 / v1.0.0.0
MiniAVC v1.0.3.2
aaa_Toolbar v1.7.17.11
MiniAVC v1.0.3.2
RemoteTech v1.8.0.0 / v1.8.13
Stock assembly: KSPSteamCtrlr v0.0.1.35

crapstar · October 9, 2018

Hi all,

I am trying to figure out if I am missing any antennapowersaver options from the menu (attached). How do I enable the Auto threshold?

TaxiService · October 9, 2018

9 hours ago, crapstar said:

Hi all,

I am trying to figure out if I am missing any antennapowersaver options from the menu (attached). How do I enable the Auto threshold?

Open Flight Computer and go to Power panel (click < or > button at top left corner). You will see 3 power buttons and one is Threshold.

linuxgurugamer · October 9, 2018

Any chance to break the flight computer out into it's own mod?

linuxgurugamer · October 10, 2018

On 10/7/2018 at 5:01 AM, TaxiService said:

I have no idea what is going on with Toolbar mod. It is throwing many exceptions in my KSP 1.4.5 and I can't test AGX properly.

One exception:


UnityException: get_dataPath is not allowed to be called from a MonoBehaviour constructor (or instance field initializer), call it in Awake or Start instead. Called from MonoBehaviour 'ToolbarManager' on game object 'ToolbarManager'.
See "Script Serialization" page in the Unity Manual for further details.
  at (wrapper managed-to-native) UnityEngine.Application:get_dataPath ()
  at KSPUtil.get_ApplicationRootPath () [0x00000] in <filename unknown>:0 
  at Toolbar.ToolbarManager..cctor () [0x00000] in <filename unknown>:0 
Rethrow as TypeInitializationException: An exception was thrown by the type initializer for Toolbar.ToolbarManager

Mod list:


Mod DLLs found:
Stock assembly: Assembly-CSharp v0.0.0.0
ModuleManager v3.0.7.0
MiniAVC v1.0.3.2
ClickThroughBlocker v0.1.6.7 / v1.0.0.0
MiniAVC v1.0.3.2
aaa_Toolbar v1.7.17.11
MiniAVC v1.0.3.2
RemoteTech v1.8.0.0 / v1.8.13
Stock assembly: KSPSteamCtrlr v0.0.1.35

Ignoring the fact that you didn't list ALL the mod DLLs, you should always provide a log file.

In thus case, I suspect you don't have the latest version of the ToolbarController installed, that was an old bug

TaxiService · October 11, 2018

On 10/10/2018 at 3:00 AM, linuxgurugamer said:

Any chance to break the flight computer out into it's own mod?

Sorry, not happening. It is deeply tied to the underlying RT components. It is easier to isolate and copy & paste into RT 2 environment as an optional package.

On 10/10/2018 at 8:25 PM, linuxgurugamer said:

Ignoring the fact that you didn't list ALL the mod DLLs, you should always provide a log file.

In thus case, I suspect you don't have the latest version of the ToolbarController installed, that was an old bug

I discovered it is the debug exe not liking something in Toolbar mod(s). It works fine in the commerical exe.

Anyway, I tested AGX 2.3.3.6 and RT 1.8.13 on KSP 1.4.5 and found pressing AG keys will result in delayed actions.

linuxgurugamer · October 11, 2018

41 minutes ago, TaxiService said:

I discovered it is the debug exe not liking something in Toolbar mod(s). It works fine in the commerical exe.

It was actually a bug in the ToolbarController, which only was obvious in the debug exe. Please update to the latest version of the ToolbarController

Drew Kerman · October 13, 2018

not sure why this MM config to add a new ground station isn't working. I read the section in the docs about doing this but could not see my second ground station in the tracking center nor did I get a connection when I dropped a probe over the coordinates. Here is the config

@RemoteTechSettings
{
  !GroundStations,* {}
	GroundStations
	{
		STATION
		{
			Guid = 5105f5a9-d628-41c6-ad4b-21154e8fc488
			Name = Mission Control
			Latitude = -0.13133150339126601
			Longitude = -74.594841003417997
			Height = 75
			Body = 1
			MarkColor = 0.996078014,0,0,1
			Antennas
			{
				ANTENNA
				{
					Omni = 75000000
					Dish = 0
					CosAngle = 1
					UpgradeableOmni = 4E+06;3.0E+07;7.5E+07
					UpgradeableDish = 
					UpgradeableCosAngle = 
				}
			}
		}
		STATION
		{
			Guid = 05f12d95-9b68-edf5-7892-27fab7e0f37b
			Name = South Pole
			Latitude = -73.10302734375
			Longitude = -56.42578125
			Height = 75
			Body = 1
			MarkColor = 1,0.8,0,0.7
			Antennas
			{
				ANTENNA
				{
					Omni = 75000000
					Dish = 0
					CosAngle = 1
					UpgradeableOmni = 4E+06;3.0E+07;7.5E+07
					UpgradeableDish = 
					UpgradeableCosAngle = 
				}
			}
		}
	}
}

I first had the MarkColor the same but even when I switched them to different colors I didn't see the station after restarting. KSC still shows up fine tho. I also checked the MM cache file and the config looks just like it should. Running KSP1.4.5 w/MH and RT1.8.12

Edited October 13, 2018 by Drew Kerman

Decus91 · October 13, 2018

Hey, I just wanted to ask the devs of RemoteTech: are there any plans to incorporate bandwidth/ transmission rate/ something akin to the radar range equation (https://copradar.com/rdrrange/) into this mod at any time in the future? I know that it would depend on having frequencies for the antennas, etc, but these could be estimated. I'd be happy to help out* if so and if this could also be back-dated to versions compatible with 1.3.1!

*I have some rl qualifications/ an MSc in the area so that should help.

Edited October 13, 2018 by Decus91

Gordon Dry · October 14, 2018

... but how can an unmanned probe core with ModuleCommand fail the check and have IsRTPowered = false in the ModuleRTAntennaPassive that I patched in?

The ModuleSPU got IsRTPowered = true btw.

TaxiService · October 14, 2018

On 10/13/2018 at 9:47 AM, Drew Kerman said:
not sure why this MM config to add a new ground station isn't working. I read the section in the docs about doing this but could not see my second ground station in the tracking center nor did I get a connection when I dropped a probe over the coordinates. Here is the config
@RemoteTechSettings
{
  !GroundStations,* {}
	GroundStations
	{
		STATION
		{
			Guid = 5105f5a9-d628-41c6-ad4b-21154e8fc488
			Name = Mission Control
			Latitude = -0.13133150339126601
			Longitude = -74.594841003417997
			Height = 75
			Body = 1
			MarkColor = 0.996078014,0,0,1
			Antennas
			{
				ANTENNA
				{
					Omni = 75000000
					Dish = 0
					CosAngle = 1
					UpgradeableOmni = 4E+06;3.0E+07;7.5E+07
					UpgradeableDish = 
					UpgradeableCosAngle = 
				}
			}
		}
		STATION
		{
			Guid = 05f12d95-9b68-edf5-7892-27fab7e0f37b
			Name = South Pole
			Latitude = -73.10302734375
			Longitude = -56.42578125
			Height = 75
			Body = 1
			MarkColor = 1,0.8,0,0.7
			Antennas
			{
				ANTENNA
				{
					Omni = 75000000
					Dish = 0
					CosAngle = 1
					UpgradeableOmni = 4E+06;3.0E+07;7.5E+07
					UpgradeableDish = 
					UpgradeableCosAngle = 
				}
			}
		}
	}
}
I first had the MarkColor the same but even when I switched them to different colors I didn't see the station after restarting. KSC still shows up fine tho. I also checked the MM cache file and the config looks just like it should. Running KSP1.4.5 w/MH and RT1.8.12

Where did you place your config in? GameData/RemoteTech folder? If so, you may need to go to Preset tab in RT Option Window in-game and rebuild your RT settings built from your current setup.

17 hours ago, Decus91 said:

Hey, I just wanted to ask the devs of RemoteTech: are there any plans to incorporate bandwidth/ transmission rate/ something akin to the radar range equation (https://copradar.com/rdrrange/) into this mod at any time in the future? I know that it would depend on having frequencies for the antennas, etc, but these could be estimated. I'd be happy to help out* if so and if this could also be back-dated to versions compatible with 1.3.1!

*I have some rl qualifications/ an MSc in the area so that should help.

Yes and no. Current RemoteTech will not have the real-world radio characteristics implemented. We are preserving the current KSP-like characteristics while we are redeveloping a next RT product baseed on KSP's CommNet. This is where this new product will have the characteristics commonly requested (K-E-R-B-A-L frequencies or Issue #462 'Reduce bandwidth when too far away').

Decus91 · October 14, 2018

1 hour ago, TaxiService said:

Yes and no. Current RemoteTech will not have the real-world radio characteristics implemented. We are preserving the current KSP-like characteristics while we are redeveloping a next RT product baseed on KSP's CommNet. This is where this new product will have the characteristics commonly requested (K-E-R-B-A-L frequencies or Issue #462 'Reduce bandwidth when too far away').

Okay, thanks for the response. Is it planned for this new RT product to be backwards compatible with 1.3.1?

David H · October 14, 2018

I can't seem to get remote tech to work.
Before ksp added antenna signal. I never had a problem.
I haven't played in awhile. New up to date install.
When I add remote tech it disables the stock code of antenna's and does not require an antenna to launch anything.

I installed kerbalism. With remote tech the power usage is fine.
Uninstalled remote tech and kerbalism changed power usage to unmanageable. Had to spam 1x1 small solar panels into every open space just to maintain power.
Removed kerbalism, remote tech installed and power usage is fine but no antenna signal needed.

I tried a couple older versions from here, going back to 1.8.11.131
https://github.com/RemoteTechnologiesGroup/RemoteTech/releases

Edited October 14, 2018 by David H

TaxiService · October 15, 2018

23 hours ago, Decus91 said:

Okay, thanks for the response. Is it planned for this new RT product to be backwards compatible with 1.3.1?

Actually, the development is on KSP 1.3 because of Unity Analytics in KSP 1.4. It makes it unnecessarily difficult to read the 1.4 codes.

15 hours ago, David H said:

I can't seem to get remote tech to work.
Before ksp added antenna signal. I never had a problem.
I haven't played in awhile. New up to date install.
When I add remote tech it disables the stock code of antenna's and does not require an antenna to launch anything.

I installed kerbalism. With remote tech the power usage is fine.
Uninstalled remote tech and kerbalism changed power usage to unmanageable. Had to spam 1x1 small solar panels into every open space just to maintain power.
Removed kerbalism, remote tech installed and power usage is fine but no antenna signal needed.

I tried a couple older versions from here, going back to 1.8.11.131
https://github.com/RemoteTechnologiesGroup/RemoteTech/releases

Can you go to Preset tab of RT Options Windows in KCS scene and click Reload button? It will reset your current RT settings to the current settings built from your installation of mods.

Decus91 · October 15, 2018

1 hour ago, TaxiService said:

Actually, the development is on KSP 1.3 because of Unity Analytics in KSP 1.4. It makes it unnecessarily difficult to read the 1.4 codes.

Interesting, well, let me know if you'd like any support in its development and I'll be happy to help out. I have plenty of space related knowledge but little in the way of coding experience. My availability is primarily during the weekend.

David H · October 15, 2018

3 hours ago, TaxiService said:

Can you go to Preset tab of RT Options Windows in KCS scene and click Reload button? It will reset your current RT settings to the current settings built from your installation of mods.

Did that. Antenna seems to work. Haven't tried kerbalism antenna.
I did however have a probe that had connection and no delay 3/4 to mun.

At 40K

http://prntscr.com/l6fivb

At 225K have control. Tested antenna. It does show signal with ksc. Turned off, kept going. Notice RT display is blank.

http://prntscr.com/l6fjlh

In space no connection but still have control

http://prntscr.com/l6fj1z

KSC I see signal but red

http://prntscr.com/l6fjb6

More screenshots mod list

Edited October 15, 2018 by David H

[1.11] RemoteTech v1.9.9 [2020-12-19]

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation