blizzy78

Please upload your toolbar-settings.dat like you did with the log file. I'd like to see that without it being mangled by the forum software.

Okay, got it. Are you using Toolbar 1.7.0? Also please post your output_log.txt.

Not sure what you are saying. The flight map is considered a separate "scene" by the Toolbar Plugin, and as such, it has its own toolbar settings.

You seem to have run out of RAM.

I'd suggest to install only the Toolbar Plugin, then adding other plugins one by one until the issue arises.

I have advised Sarbian to get rid of the little T because players can now choose themselves which buttons they want to see.

Did you set your target .NET version to 3.5? That's what KSP uses.

Try replacing the FLIGHT block with this one: FLIGHT { toolbar { x = 300 y = 300 width = 71 height = 38 autoHide = False drawBorder = True useKSPSkin = False buttonOrder = visibleButtons = } }

Please post your toolbar-settings.dat file.

Ambient Light Adjustment Plugin 1.1.0 is now available for download. You can now have two settings which you can toggle between. Also, settings are persisted between scene changes and KSP restarts.

See my tutorial.

Or IF, if you don't mind me adding that.

Statistics more interesting than these would be liftoff TWR and liftoff delta-v.

Exactly this. We need to differentiate fields into categories like "must have", "will be displayed in fixed locations", and "nice to have (ie. optional)". FWIW, I really love how the Google Play Store looks. Each app's page looks exactly the same, and you always know where to find information. No scrolling around to find stuff, and only if you're lucky that the programmer has actually added it.

I'm afraid I can't.

The stack traces do not mention the Toolbar Plugin directly, and it doesn't do anything with vessels or camera objects. So I think these are not caused by the plugin.

Need more information. Please find those exceptions in your output_log.txt, which has way more information, then post them with the complete stack trace here. As to if they're "bad": Even if they're caused by the Toolbar Plugin, they could be harmless. It's not easy to tell with too few information.

Saving the value is trivial, I just wanted to put this first version out to see what you all think about it.

Why not just bring it up to the author of pWings?

It does that to decrease the synodic period, which is the period the two vessels have their closest approach to one another. Of course you can always get a rendezvous with a vessel in a 640 km orbit by launching into a 635 km orbit, but if both are on opposite sides of the planet, it's going to take a really, really, really, REALLY - did I mention "really?" - long time.

Sounds like you could use a way to quickly toggle between two previously set slider values?

If the lit side is lit by ambient light (which I suppose it is, can't check right now), it will be dimmed. It's just the way the scene lighting is set up.

Turn the slider all the way down

I've made a new plugin called Ambient Light Adjustment that uses the new "drawables" feature. Check out the source code for an example.

(post deleted)