Search the Community

Showing results for tags 'remotetech'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • The Daily Kerbal
  • Kerbal Space Program 2
    • KSP 2 Discussion
  • General KSP
    • KSP Discussion
    • Suggestions & Development Discussion
    • Challenges & Mission ideas
    • The Spacecraft Exchange
    • KSP Fan Works
  • Gameplay and Technical Support
    • Gameplay Questions and Tutorials
    • Technical Support (PC, unmodded installs)
    • Technical Support (PC, modded installs)
    • Technical Support (PlayStation 4, XBox One)
  • Add-ons
    • Add-on Discussions
    • Add-on Releases
    • Add-on Development
  • Community
    • Welcome Aboard
    • Science & Spaceflight
    • Kerbal Network
    • The Lounge
  • Making History Expansion
    • Making History Missions
    • Making History Discussion
    • Making History Support
  • Breaking Ground Expansion
    • Breaking Ground Discussion
    • Breaking Ground Support
  • International
    • International
  • KerbalEDU Forums
    • KerbalEDU
    • KerbalEDU Website

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Skype


Twitter


Location


Interests

Found 36 results

  1. (screenshots inside) 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. Major features: Make a group of satellites (a constellation) working together to archive a single purpose eg Global GPS, Ground-to-Air Communication Assign a vessel to one or more constellations Edit a ground station Colored connections and icons in Map View Built directly on KSP's CommNet infrastructure Many frequencies (up to 32,767!) to choose for a vessel or constellation Color Picker for "infinite" color choices User-friendly interfaces, included the sort and filter capabilities for the vessel list Bonus: Designed by a RemoteTech developer as a test bed on multiple features of RemoteTech 2.x re-development 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 for some features of the RemoteTech redevelopment project. (I am a member of the current RemoteTech team) Frequent Asked Questions Mods required Module Manager Tutorials Basics and interfaces License GNU GENERAL PUBLIC LICENSE, Version 3 Download GitHub SpaceDock
  2. Contracts for RemoteTech, built using Contract Configurator! Description This is a Contract Pack for the popular RemoteTech mod. Note that I am not affiliated with the Remote Technologies Group, but think the work they do is awesome! There are 14 one-time contracts included in the pack of varying difficulty. Here's a peek at what some of the contracts look like: Download CKAN: In CKAN, Select and download the mod "Contract Pack: RemoteTech" GitHub: For the direct download option, please ensure you have all the dependencies before raising a support request: Contract Configurator is a required dependency and can be downloaded from the Contract Configurator release thread. RemoteTech is a required dependency and can be downloaded from the RemoteTech release thread. ModuleManager is a required dependency and can be downloaded from the ModuleManager release thread. The RemoteTech Contract Pack can be downloaded from GitHub. Source The full source is available on GitHub. Change Log Note for Existing RemoteTech Saves If you are installing this on an existing save with RemoteTech, the contracts will work - but the coverage system will need about two minutes either in flight or in the tracking station to fully initialize. Until then it will assume 0% coverage of all bodies - which means that the contracts offered may not be the ones you expected. New saves are not affected. License The RemoteTech Contract Pack is licensed under CC-BY-NC-SA-4.0 Like what you see? Consider donating to the coffee fund! It will not go directly to supporting this or other mods under my care, but it may keep my motivation up!
  3. What is this? A lightweight interface add-on for CommNet of Kerbal Space Program. What does it do? This add-on adds RemoteTech's MultiPath mode to the CommNet visualisation of connections. This mode is to display all working connections of every vessel in the game. Just click the 'Network' button in Tracking Station or Map View to change the visualisation mode of CommNet. Why? Useful mode without installing CommNet Constellation (also have same mode) Useful resource for other modders to look and add other CommNet modes Mods required Nope. It is a DLL file. License GNU GENERAL PUBLIC LICENSE, Version 3 DOWNLOAD Github SpaceDock
  4. RemoteTech - StockConfigs What is this? RemoteTech - StockConfigs will add several ground stations on Kerbin that are compatible with RemoteTech. They are placed in the original places of the stock dishes and named after them. What you will get: Six additional groundstations as shown in the picture below. These are: Baikerbanur with an Omni Range of 1Mm Crater Rim with an Omni Range of 30Mm Harvester Massif with an Omni Range of 30Mm Mesa South with an Omni Range of 30Mm North Station One with an Omni Range of 30Mm Nye Island with an Omni Range of 75Mm It also provides short-range communication for all 3 launch sites added with 1.4 / Making History: Dessert Airfield with an Omni Range of 1Mm Island Airfield with an Omni Range of 1Mm Woomerang with an Omni Range of 1Mm Dependencies: RemoteTech - StockCongfigs depends on RemoteTech and ModuleManager Download: You can download RemoteTech - StockConfigs via Spaceock, GitHub and Ckan Licence: RemoteTech-StockConfigs is licensed under MIT Changelog Credits: @TaxiService & @Peppie23 for RemoteTech @sarbian & @blowfish for ModuleManager
  5. The CommNet feature, introduced in 1.2, made communications-satellite constellations relevant in the base game. A three-satellite constellation, in an equatorial orbit, is a relatively easy way to provide pretty good communications coverage; but such a constellation does not provide full coverage over the entire surface of a celestial body. However, a four-satellite constellation, orbiting in a tetrahedral configuration, does! What does such a constellation look like? It looks like this... With that in mind: I've compiled a list, for every celestial body in the Kerbol system, of orbital parameters for a tetrahedral constellation. 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: Due to Ike's proximity, the correct semi-major axis of 2320000 metres causes satellites to be thrown out of orbit. The given 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. 3625000m LAN. 0° LPE. 270° MNA. 0 EPH. 0 Satellite 2 INC. 33° ECC. 0.28 SMA. 3625000m LAN. 90° LPE. 90° MNA. -1.57078 EPH. 0 Satellite 3 INC. 33° ECC. 0.28 SMA. 3625000m LAN. 180° LPE. 270° MNA. 3.14159 EPH. 0 Satellite 4 INC. 33° ECC. 0.28 SMA. 3625000m LAN. 270° LPE. 90° MNA. 1.57078 EPH. 0 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.
  6. My aim was to provide for a coherent system of comms under SCANSAT, and to provide for a set of visually tolerable science parts while eliminating the ugly or impractical ones and the Probes+ historical bling. I've also boosted P+'s RTGs, axed quite a few redundant Ven parts, refitted the aerospike to its old modded appearance (which may require parts and models from an older version of Ven's overhaul), rewrote Ven's Radial Avionics Hub to be a probe core, and included an improvised fix to an old part issue. I hereby declare them public domain, and probably crap because of my bizarre tastes; do with them what you wish. ////COMMS //Omnis @PART[RTShortAntenna1]:FINAL { @description = A specialized launch antenna resistant to airflow; switched on by default, has fairly short range %TechRequired = flightControl %MODULE[ModuleRTAntenna] { %IsRTActive = true %Mode0OmniRange = 0 %Mode1OmniRange = 500000 %EnergyCost = 0.01 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} } @PART[longAntenna]:FINAL { @description = A standard telescoping omnidirectional antenna and radio kit used for communications in Low Kerbin Orbit; it is likely to be ripped off by a strong airstream, such as during atmospheric ascent or landing !MODULE[ModuleDataTransmitter] {} @MODULE[ModuleAnimateGeneric] { %allowManualControl = false } %MODULE[ModuleRTAntenna] { %Mode0OmniRange = 0 %Mode1OmniRange = 2500000 %MaxQ = 6000 %EnergyCost = 0.1 %DeployFxModules = 0 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} } @PART[antenna_tv]:FINAL { !MODULE[ModuleDataTransmitter] {} @MODULE[ModuleAnimateGeneric] { %allowManualControl = false } %MODULE[ModuleRTAntenna] { %Mode0OmniRange = 0 %Mode1OmniRange = 2500000 %MaxQ = 6000 %EnergyCost = 0.1 %DeployFxModules = 0 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} } @PART[RTLongAntenna3]:FINAL { @description = Noticeably more robustly designed than standard Communotrons, this antenna combines enough power to operate in Kerbosynchronous orbits with improved transmission rates @MODULE[ModuleAnimateGeneric] { %allowManualControl = false } %MODULE[ModuleRTAntenna] { %Mode0OmniRange = 0 %Mode1OmniRange = 4300000 %MaxQ = 9000 %EnergyCost = 0.15 %DeployFxModules = 0 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 5 %PacketResourceCost = 20.0 } } %MODULE[ModuleSPUPassive] {} } @PART[RTLongAntenna2]:FINAL { @description = What happens when you take a C-16, install a bigger antenna, and strap in an amplifier? You get an omnidirectional power hog with enough range to reach the Mun. @MODULE[ModuleAnimateGeneric] { %allowManualControl = false } %MODULE[ModuleRTAntenna] { %Mode0OmniRange = 0 %Mode1OmniRange = 12000000 %MaxQ = 6000 %EnergyCost = 0.5 %DeployFxModules = 0 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} } //Dishes @PART[mediumDishAntenna]:FINAL { @description = The DTS series uses a retractable steerable transceiver to drastically extend its range of operation, capable of reaching across Jool's oversized moon system, so long as the target is in its 45° cone !MODULE[ModuleDataTransmitter] {} @MODULE[ModuleAnimateGeneric] { %allowManualControl = false } %MODULE[ModuleRTAntenna] { %Mode0DishRange = 0 %Mode1DishRange = 220000000 %EnergyCost = 0.2 %MaxQ = 6000 %DishAngle = 45.0 %DeployFxModules = 0 %ProgressFxModules = 1 %TRANSMITTER { %PacketInterval = 0.3 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} } @PART[LongDeployableAntenna]:FINAL { @title = Communotron DTS-M5 @description = The M5 variant is an uprating of the basic design to achieve short interplanetary range (Duna) at the cost of drastic increase of power costs and a much narrower cone !MODULE[ModuleDataTransmitter] {} @MODULE[ModuleAnimateGeneric] { %allowManualControl = false } %MODULE[ModuleRTAntenna] { %Mode0DishRange = 0 %Mode1DishRange = 35390000000 %EnergyCost = 1 %MaxQ = 6000 %DishAngle = 0.05 %DeployFxModules = 0 %ProgressFxModules = 1 %TRANSMITTER { %PacketInterval = 0.5 %PacketSize = 2 %PacketResourceCost = 15.0 } } %MODULE[ModuleSPUPassive] {} } @PART[HighGainAntenna]:FINAL { !MODULE[ModuleDataTransmitter] {} @MODULE[ModuleAnimateGeneric] { %allowManualControl = false } @description = The HG series introduces enhanced electronic subsystems which allow it to combine advantages from several antenna: it has both interplanetary range, a wide cone, and higher packet fideltiy %MODULE[ModuleRTAntenna] { %Mode0DishRange = 0 %Mode1DishRange = 60500000000 %EnergyCost = 1.0 %MaxQ = 6000 %DishAngle = 20 %DeployFxModules = 0 %TRANSMITTER { %PacketInterval = 0.2 %PacketSize = 5 %PacketResourceCost = 25.0 } } %MODULE[ModuleSPUPassive] {} } @PART[RelayAntenna5]:FINAL { @title = CommTech D-800 @description = An invention of one Ven Kerman, CommTech D-800 combines an enhanced datalink unit with a large focusing reflector dish covered in Shiny Stuff™ to maintain a reliable connection all the way out to Dres without excessive use of electric power. Canvas cover accidentally included; do not remove. !MODULE[ModuleDataTransmitter] {} %MODULE[ModuleRTAntenna] { %Mode0DishRange = 0 %Mode1DishRange = 60500000000 %EnergyCost = 0.8 %DishAngle = 0.08 %TRANSMITTER { %PacketInterval = 0.9 %PacketSize = 6 %PacketResourceCost = 45.0 } } %MODULE[ModuleSPUPassive] {} } @PART[commDishVSR]:FINAL { @title = Communotron 88-88 @description = The 88-88 is the second edition of the classic Symphonic long-range collapsible radio communications dish. Just like old one, it can reach all the way to Jool and Sarnus, but this one suffers no loss in signal quality. Our QA department assures that any "screams of the damned" heard on the channel it are purely signal interference. !MODULE[ModuleDataTransmitter] {} @MODULE[ModuleAnimateGeneric] { %allowManualControl = false } %MODULE[ModuleRTAntenna] { %Mode0DishRange = 0 %Mode1DishRange = 146220000000 %EnergyCost = 0.95 %MaxQ = 4500 %DishAngle = 0.06 %DeployFxModules = 0 %TRANSMITTER { %PacketInterval = 0.5 %PacketSize = 2 %PacketResourceCost = 20.0 } } %MODULE[ModuleSPUPassive] {} } @PART[RelayAntenna50]:FINAL { @title = CommTech D-850 @description = The D-850 builds upon the basic design through upscaling of all major components in order to perform effectively in missions to the gas giants; like the original, it sends data in large encrypted packages - stop calling our tech support !MODULE[ModuleDataTransmitter] {} %MODULE[ModuleRTAntenna] { %Mode0DishRange = 0 %Mode1DishRange = 428180000000 %EnergyCost = 1.2 %DishAngle = 0.03 %TRANSMITTER { %PacketInterval = 0.9 %PacketSize = 6 %PacketResourceCost = 50.0 } } %MODULE[ModuleSPUPassive] {} } @PART[RelayAntenna100]:FINAL { @title = CommTech D-X @description = CommTech D-X is reengineered from the ground up to retain effectiveness at extreme ranges, such as during missions to Plock; as a result, it is noticeably more efficient than all of its counterparts. Reports of packets being corrupted with the phrase "I'll be back" are greatly exaggerated. !MODULE[ModuleDataTransmitter] {} %MODULE[ModuleRTAntenna] { %Mode0DishRange = 0 %Mode1DishRange = 700360000000 %EnergyCost = 1.2 %DishAngle = 0.01 %TRANSMITTER { %PacketInterval = 0.5 %PacketSize = 6 %PacketResourceCost = 50.0 } } %MODULE[ModuleSPUPassive] {} } @PART[jx2LDA]:FINAL { @descripton = This enormous, high-powered relay antenna was commissioned by Blinkenlights LLC after someone asked "What happens if we go further out than the Kerbol system?" It most definitely is not in response to any vessels having accidentally already achieved an escape trajectory from the system. -MODULE[ModuleDeployableAntenna] {} MODULE { name = ModuleAnimateGeneric animationName = deployHexes allowManualControl = false isOneShot = false startEventGUIName = Extend endEventGUIName = Retract actionGUIName = Toggle Antenna } %MODULE[ModuleRTAntenna] { %Mode0DishRange = 0 %Mode1DishRange = 9460000000000000 %EnergyCost = 5 %MaxQ = 3000 %DishAngle = 0.001 %DeployFxModules = 0 %TRANSMITTER { %PacketInterval = 0.5 %PacketSize = 2 %PacketResourceCost = 20.0 } } %MODULE[ModuleSPUPassive] {} } @PART[ju1MDA]:FINAL { @description = This rather good sized, high-powered antenna was originally a garden variety umbrella. Unlike its CommTech competitor, it's optimized for relay operations via beamforming to expand its signal cone -MODULE[ModuleDeployableAntenna] {} MODULE { name = ModuleAnimateGeneric animationName = deployHexes allowManualControl = false isOneShot = false startEventGUIName = Extend endEventGUIName = Retract actionGUIName = Toggle Antenna } // This is what makes it work with RemoteTech. %MODULE[ModuleRTAntenna] { %Mode0DishRange = 0 %Mode1DishRange = 700360000000 %EnergyCost = 3 %MaxQ = 6000 %DishAngle = 5 %DeployFxModules = 0 %TRANSMITTER { %PacketInterval = 0.5 %PacketSize = 2 %PacketResourceCost = 20.0 } } %MODULE[ModuleSPUPassive] {} } @PART[jw1MDA]:FINAL { @description = Commissioned by Blinkenlights LLC, this part is primarily targeted for those probes and rovers destined to head a bit further out than the last lot… While using a significantly different design, it is comparable in capabilities to JU1. -MODULE[ModuleDeployableAntenna] {} MODULE { name = ModuleAnimateGeneric animationName = deployHexes allowManualControl = false isOneShot = false startEventGUIName = Extend endEventGUIName = Retract actionGUIName = Toggle Antenna } // This is what makes it work with RemoteTech. %MODULE[ModuleRTAntenna] { %Mode0DishRange = 0 %Mode1DishRange = 700360000000 %EnergyCost = 3 %MaxQ = 3000 %DishAngle = 5 %DeployFxModules = 0 %TRANSMITTER { %PacketInterval = 0.5 %PacketSize = 2 %PacketResourceCost = 20.0 } } %MODULE[ModuleSPUPassive] {} } ////PRUNING !PART[commDish]:FINAL { } !PART[SurfAntenna]:FINAL { } !PART[HighGainAntenna5]:FINAL { } !PART[RTShortDish2]:FINAL { } !PART[RTLongDish2]:FINAL { } !PART[RTGigaDish1]:FINAL { } !PART[RTGigaDish2]:FINAL { } !PART[KerbCan]:FINAL { } !PART[LargeInflatableHAB]:FINAL { } !PART[VenLV909b]:FINAL { } !PART[PoodleM]:FINAL { } !PART[stationHubLarge]:FINAL { } !PART[MK2VApod]:FINAL { } !PART[SmallInflatableHAB]:FINAL { } !PART[MicroInflatableHAB]:FINAL { } !PART[InflatableHAB]:FINAL { } !PART[size2nuclearEngine]:FINAL { } //Radial Avionics Hub refit @PART[RadialavionicsHub]:FINAL { !MODULE[ModuleSAS] { } %MODULE[ModuleSPU] { } %MODULE[ModuleCommand] { %minimumCrew = 0 %RESOURCE { name = ElectricCharge rate = 0.005 } } } //Aerospike edit @PART[toroidalAerospike]:FINAL { @author = Ven !mesh = DELETE @rescaleFactor = 1.2 MODEL { model = VenStockRevamp/Squad/Parts/Propulsion/Aerospike } @node_stack_bottom = 0.0, -0.7941136, 0.0, 0.0, -1.0, 0.0 @MODULE[ModuleAnimateHeat] { @ThermalAnim = ToroidalAerospikeHeat } MODULE { name = ModuleJettison jettisonName = fairing bottomNodeName = bottom isFairing = True jettisonedObjectMass = 0.1 jettisonForce = 5 jettisonDirection = 0 0 1 } } //Glitchy part fix @PART[ParaDockingPort]:FINAL { !DRAG_CUBE {} } //RTGs @PART[ca_rtg2000]:FINAL { %MODULE[ModuleGenerator] { %OUTPUT_RESOURCE { name = ElectricalCharge %rate = 0.75 } } } @PART[ca_rtg3900]:FINAL { %MODULE[ModuleGenerator] { %OUTPUT_RESOURCE { name = ElectricalCharge %rate = 2.25 } } } //Pruning !PART[dmUSAccGrav]:FINAL {} !PART[dmUSAtmosSense]:FINAL {} !PART[dmUSPresTemp]:FINAL {} !PART[dmUSScope]:FINAL {} !PART[dmUSImagingPlatform]:FINAL {} !PART[dmUSMat]:FINAL {} !PART[dmUSGoo]:FINAL {} !PART[dmUSGoreSat]:FINAL {} !PART[dmUSAsert]:FINAL {} !PART[dmReconLarge]:FINAL {} !PART[dmSIGINT]:FINAL {} !PART[dmSIGINT.End]:FINAL {} !PART[dmSIGINT.Small]:FINAL {} !PART[dmReconSmall]:FINAL {} !PART[dmSeismicHammer]:FINAL {} !PART[dmSeismicPod]:FINAL {} !PART[dmBathymetry]:FINAL {} !PART[SCANsat_Scanner2]:FINAL {} !PART[SCANsat_Scanner32]:FINAL {} !PART[SCANsat_Scanner24]:FINAL {} !PART[ca_fom_lander]:FINAL {} !PART[ca_vor_tank]:FINAL {} !PART[ca_vor_sp2]:FINAL {} !PART[ca_vor_sp]:FINAL {} !PART[ca_vor_sep1]:FINAL {} !PART[ca_vor_sar]:FINAL {} !PART[ca_vor_mptank]:FINAL {} !PART[ca_vor_engine]:FINAL {} !PART[ca_vor_dish]:FINAL {} !PART[ca_vor_core]:FINAL {} !PART[ca_fom_sp]:FINAL {} !PART[ca_fom_parachute]:FINAL {} !PART[ca_fom_heatS]:FINAL {} !PART[ca_vor_comm]:FINAL {} !PART[ca_fom_drogue]:FINAL {} !PART[ca_ESM2]:FINAL {} !PART[ca_ESM]:FINAL {} !PART[ca_torekkaPM]:FINAL {} !PART[ca_torekka_truss]:FINAL {} !PART[ca_louver_s]:FINAL {} !PART[ca_louver_m]:FINAL {} !PART[ca_louver_s2]:FINAL {} !PART[ca_gravioli]:FINAL {} !PART[ca_accelerometer]:FINAL {} !PART[ca_thermometer]:FINAL {} !PART[ca_tank_mp_m]:FINAL {} !PART[ca_tank_lfo_m]:FINAL {} !PART[ca_trident]:FINAL {} !PART[ca_linkor]:FINAL {} !PART[ca_lahar]:FINAL {} !PART[ca_jib]:FINAL {} !PART[ca_tank_mp_s]:FINAL {} !PART[ca_battery_m]:FINAL {} !PART[ca_battery_l]:FINAL {} !PART[sp_odyssey_b]:FINAL {} !PART[sp_odyssey_a]:FINAL {} !PART[sp_maven]:FINAL {} !PART[sp_mariner_b]:FINAL {} !PART[sp_mariner_a]:FINAL {} !PART[sp_express_b]:FINAL {} !PART[sp_express_a]:FINAL {} !PART[ca_rtg8200]:FINAL {} !PART[ca_battery_s]:FINAL {} !PART[ca_rw_xsmall]:FINAL {} !PART[ca_rw_small]:FINAL {} !PART[ca_rw_medium]:FINAL {} !PART[ca_rw_large]:FINAL {} !PART[ca_rst]:FINAL {} !PART[ca_rs04]:FINAL {} !PART[ca_rs01]:FINAL {} !PART[ca_RM04]:FINAL {} !PART[ca_RM03]:FINAL {} !PART[ca_RM02]:FINAL {} !PART[ca_RM01]:FINAL {} !PART[ca_aacs]:FINAL {} !PART[ca_startrack]:FINAL {} !PART[tatsujin]:FINAL {} !PART[quetzal]:FINAL {} !PART[barquetta]:FINAL {} !PART[torekka]:FINAL {} !PART[antenna_quetzal]:FINAL {} !PART[ca_ant_gps]:FINAL {} !PART[antenna_cone_toggle]:FINAL {} !PART[antenna_cone]:FINAL {} !PART[dish_tatsujin]:FINAL {} !PART[dish_S]:FINAL {} !PART[dish_quetzal]:FINAL {} !PART[dish_L]:FINAL {} !PART[dish_deploy_S2]:FINAL {} !PART[dish_deploy_S]:FINAL {} !PART[ca_landv_srm]:FINAL {} !PART[ca_landv_vernier]:FINAL {} !PART[ca_landv_battery]:FINAL {} !PART[ca_landv_core]:FINAL {} !PART[ca_landv_hga]:FINAL {} !PART[ca_landv_omni]:FINAL {}
  7. I have a bit of a dilemma here I could either go with remote tech and have the following mods with it and reasons why I like it. 1) Time Delay, 2) 10km EVA kerbal antenna, 3)Remote Tech Contracts, 4) KOS would work fine for the time delay. For Commnet I would use 1) Science Relay so I can send science to a science lab on a space station orbiting above 2) Commnet Constellations for better organization of signals 3) Works with my mods kerbal health so I get the perk of being connected to home Con is there is no time delay so there is no challenge or real use for KOS being used. I would like a second opinion on these thank you.
  8. I have the RemoteTech mod installed for this. I have a network of 3 comm sats around Kerbin and they have the CommTech-1 dish on it (range: 350 Gm). I also set up a network of sats around the Mun and Minmus (Mun has HG-5s that talk to each other and with Kerbin along with a C-16 omni. Minmus has DTS-M1 to talk to kerbin, HG-5s to talk to each other, and an omni). Now attempting Duna, I initially put on an 88-88 to talk to Kerbin with HG-5s to talk to each other and after launching the second sat, when its behind the planet (not in line of sight of kerbin), I get no comms even though it has connection with the 1st sat via the HG-5. I then tried the KA-100 Relay dish and am again experiencing the same issue. Any idea on what I could be doing wrong? I had no issues with the HG-5 and DTS-M1 when around Mun/Minmus.
  9. 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
  10. Hello Guys! I've started playing KSP again some coupple days ago and I have ran into a problem when I tried to work with Probes. I have an Image that is self explainatory: http://imgur.com/gallery/zUKll . But just in case, I can't send any command to my probes, I put a deployed omni antenna, have electricity, I'm in the lounchpad, the letters in the top left are green, the antennae say "Status: connected". So I don't understand what is wrong, it may be caused by some mod, since I have a lot installed -they are listed below-. The problem solves when I desactivate RemoteTech, and doesn't occur with CommNet. HELP ME PLEASE!!! The game version is: 1.2.1 Mods installed (as appear in gamedata folder): [x]-science 000_FilterExtensions 000_FilterExtensions Configs 000_Toolbar 000_USITools 0PinlineFairings AllYAll B9PartSwitch CactEye CameraFocusChanger Chatterer CommunityCategoryKit CommunityResourcePack CommunityTeachTree ContractConfigurator ContractPacks CryoTanks CTTP CxAerospace DeadlyReentry DMagicOrbitalScience DMagicScienceAnimate DMagicUtilities DockingPortAlignmentIndicator ExtraplanetaryLaunchpads Firespitter FuelTanksPlus Impact InterstellarFuelSwitch KAS-1.0 KerbalAtomics KerbalEngineer KerbalFlightIndicators KerbalJointReinforcement KIS Kopernicus ksp-precisenode-1.2.4 KWRocketry LETech MagicSmokeIndustries ModularFlightIntegrator NavyFish NearFutureConstruction NearFutureSolar NearFutureElectrical NearFutureProps NearFuturePropulsion NearFutureSpacecraft OPM PartCommanderContinued PlantaryBaseInc PreciseManeuver ProceduralFairings ProceduralParts RealChute RemoteTech REPOSoftTech SCANsat SETIcontracts SETIgreenhouse spacetux SpaceY-Expanded SpaceY-Lifters StageRecovery SurfaceExperimentPackage TarsierSpaceTech ThunderAerospace Trajectories TriggerTech UmbraSpaceIndustries UniversalStorage WaypointManager ModuleManager.2.7.5
  11. Okay, maybe this has been asked before but I can't find anything that helps. I have put RemoteTech for 1.2.2. into my GameData folder, as per usual, and KSP loads fine, until it reaches RemoteTech. As far as I can tell it will load up to the RemoteTech parts folder and stop. It won't load past it. What am I supposed to do?
  12. Hi all! I am playing in the Career mode now, in the KSP: 1.1.3 (Unix) - Unity: 5.2.4f1 - OS: Linux 3.10 CentOS 7.2.1511 64bit with changed gameplay. My main mods, for change gameplay: DMagic Orbital Science - 1.3.0.2 Kerbal Attachment System - 0.5.9 Kerbal Inventory System - 1.2.12 NearFutureConstruction - 0.6.4 NearFutureElectrical - 0.7.8 NearFuturePropulsion - 0.7.4 NearFutureSolar - 0.6.2 NearFutureSpacecraft - 0.5.1 Kerbal Planetary Base Systems - 1.1.4 DeepFreeze Continued... - 0.22.3 RemoteTech - 1.7.1 SCANsat - 1.1.6.6 StageRecovery - 1.6.4 TAC Life Support - 0.12.4 kOS - 1.0 kOS, TAC Life Support, and the RemoteTech are the main in my game balance. Unmanaged probes require connection between Kerbin and probe, or I can use Kerbonaut-pilot to local manage vessels. But Kerbonauts require life support. I must preffer umanaged probes, with kOS scripts for maneuvers(possible to run script in time when connection exist).Also I use kOS for launching tourists (to bored do it by hands, I just read books or show youtube, forums in the time of tourists flight). This game mechanics is difficult, and interesting. Also I changed gameplay by NearFuture+Kerbal Planetary Base system(amount of original parts too small, and technical tree too small for long-term game too), KAS+KIS(without these, kerbanauts- engineers really not required) , Dmagic Orbital Science(too many interesting science), and Planetary Experiments for additional fan with science. Also I used these modsfor help me in my game, and reduce bored moments: Kerbal Engineer Redux - 1.1.1 RCS Build Aid - 0.8.1 Kerbal Alarm Clock - 3.7.1 Transfer Window Planner - 1.5.1 [x] Science! - 5.0 Toolbar - 1.7.12 Also, I installed these mods for fan: LaserDist - 0.9.2 Final Frontier - 1.0.10.2467 And following mods installed by ckan (dependecy) B9 Part Switch - 1.4.3 Community Resource Pack - 0.5.4 Connected Living Space - 1.2.3 Contract Parser - 1.0.4 Contracts Window Plus - 1.0.6.4 Progress Parser - 1.0.5 JSIAdvTransparentPods - 0.1.7 RasterPropMonitor - 0.27.1 KSP-AVC Plugin - 1.1.6.1 ShipManifest - 5.1.2.2 I have a two technical problems in my career, probably related with RemoteTech: 1) If I upgrade Tracking Station in the latest upgrade, then I get problems with my 2 far vessels: with vesselin the way to the Duna, and with vessel in the Sun's orbit. If I try to go to one of these vessels after upgrade, I seen black outside in the computer screen, and no any numbers in the altitude window. These bug require KSP restarting. After restart, this far vessel disappears. 2) I can't to establish connection between far vessel and base. Using Reflectron KR-14 too I insert link to my game files. If you fast forward to the departure to the Duna, there is no connection between this vessel and Kerbin space center: https://goo.gl/YQYcL1 Please help me with fixing this problems (fix bug or may be invent any workaround).
  13. Hi Guys, Having real issues with my (fairly large) Duna probe in an RT install... my signal delay is up to about 2s and I'm trying to do a course correct ion burn... however I'm having major issues aligning with the manouver marker. Neither the ASAS nor the flight computer can actually align to the node - they just circle around it always over-correcting and wasting precious monoprop. I've checked in both RCS buildaid and as the manouvers are conducted and there's no errant 'spin' imparted by unbalanced RCS. Nor is the probe itself unbalanced... it just burns like cray in one direction, overshoots, and burns like crazy back again, like a beagle puppy on a polished timber floor... My only thought is that the computers can't cope with the sheer mass (and thus inertia) of the probe - it does weigh in at some 47,000kg... Though I packed SpaceYRCS5x7 thrusters in an effort to compensate... Help?
  14. KSP RemoteTech Antenna Selector Google Sheets: Link This document allows you to view the antennas utilized by RemoteTech to aid you in the preparation for missions to specific bodies. ----------------------------------- Antennas Sheet The 'Antennas' sheet allows you to view all the antennas listed by Mod pack grouping and all their individual statistics. ----------------------------------- Antenna Selector Sheet The 'Antenna Selector' sheet allows you to pick a celestial body and view which antennas are suitable for the application. Planets chosen are considered from Kerbin whilst moons selected are considered around their parent body. ----------------------------------- Systems Stats Sheet The 'System Stats' sheet lists details about all the available bodies to chose from if you wish to make your own calculations or assumptions. ----------------------------------- Form Submission I have included a link on the initial 'Antennas' sheet to a Google Form where you can submit details of antennas you wish for me to include on the spreadsheet. The submissions should auto-fill into the 'Form Submissions' sheet for later review. ----------------------------------- Please let me know what you think, any mistakes I have made, any ways I can improve this etc. etc. I don't have much experience with public Google docs so there may be some issues, if anyone has a better way of letting users access and change the 'Body' drop down please let me know. Hopefully you find this useful for your own games. KSP RemoteTech Antenna Selector - Google Sheets: Link
  15. There is a bug in The mod us probes and remotetech on some of the probes the antennas have a dynamic pressure limit that is set very low. As a result the antenna snaps creating an invisible part that caues clipping bugs and other problems. I don't want to uninstall remote tech as my rockets all have the antennas integrated with them as well as us probs. can someone help plz??!
  16. Constellation Builder v0.3 - Web version File version - requires GeoGebra software, download link below DIRECTIONS: Adjust slider for range of omnidirectional antenna to be used on the satellites, in 100's of kilometers. 4Mm range? Set it to 40. As of v0.3 all distance sliders display in kilometers. The grid scale is still 1 unit = 100km. Anjust slider for number of satellites in the constellation. Select connection requirements. (Do they need to connect to KSC and/or each other?) IMPORTANT: IF YOU DO NOT SELECT EITHER CHECKBOX IT WILL PUT THE CONSTELLATION IN AN ORBIT UNDER THE SURFACE OF KERBIN. This is hardcoded and keeps GeoGebra from choking on it until I implement some more features. As of v0.3 this is no longer true. An additional slider has been added to choose the orbital altitude in km, with upper and lower limits of the orange rings. Area of uninterrupted coverage will be displayed as a wireframe torus built from magenta circles and dark purple rings. Recommended constellation orbit displayed as a dark red ring. This will be removed at some point. Minimum and maximum bounds for the given parameters are displayed as orange rings. ADDITIONAL NOTES: Kerbin has a sort of halo - that's where the atmosphere is. Points representing the Mun and Minmus, along with to-scale spheres for both bodies, correct orbits, and rings representing the SOI of both bodies are present. Minmus' orbit uses y+ as the reference direction and the x-y plane as the reference plane. Zoom out far enough and you'll notice a pair of rings. The blue ring represents Kerbin's SOI. The red ring represents the max range at which KSC can connect to a satellite without relays. For the purposes of this tool, KSC is located exactly on the equator at sea level at (6,0,0) Cartesian coordinates. If you download the file, be very careful not to accidentally change something and break it. All game data from the official wiki. http://wiki.kerbalspaceprogram.com/wiki/Main_Page All RemoteTech data from https://remotetechnologiesgroup.github.io/RemoteTech/. HOW IT WORKS: KNOWN ISSUES: Selecting neither connection requirement results in a nonsensical orbit. Minimum orbit does not respect intersat connection requirement checkbox. My torus sucks. Missing "impossible orbit" checks. (inside the atmosphere, in an area swept by the Mun's or Minmus' SOI, etc.) Latitude of polar shadow is given as degrees north (it's both poles) and simply uses "?" if the coverage zone does not actually intersect Kerbin. Polar shadow calculations don't care if the constellation is actually in range of Kerbin's surface. TO-DO: Fix the known issues. Allow adjustment of the placement of the constellation within the upper and lower bounds. Right now, it places the constellation 100km inside the upper bound. Make the antenna range input in either kilometers or megameters. Draw the polar shadows of Kerbin. Right now, all it has is the latitude N or S above which there is no ground coverage. Add an option to show the calculation objects. Upload the version of this that matches the description of how it works. Add pictures. GEOGEBRA SOFTWARE LINKS: GeoGebra main page - Download GeoGebra - GeoGebra License - About GeoGebra GeoGebra user manual (more like a wiki) LICENSE (because forum rules): I did not make GeoGebra. I also did not invent math. All data related to the game and the mod came from the KSP Wiki and the RemoteTech website. What part of this I do hold the rights to is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. Have fun!
  17. Hello. I have recently installed Remotetech and I have been trying to set up a satellite network around Kerbin. I have been unable to position the satellites however. For example, I tried to get a sat directly above KSC. I tried moving the manuverability nodes around and doing different burns each time I tried, but I couldn't get the sat in the correct spot, let alone a set of three. My question is: Is there a mod that allows you to tell it where you want a satellite, and it will tell you where and when to burn? It would be even better If it can place the node for you like MechJeb can. Thank you to any feedback.
  18. So, I just discovered RemoteTech and I liked the difficulty of having to micro-manage signals and time delays. This mod, along with TAC and KCT, are serious game changers. But, in my experiment save, I tried to establish system-wide comms for the Kerbin system. I already had a triplet of comsats in a low-ish (625 km) orbit and that covered comms up to 4.5 Mm altitude. I built another satellite, with two dishes, one for each of the moons, and two omnis, and launched it into a 4.5 Mm orbit. I set Mun and Minmus as the targets for the dishes. It should help if I added my crappily-drawn diagram in MS PaintTM. Here's the part where I encountered a problem. I sent a probe out to Mun, thinking that "Aha! I have the relay-sat's dish pointed at Mun; therefore, I must be able to have comms even there!" Wrong. I lost the probe after passing 4.5 Mm, and didn't acquire until it came back into sight of the low-orbit commsat system. Experienced RT2 users: What am I doing wrong (based on both the diagram and what I've told you)?
  19. Hi, I've found a bug most likely caused by remotetech, after the recent 1.1.3 ksp update I found I couldn't launch an unmammed rocket. The main problems are "T" and the space bar don't work, these actions couldn't be clicked on either, has anyone come across anything like this? also I've deleted my add ons and isolated it to remotetech, any help would be greatly appreciated.
  20. I made a RemoteTech constellation building helper, would anyone be interested if I uploaded it? It's both a file and a web app. You'll need the GeoGebra geometry software to use the file. EDIT: Released! Find it here:
  21. I'm gonna do a Jool mission, but to get the mission working i'll need ISRU, so I made some 'scansats'. However, the VAB says they need data transmitters. I tried using stock antenas instead of remotetech ones, but that didn't help. I can't launch my mission untill I'm sure this will work. what antenae can the orbital scanner use
  22. Hi all, I'm setting up my RemoteTech relays in kerbostationary orbit. I do so by getting the sat up to approx 2866km, then burn to circularize until the orbital period as reported by Kerbal Engineer Redux is as close as I can get to 6 hours. Usually I'm not off by more than a few milliseconds (e.g. 5h 59m 59.995s or 6h 0m 0.005s). At the same time I try to get the eccentricity as close as possible to zero What I am currently observing in KSP 1.1.2, is that even with no time warping, the surface longitude reported by KER slowly drifts. If I time warp it becomes very visible. I'll get some screenshots when I get home tonight, but based on the above, is there anything obvious I'm missing? I understand that if the eccentricity is not zero there will be some oscillation in longitude, but what I see is a unidirectional drifting (I forget if west or east), it does not go back a forward. Could KER be wrong with either the orbital period or the longitude readouts? Or is there something else? Thanks for your input
  23. I recently installed the RemoteTech mod and was trying to figure out how to activate it in my game file. I can see that the KSC has the Mission Control icon over it, but I have no additional UI showing a satellite connection or range. I tested a rocket with no antenna and it worked in full orbit with no line-of-sight. Is this a mod that doesn't work in Sandbox Mode? Also, is there a way to edit the settings file to allow for RemoteTech in Sandbox Mode?
  24. Hi All, Experiencing a strange bug where on some (not all) of my vessels, I suddenly cannot toggle SAS (i.e. I could yesterday). When I hit T it goes on for a fraction of a second, thats it. Doesn't change if I hold down the key. I'm using RemoteTech which I feel might be relevant here. Anyone experienced this before? http://imgur.com/8LAukQ6
  25. So I installed the RemoteTech mod and started doing the satellite omni network tutorial here: http://remotetechnologiesgroup.github.io/RemoteTech/tutorials/c16network/ Then I ran into this bug while trying to set the orbital periods: The omni network tutorial I linked above states that the satellites' orbital periods have to be quite exactly synchronized. I'm totally new to this mod and therefore I have to ask if it's still possible to sync these satellites' orbital period so that they don't drift out of contact even with the decay bug present? Or am I just wasting my time with this for now? I'm thinking of doing the savegame editing that's explained in the bottom of the tutorial, so that their orbits decay at the same rate. I read somewhere that the decay was dependent on part count or craft mass somehow. Therefore I assume this should work assuming that the satellites are identical?