Beetlecat

Oh, no worries at all. This happens to all of us.

looks like it did. ty!

They both work fine at the same time if you don't mind the occasional double work...

Out-freaking-standing. This is a pretty jaw-dropping release in an already amazing collection. Nice!

with a big enough lever...

sheeeeeet. This is gonna be good

Rude! ;D

Probably not at all related to EVE itself, but it sounds (pun intended) like your game config got reset. The 'ambient' sounds in KSP are on their own fader, and may have somehow gotten cranked up. In-game sounds like engines are on their own channel, and likely set to be lower than the ambient noises.

Nice work! Thank you.

Make sure it's v0.0772, and not just whatever the previous one was -- there were a couple rolling updates with this latest release.

No broad experience with this -- but I'm totally guessing that blender vs. unity vs. game are probably *not* agreeing on which axis is which (and + / - getting swapped, etc.) Even when fiddling with positions for indicator lights, etc. I remember having to reverse some values to have them behave well in-game. Someone more knowledgeable can confirm.

Some/many of the new features basically require re-creation of atmosphere configs for planet packs. The funky blue overlay on spacecraft is a bug. The dev is apparently on vacation at the moment, so the best bet is to roll back to the previous 'happy' version for the time being, and just enjoy the public test version on a game you're not relying on for screenshots.

Hey, @Caerfinon -- did I see you mention somewhere you had configs to swap the Otter Submersible's ballast tanks to work with Sunkworks? I suppose I could just make them regular fuel tanks and let SW handle the rest...

That might be better for the Kerbal Konstructs thread, or even the JNSQ one (since those bases were created there) -- I've noticed some similar shenanigans with the the test pads on KSC Extended. The opening / closing mechanic may be a bit slippery. Moments like that I would have ZERO issue with just popping alt-12 and giving myself enough cash to do what it takes.

I'm really loving these!

The blue (or colored) spacecraft glitch is something that I'll happily live with for all the other awesomeness this new version provides. No doubt this is only a temporary state.

I don't think any rudeness was coming across--but just a different interpretation of what "real time" means --- in reality, as soon as craft separate they become distinct vessels, and go on with the rest of their flight: either to orbit or landing/crashing. The specific game/engine limitation is that we only control one active vessel at a time. The vessel unloading distance is also a potential factor. You can trick/fudge that a bit like what's described above, but a more realistic simulation *is* using something like FMRS so that you can perform the landing in the same slice of time that the upper part of the craft would continue to orbit without having to artificially lob it inefficiently high. Part of me wonders what aspects a multi-player server could accommodate for this scenario... Literally running a KSP instance for each active craft.

I'm going to do you one better -- I just fired it up in 1.12.2 and... They seem to be working fine! YMMV with some of the functionality here or there, but they're working for all the mainly needed dials and gauges.

Some of these seem pretty handy! Thanks for sharing this collection. The JNSQ CNC fixes are the same as the ones released in JNSQ 1.10.1 last week, right? At least the file looks the same. I'm also noticing a B9 thingy probably connected to the RTG integrations. I'll submit a git thingy.

Shoot -- Just confirming that in my game. I won't hold my breath for official updates (although they should, dang it can look so wonderful!), but hopefully somebody (or me) takes a stab at it by the time I start planning trips to Eve or far beyond in my current game

Is the "Simulation mode" toggle button actually functional? I was just fiddling around with something else and teleported a stock lander craft to Munar orbit, when suddenly faced with the inability to activate the landing engines! (craft also doesn't have RCS thrusters) I'm noticing that remaining ignitions and ullage requirements are still being enforced no matter which state the toolbar button is in. Does this need to be set ahead of loading/launching a craft to have an impact, or should it literally be available whenever?

I was getting frustrated trying to use vehicles from the Grounded mod with Kerbalism installed-- they have plenty of power (at the expense of fuel, of course) but B-V wasn't detecting it after a few in-game minutes. Knowing the cheat works is a fine workaround, since in-game, Kerbalism ignores the stock EC anyway, so it won't affect any craft that aren't under control of Bon Voyage. I look forward to anything new you have in mind, but for now we're in good hands.

Nice. Thanks for helping me do some SCIENCE here -- I've not done a great deal of flying around yet, so it remains to be seen if I somehow have a mis-aligned JNSQ Kerbin. The KSC values seem spot-on, so it's not just a simple global shift. I didn't think to drop waypoint markers at the actual marker locations like you illustrated, so I'll do that next to better visualize what's going on. [Edit/Update/Etc.] So I'm not at all sure what was happening, but I'm not going to rule out pilot error. Plopping down the lat/lon markers show them lined up exactly centerline on the runway. Manually adjusting the #s to match the 90 approach, even made me come in slightly *south* of intended. It's entirely possible that the tighter tolerance of the short runway (plus lack of visual distance as with the KSC runway) makes it easier to drift off of center. Doesn't seem like NavUtils is doing this to me!

Oh, that's totally fair, and I don't blame them--considering the fantastic work they've done all across Kerbin. The 27 approach is probably a rarely-used one, especially considering the state of the services there. There's not even a functioning washroom! Anywho, I did a simulated daytime approach to confirm my suspicions, and it is indeed situated a bit to the right/north of the runway: I'll try duplicating the latitude #s from the opposite approach (which seems fine).

Just to confirm--the ones I quoted are from the JNSQ.cfg already distributed with NavInstruments. I'm guessing the gsLatitude and locLatitude should be closer to matching the opposite direction since the runway is 100% East-west oriented. I'll try those other values and report back if I get some KSP time in later this evening.