Cilph

Release 1.2.1: Removed kOS integration; Many thanks to the lovely folks on 4chan who'd rather bitch and whine than file helpful bug reports. The extension DLL was causing Kethane and possibly other mods not to work and for some reason wouldn't even properly load half the time for arcane reasons involving dll load order, versions and time of day. As for the syntax error thing in kOS. Beats me. I edited steering bindings, added two commands, and edited ImmediateMode a bit. If you could pass me your script I can use it for debugging. Here's a screenshot to fix your / my mood.

Argh, the kOS integration seems to be fiddly with other mods. If you have issues like Kethane maps disappearing, delete the kOSExtension dll even if you do not have kOS. Scrapping kOS support till this is fixed.

Unrelated to RemoteTech. Sorry. None of my part modules use constant fields.

I did not change anything save wise between 1.1 and 1.2 :x.

I see no reason for it to be incompatible, so take it up with the SCANsat author.

Ahem..........

It was a pretty minor one too. Seems like the antenna configuration window throws an exception during vessel switching because RemoteTech's core got renewed and deleted as well. The window was trying to properly unregister itself with the core, but since it no longer existed... I wish Scott had been nice and sent me a bug report though. It would've been easier to fix that way. No communication whatsoever even though I sent him messages :/.

Well, I found the bug that glitched out Scott Manley's game in one of his interstellar videos, so I decided to put up 1.2.0. Have fun and don't kill me if anything goes wrong. Release 1.2.0: Fixed (probably) the bug that humiliated me in one of Scott Manley's videos; Flight Computer and kOS integration! (details below); Requires patched dll for now! Fixed Delta-V burns; Cilph can't do basic vector math late at night; "N/A" on TimeQuadrant when no SPU is available; "Connected" when signal delay is disabled; Allow docking node targeting when the other vessel is disconnected; Halved antenna power consumption; Signal Delay is now on by default; Quick hack to not cache lines/cones that are disabled to increase performance for some; Possible fix for long range planet targeting being twitchy; Two new dish parts by Kommit! The KR-7 and KR-14 replace the SS-5 and LL-5 respectively. The old parts will be deprecated but still included so as not to break existing crafts; Settings File is now properly created on load. kOS integration: All immediate mode actions now require signal delay to pass; Steering locks now work when the vessel is disconnected; Action groups no longer trigger when kOS has them blocked; "BATCH" and "DEPLOY" commands to send a list of commands as one packet; Flight Computer: Works pretty much like MechJeb's SmartASS; Use "Enter" to confirm changes in most text fields; Duration format: "12h34m45s" or "12345" for plain seconds; Delta-V burn format: "1234m/s"; Cancel commands by clicking on the X in the queue, sends signal ASAP, but delay still applies. Use the queue to view any delayed command; even right-click menu events.

It's included in the GameData folder. Drop that folder in place exactly as in the zip. If you have ModuleManager.dll in the GameData folder it should work as intended.

I'm guessing DerekL did not install MM correctly.

Connections refresh every few seconds, not milliseconds.

You mean the blinking connection issue on github? I have a potential fix prepared for that. Or what did you mean?

Assuming no configuration error: bug.

*bzzt* *beep* To report a bug please follow these steps: Document what is going wrong; Document what you expected to happen; Copy your KSP_Data/output_log.txt; Copy your persistence.sfs file describing the situation; Post all of the above to https://github.com/Cilph/RemoteTech2/issues?state=open Sign a contract promising me your first-born if the error is determined to be the user's fault. You have received this automated response because you were unable to read basic instructions. Please refrain from triggering the automated response system any further. Attachment: User Message. User Message: Bug known but never reported on the tracker, so I just forgot. This is why you report your bugs.

Problem Exists Between Probe/Keyboard And Chair, Layer 8, ID-Ten-T. Same thing.

If someone is up for writing proper documentation, let me know. People are whining "installation instructions aren't clear", or "my science stopped working!". As the main dev and non-native speaker I just don't have the right point of view to write such a thing.

Presenting the KR-7 and KR-14 dishes made by kommit. Will replace the SS-5 / LL-5. (Existing crafts are fine.) PS. KR stands for Kommit Rules.

*bzzt* *beep* To report a bug please follow these steps: Document what is going wrong; Document what you expected to happen; Copy your KSP_Data/output_log.txt; Copy your persistence.sfs file describing the situation; Post all of the above to https://github.com/Cilph/RemoteTech2/issues?state=open Sign a contract promising me your first-born if the error is determined to be the user's fault. You have received this automated response because you were unable to read basic instructions. Please refrain from triggering the automated response system any further.

If you can't produce a persistence file, just send me that KSP_Data/output_log.txt of a game session where the error occurred. I've had people send me irrelevant logs of vanilla KSP for no reason...

+ KSP_Data/output_log.txt + persistence.sfs.

Possibly. I noticed it was the only place where I still used single precision. Although the angle calculation was always in double precision. Fixed it and maybe it'll solve the issue.

Known issue: https://github.com/Cilph/RemoteTech2/issues/122 I have no idea what is causing it yet or if it is even a bug and not user error. Looking at it after I do kOS.

That's definitely what that button does. Though, cones only show when targeting planets.

Can we please start using the bug tracker and uploading KSP_Data/output_log.txt plus persistence.sfs file WITHOUT me having to ask. Thank you? Anyhow, there should be no place where I am checking what SoI a satellite is in, the problem must be unrelated to the SoI.

There's an official release thread and zip on spaceport. Weee.