Astraph

March 20

35 minutes ago, Ker Ball One said:

Looks like a known issue

Yeah, I am fully aware of this note, but the mod compatibility page has not been updated since 2022 (at least if I can read GitHub's GUI correctly - I always have issues with that) and it references IE version 1.22.1, while according to CKAN we now have 1.29.6... So I was hoping that maybe, somehow those compatibility issues got worked out one way or another, as both mods are very popular and I find it hard to believe I'm the only one who'd love to get them combined in their build... ^^'

March 19

2 hours ago, Ker Ball One said:

@Astraph I'm trying to reproduce your conditions. I've installed Kerbal atomics and have a simple remote guidance probe core, with those same solar panels and a nuclear engine. The solar panels do seem to work when unloaded. But not seeing power from the RTG on the nuclear engine.

What is the exact part name for your nuclear engine? Have you tested without any SCANsat parts? You should be able to test on the launchpad. Also, can you upload a list of all your mods.

I guess the list of all mods is the point where anyone working on Kerbalism will bonk my head and say they're not even touching it, but welp, 'ere we go:

https://imgur.com/a/MJ5Khqb

The exact name of the engine I'm using is CANDLE Travelling Wave Reactor Engine from Interstellar Extended. I completely forgot IE comes with its own set of stand-along nuclear engines, not just nozzles you need to attach to a Thermal Generator... I apologize for confusion here.

Since I'm also running KTC, launchpad tests would be a hassle, with all the rollout/editing times... I fully admit I might've borked myself with my modding, but after all those years (and KSP2 being the thing I don't wanna talk about) I really wanted a KSP run that'd give a big system for exploration, realistic mechanics and interstellar lategame... So JNSQ, Kerbalism and KSP Interstellar sounded like a way to go.

I do realize the devs explicitly said IS might not be fully compatible with Kerbalism, but I'm not sure if there's another mod that adds such nice beam power system and complex ISRU.

March 19

Yeah, this ship has an RTG nuclear engine from (IIRC) Kerbal Atomics - it should be producing some miniscule amount power, so I was not surprised by the "converter" thing - I assumed it's just it's electric output.

March 19

I'm encountering an issue with my ScanSat satellite.

I made a simple ScanSat thingy with 3 scanners and 3 OX-10L solar panels. In both VAB and in-flight, they work fine; a solar panel produces ~7.7 EC/s, while the scanners combined consume around 4.3 EC/s:

Yet as soon as I switch away from the satellite, it starts running out of EC real fast, regardless of whether it's in shadow or full sunlight. As soon as I switch back to the probe it all starts working again, but it obviously kinda screws up my scanning operation (which I wanna do in the background while I do stuff with other craft) and ruins the point of running any cryogenics (as my fuel boils off real fast)...

Looking at the readout in Tracking Center, it seems that the game simply forgets the panels are there in the first place:

Is this some unsolveable compatibility issue, or is thare any workaround it?

EDIT: Welp, it seems OX-10Ls are stock panels, so dunno if that's even a compatibility issue... I'm honestly at a loss here.
EDIT2: I do admit I'm running a hefty package of mods, but I don't think any parts included here (other than maybe JNSQ planet pack, which is listed as compatible) would be at play here...

January 31

One question about training - what is the best way to train Kerbals for longer missions? I am prepping an Eve mission, wanted to first make a 200-days long high Kerbin orbit mission for the crew to gain experience... But due to health issues, I had to deorbit after just 30, with the crew barely getting 6% training.

I tried using the KSC training option, but I find it confusing to track how long does the training take, what is the current progress and how long do I have to wait before I can launch the mission... Plus sometimes it seems that Kerbals just stop their training midway and I have to hop into VAB and start the whole thing anew...

January 23

23 hours ago, garwel said:

And here is the hot fix:

Kerbal Health 1.6.8

Fixed freezes on some radstorms (the problem was due to an error in handling numeric strings)

Download here

Just checked, it works! Thanks a lot!!!

January 21

I've run into a problem with Radiation Storms in my (admittedly, very heavily modded) game.

Basically, when a RadStorm happens, my game gets essentially bricked - I am unable to launch new ships, switch scenes, pretty much anything. I am able to open various windows and enter Research Centre, but Flight Tracking, VAB/SPH or even quitting the game are out of the question.

That's what I get from the Console - I sadly have absolutely no coding experience, so I can't make any heads or tails outta it other than "something's wrong with the RadStorm".

Looking at the log, the exact report seems to be:

Spoiler

[LOG 20:43:11.413] [KerbalHealth] Radstorm 0 hits Kerbin with magnitude of 2495202.53416848 (2495202.53416848 before modifiers).
[EXC 20:43:11.415] IndexOutOfRangeException: Index was outside the bounds of the array.
   KerbalHealth.Core.PrefixFormat (System.Double value, System.Int32 digits, System.Boolean mandatorySign) (at <3e097026fbdf4d639c179ca8e6ef8031>:0)
   KerbalHealth.KerbalHealthScenario.UpdateKerbals (System.Boolean forced) (at <3e097026fbdf4d639c179ca8e6ef8031>:0)
   KerbalHealth.KerbalHealthScenario.FixedUpdate () (at <3e097026fbdf4d639c179ca8e6ef8031>:0)
   UnityEngine.DebugLogHandler:LogException(Exception, Object)
   ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object)
   UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object)

Is there any workaround for this? I tried waiting for 10 in-game days, but the error just kept repeating, and I can't really wait any longer (I have a ship in LKO that needs crew evacuated, I can't launch a shuttle because of this bug and in 11 days the first Kerbal will die to HP loss)...

If needed, I can provide the complete log. I guess I can always just remove Kerbal Health from this run, but I really wanted it to spice up my interplanetary missions...

September 11, 2022

7 hours ago, Lisias said:

In the hopes to reduce the scope of potential troublemakers, what were the latest add'ons you installed before getting this error?

Now that's a good question... I did the most reasonable thing ever and just went into CKAN, ticked GU, MKS, USI, GPP and a total of 120 mods, installed them and then booted up the game. The last ones I meddled with were MSI/USI and Firespitter,

