![]() ![]() Get shortest possible delay to given Vessel It is better to use addons:available("IR") for this. True if RT is installed and RT integration enabled. Documentation of Connection class contains further information on how RemoteTech will change the behaviour In order to send a message to another vessel a valid RemoteTech connection will have to exist between themĪnd of course messages will arrive to their destination with a proper delay. When installed RemoteTech will influence communication between vessels. The default ground station is called “Mission Control”. ![]() You can use RTADDON:GROUNDSTATIONS to get a list of all ground stations. M : SETFIELD ( "target", "minmus" ).Ī string containing the name of a body or vesselĪ string containing the name of a ground station (case-sensitive) M : SETFIELD ( "target", "Mission Control" ). SET M to p : GETMODULE ( "ModuleRTAntenna" ). SET P TO SHIP : PARTSNAMED ( "mediumDishAntenna" ). This implementation may change in the future to account for delays in reading and writing data over the connection. Under the current implementation, there is no delay when accessing the archive with a local terminal. The archive will still be inaccessible without a connection to the KSC. If you launch a manned craft while using RemoteTech, you are still able to input commands from the terminal even if you do not have a connection to the KSC. This will require you to plan ahead and copy necessary scripts for your mission to probe hard disk, if your kerbals and/or other scripts need to use them while not connected. But you should note, that when there is no connection to KSC the archive volume is inaccessible. Scripts launched when you still had a connection will continue to execute even if your unmanned craft loses connection to KSC. When you have RemoteTech installed you can only interact with the core’s terminal when you have a connection to KSC on any unmanned craft. All of the previous implementation as detailed on this page ![]() the spreadsheet is based on a very useful one I grabbed once from RT or RO posts, but don't remember where, anymore.New in version v1.0.2: kOS now supports access to connection informaion from a unified location. I went from RT to AntennaRange, but with Root Mode, back to RT. It takes a bit of tweaking to find what suits you, but all in all, it makes RT to be much more than it seemed to be. But that would be really helpful in spacecraft pairing at these lower rm values, as 2 antennas only reach a performance of ~54%. There is an additional config value allowing combined effect of multiple omnis, but its implementation seems to be a little unclear github #594. Green stations can lock omnis at synchronous orbits and narrow-beam dishes can, at moments, easily call home from the inner planets. Numerous, but short range yellow stations now greatly expand ground contact coverage for big antennas up to the Moon. Values between 0.1-0.333 start to make sense, depending on decisions like if you want to reach the Moon with omnis or not. Note: RT in RSS doesn't seem to change ground station range when rm is used. The recommended multiplier (0.5) is too much here, considering the massive range of real dishes - the small 500km reflectron could be picked up at GPS orbit by the DSN Root mode really comes into play as it gives the 'deep space' a meaning again. So big, that you need a lot of ground stations beyond KSC just to start, and still be out of touch almost half the time. A green value means the gain is hard capped by the "root flat max" limit. Also more antenna/relay combos are possible for other planets.Ĭircles designate LKO/KSO/Munar/Gigameter ranges. You can kick off your Keosynchronous satellite network (~3.0Mm) up with the VR-2 omni, a single 88 dish can put omnis on Mun and KSC can almost reach to a medium dish around Duna (10-20Gm). What this does, it "opens" up the hard cap of the standard mode, but in a more stricter way than the 0.5 modifier, while two identical antennas still maintain 90% of their "nominal" range. Stock RT with lower RangeMultiplier (0.333) With the exposure of the RT configs in the UI, it is now easier to activate and offers a whole range of difficulty scaling.Īnd if you are playing a RSS or any other scale mode, you will love it.Įxample 1. It's details and calculations with the base RangeMultiplier are well documented, I'll try to show you what else it enables you to do for your gameplay. A stronger antenna on one end will "boost" (gain) the range of the weaker one. In essence, it calculates antenna ranges based on their combined performance (optionally their count). Want bragging rights to claim playing KSP w/RT? ![]() The Undervalued "Root Mode" in RemoteTechĪre you confused that a ground dish of the size of a whole rocket cannot communicate with the nearest moon?ĭo you find standard Remote Tech too challenging, but like the line-of-sight logic? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |