Darkherring

Hi, I'm having a small issue with KER after update to 1.8.1. It doesn't remember the GUI size I've selected. After every restart of a game I have to chance GUI size from 0 to 3. Is there a quick fix for that?

Does BDB support Cryo Tanks mod in any way? As those use totally boiloff mechanics, and I wonder if it can somehow merge to have similar experience with both BDB and cryo tanks EDIT: I've found answer in previous posts

Yep, me too I had also one version with nice, asymmetric, single SRB. I'll post some pictures when I'll launch it next time.

The rocket is nothing remarkable - just bunch of random parts that kind of work together . And it also changed a bit already. Here are the pictures of the latest iteration.

Here are the links for output_log and for KSP.log https://drive.google.com/file/d/12fxp6CCczcKAGKg-dJNfzetpHtPiR56j/view?usp=sharing https://drive.google.com/file/d/1cEh1FNX6CeTLGlzFyBXv1t4phKrL9V3e/view?usp=sharing I'm really grateful for your help EDIT: Damn... I got it! It was a small MM Patch making engines spool up. Those engine have their own spooling mechanism, so that made a problem. Patch source - Thank you once again for your engagement!

The ignition amount comes from Kerbalism. And I'm quite sure its not the reason of the problem, as it shows the ignition problems differently. Here is the Game Data And here is the Config Cache https://drive.google.com/file/d/1_rMb598a9sitD6LNMMobFbOS2RkGH5vO/view?usp=sharing I've got something similiar with Asteria-A engine. The main engine doesn't work, but the vernier thrusters work fine

@CobaltWolf is it a know issue? I was searching in this thread but I couldn't find anything.

@Pappystein i had the same problem with one of the LH2O engine. One of the early ones.

No engine ignitor. Fuel load is a regular LFO. That's a SRB. I've used B9PS.

I'm having problem with Prometheus engines. They don't generate any thrust. I have the CRP installed. Any idea what is wrong?

What is your KSP version and Kopernicus version?

Did you install dependencies?

Just ignore it an have fun.

I meant x3.2 compared to stock size. Writing own config would take some time I hoped I could just adjust 2-3 variables to make it work

Probably its the Kopernicus issue with Breaking Grounds terrain features. My workaround was to uninstall Breaking Grounds until the fix will come. I would have another question. Is is possible to rescale JNSQ to x3.2 just by making some changes in the config? Or should I use rescale despite it is discouraged to do?