I guess I could make a fresh install the proper way, going a few mods at a time and seeing when the error shows up. I have absolutely no coding experience whatsoever (apart from VBA, but I already learnt that it's not something I should mention around people doing actual coding), but from what you're writing I assume my case is some pretty werid one... So, as much as I feel bad to take so much of your time already, I also hope that at least something good comes out of it in the form for fixing some weird issue other people might have in the future ^^'

September 10, 2022

12 hours ago, Lisias said:

Later, I found many, many exceptions about Kopernicus but, frankly, knowing KSP as we know, I can't rule out Kopernicus being screwed by this first problem.

Well, weird new things usually demands weird new procedures. Let's eliminate some variables from this equation, being them

000_Harmony

000_KSPBurst

Remove these two folders and rerun KSP and send me the new KSP.log to see what we get. I think the real problem will happen again, but this time without someone in the middle borking while handling the bork and, so, we will get the problem being properly logged and can do something about.

Once we fix the problem, you can install them back.

By the Twin-Tailed Comet... I swear that this build was, for once, made only using CKAN, without manually adding anything (the only stuff I did was overriding CKAN's version compatibility to install USI and MKS - the app says they should be compatible with 1.12, so I didn't think this would cause any problems...)

Either way, I removed both folders (as in, manually moved them from GameData to an outside folder. Uninstalling them in CKAN would also uninstall Galaxies Unbound, FAR and a bunch of other mods - as you asked to remove only those two, I understood that would go against your testing plan. ^^'

Anyway, here's the new ksp.log: https://drive.google.com/file/d/1NmOIwTlX1SEK9lQ7MksriE6kpuuBRT15/view?usp=sharing

I'm very, very grateful for your time, I hope we can find the culprit... ^^'

September 9, 2022

2 hours ago, Lisias said:

ScrapYard is complaining that it needs Contract Configurator. The Add'On thread says Contract Configurator is only needed on KSP 1.12,x - don't have a clue about the reason CKAN din't installed it!

I think you need to talk to CKAN guys to sort it out to preventing getting hit by this problem next time you reinstall things!

Thanks a lot! And while Contract Configurator did solve that issue, I got a completely different one now... This time it also drops an error about Kopernicus, which I assume to be possibly related to the fact I installed Galaxies Unbound on top of GPP (which should be OK, from what I read in their thread) and GEP (which might not be)... ^^'

Ksp.log again -> https://drive.google.com/file/d/1NmOIwTlX1SEK9lQ7MksriE6kpuuBRT15/view?usp=sharing

This time I let the game load completely (I used the OK button from the error message and closed it mid-loading the previous time, maybe that's why it got cut off), so hopefully this log is going to be ok... Sorry about last time.

September 9, 2022

I decided to come back to KSP after a year... and I got hit with the missing .dll issue as well.

KSP.log -> https://drive.google.com/file/d/1NmOIwTlX1SEK9lQ7MksriE6kpuuBRT15/view?usp=sharing

This is a semi-fresh install (I removed all mods using CKAN, purged GameData of all files other than Squad folder and used CKAN to reinstall mods from cache), so I'm kinda surprised to see this happen... Especially since this is the first time I made build only with CKAN, without manually adding some other mods. I also see some other warnings in the loading screen, but to be absolutely frank, I always had at least some and my game never broke up... So I just decided to ignore them in the true Kerbal fashion ^^'

January 21, 2021

Hey there Just in case - is your star pack compatible with Sigma Dimensions? I seem to be getting some error messages on startup, but upon getting into a bunch of errors related to Dimensions... But upon startup, I don't see any issues - planets in Tracking Station look ok-ish and there seem to be no issues with how the atmospheres/surfaces are displayed...

Actually, just had another thought... How exactly are stars spaced in your pack? Are the distances real-life (so ~3.4 ly to Kiribani, etc), or are they compressed to KSP's regular 0.1x? I kinda want the increased challenge from the 3.5x scale system I usually use, but I also don't want to get truly 30 ly spacing between closest stars ^^'

November 15, 2020

Ok, so this is an issue that's really making my head spin.

I tried playing BH - every time I start the game up, all loads fine, all planets look the way they should, KSC works fine... But after 10-15 minutes, the game just randomly crashes. It doesn't just crash to desktop, I get the whole Unity crash reported thing turn on, mull something and then the whole game promptly closes. I've been trying to replicate this with several KSP builds, finally made a fresh install with only BH + Parallax + Kopernicus and the thing keeps happening - so at least I hope it got narrowed down to these three mods.

So, first of all, the log (please let me know if that's the right file - it's been a while since I last had issues and back in those ancient 1.7.3 times the file was still named output_log ^^'):
https://gofile.io/d/ndfitn

Second, system specs:

Windows 10 64 bit
i5-4460 @ 3.20 GHz
16 GB RAM
Radeon RX560 Series

Third, mod list:

KSP 1.10.1
Kopernicus Bleeding Edge Release 45
Beyond Home 1.5.2
Parallax 1.0.1

I initially suspected Discord (after every crash, Discord popped up a "New Audio Device Found" notification), but the crash appears regardless of me having Discord open or not. It usually happens when the game is tabbed away (I have two screens, so I often browse Reddit/chat/watch YT while playing), but it also happens when actually playing the game. I tried making a fresh KSP reinstall (as in, Uninstall on Steam + Ctrl-Del the game folder before reinstalling), updating GPU drivers and monitoring the PC during the crash (sadly I didn't use any specialist software, only Task Manager - but it didn't show any spike in GPU temperature / RAM usage around the moment the game crashes - temperature is stable at ~73 C, drops to 53 C one game crashes), so I excluded overheating or memory leak as potential reasons. One observation, possibly irrelevant but no harm in mentioning it - the game usually crashes when I'm scrolling or clicking on something, either in-game or when tabbed out.

I tried going through this thread and some other discussions, but I failed to find anyone having the same issue as I do, sadly...

August 23, 2020

Hey there

I appear to be encountering the same problem as one used two years ago - game startup freezes at loading Space Crane. I tried troubleshooting the issue the same way you advised back then (making sure GameData/ConfigurableContainers/TankTypes.cfg is present among the game files), but to no avail. I tried reinstalling GC and CC, as well as manual download - nothing helped.

There goes the output log:

Quote

[LOG 01:00:26.953] PartLoader: Compiling Part 'DockingCamKURS/Parts/OnboardCamera/OnboardCamera'
[ERR 01:00:26.967] Action 'DeployExperiment' already defined.

[ERR 01:00:26.967] Action 'ReviewDataEvent' already defined.

[ERR 01:00:26.976] Action 'DeployExperiment' already defined.

[ERR 01:00:26.976] Action 'ReviewDataEvent' already defined.

[LOG 01:00:26.984] PartLoader: Part 'DockingCamKURS/Parts/OnboardCamera/OnboardCamera' has no database record. Creating.
[ERR 01:00:26.986] Action 'DeployExperiment' already defined.

[ERR 01:00:26.986] Action 'ReviewDataEvent' already defined.

[LOG 01:00:26.989] DragCubeSystem: Creating drag cubes for part 'OnboardCamera'
[LOG 01:00:27.034] PartLoader: Compiling Part 'GroundConstruction/Parts/DIYKit/DIYKit/DIYKit'
[WRN 01:00:27.057] File 'G:\Gry\Kerbal Space Program - GPP 1.9.1\GameData\000_AT_Utils\Plugins\..\000_AT_Utils.user' does not exist
[LOG 01:00:27.059] [000_AT_Utils: 01:00:27.059 54661] Meshes to skip: Count: 2
[
flagtransform,
canopy
]
[LOG 01:00:27.059] [000_AT_Utils: 01:00:27.059 54661] Bad parts: Count: 5
[
RadialDrill,
MKS.Drill.02,
MKS.Drill.03,
dmFlexoTube,
UniversalDrill
]
[LOG 01:00:27.119] PartLoader: Part 'GroundConstruction/Parts/DIYKit/DIYKit/DIYKit' has no database record. Creating.
[LOG 01:00:27.129] DragCubeSystem: Creating drag cubes for part 'DIYKit'
[LOG 01:00:27.199] PartLoader: Compiling Part 'GroundConstruction/Parts/DIYKit/OrbitalKitContainer/OrbitalKitContainer2'
[LOG 01:00:27.237] PartLoader: Part 'GroundConstruction/Parts/DIYKit/OrbitalKitContainer/OrbitalKitContainer2' has no database record. Creating.
[LOG 01:00:27.250] DragCubeSystem: Creating drag cubes for part 'OrbitalKitContainer2'
[LOG 01:00:27.315] PartLoader: Compiling Part 'GroundConstruction/Parts/DIYKit/OrbitalKitContainer_old/OrbitalKitContainer'
[LOG 01:00:27.339] PartLoader: Part 'GroundConstruction/Parts/DIYKit/OrbitalKitContainer_old/OrbitalKitContainer' has no database record. Creating.
[LOG 01:00:27.354] DragCubeSystem: Creating drag cubes for part 'OrbitalKitContainer'
[LOG 01:00:27.427] PartLoader: Compiling Part 'GroundConstruction/Parts/MagneticFork/MagneticFork/MagneticFork'
[LOG 01:00:27.558] PartLoader: Part 'GroundConstruction/Parts/MagneticFork/MagneticFork/MagneticFork' has no database record. Creating.
[LOG 01:00:27.571] DragCubeSystem: Creating drag cubes for part 'MagneticFork'
[LOG 01:00:27.606] PartLoader: Compiling Part 'GroundConstruction/Parts/SpaceCrane/SpaceCrane/SpaceCrane'
[LOG 01:00:27.701] PartLoader: Part 'GroundConstruction/Parts/SpaceCrane/SpaceCrane/SpaceCrane' has no database record. Creating.
[LOG 01:00:27.716] DragCubeSystem: Creating drag cubes for part 'SpaceCrane'
[EXC 01:00:27.774] MissingMethodException: AT_Utils.UIBundle AT_Utils.UIBundle.Create(string)
   System.Reflection.MonoCMethod.InternalInvoke (System.Object obj, System.Object[] parameters) (at <ad04dee02e7e4a85a1299c7ee81c79f6>:0)
   Rethrow as TargetInvocationException: Exception has been thrown by the target of an invocation.
   System.Reflection.MonoCMethod.InternalInvoke (System.Object obj, System.Object[] parameters) (at <ad04dee02e7e4a85a1299c7ee81c79f6>:0)
   System.RuntimeType.CreateInstanceMono (System.Boolean nonPublic) (at <ad04dee02e7e4a85a1299c7ee81c79f6>:0)
   System.RuntimeType.CreateInstanceSlow (System.Boolean publicOnly, System.Boolean skipCheckThis, System.Boolean fillCache, System.Threading.StackCrawlMark& stackMark) (at <ad04dee02e7e4a85a1299c7ee81c79f6>:0)
   System.RuntimeType.CreateInstanceDefaultCtor (System.Boolean publicOnly, System.Boolean skipCheckThis, System.Boolean fillCache, System.Threading.StackCrawlMark& stackMark) (at <ad04dee02e7e4a85a1299c7ee81c79f6>:0)
   System.Activator.CreateInstance[T] () (at <ad04dee02e7e4a85a1299c7ee81c79f6>:0)
   AT_Utils.PluginGlobals`1[T].init_instance () (at <dfa2fbe96124462794ebeceb1d666cb2>:0)
   AT_Utils.PluginGlobals`1[T].Load () (at <dfa2fbe96124462794ebeceb1d666cb2>:0)
   AT_Utils.PluginGlobals`1[T].get_Instance () (at <dfa2fbe96124462794ebeceb1d666cb2>:0)
   ThrottleControlledAvionics.TCAScenario.get_HasTCA () (at <37e93c759a3a4d508f76af0cdd7738b7>:0)
   ThrottleControlledAvionics.TCAScenario.ModuleStatusString () (at <37e93c759a3a4d508f76af0cdd7738b7>:0)
   ThrottleControlledAvionics.ModuleTCA.GetPrimaryField () (at <37e93c759a3a4d508f76af0cdd7738b7>:0)
   PartLoader.CompilePartInfo (AvailablePart newPartInfo, Part part) (at <55ba45dc3a43403382024deac8dcd0be>:0)
   PartLoader+<CompileParts>d__56.MoveNext () (at <55ba45dc3a43403382024deac8dcd0be>:0)
   UnityEngine.SetupCoroutine.InvokeMoveNext (System.Collections.IEnumerator enumerator, System.IntPtr returnValueAddress) (at <5aeafee3fea24f37abd1315553f2cfa6>:0)
   UnityEngine.DebugLogHandler:LogException(Exception, Object)
   ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object)
   UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object)

As mentioned above - I tried reinstalling both GC and CC, both manually and via CKAN, to no success. I double checked the contents against manually downloaded pack. I also tried booting with only GC installed (re-adding the CC folder from the manually downloaded GC pack)... It still freezes, though the log changes a bit each time (attached above is the latest iteration).

I really want to try this mod out and don't wanna return to EL...

November 17, 2019

XVI
Laying the Path

With technical solutions worked out and prototypes tested, construction of final components for the Niven mission was authorized. Following the final revision, the stationary part of the Sidonia complex was to consist of three modules:

Sidonia Cygnus - a refined version of Cygnus refinery, with upgraded heat management modules, optimized for atmospheric cooling. The vessel took its name from Cygnus - a minor goddess of Gaelian pantheon, known for her excellent technical and mechanical skills.

Sidonia Moriya - named after a sacred temple of ancient Gaelian faith, the lander was to provide habitat and supplies during extended stay on planet's surface.

Sidonia Anna - named after Cygnus' mistress and legendary warrioress, Anna was designed to deliver all components and devices required for proper assembly of Moriya and Cygnus' facilities.

All three components have been launched on the same day - the biggest and most complex operation ever conducted by the Agency.

Sidonia complex launch [Y5 D116]

Spoiler

Cygnus launched using a brand new Ferrum IIb booster - Marvin.

The booster nailed its landing on Gooney Island, while the lander itself moved on, pushed by the rocket's second stage and its own set of liquid fuel engines.

Moriya followed, its booster - Hello Ground - also performing a successful touchdown.

Anna completed the hattrick, with its Flowerpot achieving a third soft landing in a row. All three boosters have been loaded on transports and shipped back for KSC for refurbishment and relaunch.

Ferrum booster, as powerful as it was, lacked the capability to put a fully fueled Heart of Kerbold into orbit; due to this, an orbital propellant depot had to be included in mission architecture. Fully automated, the depot was to operate two robotic landers, collecting water and ore from Iota's surface and delivering it for processing in moon's low orbit.

Orbital Propellant Depot (OPD) assembly

Spoiler

The first part of the complex - core module, containing HTP tanks, powerplant and refineries - was launched using the refurbished Marvin, making it the first Ferrum reflight in program's history.

Unfortunately, guidance systems failed to cancel out horizontal velocity - and the booster slammed into Gooney Island, completely obliterated in the process.

Following station's orbital insertion, two mining drones - dubbed Harvester and Aquarius - were launched. This time, both boosters performed splendidly, landing back at their island zone.

On its way, Aquarius deployed a small satellite, designed to pinpoint ore and water rich areas around Iota's equator.

While the drones arrived and began their work on Iota, the final part of depot's assembly began; extensive radiator panels had been launched. Due to their size, they had to be delivered separately and assembled in place.

A lightweight version of Ferrum booster was used for orbital insertion, while delivery and assembly were handled my crewed Nadir spacecraft. Unfortunately, out of three rockets used, only one managed to perform a successful reentry and landing.

A total of three flights was performed, each delivering a single radiator module. Their size alone made the assembly the hardest and most complex of all performed so far - but in a remarkable feat of skill, no mishaps took place.

With both drones making a round trip every few days, the depot was gradually filled up with hundreds of tons of liquid fuel and HTP, waiting for the Heart of Kerbold to come and dock.

With the depot in place, and all three landers en route, the Agency's crews returned to patient waiting. Should all three landers touch down successfully, the next transfer window two years later would signal the beginning of the main, crewed phase…

November 2, 2019

On 10/28/2019 at 12:11 AM, Kerballing (Got Dunked On) said:

the OH NO NOT AGAIN and 42... those are Hitchhiker's Guide to the Galaxy references aren't they?

Can I suggest that the next one be named Ford?

The whole Niven project is ended, so I have its name list closed... But for the next mission, why not

On 10/28/2019 at 5:38 PM, fulgur said:

The oblique references would be better continued with Restaurant perhaps, or Chelsea Sofa. Or maybe just It'll All Have To Go.

Well, it will.

Adds to the list.

On 10/28/2019 at 8:22 PM, Pleb said:

Will you be featuring a bistromathics drive in one of your future vessels?

Good stuff though, keeping up!

So far, updating KSP-I resulted with my HTP drive becoming non-functional due to change in propellant compatibility... But if I ever get to warp or other ridiculous tech, why not try explaining the black magic behind them in Adams' style

October 31, 2019

Oh! Good to know that. But, if that's WAD, then we still have one issue that started my whole thread here...

Here's my ship, put in orbit using KRASH. Literally the second the simulation kicks in, wrappers around the reactor explode (F3 readout shows 3352/2698 K temperature at the moment of meltdown), and wrapper radiators start burning. They don't get destroyed (though when I tried to rememdy this by putting more radiators, some of them melted down upon entering simulation anyway).

Quote

Notice there is a hidden amount of wasteheat reduction which scales lineary with vessel mass and not visible in Wasteheat Management DIsplay.

Well, that'd make sense, taking into account a fully loaded ship is >400 tons and it's powered by a 0.625m Molten Salt... (And by 'sense' I mean the heat management algorythm going mad and somehow glitching the radiators in this situation) What confuses me though is the VAB power readout:

it's all in red, with 588 MW produced and 58 MW dispearsed. As I said, I initially tried to fix it by adding more wrappers - but even when I brought radiator resting remperature well below 2000 K, the burning effect persisted and random wrappers went poof the second I loaded the ship.

I just made a test - slapped a 2.5m Molten Salt reactor with an electric generator on top of the ship and launched it. In-atmosphere, there was some Waste Heat prodution, but other wise things worked well. In-orbit, both Radiator Temperature and Power Radiated readouts show some positive values - but wrappers still explode and burning effect persists.

Here are the readouts for the additional 2.5m reactor variant. I'm frankly at a loss what is causing this effect and how it might affect my ship during long-term flights. Especially since, from what I see, NERVAs no longer use HTP - so I either need to redesign propulsion to incorporate Thermal Nozzles (which means slapping two more reactors onto the ship), or try to somehow design a compact hydrogen/helium fuel tank that would still give me enough dV...

October 31, 2019

Before anything - I loaded my craft and started stripping radiators all the way to wrappers around the reactor (which worked fine in my previous designs) - nothing. WasteHeat change is a nice, round 0 and 0 KW power is being radiated via wrappers.

I tried installing the latest 1.4.5-compatible version of KSP-I you have linked in the release thread (TBH I was still using the one I downloaded via CKAN back in July 2018...). I already see Module Manager is WAY more up-to-date than mine (mine was 3.0.7), but the upgrade didn't help either. The only actual change I see is making all my designs obsolete, as it moved the Thermal Power Generator up the tree... But at least I have a replacement part, so that's something..

Anyway, here are the other radiator configs I used previously and which work fine upon loading:

Space station, using stock radiators in vacuum:

Non-zero WasteHeat amount, radiators radiating KW into space with no issue

Niven habitat with graphite radiators and wrappers (I apologize for nightime screenshot):

Here radiators emit 0 KW, but WasteHeat production looks legit. Niven has a Duna-like atmosphere, no idea if convection would cause those effects.

My current design - back to Gael, all radiators safe from reactor-mounted wrappers removed:

WasteHeat production is 0, radiators radiate 0 KW, radiator temperature is 0K (!).

EDIT: Oh, also noticed that after upgrade I can no longer use HTP as NERVA propellant.Oh yeah, sounds like a complete redesign anyway!

October 29, 2019

Something's wrong with my radiators again.

I got some science from my last mission, researched Graphene radiators, alongside a Molten Salt Reactor upgrade... And it all just stopped working.

Long story short, when I decide to test my new design (using the KRASH mod to put it into orbit to test vacuum heat management), half the radiators pop due to overheating the second game loads, and the rest just burns - they have reentry effects on and are engulfed with flames. I checked the readouts - and they are all just WRONG. Lemme use screenshots to explain:

Radiators show 0 KW being radiated, despite of their status. I loaded the ship on Gael to check if maybe there's something wrong with atmospheric convection - but nah. Also, in atmosphere the radiators don't even get hot, despire literally nothing changing in terms of thermal readout. Take note there is no Waste Heat produced at all as well. The reactor is reduced to 0.625m with TweakScale with Thermal Electric Generator attached directly to it.

KSPI readouts for reference. I admit I have no idea what is wrong here - I suspect launch clamps might have something to do with the ship not melting, but I'm not really sure. I can't really roll the craft out without the clamps, as in its current state the legs just collapse under its weight ^^'

Finally, in-VAB readout. Numbers are in yellow, true, but I am running the reactor at 10% power anyway (I just want it as backup for long nights on tidally locked moons and in low orbit), so I reckoned things should be working just fine... Apparently they don't.

A few bonus notes, just in case:

Ships I had launched earlier work just fine. I tested my orbital propellant depot, powered by a 2.5m reactor and cooled with stock radiators - things worked fine, panels dumped WasteHeat as they should.
I also tried swapping some radiators for stock ones - the issue persisted. What I didn't try, though, was getting rid of all Graphene radiators and replacing them with stock ones.
I'm running KSP 1.4.5

Let me know if I should post screenshots of other situations/configurations.

October 27, 2019

XV
Trial by Ice

"Sometimes you need to start at the beginning"
-Cpt. Obvious

(This update is sponsored by this magnificent suite from ThePrimeCronus YT channel. Full credits in vid's description.)

With design finalized and first prototype well under construction, the Sidonia programme pushed on to next stage.

Logistics of interplanetary flight have always been a subject of a heated debate. The simplest solution - taking all life support supplies, fuel and other resources from Gael directly - would result in an overbloated spaceship, well beyond the capabilities of any reasonable launch system. Therefore, the mission architecture had to be split into segments, each responsible for one critical component:

Crew transport and en-route life support -> Handled by Sidonia proper.
Propulsion production -> Handled by a specialized refinery complex, extracting and processing resources from planetary atmosphere and crust
Cargo and instrument freight -> Handled by a specialized cargo craft, tentatively dubbed "Big, Dumb Freighter".
Long term habitation and work space -> Handled by a specialized lander, containing inflatable agroponics and habitation modules.
Orbital delivery -> Handled by a super-heavy Ferrum booster.

To reduce costs and simplify deployment and utilization, all four lander components were determined to use the basic template laid out by Sidonia.

The dual propulsion Sidonia used had several implications for refinery design; in-situ refueling would require two basic resources - water and karbonite. Processing karbonite to rocket fuel was a well known and relatively simple process; by a combination of distillation, fracking and black magic, the omnipresent compound could have been reduced to a highly energetic mixture of hydrocarbons. HTP, however, was more complex to obtain.

The anthraquinone process required two things; purified water and lots of electric energy. Water was first dissolved into hydrogen and oxygen, and then both molecules would recombine in a catalyst-laced chamber, producing hydrogen peroxide to be stored in specially insulated tanks. Similarly to karbonite, water was ubiquitous in the system. Energy - not so much.

The prototype Cygnus refinery was designed to combine those two processes; upon landing, the device would deploy it drills, extracting water and karbonite, and then use its onboard reactor to process them into usable resources. Extendable radiators were to expel heat into space, keeping internal temperature optimal for fuel production.

Render of Cygnus refinery prototype

As fuel production was deemed to be the most unproven part of the process, a test mission was scheduled to examine the integration of refinery modules and refueling technology. Heart of Kerbold and the prototype Cygnus refinery were rolled out, stacked on top of two next-generation Ferrum boosters and prepped for launch.

Ferrum booster promised to deliver a whole new quality to the Space Program - with 250 tons of low orbit capability, it easily dwarfed the preceding Electrum. Unfortunately, this also increased manufacturing costs and technical complexity to monstrous proportions - which, in turn was to be mitigated by the booster's unique and unprecedented feature.

Sidonia Iota Phase I - Cygnus

Spoiler

The first booster, dubbed Oh No Not Again, carried the Cygnus refinery into orbit.

Upon reaching high atmosphere, the second stage continued its flight, while first stage initiated a reentry burn.

The landing zone was located on Gooney Island - a large, relatively flat patch of land in the middle of Gelar Ocean.

Following a few dramatic seconds, Oh No Not Again touched down on Gooney Island. Engineering crews rushed to inspect the booster, while a specially designed crawler made preparations to deliver it to the closest port - where it would be loaded on a transport barge and delivered back to KSC for reflight.

Cygnus Iota touched down near the moon's north pole after a few days' cruise and deployed its drills. The smaller satellite was chosed due to practical reasons; in case of Heart of Kerbold's malfunction, a Zenith lander could be used for a recovery mission. Additionally, Iota's icy crust offered a perfect chance to test the basics of water-based HTP production scheme.

Phase II - Heart of Kerbold

Spoiler

Due to its bulk and mass - as well as in order to reduce operation costs by maximizing reusability - Sidonia was designed to operate as both an independent spaceship and Ferrum booster's 2nd stage.

Following stage separation, Heart of Kerbold used its Eaglet and NTRs to push itself into parking orbit, while the 1st stage (dubbed 42) flew towards Gooney Island.

Unfortunately, a design flaw lead to the booster having insufficient battery capacity - resulting in the rocket running out of power mid-flight and crashing violently.

Once Heart of Kerbold reached stable orbit, the Eaglet was shut down and the rest of flight was conducted using NTRs only.

Following touchdown, the crew - Varyag, Charlie and Jolly - conducted a series of tests to evaluate Sidonia's performance in vacuum.

The ability to conduct suborbital 'hops' was deemed a key component of every long-term mission. According to Sidonia planners and their hopes, it not only allowed to access multiple areas during a single flight, but also allowed more flexibility when assembling the compound.

Multiple refueling techniques - from direct pumping to transporting fuel via containers - have been tested during the mission.

During its extended stay, the crew tested Sidonia's systems in multiple situations. The mission took two full Iotan days, equating to just shy of 50 Gael days, during which the spaceship endured the noon heat, deep-night freezing temperatures, corrosive salts contained in icy crust and space radiation, to name a few.

Phase III - Deep Space Cruise & Return

Spoiler

Following refueling, Heart of Kerbold blasted off Iotan surface, heading towards its deep-space trial.

Following a departure from Iota, the spaceship set its course towards Ceti, looping around the moon before heading back towards Gael.

This provided an opportunity to test the Eaglet engine for precise, deep-space course corrections.

Using upper atmosphere passes to bleed out excessive speed, Heart of Kerbold performed a successful reentry, bringing her crew safely back to surface - fulfilling a dream almost given up following the shortcomings of the Zenith program.

Lauded as a stunning and outstanding success, the first flight of Sidonia completed all of its primary objectives:

Feasibility of Ferrum boosters has been confirmed. The loss of 42 resulted in future examples having doubled battery capacity. The reentry profile has also been adjusted slightly, adding a mid-entry burn to allow engine alternators to charge up the batteries.
Dual propulsion system has proven its reliability and effectiveness, despite apparent complexity. While sceptics were quick to point out that four Vectors offered excessive thrust for Niven operations and fuel tanks were insufficienct for a confident mission to bodies larger than the Yellow Planet, redesigning the array was deemed too risky and expensive to be considered without endangering the mission schedule
Cygnus refinery has proven its feasibility, although with several caveats; heat management systems worked very porly in vacuum despite extending radiator surface, resulting in the reactor rapidly overheating and limiting its working regime to relatively short pulses. This, in turn, reduced the overall HTP output, meaning that despite spending almost 50 days on Iota, Sidonia took off without fully filled tanks.
Life support and flight control systems on Heart of Kerbold worked flawlessly; the biggest issue detected was related to power; it was hoped NTR reactors would be sufficient to power up all systems while the spaceship remained in a celestial body's shadow - unfortunately, wiring and generator issues forced the crew to revert to emergency power whenever the blackout exceeded 5 minutes. While this didn't affect life support systems, disturbance in cooling resulted in a non-negligible boiloff of HTP from the ship's tanks.

With this, the final phase of preparations was given a green light to proceed...

October 15, 2019

Quote

This thread is quite old. Please consider starting a new thread rather than reviving this one.

How about I revive my thread anyway, huh?

Again, a very long break... but I actually spent it playing, so that I'm able to post the results without fearing the project gets dropped midway. But I'm back, screenshots sit firmly on my SDD, so without furhter ado - let's get it going!

_________________________________________________________________________________________

XIV
Hopping across the Heavens

"Prettier than a water tower!"
- Astraph Kerman

Picking the exact architecture for the Niven mission was a matter of fierce and prolonged debate. The objective - getting to the Yellow Planet, landing on its surface and returning to Gael - was obvious and undisputed. The method of achieving it, however, brought leading design bureaus to the verge of an actual war, with arsenals of paper airplanes and rubber band machine guns readied in amounts hithereto unheard of.

Kyakovlev Industries, with their reputation (and financing) saved by the successful Nadir spacecraft, moved on with their Apex Sidonia design. A massive spacecraft, measuring 5 metres in diameter and over 20 in height, was to combine the functions of both cruise stage, lander and habitat during surface stay. Unlike earlier designs, Apex Sidonia was to utilize two separate types of propulsion - LH/Ox for landing and take off, and a Nuclear Thermal Rocket for interplanetary cruise and deep-space manuvers.

Much deliberation was put into what kind of facilities would be included in the final, full-sized spaceship; Kyakovlev higher-ups pushed for a "single package" design, with a single Sidonia containing her own habitat, ISRU refinery, cargo hold and science laboratory. At the same time, the spaceship was to be fully resuable, with propulsion and delta V capabilities sufficient for landing and take off from worlds more massive than Niven. The preliminary mass estimate of the complete spacecraft was just shy of 300 tons - more than the Portal station with full loadout.

With those requirements in mind, the first prototype - dubbed Hopper - was to test the very basic concept required for the whole project to succeed; namely, precise manuvering during atmospheric descent and pinpoint landing.

Apex Sidonia Hopper flights

Spoiler

Testing profile was not overly ambitious - a suborbital flight to roughly 20 km altitude, followed by a vertical landing

Mk I's bulk and lack of large steering surfaces made it extremely unwieldy - thrust vectoring was not enough to maintain attitude, resulting in the prototype crashing upon landing attempt

Mk II featured extended aerobrakes and improved flight computer. The flight evenlope has also been extended to over 30 kilometres, to ensure relatively thick atmosphere does not impede landing flip.

Mk II's landing attempt was cut short by a steep slope the hopper ended upon. Still, the test was declared only a partial failure, as all flight and attitude control systems worked correctly all the way until touchdown.

MK III - basically a slightly updated clone of Mk II - was directed towards a nearby plain to ensure it had a flat landing zone. However, while landing managed to kill vertical velocity, the hopper retained excessive horizontal movement, which resulted in it tipping over upon touchdown and disintegrate as well.

The failure of suborbital 'hops' meant that the whole Sidonia concept has been pushed back to the drawing board - albeit briefly. Out of the alternatives considered, neither managed to show much promise; a separate lander/transfer stage combo offered a chance to save mass, but in returned presented a risk of transfer stage becoming inoperational beyond repair during crew's stay on the surface. With little research put in aerodynamics following the Piñata's flight, NASEK's proposition to create a shuttle-style lander has also been declined as implausible. Ultimately, the sunken cost fallacy won the day - and Kyakovlev was given a short deadline to present a revised design, along with a working prototype.

A few dozen restless days and sleepless nights gave birth to a revised Sidonia design; dropping the notorious (and seemingly jinxed) "Apex" designation, the new spaceship towered above the Hopper prototype, having over 7.5 metres in diameter and well over 20 in height. Its habitation module was expanded, providing life support and space for 6 crew members - twice the amount forseen for initial design.

Propulsion has also been revised completely; liquid hydrogen as fuel has been dropped completely, due to its bulky and unwieldy tanks. Heat shielding during reentry - and even moreso, limitations of lifter rocket fairings - required the ship to be as compact as possible. However, using old-fashioned propulsion for interplanetary transfers would bring the mass much above the limits given by available lifter rocket technology - so a compromise had to be reached.

The design went through several iterations, with the one ultimately presented using a dual propulsion method; landing and launch back into orbit were to be facilitated using old-fasioned LFO engines. The cluster of 6 Vulcan engines has been replaced with 4 Vectors - combining high thrust, compact design and outstanding gimbal range, those engines were considered an excellect choice for controlled descent.

Two prototype iterations - older, Vulcan-powered on top and the updated Vector configuration below.

Initial concepts for the reviewed interplanetary stage called for using pure water as propellant; readily accessible throughout the solar system and easy to refine and handle, it seemed like a natural choice due to its high density (and thus low storage volume). However, its low specific impulse meant that the advantage of using it over regular chemical propulsion would be marginal at best. Instead, final iterations switched to high-test hydrogen peroxide (HTP) instead. While more difficult to process and more violate and than regular water, HTP offered a visible advantage in specific impulse. Instead of just heating it up with thermal reactor and expelling through the nozzle, HTP was to be first ran through a catalyst, where it violently decomposed to superheated water vapour and oxygen - and which was then heated up even more before being expelled. The result offered around 600 seconds of impulse, compared to 250 seconds for regular water and 800 seconds for liquid hydrogen.

NTR's high performance came at a price, however; since throttling was made by regulating reactor thermal output, precise thrust control via shutting down and reigniting the engine was not possible. While this was of little consequence during deep space manuvers, precise trajectory adjustments would provide considerable difficulty. To mitigate this, a single vacuum-optimized Eaglet LFO engine has been added to the Vector cluster.

The final design of the SIdonia spaceship

The first example - named Heart of Kerbold, to honour a late Kerbal writer and utopist Douglas Kerman - has been assembled and presented to the public shortly before the deadline passed. Wet dress rehearsals, static burns and hover tests confirmed all the systems cooperated correctly. Computer simulations indicated the complex was powerful enough to land and lift off from Niven. There was, however, one big question that could have only been answered up there, in the void:

Would reality approve?

July 16, 2019

A short preface this time - phew, I never thought I'd come back to KSP with such zeal anymore. The past two weeks were spent almost exclusively in the game, designing, tweaking and refining my crewed mission architecture. Having to deal with science mode limitations is a pretty new thing for me (as I said, none of my campaigns actually progressed to interplanetary crewed flights), and it's way easier to just slap together a Dres mission in sandbox. Anyway, let's go!

______________________________________________________________________________________________________________________________________

XIII
One step back, two steps forward

With Ceti and Iota samples delivered onboard the Portal, Ace and Shigu sat down to tedious laboratory experiments and tests. Zero-g environment in Gael orbit and lack of local contamination helped preserve the samples' pristine condition - but the complete novelty of such laboratories meant research lagged considerably. What was designed as a 200 day long stay ended up lasting over twice as long - a whole Gaelian year. Portal's life support system was not designed for such prolonged stay; a mid-year resupply mission had to be undertaken.

While Kyakovlev still had several examples of Zenith at the ready, its unsuccessful landing attempts discouraged using them for a crewed mission. Moreover, preliminary Niven mission concept studies made it apparent that any reasonable Niven-capable spaceship had to be designed from scratch. This meant the end of both Apex and Zenith projects, as all manpower and resources were to be directed towards this completely new craft.

However, flights to Portal still had to be undertaken; to this end, Kyakovlev Industries presented a low-cost, expendable crew and supplies delivery system, dubbed Nadir.

Vastly simpler than Zenith Heavy, Nadir was designed around completely opposite principles - the whole service and cargo module was expendable, with only the capsule designed for recovery. Dual karbonite/liquid fuel propulsion system has been replaced with a set of simple, lightweight monopropelant engines. A strictly low-orbit vessel, Nadir was painfully limited - but at the same time, it was perfectly tailored for its designed purpose.

Nadir 1 & 2 flights to Poral station

Spoiler

As part of cost saving measures, Nadirs were designed to be launched using proven Corundum boosters. The first mission, undertaken during

With their limited performance and fuel capacity, those ships required a substantial kick to a high, sub-orbital trajectory. Corundum 2nd stage was used to filt the capsule all the way to Portal orbital height.

Following Nadir 1's docking and supply transfer, Scoots performed a bried EVA to install a broadband radio transmitter to facilitate communication between Gael and the station

Undocking, reentry and splashdown proceeded without anomalies, marking the decisive success of the unorthodox "simpler is better" approach.
Portrayed: Scoots, delighted with the colourful display of plasma dancing around the capsule.

Nadir 2 launched by the end of Ace and Shigu's mission, followed the same pattern as its predecessor - high suborbital launch, docking and recovery.

Ace and Shigu's 400 day long stay onboard Portal marked a new record in terms of long duration missions.

Ace and Shigu's prolonged mission meant that the overambitious goal set up by Astraph Kerman - to land on Niven before the second anniversary of first crewed flight - has not been met. Shelving of both Apex and Zenith projects also meant that no crewed flights beyond Portal orbit have been undertaken for the whole year. But this didn't mean the second year passed without any breakthroughs; quite the contrary.

As soon as Portal became fully operational, the second phase of Niven mission came into motion; Niven Prospector.

The largest probe up to date, the Prospector consisted of four separate vessels:

Bus - the structural and propulsive module; powered by four experimental Candle RTG engines, it was to deliver the 3 probes to Niven, while serving as a testbed for nuclear space propulsion technnologies
Scanner - an autonomous satellite, equipped with sophisticated surface imaging devices.
Surface Component - twin landers, designed to achieve soft descent and collect surface samples for analysis.

Mission summary

1) Launch & Coast

Spoiler

Due to Prospector's considerable mass, Electrum booster was required to push the spaceship into transfer orbit.

While still in Gael orbit, the probe callibrated its optical instruments. Electrum 2nd stage visible in upper-right corner.

Mid-course trajectory correction was performed using the Candle thrusters. Their unique architecture - an RTG heating up propellant instead of using oxidizer - provided excellent efficiency, at the expense of thrust. It was hoped that clusters of such engines could reduce Niven transfer time to 100 days and below.

Deep space conditions provided excellent opportunity to adjust instrument callibration as well.

2) Orbital insertion & Scanner deployment

Spoiler

Upon arrival, the Prospector used Niven's thin atmosphere to facilitate orbital insertion into an eliptical, polar orbit.

The Scanner has been released into retrograge orbit to test multiple object control and coordination systems on Gael.

Following a braking maneuver, the scanner poised itself above the Yellow Planet, its findings beamed back to Gael via Prospector's relay.

3) Probe landing

Spoiler

Several days later, after preliminary landing spots have been picked, the Prospector lowered its orbit in preparation for Surface Component release.

Even though Niven's atmosphere had already been confirmed to be thin and wispy, the landers were designed with a robust reentry system - a thick heat shield, thrusters and kevlar parachutes. However, the heatshield's design required the Prospector to temporaly lower its periapsis belore release, as landers lacked their own propulsion during initial descent stage.

The first lander touched down safely in a dark, dust-covered valley.

The second lander touched down on a slope; while it was initially feared it toppled and tumbled down the hillside, emergency systems managed to anchor it in place and succesfully deploy all devices.

The Prospector mission provided valueable insight into Nivenian environment. The surface and relief appeared relatively young, which implied a set of active geological conditions - be it tectonics, volcanism or aeolian erosion. No traces of surface water have been detected - and lack of atmospheric vapour precluded the existence of an active hydrosphere. However, considerable amount of hydrates and gypsium have been found - which meant that extracting water from soil was a viable option. This, combined with confirmed karbonite presence, meant that a wide selection of potential fuels was available for production - from hydrogen, through water, to simple synthetic hydrocarbons.

Of special significance was discovery of aerial methane and ammonia. Unstable and highly reactive, those compounds could not last long in the atmosphere without a source to replenish their supply - with organic metabolism being the most exciting possibility. Out of other atmospheric gases, the results were neither spectacular nor surprising - high carbon dioxide content and was confirmed during first the very first mission to Niven and trace gases composition matched theoretical models made up back on Gael.

Prospector's findings, combined with data collected during first flyby, finally provided the Agency with the bare minimum of data required to organized the crewed mission. With concept studies on Gael reaching their ending, time has come to move on to another great step - creation of an actual interplanetary spacecraft...

One of preliminary designs for Apex Sidonia, with mass simulator replacing the actual crew module.

July 16, 2019

@Jumberlack thanks for confirming my suspicions. I actually got the next tier of reactors (including the Interstellar's Molten Salt one), and miraculously I am finally able to generate power without crashing my whole setup. Barely 30 MW, but it's enough to actually run the H2O electrolysis without the whole thing imploding on itself. I also ~~cheated~~ tinkered a bit with TweakScale and by using 2.5x sized radiators managed the final iteration to look nice and actually work at the same time.

July 11, 2019

Aesthetics be damned, I just slapped as many radiators on a reworked refinery as I could.

However, when I'm launching KRASH to test the whole setup, both generators shut down due to... no radiator being available.

I have absolutely no idea what's wrong. Generators are connected directly to reactors, reactors are working (producing actinides and so on). I have no idea what I'm doing wrong here...

EDIT: I just noticed that my generator's Cold Bath temperature (500 K) is higher than Hot Bath (300 K)... Is that working as intended?

EDIT2: Just in case - Reactor Control window

EDIT 3: Looks like my initial suspicions were true - I am stupid and failed to notice key things (like the whole in-flight thermal readout function). Here's my troubeshooting, I'd be most grateful if someone more experienced verified my conclusions ^^'

1.25m reactors have laughable output (6.7 MW with 4 reactors) at tier 1, while electrolyzer alone gobbles up 20 MW. I tried to reduce its power consumption to 10% with the slider, but it did little to fix the issue, it still goes at full power when activated.
USI reactors apparently have their own generator integrated, so I guess the mod does not recognize them as 'proper' reactors for thermal power production.
My tech is tier 1, so obviously, radiators are also excrements at dispelling heat.

My plan for tomorrow is to return to 2.5m reactor, but tweak its power output so levels manageable without turning the whole refinery into a radiator chrysantemium. Guess more advanced technology will allow me to build something more ambitious in near future.

July 11, 2019

Yeah, when I click on Reactor Control window, things seem working - I have actinides being produced, temperature goes up and heat is produced. If I fire up only less power-hungry modules (like the Ore processor) or just the drill, they work indefinitely. Issues begin when I fire up all converters and the drill at the same time.

As I mentioned, I know I used too little radiators to have 100% efficiency - but I see no way to add more without making majority of lander's parts radiators... If anyone could share their reactor setups, I would happily try to reverse-engineer them.

Oh, and one last detail, though I am not sure how relevant is that - since I'm playing GPP, I am using the older version of the mod (though I can't provide the exact version number right now, as I am at work)

Profiles

Forums

Developer Articles

KSP2 Release Notes

Bug Reports

Posts posted by Astraph