![]() So you typically have satellites aimed at different bodies and thus, constellations. If you have a directional dish aimed at Duna, it's not likely to be able to communicate with Moho or Eve for very much of the time. Constellations are almost inherent, maybe not as much as the mod adds, but they are there. Combining antennas isn't entirely accurate either (though this is a thing IRL, called antenna arrays).įrom what I'm reading about Comnet Consteallations, I don't think the feature is as necessary with RemoteTech because of the directional antennas. What isn't realistic is having dish antennas behave as omnidirectional, having your antennas more powerful because you upgraded the ground station, and having "partial control" (seriously? What is this, analog computing? It's all or none, it either gets a actionable message or it doesn't.). Just to add, what I mean by little reality, of course it has antenna communications and signal occlusion, that is realistic. That makes the whole thing insanely confusing (at least for me who has a small amount professional experience working with real radio systems, I suppose results may vary).Īs for your mods, I have no experience with any of those so I can't really provide a good opinion either way there. Yes, it works, but it is a completely made up rule set based on little reality. This is where ComNet fails, RemoteTech is an abstracted form of real communications while ComNet is fiction. ![]() I hate to cry "realism" but a certain degree of realism can help with understanding of a concept. Returns True if vessel has local control (and thus not requiring a RemoteTech connection).I prefer RemoteTech because quite frankly, it makes sense so it's easy to understand. RTAddon: HASLOCALCONTROL (vessel ) ¶ Parameters: Returns True if vessel has connection to KSC. RTAddon: HASKSCCONNECTION (vessel ) ¶ Parameters: Returns True if vessel has any connection (including to local command posts). RTAddon: HASCONNECTION (vessel ) ¶ Parameters: Returns True if part has any connection (including to local command posts). RTAddon: ANTENNAHASCONNECTION (part ) ¶ Parameters: Returns delay in seconds from KSC to vessel. RTAddon: KSCDELAY (vessel ) ¶ Parameters: Returns shortest possible delay for vessel (Will be less than KSC delay if you have a local command post). It is better to use ADDONS:AVAILABLE("RT") first to discover if ![]() True if RT is installed and RT integration enabled. True if given Vessel has connection to KSC Get shortest possible delay to given Vessel It is better to use addons:available("IR") for this. Starting version 0.17 of kOS you can access structure RTAddon via ADDONS:RT. 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 New in version v1.0.2: kOS now supports access to connection informaion from a unified location. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |