SilverlightPony

@JayPee Protip: If you set the "Save as type" to plain text (.txt) when exporting CKAN's list, it skips all the machine-readable formatting and just gives you a straight (more easily) human-readable list.

Okay, new problem. Still on my 1.1.2 career, ASS v1.1.3, KK Utilities v1.3.8. I turned ASS off a while back (I had a good reason at the time, I just can't remember what it was), and now I can neither turn it back on nor bring up the settings window. Any ideas short of just reinstalling the mod?

This, basically. If you want better-looking plumes without the spreading, try HotRockets.

Um...1.0 (actually 1.0.5) was a while back. They just released 1.2 a few days ago.

I fixed it. Had to roll back SmokeScreen to 2.6.17; apparently 2.6.18 isn't fully compatible with 1.1.2.

What's the latest version that should work with 1.1.2? CKAN is saying "2v10.5.1" (which I'm guessing is 0.10.5 in the changelog), but the changelog doesn't mention specific KSP versions until 0.11 for KSP 1.2.

The only dependencies listed are Module Manager and SmokeScreen, which (along with RealPlume) are all installed via CKAN. Like I said, I even tried removing and reinstalling them. After making that post, I noticed that I was getting some rather small particle effects on the SPS engine for my Munar service module (KW Rocketry Service Module Propulsion System), but again, no noticeable particles from the lander's engine (LV-900 Beagle). I originally noticed the lack of particles on my main heavy lifter, which uses five RE-D7 Bollards and four Mk55 Thuds; this did not change with the reinstall.

Are there any known bugs or conflicts with other visual mods that would prevent the rocket plume from appearing entirely? I was quite enjoying RealPlume, but recently when I fire a rocket, it produces no particle effects whatsoever. (The launch pad still spits out a little smoke from the flame trenches, but very little) The only change I made that I think might be relevant is that I installed a couple of visual mods, like Scatterer and Realistic Atmospheres. I already uninstalled Scatterer, and uninstalled/reinstalled RealPlume and SmokeScreen, but the problem persists. Any ideas? [EDIT] Almost forgot, screenshot of engine burning with no particle effects:

May I ask your reason for not supporting CKAN? (I'm just curious.)

In that case, I think CKAN metadata may need to be updated; it lists CXA v 1.1 as the last version that works with 1.1.2.

I had the docking problem as well. Station with nothing but APAS(passive), fuel tanker with APAS(active), tried both MJ docking autopilot and manual docking; would not lock, just kept bouncing off. KSP 1.1.2.

Done and done.

Would the files you need be in the 1.1.2 game download? 'Cause I have the original .ZIP file straight from the KSP site saved. (I also have the .ZIP for 1.1.3, if you want it.)

Quick question: I'm guessing this version is not back-compatible with KSP 1.1.2. Is that correct? If that's the case, how would one go about backporting this-- ---to the 1.1.2 version of RT? Most of my comsats have 4 omnis for mass distribution reasons, and I'd like to get some kind of signal benefit from that without quadrupling the range of them.

Bishop's problem is on 1.1.3, not 1.2.

I've got a comsat on its way to Duna that I want to rename. However, I cannot right-click on the probe core to do so. I can still right-click on other parts of the same craft, just not the probe core. Testing other comsats shows the same problem with the ones headed for Moho and Eve, but not one in orbit of the Mun. I'm using RemoteTech, but all 3 comsats with the problem have active connections, and I can still control their attitude and throttle, so it's not a signal or EC problem. I'm playing on 1.1.2, so I can't rename them from the Tracking Station or map view (due to this bug, which was apparently fixed in 1.1.3). Is there any other way to rename the vessel (aside from editing the save file; I'm not that desperate)? Or any fix/workaround that will restore my ability to right-click on the probe core?

