Version 0.6.6.1

This is our second update since we entered Early Access. We are still focusing on bug fixes, but we did add the Delta-V display in the designer, which has been very highly requested. If you want to help us decide on what to do next, make sure you vote on the stuff on the Roadmap!

ENHANCEMENTS

Added Delta-V, TWR, and Burn Time information to the designer. It can be toggled on/off with the button in the top right of the Staging Editor.

Improved craft switching in the Map View to not require the flight scene to reload when the craft is nearby.

Upgrading to 2018.2.15f1

Photo library now automatically selects the Camera Roll album when opened.

Smoothly transition camera back to craft when clicking RECENTER button in flight.

BUG FIXES

Increased the buoyancy of the command pod

Fixed a bug that would cause docked crafts to spin.

Fixed a bug that could cause crafts to appear to randomly disappear during flight.

Fixed a bug where RCS would stop working when the center of mass became very close to the nozzles.

however it would be very difficult to find all the buttons to use, like, would throttle be holding a trigger, and detachment is a button? But flying would be easy it’s building I’d be concerned about because there is so many things to do that you might need to use button-combos. But that’s up to the devs...
@MrAspy

@Klosskopf Thanks for letting me know! That's terrible! As a workaround, you can still force the loading screen by switching crafts and then do a Quick Save and Quick Load. I will need to look into this more. Would it be possible for you to submit a bug report so I can track this?

@AndrewGarrison For example my Curiosity rover. Before the update it was possible to activate the rope.
It seems to be related to the seemless transition between crafts. With a loading screen the rope can be activated by a second command chip.

@Klosskopf That is how it works by design. Rotators are wired up to a single command pod/chip. What are you trying to do exactly? We have considered the idea of adding a master/slave setting so you can change command pods and enable master mode, so all other command pods will listen to the master and repeat its roll, pitch, yaw, etc inputs.