Beetlecat

Whoa! I'm not sure what happened, but my Kerbal just walked straight *through* the sideways-facing gear on APP Aeris 2 craft. Totally trippy. Is there something up with gear colliders? I'll come back with an actual bug report/notice in a bit. EDIT: Never mind for the moment -- It looks like the regular stock gear are doing it, too. This stuff is silly, sometimes.

I hadn't used the steam craft download thing yet, and its.... interesting. It looks like once you load/subscribe a craft it parks it over in the steam library's workshop downloads folder, rather than the usual saved game location. I assume once you make some tweaks or edits and re-save, it'd put it in the normal saved game location and available to KerbalX/Craft Manager.

Nah, just tied to KerbalX -- which is pretty much *better* than Steam Workshop for a lot of reasons, but craft manager *does* enable you to "manage" your local craft just fine. You can even tag and upload them to KerbalX if you like.

While eagerly awaiting the 1.5.1 version sync with Kopernicus, and for NESD to finish the new bits, I threw this together to use the in-game texture switcher to swap between the plain, color stripe, and symbol textures on the Streamline fuel tanks: @PART[nesdmk1lf050,nesdmk1lf50,nesdmk1lf100,nesdmk1lf200,nesdmk1lf400,nesdmk1lf800,nesdmk1mp125,nesdmk1oxi050,nesdmk1oxi50,nesdmk1oxi100,nesdmk1oxi200,nesdmk1oxi400,nesdmk1oxi800]:NEEDS[StreamlineEnginesTanks] { MODULE { name = ModulePartVariants primaryColor = #ffffff secondaryColor = #ffffff baseDisplayName = Plain baseThemeName = Plain VARIANT { name = ColorStripe displayName = Color Stripe themeName = ColorStripe primaryColor = #3f69ae secondaryColor = #a94d4f TEXTURE { mainTextureURL = StreamlineEnginesTanks/Parts/Ox-LF_Tanks/LF-Ox-Color } } VARIANT { name = Symbols displayName = Symbols themeName = Symbols primaryColor = #cccccc secondaryColor = #cccccc TEXTURE { mainTextureURL = StreamlineEnginesTanks/Parts/Ox-LF_Tanks/LF-Ox-Signs } } } } Note: This is a pretty rudimentary patch file, and I may be omitting some MM best practices. Also, you need to extract the other DDS files from the "Extras" folder, and rename them "*-Color.dds" and "*-Signs.dds" so all three textures are together in the same folder.

CKAN seems to be pointing here: https://github.com/pizzaoverhead/WheelSounds Which is the "current" version. I think the 1.5 was added to the topic title since it does seem to work fine in 1.5*. It's only tagged to work with 1.2, so your eyes aren't deceiving you.

I LOVE this kind of troubleshooting. Part luck, part skill, all terrific.

Looks like these are working okay in 1.5/1.5.1! I wonder how it would be to hook up the alternative textures into the stock swapper?

Could this be a terrain detail issue?

Sorry Snark! Mea culpa. My only follow-on thought from getting clarity on the "bug" was whether or not you'd consider it something you'd prefer to override with BBT again. Otherwise, you're totally right -- not *your* issue. If it turns out this is WAD on Squad's part, then yeah, I'll add my voice to the chorus of "bring it back!" I *do* wonder about the possibility of bringing back the dots, though. I find I much preferred them to a literal timer ticking down. Something about them being more of a visual abstraction among all the other values and formulas, etc. Even though I know there are numbers driving them. And this interesting wrinkle is interesting.

So, to clarify the issue described, the stock burn time is essentially showing the total available burn time in the craft (the same figure Kerbal Engineer is displaying above in that screenshot), rather than what's going to be needed for the upcoming burn? The burn indicator bar (with the staging segment) does seem correct, since it's showing 1532m/s (total) which requires a stage after burning the 1197m/s available in the current stage.

Quite often, mods *are* perfectly compatible with a new version of KSP, but simply give a warning to let you know they've not been officially updated to the new version. This version change has been pretty easy on a lot of mods.

I managed to dump the new save values into an existing game recently by comparing the save file contents. The planets were then "hidden" as expected. Not sure if it wouldn't break anything else down the line, though :I

Yeah, it's pulling me away from TR/TRR in favor just simpler skybox or suit replacements. I *do* like being able to take the helmet off my Kerbals from time to time, though. (I know this is off-topic, but I have to share in the utter bafflement at that particular situation. Not to mention Sigma replacements, etc. )

Oh, good lord. :I I don't envy you this frustration

Awesome! This was going to be part of setting up a new 1.5 career. (+Monthly budgets, KCT, Oh Scrap, etc.) Thanks for sharing!!

Ha! Cheers for the 1.5 update. The second bullet seems like it may be a short-lived "fix" -- but appreciate the consideration, just the same

Are you sure? I'm running 1.5 copied to a new drive w/o steam running right now as I type this.

You can always keep/revert back to the previous version(s).

I was going to say something similarly snarky --- lest Snark-Actual comes in and regulates instead. Just follow the thread and see if anyone offers some updates or fixes. The "You" in this forum has said the titular Farewell.

Well, this is clever. The stock externalCommandSeat.cfg now has a single new line in the PART declaration: CrewCapacity = 1 Added that to the MK1 Open and it worked like a charm. Now all we need is a series of MM patches for other seats. Currently active mods can just add it, but older stuff like the Kerbonov heavy seat will likely need a custom patch. Any notion that TCC would "devolve" into this supporting role, or just sunset as a mod altogether?

Okay -- insta-test with @NESD's Mk1 Open Cockpit: KSP 1.5 does *not* recognize it as a command seat/fill with pilots in the VAB/SPH. Could Take Command Continued still serve as a "recognize this part as a command seat" set of configs for MM for lots of seats like the MK1 Open, Kerbonov, USI Explorer, SXT, etc.?

Aw. Will miss the dots, but cheers all the same!

It is designed/coded to *not* load into a game that's any version different than what it was released for. When we load old savedgames we're essentially loading them *without* the mod installed, and it'll choke the old saves.

Standing by to see if mod-added control seat/pods will still require mod-assistance to function. I'll drop a line here later to note if MK1 Open Cockpit, etc. work w/o TCC. 1.5 fun tonight!

Hopefully there are at least some news "stock" toys /trackers to play with and enhance. KSP has had some good stepwise improvement in *some* areas, it's just a shame it winds up *almost* replacing needed mod-provided features