Aerospike

Ok so I ran a few quick tests around KSC today and KISS seems to work just fine with KSP 1.12.3 So I'll update the info here and on spacedock.

Hello, Yes, KISS is still supported, but I didn't have much time/motivation for KSP recently. 1.11.x was the last version that I have tested KISS against, and I have marked it as compatible on Spacedock (that is where CKAN gets its information from) . Guess I forgot to update the thread here. I'm too busy this weekend to do anything, but I will run some tests with 1.12.3 next week and update spacedock and this thread.

Thank you Squad for this incredible game and 10 years of awesome updates and DLCs! Looking forward to your contributions to KSP2!

I can't reproduce this issue. I tried it with a clean install multiple times, but the config file was always created. I have released a small update anyway. It's just a recompile against KSP 1.9.1, so don't expect anything new.

Thank you for taking a second look! I'm glad that you didn't spot any obvious issues. Still there is a lot of work to do for me, beginning with the old legacy UI and the overall structure of the plug-in. I really should refactor the code quite a bit.

@linuxgurugamer Could you please explain this issue in more detail? I just looked at the code of KISS (haven't really done that in many months...) and I can't find any explicit use of threads. Of course there might be some implicit use of threads by Unity (or System) classes but I would not know where to start in finding any of those "hidden" issues. Also: what gitlab issue are you talking about? My source is on github and I can't find any new issue there...

Thank you for making me aware about the issues. I'll look into it as soon as possible.

I'm not so sure about that. We haven't heard a single *beep* about KSP2 since end of October 2019, that was 3 1/2 months ago! Originally KSP2 was teased as being released in "Spring 2020" (very vague, and officially it was only ever advertised even vaguer as simply "in 2020") and later confirmed to definitely not being released before April 2020 (Begin of Take 2's fiscal year 2021). For a game that is supposed to be released in just a few months, they have shown very little to get their intended audience excited about it. So given what we know and how much we have been shown, I would not expect KSP2 to be released any earlier than Q4 2020.

Thank you so much for listening to the community regarding the Mainsail and Skipper revamps! While I have to admit that the "improved" revamped Mainsail is still not my favorite engine design in the game, it certainly looks better than the first publicized version. Oh and the new variants for both engines are HIGHLY appreciated! Fantastic work Squad!

I am very grateful for squad still updating this game after all those years (almost 9 years since I first tried it! ), So grateful in fact, that I own multiple copies of the game and the DLCs (steam, gog, ksp store). Could not have said it better. Nobody here wants SQUAD to stop updating this amazing game and most of us really appreciate the content they provide (at least most of the time). But here and now some of us provide (hopefully constructive) criticism about a part revamp that we think doesn't stay true to the spirit of the part.

Well it certainly is a pretty good analogue of the original Vulcain engine (or apparently also for the new upcoming Vulcain 2.1 for Ariane 6, as that one re-introduces those 2 turbopump exhaust pipes that run all the way down the engine bell). But for me there are at least 3 things that feel "wrong" about this design: 1) The (Revamped) Skipper seems to be based on the Vulcain 2 (so basically the same kind of engine) and while that design (or rather its proportions) works great for a sustainer or upper stage engine (imho), it's appearance lacks that "MOAR POWER!!" vibe that the original Mainsail had. Simply up-scaling the nozzle compared to the rest of the engine apparently isn't enough to make it look powerful. Something along the lines of Rocketdyne F-1 would have been a better source of inspiration in my opinion ("sadly" that is already covered by the MH expansion). 2) While faithfully recreating the aeroshell that hides/protects all the plumbing and turbo machinery may make that design more true to the original, it also makes it bland and uninteresting to look at in a game. Also to me this "sleek" look again takes away from the aura of power that the old design had. 3) Those exhaust pipes are possibly the worst offender here. They already look a bit strange on the real Vulcain (at least after seeing the Mainsail revamp), but in their stylized KSP representation, they make the whole engine look outright goofy. "But this is KSP, Kerbals are pretty much the definition of goofy!" I hear you scream. But for a "Mainsail" engine, it is the wrong kind of goofy imho. I feel it should look outright ridiculously powerful, not "hey, I look like a toy" or "hey, I look like the backside of a horse". Oh and before I forget: I too belong into the camp of people who are disappointed by the apparent lack of variants for the new mainsail and skipper revamps. After the last few engine revamps I was hoping that this would become the new norm for all engines.

My first reaction was to like it because "whoohoo, part refresh of something that is truly starting to show its age" and " fascinating, looks like it is base on some real engine I know" (although I didn't recognize it as a Vulcain 1 / Vulcain 2.1 at first). But the longer I look at it, the less I like it as an engine in KSP. As others have already noted it doesn't really have anything interesting about it and some have already articulated some reasons as to why it isn't a good design choice in general and for the role as "Mainsail" in particular (kudos to Nertea, LittleBitMore, et al). It really is the first part revamp that I do not like.

Wow! Trip back memory lane! I had a grasshopper II as a kid. Terrible RC car (weak motor, only 2wd, no individual suspension on rear axle, no (oil) shock absorbers (only springs)), but man I loved that thing! Really like your build so far!

Working on a KSP analogue of NASA's SEV (space exploration vehicle) concept. I've been wanting to do this ever since the new MK2 Lander Can came out (and before I even contemplated to create my own model for a "look-a-like" rover cockpit). All Stock (with possibly both DLCs) with the exception of Aviation Lights on the top of the cockpit. Available parts severely limited because of the current progress in my career game. Current problems: 1) I'm not yet satisfied with the looks, especially the bottom "service bay" section with fuel tanks and solar panels. Maybe I need to build it in sandbox or wait until I have more structural parts unlocked in career... 2) Without some serious use of BG robotics (which I haven't used before) to create some arms, it actually has no ingame use for me. A Klaw below the cockpit to grab things would be nice, but it just doesn't fit the scale (it is way to big).

So I have finally been able to try the versions that came up after my little contribution to the whole engine plate issue: * 1.9.1.4: engines are not considered as a part of the same stage as the engine plate and if I remember correctly, now it seems that "ConsolidateStages" is broken, because every one of the 7 engines on my plate is considered as a separate stage. Unfortunately I don't have a screenshot, and now it seems I have trashed the config somehow (see below) * 1.9.1.3: engines are in 1 stage together, but still in a different stage than the engine plate. Engines attached to the plate get no highlight at all (neither red nor green). * 1.9.1.2: can't test it because somewhere in the process of starting and shutting down KSP multiple times and switching out SR versions in between I must have corrupted something, because now the UI for SR doesn't show up no matter which version I use. (button on toolbar is visible). Is there some method that SR uses to remember window positions? So that I can reset it? I can't find any obvious file for this.