crooks4hire

Happens to me too. I've tried pushing the envelope using single engines. They heat up quickly, but they tend to hover just on the brink of exploding; never crossing the threshold...

As far as copyrights are concerned, it is illegal to copy the work for redistribution. To my understanding, it is not illegal to derive a mod from ISAMapSat (the idea, not the source code). Just because Innsewerants developed the first mapping mod for KSP doesn't mean another modder can't develop his own mapping mod...

Just to clarify, B9 is on the latest KSP Weekly apologizing for missing the last one. (8/13)

Been playtesting for a week and a half. The anticipation of RT2's release is already rustling my jimmies...

mike88cab, Bac9 works for SQUAD now if you didn't know. He's the one that updated the space center buildings.

Any news on if/when the S3's hypersonic mode is coming back?

Does R4.4 fix the animation issues with the large panels?

I just started playtesting RT2 and I haven't had time to explore it much (currently at work x.x). I believe I read this earlier but can't find it... Do the stock probe cores count as spu's?

A thousand times this. Lol. The DCPU is going to add a whole new level of probe-immersion. You won't have to sit and wait for your probe to come back into communication to do stuff. You could write entire missions while it's on the other side of the Mun!!

One more question lol. Is IR included in the Magic Smoke docking washer download or do I need to download it separately from github?

Will IR play nicely with DROMOMAN?

Derp, I'm sorry. Lazy and didn't read back very far... Don't get me wrong though, I'm not picking on anybody. I just think the negative reaction to the DCPU was a bit of kneejerk panic.

It kinda seems like people fussing about the programming and time-delay features are misinterpreting this mod. RemoteTech is intended to add some realism to unmanned missions. The biggest realistic issue with an unmanned mission is the delay between command inputs and probe execution and overcoming this issue via communications arrays/relays. You're not going to be required to rewrite an operating system to get your rover to drive the next few kilometers. The programming that some people fear could be as simple as: send.throttle_up25.pro.10000; which, in probe-language means increase throttle to 25%, point attitude prograde, hold for 10sec(10,000ms), shutdown I doubt very highly you will require any prior knowledge of coding to manage RT2 programming. As for sending a manned mission to complete an unmanned mission (ie: we'll need kerbals in Low-Duna orbit to manage rovers on the surface effectively). This is simply to decrease the time-delay effect. If you think you can't manage to control a Duna surface rover from Kerbin, send some kerbals closer to bridge the time-gap. It's not required. It's just more convenient...

[strikethrough]Dunno what the problem is. Fresh install of R3.3 on a fresh .21 save and all of my control surfaces freak out...[/strikethrough] I think I may have just been overdoing it with control surfaces lol. Was using the largest ones on a very small .craft. I downsized and it's running like a dream.

I read back a few pages and couldn't see anything about it. Is the SAS updated or not? Mine still flaps about like crazy...