Maelstrom Vortex

Is there a way we can make auto-strutting on docked ships more stable so auto-strutting becomes more useful? Like maybe have it keep some form of internal record of the boundaries between docked craft and only allow strut linking to parts internal to that segment of the total craft? It should hopefully radically reduce auto-krackens and make auto-strut more useful. This post contains an example of said instability:

I have a craft that's spontaneously destroying itself on load. It appears to load normal at first, then suddenly reorients itself and shatters. Any ideas? Tried removing Krebal Joint Reinformcement, no difference.. so I think it's something else, but have no idea where to begin. Logging is spammed so hard it wasn't very useful. Link to log file: http://order.synology.me/KSP.log Starts about: [LOG 03:19:47.792] Unpacking Minmus Orbital Lab From what I can tell. Appears error errupts here causing debris creation: [ERR 03:20:13.969] A joint can't connect the body to itself. Looking like an auto-strut kracken, wonder if turning off advanced tweakables will fix or if it's too late.

I can get that at a about a 5 meter scale. However, Not only do you get 50 times the energy, you also get the heat that goes with it, as I said, if you change scales there is some adjusting to do.

I do not have any screenshots currently of that particular config as I remedy it between alterations, but essentially reactor output in KSPIE mode is 50x that of USI-NF compatible mode. Reactors that normally give giga-watts are capped at megawatts. Easy to see on ones own, just cut the file from the patch directory, post to desktop, reload game, look at a reactor's output.. then put back in.

Long time experience tip: Near future likes to restrict power levels on the KSPIE power scales. If you want to play with NF with the power scales on KSPIE scales, you can kill the NF/USI patch but have to watch for the effect the changes cause to the function of the equipment given the scale is about 50 fold difference.

The satellites had drifted some, but it still determined that it was better to go to mun than to a slightly off facing satellite.. was that the issue you found? Once I corrected the positioning of the satellites they appeared to pick normal priority.

You already did that. I've set them each time using it. But for some weird reasons each time I've patched IE, it changes the wavelength back to microwave on two sats. I'm going to see if just swapping them may help. Maybe some sort of save error? Not sure. Strangest part is, other sats, exact same model, not same behavior.

Every time I update interstellar, my satellites using the phased array bulbs are converting to w-band microwave on their own and having to manually be set back. Nevermind, it appears just to be the one, think I may replace it, may be bugged or something. Nevermind that nevermind, found a second one doing the same thing and it won't let me correct it!

Something seems wrong after the patch: I have several large apperature satellites including a polar, what's going on here? The aperatures on the relays were calculated to receive and relay full power to a 3 m spot size prior to patch they were working as intended with craft getting full 3 gigwatts. Power station was checked, it was also full 3 Gigawatt to wall to beam. Also got some odd messages about tweakscale ui prior to game load, not sure if that may be affecting existing apperatures. ... I just noticed it looks like it is favoring bouncing from Mun back to the satellites around Kerbin for.. some.. reason? *headscratch*

That's cool if that is what was intended! However, is it realistic? That's my goal. If it's truly impossible to get energy down to the surface of such a world then sticking to reactors just seems like a technical challenge. But now that I think about it.. if sunlight can get down there.. surely IR can.

Fairly certain it was a very large antennae, 100 m. I was using LR Infrared, hooked to tri-alpha.. lost contact around 30,000 meters. This was a long time ago though, it is possible changes have been made since then. W-Band Microwave has the best shot?

Wanted to ask if it's possible to penetrate Eve's atmosphere with beamed power to the surface on any band? I've tried and it seems like it just isn't doable, meaning reactor required on ground with ground broadcast station for any local beamed power and I've put some serious power into it. Like at a certain altitude it goes to 100% loss no matter the band or power input.

Yeah, i got that as well. Patch actually made it worse as recommended by a prior user. To the point it would not load. Makes me wish I could simply disable its logging. The patch appears to have destroyed my save file. Further research has validated a conflict between this version of transfer window planner and Koppernicus. Regrettable. This is likely the cause of the above poster's NRE's also. Reverted to old twp Verified patch is actually safe and effective.. highly recommend. Purely TWP causing the issues on my end.

I hope we get a patch for the relays soon, really holding me up over here.

In line phased array appears not to be relaying in relay mode. Registers receipt from reactor, but no other objects register it. Spot size is well more than required to be seen by the other objects and a smaller similar design sat using the regular phased array with a smaller relay aperture was detected. Verified wavelengths are all set correctly at the same long IR setting. Made many geosats like this before, first time one was not seen at all by other vessels with relay active.

Were the exploding thermals in 1.5 fixed? If so I may be updating soon to bring my campaign up to speed.

I pulled off the nerve wracking just in the nick of being short of fuel:

I think that's my problem.. 7 GW worth of cooling.. and stock heat still detonates.

To emphasize, this appears to be a stock heat issue. Disregard if that's what you mean. The waste heat levels barely get touched before the engine explodes. It appears all the graphene ones and even the tangential attachable grill radiators designed to use airflow are not appearing to take on or reduce stock heat at any significant rate. See 55 minute mark. This happens with all thermal engine designs at different rates. For your assistance FT: There is a point in there I get up the KSPIE views while the engines are revving. Thermal receiver barely takes on any power before detonating.

Pretty much every thermal engine I hook up to my mk3 receiver is detonating on formerly functional craft. Even using compressed air. Don't even have to give it a lot of power, just a few hundred kilonewtons and BOOM. Added precoolers, still boom. Added titanium heat vectors, still boom. Rolling back to prior version. Might I suggest if we're going to use stock heat radiation that it apply to all radiators as well so that all radiators are stock radiators. Heat is heat.

My thanks FT. Hey, did the power adjustment affect all the reactors? Or was that the bug? It seems all my reactors have dropped output some, but maybe that was just where one of them ran out of fuel.

Why would it not find the correct interface? They are directly connected and this craft worked pre-patch. I completely removed and refitted both the engine and the thermal receiver in an attempt to resolve the issue with no change. Beyond that, why won't the nozzle find the fuels now? Beyond that, this is occurring with every craft in this configuration that has worked previously. I have poured through the patch notes trying to something which would cause this behavior and not found anything mentioned that seemed related. The Receiver and the Engine are at default sizes. The fixed update with file unknown error messages are interface related? Is this something that will need patched? No matter how I connect, disconnect, or reconnect these parts, the error you have mentioned has recurred rendering them unusable. How would I correct this? Does anyone know what is happening with this? I'm pretty desperate to fix it so I can update. Rolling back to last known functional good config, 1.19.4 for now. Revert to 1.19.4 successful, function of parts restored.

Last like 30 something minutes was me trying to get a formerly working craft in .4 flying. The only engine failing was the thermal.It did not recognize the compressed air on board. It appeared to not be recognizing ISF fuel types, or even stock fuel types at all.

I've had this happen repeatedly on stream. Also.. since .9 I have not been able to get my thermal ramjets to work. They do not recognize the fuel payloads on board and cannot seem to locate a thermal source on board the craft even when directly connect. You can see my last KSP stream near the end for example. I even purged the warp plugin directory and reinstalled, still occurs. They appear to be refusing to recognize anything but LH2 as an input.

As of the last patch my thermal rockets seem suddenly broken and one keeps constantly firing and giving a missing asset / null reference message.