Cilph

Yessir I do.

No worries, I run Linux all the time so the case-sensitivity is baked into my head. Enjoy the bugs. I'm still busy fixing the bug reports I get sent .

I dont see why other mods require Windows....? I don't think I do. I haven't run it on Linux but I don't see why it wouldn't work. Oh, and I don't do an open beta because (sorry) some individuals are idiots and can't read instructions.

I'd like for five people to test RT2 for two/three days before I put out any releases. If there are volunteers, please send me a PM. Please be a competent individual with programming or testing experience. EDIT: Sent to NathanKell, acc, MedievalNerd, TaranisElsu and Vrana .

Signal Delay is implemented, it's just switched off until I finish the flight computer in a future release. That will probably come with kOS integration out of the box. Career stuff! http://i.imgur.com/OkwRzka.png Communotron 16 (2.5Mm) Start Communotron 32 (5Mm) Large Electrics Reflectron DP-10 (500k) Flight Control CommTech EXP-VR1 (3Mm) Specialized Electrics Communotron DTS-M1 (50MM) Science Tech Communotron 88-88 (600Mm) Electronics Reflectron SS-5 (90Mm) Electrics Reflectron LL-5 (450Mm) Large Electrics Reflectron GX-128 (4Gm) Adv Science Tech CommTech XYZ (3.5Gm) Specialized Electrics Antenna omni range in off mode reduced to zero. To compensate ProbeCoreOcto, CoreCube, StackSmall, StackLarge will receive an integrated 3km antenna at no cost. None for the Sphere, Hex or FlatOcto Antennas will receive a passive SPU to allow for participation in routing and science transmission on manned pre-probe vehicles. (TODO) COMMENTS?

We're getting so close that I'm nervously looking for more stuff to do :/.

Current todo list: Planet targeting (Testing) Enforce antenna configuration conditions (Testing) EVA configuration / override (Testing) (Done) Max Q (Minimal, breaks part right off the vessel instead of splintering ) Drawing active connection line in both Flight and Tracking Station Gear/Lights/Brakes UI override Passive SPU Debug dump unit Settings Career Mode Integrated antennas on high-end probes Remaining Bugs on Github If there's nothing to add to the list, I'll put out a Release Candidate. If no new bugs are found for a week, and all major bugs are fixed, I'll mark it stable.

public Vector3 Position { get { return FlightGlobals.Bodies[1].GetWorldSurfacePosition(-0.1313315, -74.59484, 75.0151197366649); } } It uses latitude, longitude and sea-level altitude, so you're set.

Planet radii aren't hardcoded. Mission control uses polar coordinates and line of sight takes the planet's radius as defined on the CelestialBody itself. AFAIK RT1 did the same thing.

Yeah, I'll put them in the tech tree based on their ranges, but not awfully late or anything. You should be able to head for Jool without a complete tree.

Sorry, I'm really not considering any other range models for now. It's meant to be easier to use for a larger userbase. As for point two, you may always fork it. I'll stress that I am not considering any other range models for the first release. Luckily different range models involve a single function in the NetworkManager class. Power consumption is based on the area it covers, so that scales quadratically which is like real life. If you want to base it on the volume of coverage, you're going to see it climb even steeper. You're also not meant to bridge an entire SoI with just omni antennas. Dishes are meant to do that. Omni antennas are for crafts on land or LKO. My preferred way is to set up a static relay network using dishes, and then use omni antennas on any craft that goes near them. I've halved the ranges on the omni's. Let me know if that is okay.

Fixed that. Didn't know that required a separate permission.

Dish Balancing: https://docs.google.com/spreadsheet/ccc?key=0AuCB6Oku9wiAdHlYc0prMFlTeGZ2TFRvTVNGTjlVUlE&usp=sharing Feel free to leave comments directly on that.

That's the point of the dipole antennas or non-folding dishes.

Signal Delay / Control blocking is back in with a few minor bugs that need fixing. I might add the attitude control flight computer back in and release with signal delay after all. You can still target individual satellites without this cone.

Theoretically, perfectly possible. You just slap an animation-less ModuleRTAntenna on a probe body. I won't be doing that in the mod though. However I will be adding them to launch clamps. The small RT1 dipole will make a return and you can easily put that on a probe body.

But I'm going to be using the simple RT1 range system for now...The cone of vision thing only applies to the lazy planet targeting.

Don't push me. Just go play 0.22 without RemoteTech :/

I'll put that one back in.

1. Too complicated for mental calculations. If I wanted to do it right I'd just use a gain system. The old RT1 system was simple. In a future I might switch over to a system of gains and minimum signal/noise ratios. 2.I didn't really like most of the AIES parts we had for RT2. They're nice but I prefer to stick to the stock look. That's also why it's less of a menu-fest and tries to fit in more with the standard UI. If someone can make me stock looking antennas, I will gladly include them. Which antenna are you referring to? Remember that since RT2 was never released I have no obligation to support it. Stock parts will always be supported.

A few other things: Range: Old-RT1 style. 10km distance means both antennas require minimum 10km range. Simple. Dishes: Dishes can target planets and this will turn the link into a "cone of vision" using a dish angle that will be balanced at 2 kerbin diameters at max range. Parts: I intend to mod the stock parts as well as include a few of the RT1 parts, and maybe a small AIES part. Science: Science can now only be transmitted across antennas that are a part of a connection to KSC. No cheating by using a low-cost omni while a high power dish maintains the connection. Implementation might be a bit buggy as of now, but we'll fix that in testing. Quick TODO: User interface, adding planet targeting back in, adding control block / delay framework.

https://github.com/Cilph/RemoteTech2/tree/lite Quick TODO: Redo pathfinding to be 'network interface'-based, sort out science, add configuration UI, add in control blocking / delay framework.

Speaking of core functionality, I'll have to modify some core bits. I want the science routing to only work on the antenna that is maintaining the actual connection. Currently connections are just straight edges from satellite to satellite, taking the Max() of Omnidirectionals plus individual targeting for the dishes. However I need to change this into interface-based routing, where the incoming/outgoing antennas are collected as well. Just giving a heads up on what I'll probably be working on tomorrow. I've written up a new ModuleDataTransmitter that replaces the stock one for easier modding. Squad forgot to actually use their CanTransmit() functions so I will have to come up with a way to add/remove the partmodules as a connection is established. Probably a notification event when routing involving the antenna gets updated.

I decided to go with requiring a direct feed to KSC for science transmissions. No storing on space stations for now. Kerbals haven't invented multi-Mit harddrives suitable for space yet. Maybe they will eventually. I think we found a nice tech tree addition.

@NeoSky: Some day, maybe. I can't simulate energy consumption in unloaded vessels and this is a very complicated system even without that. How do we handle science transmission on manned capsules? Currently, satellites are only recognised as such when they have a signal processor onboard, which manned capsules currently do not have. Without being marked a satellite and having the equivalent of a signal processor, it can not participate in routing. This would disallow transmitting in early game without the Stayputnik. Proposal #1: Add a passive signal processor to antennas that allow them to become a satellite, take part in routing, and send data, but only when it is the active vessel and otherwise controllable. Proposal #2: Move the Stayputnik to Basic Rocketry and require a probe for science transmissions. Proposal #3: Move antennas to Stayputnik tier or later.