Scottmm78 Posted July 12, 2018 Share Posted July 12, 2018 hope this is the correct place to ask this but does remotetech detect sigma rescales like 2.5 scale, and adjust the ranges accordingly. or do i need to ajust the ranges in remotetech to equal the rescale Quote Link to comment Share on other sites More sharing options...
The_Joe Posted July 16, 2018 Share Posted July 16, 2018 I know this is a dumb question, how do I disable the other ground stations? Now that I have a complete relay system in orbit I would like to have less ground stations cluttering my menu. Quote Link to comment Share on other sites More sharing options...
Just Jim Posted July 16, 2018 Share Posted July 16, 2018 1 minute ago, The_Joe said: I know this is a dumb question, how do I disable the other ground stations? Now that I have a complete relay system in orbit I would like to have less ground stations cluttering my menu. Not a dumb question. There is an option in your game settings to disable the other ground stations. You just need to turn them off. Quote Link to comment Share on other sites More sharing options...
MysticDaedra Posted July 16, 2018 Share Posted July 16, 2018 I have a connection through relay to KSC through relay, but I cannot open the flight computer, I click on the button but nothing happens. Bug, or am I screwing up somewhere? Quote Link to comment Share on other sites More sharing options...
TaxiService Posted July 18, 2018 Share Posted July 18, 2018 (edited) RemoteTech 1.8.12 for KSP 1.4.4 released This release is a recompilation for KSP 1.4.4. What are fixed/changed: Recompiled for KSP 1.4.4 New power command (based on this) of Flight Computer to de-activate or re-activate individual antennas, based on their power thresholds. For example, a dish will shut down at 20% EC and open itself at 70% EC. Each antenna has own power thresholds to configure through Part Action Menu. Complete changelog is below: Spoiler What's New? =========== * Recompiled for KSP 1.4.4 * Automatic antenna shutdown and re-activation based on power thresholds (thanks to rsparkyc's AntennaPowerSaver) Detailed Changelog ================== Fixed Issues ------------ * Issue #451: Automatic hibernation when power low [requested by: ec429] Pull Requests ------------- 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. Edited July 18, 2018 by TaxiService Quote Link to comment Share on other sites More sharing options...
TaxiService Posted July 18, 2018 Share Posted July 18, 2018 On 7/17/2018 at 2:08 AM, MysticDaedra said: I have a connection through relay to KSC through relay, but I cannot open the flight computer, I click on the button but nothing happens. Bug, or am I screwing up somewhere? Hi, may I have a screenshot of your vessel and the flight-computer button? The flight computer is not available if your vessel does not have any probe core. Quote Link to comment Share on other sites More sharing options...
katateochi Posted July 20, 2018 Share Posted July 20, 2018 I just want to say how much I love this mod. Been using it since the dawn of time, (or at least since it was the only way to have unmanned craft) and it's grown and changed and continues to be one of my favourite must-have mods. One of my fav things is the flight computer (even if it doesn't always complete a maneuver node quite as expected). I quite often use it on manned craft to execute a maneuver node, cos I know I'm bound to get distracted by something on the forum while waiting to timewarp to the node! One thing I enjoy doing (although it often goes wrong) is using it to sequence atmospheric reentry in the blind; perform burn, deploy drogue chute, drop shield, open main chute and deploy legs....and then wait a little while before re-opening antenna and reconnecting. But working out the time intervals for when to have those events happen can be a bit tricky. My method is to create a maneuver node and drag the retrograde marker so the projected trajectory puts an Ap marker at the node, then I can slide the node back and forth and get an idea of how long to X altitude and then create the flight computer event based on that. Problem is that doesn't account for how the atmosphere will decelerate the craft, so it's a bit of guess work (so many probes smashed into Duna). What would be really cool is if the flight computer could trigger events based on altitude. So rather than guessing how long before needing to deploy landing legs, be able to say when alt <= 200m then run action group G or whatever. Also, got a question about remote tech and tweakscale. I am able to scale the size of the dishes, but that doesn't seem to change their characteristics, they still have the same range and power consumption. I saw this post from way back, but can't find anything else referencing remote tech and tweakscale. Would the MM patch from that post still work? I'm running KSP 1.4.3 and RT 1.8.11 Quote Link to comment Share on other sites More sharing options...
cyberpunkdreams Posted July 20, 2018 Share Posted July 20, 2018 1 hour ago, katateochi said: What would be really cool is if the flight computer could trigger events based on altitude. So rather than guessing how long before needing to deploy landing legs, be able to say when alt <= 200m then run action group G or whatever. You can use kOS to do things such as that. It's not nearly as hard to learn as it looks. Quote Link to comment Share on other sites More sharing options...
danielboro Posted July 21, 2018 Share Posted July 21, 2018 Smart parts cam do that too Quote Link to comment Share on other sites More sharing options...
Gordon Dry Posted July 22, 2018 Share Posted July 22, 2018 (edited) Could it be that allowManualControl = false is the reason for not being able to extend an antenna in VAB? Main config: GameData\Bluedog_DB\Parts\Antennas\bluedog_solarAntenna.cfg PART { name = bluedog_solarAntenna module = Part author = CobaltWolf MODEL { model = Bluedog_DB/Parts/Antennas/bluedog_solarAntenna } scale = 1 rescaleFactor = 1 node_attach = 0.0, 0.0, 0.0, 0.0, 0.0, 1.0 TechRequired = engineering101 entryCost = 240 cost = 300 category = Communication subcategory = 0 title = M17 Solar Antenna //Vanguard I made orbit on March 17th, 1958 manufacturer = Bluedog Design Bureau description = Wehrner grew tired of losing communications with probes every time they run out of battery. This antenna breaks convention by including a small solar cell directly connected to the antenna. Never run out of juice again! attachRules = 1,1,0,0,1 mass = 0.005 dragModelType = default maximum_drag = 0.2 minimum_drag = 0.2 angularDrag = 2 crashTolerance = 7 maxTemp = 2000 // = 3000 PhysicsSignificance = 1 bulkheadProfiles = srf tags = aerial antenna radio signal transmit comm communicat dish vanguard MODULE { name = ModuleAnimateGeneric animationName = extendAntenna isOneShot = false startEventGUIName = Extend endEventGUIName = Retract actionGUIName = Toggle Antenna allowAnimationWhileShielded = False } MODULE { name = ModuleDataTransmitter antennaType = DIRECT packetInterval = 0.6 packetSize = 2 packetResourceCost = 12.0 requiredResource = ElectricCharge DeployFxModules = 0 antennaPower = 500000 antennaCombinable = True } MODULE { name = ModuleDeployableSolarPanel sunTracking = false raycastTransformName = catchThis pivotName = catchThis isBreakable = false resourceName = ElectricCharge chargeRate = 0.1 } } Inside ModuleManager.ConfigCache: UrlConfig { name = bluedog_solarAntenna type = PART parentUrl = Bluedog_DB/Parts/Antennas/bluedog_solarAntenna PART { name = bluedog_solarAntenna module = PartTapIn author = CobaltWolf scale = 1 rescaleFactor = 1 node_attach = 0.0, 0.0, 0.0, 0.0, 0.0, 1.0 TechRequired = engineering101 entryCost = 240 cost = 300 category = Communication subcategory = 0 title = Vanguard Solar Antenna manufacturer = Bluedog Design Bureau description = Wehrner grew tired of losing communications with probes every time they run out of battery. This antenna breaks convention by including a small solar cell directly connected to the antenna. Never run out of juice again! attachRules = 1,1,0,0,1 mass = 0.005 dragModelType = default maximum_drag = 0.2 minimum_drag = 0.2 angularDrag = 2 crashTolerance = 7 maxTemp = 2000 PhysicsSignificance = 1 bulkheadProfiles = srf tags = aerial antenna radio signal transmit comm communicat dish vanguard description = <color=orange>Class 2 RT Antenna OMNI.</color> Wehrner grew tired of losing communications with probes every time they run out of battery. This antenna breaks convention by including a small solar cell directly connected to the antenna. Never run out of juice again! MODEL { model = Bluedog_DB/Parts/Antennas/bluedog_solarAntenna } MODULE { name = ModuleAnimateGeneric animationName = extendAntenna isOneShot = false startEventGUIName = Extend endEventGUIName = Retract actionGUIName = Toggle Antenna allowAnimationWhileShielded = False allowManualControl = false } MODULE { name = ModuleDeployableSolarPanel sunTracking = false raycastTransformName = catchThis pivotName = catchThis isBreakable = false resourceName = ElectricCharge chargeRate = 0.05 useKopernicusSolarPanels = false } MODULE { name = AYA_Solar } MODULE { name = AnimatedAttachment } MODULE { name = ModuleRTAntenna Mode0OmniRange = 0 Mode1OmniRange = 1000000 EnergyCost = 0.00033 MaxQ = 6000 DeployFxModules = 0 TRANSMITTER { PacketInterval = 0.35 PacketSize = 2 PacketResourceCost = 0.012 } } MODULE { name = ModuleSPUPassive } MODULE { name = TweakScale type = BluedogAntenna } MODULE { name = ModuleAGX } MODULE { name = ModuleSYPartTracker } MODULE { isEnabled = True name = BuoyancyControl enabled = true } MODULE { name = HotSpotModule } MODULE { name = WarpFixer } MODULE { name = Reliability type = ModuleDeployableSolarPanel title = Solar Panel redundancy = Power Generation repair = true mtbf = 81546067 extra_cost = 2.5 extra_mass = 1.0 } MODULE { name = PlannerController title = transmitter considered = true } MODULE { name = Reliability type = Antenna title = Antenna redundancy = Communication repair = Engineer mtbf = 72576000 extra_cost = 1.0 extra_mass = 0.1 } } } Edited July 22, 2018 by Gordon Dry Quote Link to comment Share on other sites More sharing options...
PyjackMeat Posted July 24, 2018 Share Posted July 24, 2018 Does anyone have a working cfg for BDB? Quote Link to comment Share on other sites More sharing options...
123nick Posted July 24, 2018 Share Posted July 24, 2018 i have a bug, where pressing the remote tech button on the bottom edge of the screen, just causes FPS drop and nothing shows up within the GUI window that comes up. i remember planets showing up in the window that came up, but now just lag, and nothing is in the console so i dont see any error msg being spammed. any idea what could cause this? Quote Link to comment Share on other sites More sharing options...
se5a Posted July 24, 2018 Share Posted July 24, 2018 (edited) I've been trying to stick little remote com sites around Kebin, unfortunately it's a pita to do so, numerous problems such as having them blow up if I switch to them (they'll 'spawn' way above the surface, then drop to the surface and explode, etc) placing them is a pain, I've been trying to do it in a firespitter Helli, which has it's own problems, like, trying to land on top of a mountain without crashing. I recall years ago trying to drop them with parachutes but had problems there too, iirc I'd leave physics range before they landed etc, and dropping them to hit where I wanted was never easy either. (again, ontop of a mountain) Just building a design which can hold one of these little remote com thingies is a pain, since the OKTO wont stick to anything other than to its base or top, and using it as a sub assembly seems to be impossible. My last hellie design had one of these devices either side of it, attached to Modular Girder Segments (looks ugly AF), landed, and set one up (using the KIS spanner), did some science, then took off and went to another place... and promptly crashed trying to land due to the imbalanced weight distribution. https://imgur.com/a/u8qtLwP I also used to load up a container with bits and construct it manually a bit at a time on the ground, though I recall that used to be extremely annoying (and sometimes expload-y and fall through the ground-y) as well. Anyone else tried doing this? how did you go about doing it and what sort of designs did you use? Edited July 24, 2018 by se5a Quote Link to comment Share on other sites More sharing options...
fitemesquirrel Posted July 25, 2018 Share Posted July 25, 2018 On 7/24/2018 at 4:05 AM, se5a said: I've been trying to stick little remote com sites around Kebin, unfortunately it's a pita to do so, numerous problems such as having them blow up if I switch to them (they'll 'spawn' way above the surface, then drop to the surface and explode, etc) placing them is a pain, I've been trying to do it in a firespitter Helli, which has it's own problems, like, trying to land on top of a mountain without crashing. I recall years ago trying to drop them with parachutes but had problems there too, iirc I'd leave physics range before they landed etc, and dropping them to hit where I wanted was never easy either. (again, ontop of a mountain) Just building a design which can hold one of these little remote com thingies is a pain, since the OKTO wont stick to anything other than to its base or top, and using it as a sub assembly seems to be impossible. My last hellie design had one of these devices either side of it, attached to Modular Girder Segments (looks ugly AF), landed, and set one up (using the KIS spanner), did some science, then took off and went to another place... and promptly crashed trying to land due to the imbalanced weight distribution. https://imgur.com/a/u8qtLwP I also used to load up a container with bits and construct it manually a bit at a time on the ground, though I recall that used to be extremely annoying (and sometimes expload-y and fall through the ground-y) as well. Anyone else tried doing this? how did you go about doing it and what sort of designs did you use? Eh, I built a low-stall-speed prop plane. Just dropped my relays out the back of it with parachutes, switched to the probe in as it was falling then back to the plane, set the plane with trim to just circle the drop site slowly, and wait for the relay to land. That's how I've been dropping mine, at least. Quote Link to comment Share on other sites More sharing options...
Vrana Posted August 2, 2018 Share Posted August 2, 2018 I couldn't find an up to date patch for Tantares antennas so i made one. Not saying this is balanced or even thoroughly tested(quite a few antennas in Tantares) but it seems to work. So, in case someone needs a Tantares compatibility patch or a starting point for making their own, here goes: //ANY folder //standard probe @PART[Castor_Control_1_N]:FOR[RemoteTech] - standard probe -Vrana { %MODULE[ModuleSPU] { } %MODULE[ModuleRTAntennaPassive] { %TechRequired = unmannedTech %OmniRange = 3000 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } } //standard probe @PART[Castor_Control_1_O]:FOR[RemoteTech] { %MODULE[ModuleSPU] { } %MODULE[ModuleRTAntennaPassive] { %TechRequired = unmannedTech %OmniRange = 3000 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } } //standard probe @PART[Castor_Control_1_P]:FOR[RemoteTech] { %MODULE[ModuleSPU] { } %MODULE[ModuleRTAntennaPassive] { %TechRequired = unmannedTech %OmniRange = 3000 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } } //FGB folder //small dish @PART[Alniyat_Antenna_2_1_1]:FOR[RemoteTech] { @MODULE[ModuleDeployableAntenna] { %name=ModuleAnimateGeneric %allowManualControl = false %actionAvailable = false %eventAvailableFlight = false %eventAvailableEditor = false %eventAvailableEVA = false } %MODULE[ModuleRTAntenna] { %Mode0DishRange = 0 %Mode1DishRange = 8000000 %EnergyCost = 0.3 %MaxQ = 6000 %DishAngle = 0.1 %DeployFxModules = 0 %ProgressFxModules = 1 %TRANSMITTER { %PacketInterval = 0.15 %PacketSize = 3 %PacketResourceCost = 20.0 } } %MODULE[ModuleSPUPassive] {} } //small dish @PART[Alniyat_Antenna_2_1_2]:FOR[RemoteTech] { @MODULE[ModuleDeployableAntenna] { %name=ModuleAnimateGeneric %allowManualControl = false %actionAvailable = false %eventAvailableFlight = false %eventAvailableEditor = false %eventAvailableEVA = false } %MODULE[ModuleRTAntenna] { %Mode0DishRange = 0 %Mode1DishRange = 8000000 %EnergyCost = 0.3 %MaxQ = 6000 %DishAngle = 0.1 %DeployFxModules = 0 %ProgressFxModules = 1 %TRANSMITTER { %PacketInterval = 0.15 %PacketSize = 3 %PacketResourceCost = 20.0 } } %MODULE[ModuleSPUPassive] {} } //small omni @PART[Alniyat_Antenna_2_3_1]:FOR[RemoteTech] { @MODULE[ModuleDeployableAntenna] { %name=ModuleAnimateGeneric %allowManualControl = false %actionAvailable = false %eventAvailableFlight = false %eventAvailableEditor = false %eventAvailableEVA = false } %MODULE[ModuleRTAntenna] { %Mode0OmniRange = 0 %Mode1OmniRange = 2500000 %MaxQ = 6000 %EnergyCost = 0.13 %DeployFxModules = 0 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} } //small omni @PART[Alniyat_Antenna_2_3_2]:FOR[RemoteTech] { @MODULE[ModuleDeployableAntenna] { %name=ModuleAnimateGeneric %allowManualControl = false %actionAvailable = false %eventAvailableFlight = false %eventAvailableEditor = false %eventAvailableEVA = false } %MODULE[ModuleRTAntenna] { %Mode0OmniRange = 0 %Mode1OmniRange = 2500000 %MaxQ = 6000 %EnergyCost = 0.13 %DeployFxModules = 0 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} } //FOBOS folder //small med dish @PART[Ara_Antenna_1]:FOR[RemoteTech] { !MODULE[ModuleDataTransmitter] {} @MODULE[ModuleDeployableAntenna] { %name=ModuleAnimateGeneric %allowManualControl = false %actionAvailable = false %eventAvailableFlight = false %eventAvailableEditor = false %eventAvailableEVA = false } %MODULE[ModuleRTAntenna] { %Mode0DishRange = 0 %Mode1DishRange = 4.8E+10 %EnergyCost = 0.55 %DishAngle = 10 %TRANSMITTER { %PacketInterval = 0.56 %PacketSize = 5 %PacketResourceCost = 20.0 } } %MODULE[ModuleSPUPassive] {} } //LK folder //small omni @PART[Libra_Antenna_1]:FOR[RemoteTech] { @MODULE[ModuleDeployableAntenna] { %name=ModuleAnimateGeneric %allowManualControl = false %actionAvailable = false %eventAvailableFlight = false %eventAvailableEditor = false %eventAvailableEVA = false } %MODULE[ModuleRTAntenna] { %Mode0OmniRange = 0 %Mode1OmniRange = 1800000 %MaxQ = 6000 %EnergyCost = 0.1 %DeployFxModules = 0 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} } //small dish @PART[Libra_Antenna_2]:FOR[RemoteTech] { !MODULE[ModuleDataTransmitter] {} @MODULE[ModuleDeployableAntenna] { %name=ModuleAnimateGeneric %allowManualControl = false %actionAvailable = false %eventAvailableFlight = false %eventAvailableEditor = false %eventAvailableEVA = false } %MODULE[ModuleRTAntenna] { %Mode0DishRange = 0 %Mode1DishRange = 2.4E+10 %EnergyCost = 0.5 %DishAngle = 10 %TRANSMITTER { %PacketInterval = 0.56 %PacketSize = 5 %PacketResourceCost = 20.0 } } %MODULE[ModuleSPUPassive] {} } //MIR folder //small omni @PART[Eridani_Antenna_1]:FOR[RemoteTech] { @MODULE[ModuleDeployableAntenna] { %name=ModuleAnimateGeneric %allowManualControl = false %actionAvailable = false %eventAvailableFlight = false %eventAvailableEditor = false %eventAvailableEVA = false } %MODULE[ModuleRTAntenna] { %Mode0OmniRange = 0 %Mode1OmniRange = 1800000 %MaxQ = 6000 %EnergyCost = 0.1 %DeployFxModules = 0 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} } //med omni @PART[Eridani_Antenna_2]:FOR[RemoteTech] { @MODULE[ModuleDeployableAntenna] { %name=ModuleAnimateGeneric %allowManualControl = false %actionAvailable = false %eventAvailableFlight = false %eventAvailableEditor = false %eventAvailableEVA = false } %MODULE[ModuleRTAntenna] { %Mode0OmniRange = 0 %Mode1OmniRange = 2500000 %MaxQ = 6000 %EnergyCost = 0.15 %DeployFxModules = 0 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} } //large omni @PART[Eridani_Antenna_3]:FOR[RemoteTech] { @MODULE[ModuleDeployableAntenna] { %name=ModuleAnimateGeneric %allowManualControl = false %actionAvailable = false %eventAvailableFlight = false %eventAvailableEditor = false %eventAvailableEVA = false } %MODULE[ModuleRTAntenna] { %Mode0OmniRange = 0 %Mode1OmniRange = 6000000 %MaxQ = 6000 %EnergyCost = 0.2 %DeployFxModules = 0 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} } //med dish @PART[Eridani_Antenna_4]:FOR[RemoteTech] { !MODULE[ModuleDataTransmitter] {} @MODULE[ModuleDeployableAntenna] { %name=ModuleAnimateGeneric %allowManualControl = false %actionAvailable = false %eventAvailableFlight = false %eventAvailableEditor = false %eventAvailableEVA = false } %MODULE[ModuleRTAntenna] { %Mode0DishRange = 0 %Mode1DishRange = 4.8E+10 %EnergyCost = 0.55 %DishAngle = 10 %TRANSMITTER { %PacketInterval = 0.56 %PacketSize = 5 %PacketResourceCost = 20.0 } } %MODULE[ModuleSPUPassive] {} } //SOYUZ folder //small dish @PART[Tantares_Antenna_1]:FOR[RemoteTech] { !MODULE[ModuleDataTransmitter] {} @MODULE[ModuleDeployableAntenna] { %name=ModuleAnimateGeneric %allowManualControl = false %actionAvailable = false %eventAvailableFlight = false %eventAvailableEditor = false %eventAvailableEVA = false } %MODULE[ModuleRTAntenna] { %Mode0DishRange = 0 %Mode1DishRange = 2.4E+10 %EnergyCost = 0.5 %DishAngle = 10 %TRANSMITTER { %PacketInterval = 0.56 %PacketSize = 5 %PacketResourceCost = 20.0 } } %MODULE[ModuleSPUPassive] {} } //small dish @PART[Tantares_Antenna_2_1]:FOR[RemoteTech] { !MODULE[ModuleDataTransmitter] {} @MODULE[ModuleDeployableAntenna] { %name=ModuleAnimateGeneric %allowManualControl = false %actionAvailable = false %eventAvailableFlight = false %eventAvailableEditor = false %eventAvailableEVA = false } %MODULE[ModuleRTAntenna] { %Mode0DishRange = 0 %Mode1DishRange = 2.4E+10 %EnergyCost = 0.5 %DishAngle = 10 %TRANSMITTER { %PacketInterval = 0.56 %PacketSize = 5 %PacketResourceCost = 20.0 } } %MODULE[ModuleSPUPassive] {} } //ANDROMEDA folder //small omni @PART[Andromeda_Antenna_1]:FOR[RemoteTech] { @MODULE[ModuleDeployableAntenna] { %name=ModuleAnimateGeneric %allowManualControl = false %actionAvailable = false %eventAvailableFlight = false %eventAvailableEditor = false %eventAvailableEVA = false } %MODULE[ModuleRTAntenna] { %Mode0OmniRange = 0 %Mode1OmniRange = 1800000 %MaxQ = 6000 %EnergyCost = 0.1 %DeployFxModules = 0 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} } //small omni @PART[Andromeda_Antenna_2]:FOR[RemoteTech] { @MODULE[ModuleDeployableAntenna] { %name=ModuleAnimateGeneric %allowManualControl = false %actionAvailable = false %eventAvailableFlight = false %eventAvailableEditor = false %eventAvailableEVA = false } %MODULE[ModuleRTAntenna] { %Mode0OmniRange = 0 %Mode1OmniRange = 2000000 %MaxQ = 6000 %EnergyCost = 0.1 %DeployFxModules = 0 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} } On 7/24/2018 at 2:22 AM, PyjackMeat said: Does anyone have a working cfg for BDB? I think Bluedog DB comes with its own RT patch. Look under: ..\GameData\Bluedog_DB\Compatibility\RemoteTech Quote Link to comment Share on other sites More sharing options...
Trigant Posted August 13, 2018 Share Posted August 13, 2018 Hey Noob question here: (sorry for that) How do I add the KerbinSide Stations to the Remotetech cfg? I have the newest version of KK, Kerbinside, RT and KSP and dozens of stations but only the KSC as a possible connection? Installed the KerbinSide Complete Pack here is my modlist: Spoiler KSP: 1.4.5 (Win64) - Unity: 2017.1.3p1 - OS: Windows 10 (10.0.0) 64bit ClickThroughBlocker - 0.1.6.7 TexturesUnlimited - 1.1.2.14 Toolbar - 1.7.17.11 ToolbarControl - 0.1.6.13 Adjustable Mod Panel - 1.5 Astronomer's Visual Pack - 3.7.2 B9 Part Switch - 2.3 Bluedog Design Bureau - 1.1.6 Chatterer Extended - 0.6.2 Chatterer - 0.9.95.2110 Community Resource Pack - 0.10 CommunityTechTree - 3.3.2 Contract Configurator - 1.25 Contract Pack: RemoteTech - 2.1.4 DecouplerShroud - 0.5 DSCore - 3.0.2 ThorTech - 0.9.6.3 AGExt - 2.3.3.6 DistantObjectEnhancement - 1.9.1 DynamicBatteryStorage - 1.3.2 EditorExtensionsRedux - 3.3.19.5 Environmental Visual Enhancements - 1.4.2.2 Ferram Aerospace Research - 0.15.9.3 FMRS (Flight Manager For Reusable Stages) - 1.2.7.2 FShangarExtender - 3.5.3.2 FuseBoxContinued - 0.1.16.5 HideEmptyTechTreeNodes - 1.0.4 JanitorsCloset - 0.3.4.1 Kerbal Engineer Redux - 1.1.5.3 KerbalKonstructs - 1.4.5.2 KerbinSide-Complete - 1.4.5 <b><color=#CA7B3C>Kopernicus</color></b> - 1.4.5.2 KSP-AVC Plugin - 1.2.0.2 LoadingScreenManager - 1.2.5 Modular Rocket Systems - 1.13.2 ModularFlightIntegrator - 1.2.5 Docking Port Alignment Indicator - 6.8.2 NearFutureElectrical - 0.10.2 NearFutureProps - 0.3.3 NearFuturePropulsion - 1.0.2 NearFutureSolar - 0.8.12 NearFutureSpacecraft - 0.7.10 PlanetShine - 0.2.6.1 Precise Maneuver - 2.4.1 Procedural Parts - 1.3.15 Recovery Controller - 0.0.3.2 RemoteTech - 1.8.12 SmartActuation - 1.1.1 SmartTank - 0.1.2 TextureReplacer - 3.2 Trajectories - 2.2.1 Kerbal Alarm Clock - 3.9.1 Transfer Window Planner - 1.6.3 TweakScale - 2.3.12 Waypoint Manager - 2.7.2 [x] Science! - 5.16 and here is the log file: output_log.txt Quote Link to comment Share on other sites More sharing options...
Nicholander Posted August 13, 2018 Share Posted August 13, 2018 Sorry for a dumb question, but I'm having a problem adding a comm station in RSS. I editied the RemoteTech_Settings.cfg file in the GameData/RealSolarSystem folder, adding another station with a new Guid and such. It didn't show up when I loaded the game. I checked if the brackets were all correct and such and it still didn't work. I even tried changing the data for one of the existing stations, and there was no change. (Like that file isn't even controlling what the stations are.) Is this a known problem with RSS/RO? Or is is just a different file that determines the stations and I missed it? (Sorry that this is a more RSS/RO oriented question, but RemoteTech seems to be the only thing having this kind of issue. (I was able to add more launch sites in RSS just fine.)) Quote Link to comment Share on other sites More sharing options...
TaxiService Posted August 13, 2018 Share Posted August 13, 2018 11 hours ago, Trigant said: Hey Noob question here: (sorry for that) How do I add the KerbinSide Stations to the Remotetech cfg? I have the newest version of KK, Kerbinside, RT and KSP and dozens of stations but only the KSC as a possible connection? Installed the KerbinSide Complete Pack here is my modlist: Reveal hidden contents KSP: 1.4.5 (Win64) - Unity: 2017.1.3p1 - OS: Windows 10 (10.0.0) 64bit ClickThroughBlocker - 0.1.6.7 TexturesUnlimited - 1.1.2.14 Toolbar - 1.7.17.11 ToolbarControl - 0.1.6.13 Adjustable Mod Panel - 1.5 Astronomer's Visual Pack - 3.7.2 B9 Part Switch - 2.3 Bluedog Design Bureau - 1.1.6 Chatterer Extended - 0.6.2 Chatterer - 0.9.95.2110 Community Resource Pack - 0.10 CommunityTechTree - 3.3.2 Contract Configurator - 1.25 Contract Pack: RemoteTech - 2.1.4 DecouplerShroud - 0.5 DSCore - 3.0.2 ThorTech - 0.9.6.3 AGExt - 2.3.3.6 DistantObjectEnhancement - 1.9.1 DynamicBatteryStorage - 1.3.2 EditorExtensionsRedux - 3.3.19.5 Environmental Visual Enhancements - 1.4.2.2 Ferram Aerospace Research - 0.15.9.3 FMRS (Flight Manager For Reusable Stages) - 1.2.7.2 FShangarExtender - 3.5.3.2 FuseBoxContinued - 0.1.16.5 HideEmptyTechTreeNodes - 1.0.4 JanitorsCloset - 0.3.4.1 Kerbal Engineer Redux - 1.1.5.3 KerbalKonstructs - 1.4.5.2 KerbinSide-Complete - 1.4.5 <b><color=#CA7B3C>Kopernicus</color></b> - 1.4.5.2 KSP-AVC Plugin - 1.2.0.2 LoadingScreenManager - 1.2.5 Modular Rocket Systems - 1.13.2 ModularFlightIntegrator - 1.2.5 Docking Port Alignment Indicator - 6.8.2 NearFutureElectrical - 0.10.2 NearFutureProps - 0.3.3 NearFuturePropulsion - 1.0.2 NearFutureSolar - 0.8.12 NearFutureSpacecraft - 0.7.10 PlanetShine - 0.2.6.1 Precise Maneuver - 2.4.1 Procedural Parts - 1.3.15 Recovery Controller - 0.0.3.2 RemoteTech - 1.8.12 SmartActuation - 1.1.1 SmartTank - 0.1.2 TextureReplacer - 3.2 Trajectories - 2.2.1 Kerbal Alarm Clock - 3.9.1 Transfer Window Planner - 1.6.3 TweakScale - 2.3.12 Waypoint Manager - 2.7.2 [x] Science! - 5.16 and here is the log file: output_log.txt You can create a new file with extra ground station examples below, save it to GameData/KerbinSide or RemoteTech folder and click 'Reload' button in RT Option window (see below) to load starting settings built from your installed mods, included this file. Spoiler @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 = c4020a3a-3725-4644-9185-e092ea000772 Name = North Station One Latitude = 63.0959948383325 Longitude = -90.0686195497409 Height = 2864.02024834626 Body = 1 MarkColor = 1,0.8,0,0.7 Antennas { ANTENNA { Omni = 1E+06 } } } STATION { Guid = a48ebe2b-dd33-43cd-b6fc-0ff01d286a28 Name = Baikerbanur Latitude = 20.6820169733268 Longitude = -146.499776485631 Height = 426.953797265305 Body = 1 MarkColor = 1,0.8,0,0.7 Antennas { ANTENNA { Omni = 1E+06 } } } STATION { Guid = 1b85e542-f333-42c4-b947-63c68fa1c07e Name = Crater Rim Latitude = 9.44728971864159 Longitude = -172.106644413907 Height = 4115.64748514118 Body = 1 MarkColor = 1,0.8,0,0.7 Antennas { ANTENNA { Omni = 1E+06 } } } STATION { Guid = 924a1f04-65fd-43b0-b5d9-92b42622b47a Name = Mesa South Latitude = -59.5861679042582 Longitude = -25.8627095278566 Height = 5455.44101071125 Body = 1 MarkColor = 1,0.8,0,0.7 Antennas { ANTENNA { Omni = 1E+06 } } } STATION { Guid = 5ff6a830-98a2-488f-bdd4-4322511222d6 Name = Harvester Massif Latitude = -11.9503778337192 Longitude = 33.7373248915106 Height = 2701.44694075082 Body = 1 MarkColor = 1,0.8,0,0.7 Antennas { ANTENNA { Omni = 1E+06 } } } STATION { Guid = 6de2d751-bbbc-4892-80d7-d3852ab99d9b Name = Nye Island Latitude = 5.36081966792828 Longitude = 108.546677792524 Height = 411.161351518473 Body = 1 MarkColor = 1,0.8,0,0.7 Antennas { ANTENNA { Omni = 1E+06 } } } } } 7 hours ago, Nicholander said: Sorry for a dumb question, but I'm having a problem adding a comm station in RSS. I editied the RemoteTech_Settings.cfg file in the GameData/RealSolarSystem folder, adding another station with a new Guid and such. It didn't show up when I loaded the game. I checked if the brackets were all correct and such and it still didn't work. I even tried changing the data for one of the existing stations, and there was no change. (Like that file isn't even controlling what the stations are.) Is this a known problem with RSS/RO? Or is is just a different file that determines the stations and I missed it? (Sorry that this is a more RSS/RO oriented question, but RemoteTech seems to be the only thing having this kind of issue. (I was able to add more launch sites in RSS just fine.)) Since you said RSS has RemoteTech_Settings.cfg, please try this Reload button in RT Option window to load starting settings built from your installed mods, included RSS. Quote Link to comment Share on other sites More sharing options...
Trigant Posted August 13, 2018 Share Posted August 13, 2018 (edited) 3 hours ago, TaxiService said: You can create a new file with extra ground station examples below, save it to GameData/KerbinSide or RemoteTech folder and click 'Reload' button in RT Option window (see below) to load starting settings built from your installed mods, included this file. edit 2: I think you could've linked your modder explanation site for further understanding to your explanation. An hour looking for the explanation I understood GUID is just a "random number". Welp, I will share the renewed cfg file for further use for all KerbinSide users here once it's finished Edited August 13, 2018 by Trigant step by step Quote Link to comment Share on other sites More sharing options...
TaxiService Posted August 14, 2018 Share Posted August 14, 2018 21 hours ago, Trigant said: edit 2: I think you could've linked your modder explanation site for further understanding to your explanation. An hour looking for the explanation I understood GUID is just a "random number". Welp, I will share the renewed cfg file for further use for all KerbinSide users here once it's finished My bad, I completely forgot about the online manual on extra ground stations. I will keep this in my mind next time. Quote Link to comment Share on other sites More sharing options...
Trigant Posted August 14, 2018 Share Posted August 14, 2018 THE RemoteTech config cfg with all KerbinSide Groundstations for v1.45! RT config DropBox Link Install instructions: Put the RemoteTech config.cfg in you KerbinSide folder Load a savegame or create a new one In the RemoteTech options menu click preview In there you click on Reload in the "RemoteTech Starting Settings" line Bam, Finished! The direct code: Spoiler @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 = 0443e078-8d87-b2a3-ecd0-f2fc1dae15fb Name = Brownrock Latitude = 3.3292093854339826 Longitude = -37.145678538226967 Height = 132.450424 Body = 1 MarkColor = 0.996078014,0,0,1 Antennas { ANTENNA { Omni = 80000000 } } } STATION { Guid = 4278e430-5fd9-81bd-eecc-112b4fd3775c Name = Goldpool Latitude = -1.157746862668841 Longitude = 17.392106024154447 Height = 5.64185953 Body = 1 MarkColor = 0.996078014,0,0,1 Antennas { ANTENNA { Omni = 80000000 } } } STATION { Guid = 7a9d33fd-cc48-fbe0-0778-683baed45d9a Name = Lushlands Latitude = 2.1640513598116669 Longitude = 26.585832736430074 Height = 19.745575 Body = 1 MarkColor = 0.996078014,0,0,1 Antennas { ANTENNA { Omni = 80000000 } } } STATION { Guid = e3737b26-90fc-856b-10dc-64909d2eb957 Name = LodnieIsles Latitude = 29.448387629733272 Longitude = 13.088535751493195 Height = 34.2646027 Body = 1 MarkColor = 0.996078014,0,0,1 Antennas { ANTENNA { Omni = 80000000 } } } STATION { Guid = 597d7d59-12ab-667d-154d-b543972420d1 Name = CentralLakes Latitude = -15.309969427682777 Longitude = 91.323846276329064 Height = 11.9748478 Body = 1 MarkColor = 0.996078014,0,0,1 Antennas { ANTENNA { Omni = 80000000 } } } STATION { Guid = 542ad8c9-4c12-75e4-aa27-d1c4d8aab0cb Name = SeasEnd Latitude = -34.137795517631098 Longitude = 79.771967198329619 Height = -6.93864393 Body = 1 MarkColor = 0.996078014,0,0,1 Antennas { ANTENNA { Omni = 80000000 } } } STATION { Guid = 68a61022-8b8c-4951-3f65-d2dee4fd064c Name = Zebedee Latitude = 78.608115727152907 Longitude = 147.49162079537359 Height = 178.656693 Body = 1 MarkColor = 0.996078014,0,0,1 Antennas { ANTENNA { Omni = 80000000 } } } STATION { Guid = 97f269b1-60d5-b0be-8908-3a5c648a4dac Name = Northpole Latitude = 79.458003716077826 Longitude = -77.393313767136448 Height = 1.92135048 Body = 1 MarkColor = 0.996078014,0,0,1 Antennas { ANTENNA { Omni = 80000000 } } } STATION { Guid = e82ab9d0-fdc5-998c-8ca2-4d6c65e4161c Name = Arakebo Latitude = 8.4197143082890022 Longitude = 179.69866327298033 Height = -120.593079 Body = 1 MarkColor = 0.996078014,0,0,1 Antennas { ANTENNA { Omni = 80000000 } } } STATION { Guid = f4a6f60b-a313-b12c-3347-24477fcc1c25 Name = CoalerCrater Latitude = 35.348963157313428 Longitude = -98.887282058069403 Height = -3.47430301 Body = 1 MarkColor = 0.996078014,0,0,1 Antennas { ANTENNA { Omni = 80000000 } } } STATION { Guid = 14848dab-83bb-942a-cad7-6ace7977c674 Name = DeadkerbalPit Latitude = 14.733631590672084 Longitude = -127.01765575725295 Height = 92.9095612 Body = 1 MarkColor = 0.996078014,0,0,1 Antennas { ANTENNA { Omni = 80000000 } } } STATION { Guid = 06e83996-5707-9fde-dbf2-82771264c7e5 Name = GreenCoast Latitude = -3.4723687631760938 Longitude = 179.18139013170878 Height = 19.2983284 Body = 1 MarkColor = 0.996078014,0,0,1 Antennas { ANTENNA { Omni = 80000000 } } } STATION { Guid = 521941ae-f4af-1ba9-4f3b-8505b17f5718 Name = GuardiansBasin Latitude = 41.762245857654527 Longitude = -50.281306497678727 Height = 19.4952507 Body = 1 MarkColor = 0.996078014,0,0,1 Antennas { ANTENNA { Omni = 80000000 } } } STATION { Guid = b7445aab-510a-349e-f98b-ee43fa45e796 Name = HanbertCape Latitude = -22.637848642473806 Longitude = -140.2498425069202 Height = -7.99949455 Body = 1 MarkColor = 0.996078014,0,0,1 Antennas { ANTENNA { Omni = 80000000 } } } STATION { Guid = 77b80b2c-39b0-9bab-9e3c-f1fbd5a83276 Name = JebsRetreat Latitude = 5.5910286026764897 Longitude = -61.303538280930788 Height = 101.342873 Body = 1 MarkColor = 0.996078014,0,0,1 Antennas { ANTENNA { Omni = 80000000 } } } STATION { Guid = 81508afa-d79c-e44a-a7de-f321b209e3af Name = KerbinsBottom Latitude = -50.470100865846113 Longitude = 170.56924675030524 Height = 4.97224045 Body = 1 MarkColor = 0.996078014,0,0,1 Antennas { ANTENNA { Omni = 80000000 } } } STATION { Guid = 1a05e1dc-3456-cfad-d28f-a2b2834b564c Name = KKVLA Latitude = 10.605790712781179 Longitude = -132.26753817683533 Height = 17.1549816 Body = 1 MarkColor = 0.996078014,0,0,1 Antennas { ANTENNA { Omni = 80000000 } } } STATION { Guid = 74b170f5-8d93-c843-e28e-b9cd3de86f40 Name = MountSnowey Latitude = 20.453920016626476 Longitude = -78.09383120123924 Height = 42.4425316 Body = 1 MarkColor = 0.996078014,0,0,1 Antennas { ANTENNA { Omni = 80000000 } } } STATION { Guid = 1d9cef86-6873-e41c-300b-a77bf391d3ad Name = SouthPoint Latitude = -17.85670976297752 Longitude = 166.42691679572926 Height = 0.998443723 Body = 1 MarkColor = 0.996078014,0,0,1 Antennas { ANTENNA { Omni = 80000000 } } } STATION { Guid = 53cc0a5a-7c1b-3627-0c1a-90f6ad17e456 Name = TwinPeaks Latitude = 16.043645181791415 Longitude = -156.86419370703021 Height = 98.9122009 Body = 1 MarkColor = 0.996078014,0,0,1 Antennas { ANTENNA { Omni = 80000000 } } } } } Have fun! Quote Link to comment Share on other sites More sharing options...
TaxiService Posted August 19, 2018 Share Posted August 19, 2018 RemoteTech 1.8.13 for KSP 1.4.5 released This release is a standard maintenance, as well as a new back-port to KSP 1.3.1. What are fixed/changed: Recompiled for KSP 1.4.5 Flight Computer's delayed commands should be able to start precisely on time New API methods for connections and vessels for third-party mods Signal lines are back to the solid color instead of weird fading style. Complete changelog is below: Spoiler # Version 1.8.13.131 **Released August 19, 2018** What's New? =========== * Recompiled RemoteTech 1.8.13 for KSP 1.3.1 due to the significant number of players Detailed Changelog ================== Fixed Issues ------------ Pull Requests ------------- *** # Version 1.8.13 **Released August 19, 2018** What's New? =========== * Recompiled for KSP 1.4.5 * Tightened the precision of Flight Computer commands' extra delay * Resolved ambiguous wording of antenna deployment/retraction in Editor * Modernised and streamlined csproj * Switched to KSP's coloruful console message style * New API methods for connections and vessels * Resolved the material error on signal lines Detailed Changelog ================== Fixed Issues ------------ * Issue #661: RT-C tries to execute node too early? [requested by: WildLynxDev] * Issue #693: Error when signal lines are shown in a map or in the tracking station [requested by: jarosm] * Issue #752: Status near PAW buttons is not actually, is what happens when clicked [requested by: Gordon-Dry] Pull Requests ------------- * PR #753: Building with Visual Studio [PR by: PiezPiedPy] * PR #754: API methods primarily to support Kerbalism but can be used by others [PR by: PiezPiedPy] 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. Quote Link to comment Share on other sites More sharing options...
Tested&Launched Posted August 24, 2018 Share Posted August 24, 2018 Hi all - am new to Remote Tech but have a basic question - doesn't stock KSP already require a link to KSC in order to control unmanned probes? Just saying because the description on p1 for this mod says " It does this by requiring unmanned vessels have a connection to Kerbal Space Center (KSC) to be able to be controlled. " What does RemoteTech do that stock KSP doesn't? Does it take into account signal (speed of c) lag? What am I missing? Quote Link to comment Share on other sites More sharing options...
Tacombel Posted August 29, 2018 Share Posted August 29, 2018 Hi, all: There is something I quite not understand. I have a station orbiting duna. This station is connected to Kerbin with a 88-88, but when I try to connect a probe to Kerbin using the station as relay, I can't get it working. It doesn't matter if the probe is in omni range (Communotron 32 on both ships) or if I try to establish a point to point link with a dish like the DTS. The probe antenna says connected, but there is no control. There is no pilot on the station, if that matters. Thx in advance. Quote Link to comment Share on other sites More sharing options...
petlahk Posted August 30, 2018 Share Posted August 30, 2018 Hello. I've been playing KSP for a while now and using remote tech for about as long. I vastly prefer remote tech to the default comm network but it seems to just be completely borked in newer versions. When the remote tech thing says I don't have connection, for example, the ship is still completely controllable in every way despite being out of range. I even tried turning off all antennas then trying. I just turned off the Antenna controllable without connection cheat too, and the ship is still completely controllable. When I'm behind a moon, It's also still completely controllable. And no, this probe doesn't have SETI probe parts on it. And yes, I am using KSP 1.4.5.2243. Issues similar to this have been in remote tech for a *long* time. Please fix them. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.