Bug encountered! Installing via CKAN. Core mod, stockalike config, and inner stock system data installed fine. When I check the box for "outer stock system data", CKAN throws an unhandled exception error, saying "Cannot install <insert random already-installed mod here>". I tried removing the first mod the error mentioned from CKAN and reinstalling that mod manually, but the error just changed to mentioning a different mod. Additionally, the mod mentioned in the error no longer shows up in CKAN's list when the filter mode is set to "compatible" (it will show up, still checked, with the filter set to "installed" or "all"). I'm on KSP v1.1.2. Detailed error output (from the "more info" part of the error window): See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** CKAN.ModuleNotFoundKraken: Cannot install KerbalSpacePonies, module not available at CKAN.CkanModule.FromIDandVersion(IRegistryQuerier registry, String mod, KspVersion ksp_version) at CKAN.RelationshipResolver.<RelationshipResolver>c__AnonStorey0.<>m__0(String name) at System.Linq.Enumerable.WhereSelectListIterator`2.MoveNext() at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection) at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source) at CKAN.RelationshipResolver..ctor(IEnumerable`1 module_names, RelationshipResolverOptions options, IRegistryQuerier registry, KspVersion kspversion) at CKAN.MainModList.ComputeConflictsFromModList(IRegistryQuerier registry, IEnumerable`1 change_set, KspVersion ksp_version) at CKAN.Main.<UpdateChangeSetAndConflicts>c__async1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at CKAN.Main.<ModList_CellValueChanged>c__async0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_0(Object state) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.6.1586.0 built by: NETFXREL2 CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll ---------------------------------------- ckan Assembly Version: 0.0.0.0 Win32 Version: 0.0.0.0 CodeBase: file:///f:/Users/silve/KSP%20Mods/ckan.exe ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.6.1586.0 built by: NETFXREL2 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.6.1586.0 built by: NETFXREL2 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.6.1586.0 built by: NETFXREL2 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.6.1586.0 built by: NETFXREL2 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.6.1586.0 built by: NETFXREL2 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.6.1586.0 built by: NETFXREL2 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Transactions Assembly Version: 4.0.0.0 Win32 Version: 4.6.1586.0 built by: NETFXREL2 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll ---------------------------------------- Microsoft.GeneratedCode Assembly Version: 1.0.0.0 Win32 Version: 4.6.1586.0 built by: NETFXREL2 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Numerics Assembly Version: 4.0.0.0 Win32 Version: 4.6.1586.0 built by: NETFXREL2 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll ---------------------------------------- System.Runtime.Serialization Assembly Version: 4.0.0.0 Win32 Version: 4.6.1586.0 built by: NETFXREL2 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll ---------------------------------------- System.Xml.Linq Assembly Version: 4.0.0.0 Win32 Version: 4.6.1586.0 built by: NETFXREL2 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll ---------------------------------------- System.Data Assembly Version: 4.0.0.0 Win32 Version: 4.6.1586.0 built by: NETFXREL2 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll ---------------------------------------- Anonymously Hosted DynamicMethods Assembly Assembly Version: 0.0.0.0 Win32 Version: 4.6.1586.0 built by: NETFXREL2 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/mscorlib/v4.0_4.0.0.0__b77a5c561934e089/mscorlib.dll ---------------------------------------- Microsoft.CSharp Assembly Version: 4.0.0.0 Win32 Version: 4.6.1586.0 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.CSharp/v4.0_4.0.0.0__b03f5f7f11d50a3a/Microsoft.CSharp.dll ---------------------------------------- System.Dynamic Assembly Version: 4.0.0.0 Win32 Version: 4.6.1586.0 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Dynamic/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Dynamic.dll ---------------------------------------- System.EnterpriseServices Assembly Version: 4.0.0.0 Win32 Version: 4.6.1586.0 built by: NETFXREL2 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll ---------------------------------------- Accessibility Assembly Version: 4.0.0.0 Win32 Version: 4.6.1586.0 built by: NETFXREL2 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.

Supposedly (I haven't looked for it myself yet), current RT has a "current vessel" option in the target menu; selecting this will cause the dish in question to always point at whatever vessel you happen to be controlling, including following you when you switch vessels.

It is in CKAN, but it will only show up if your copy of KSP is a version the mod is compatible with. Judging by the changelog in that mod's thread, it hasn't been updated to 1.1.3 yet, so if you're using 1.1.3, you won't see it. (Mods not being updated yet is the reason my main career game is still on 1.1.2.)

It's in the in-game RT settings menu, on one of the other tabs.

AFAIK it only triggers the experiment. You still have to store/transmit/discard the results manually.

@Suedocode That would be less realistic, and some people want more realism in how things work, but there's nothing inherently wrong with either opinion. Ideally, there would be an option in the settings as to which type of functionality you want to use.

I think the only way to do what you want is to set the fairing "decouplers" staging icon in a stage that happens to trigger either high in the atmosphere or above it entirely, but before the circularization burn. In my experience (using FAR), it's usually safe to deploy the fairings once you're above 50km altitude.

It's not about transmit/receive; in RT, dish antennas can only point in one direction, whereas dipole antennas (like the Communotron 16 and 32) are omnidirectional, but any antenna (or more accurately, pair of antennas on a single craft) can be used to relay a signal. With 1.2's ComNet, you've got normal antennas that are equipped on a probe you want to control, and specific "relay" antennas that can relay a command signal to another probe.

Agreed--and I prefer the RT implementation.