joinedup

Not in favor of the instant planetary scan*, I appreciate people play the game differently but for me a large part of it is about resource management, working within constraints and trying to find creative solutions. 90% of people might just achieve polar orbit and hit timewarp, but perhaps some of the 10% would have fun trying to beat the constraint by some creative method which they'd enjoy doing - perhaps having several scanners in different polar orbits to finish in less game time (dunno if that'd work but I suppose it could be made to) or doing something else while the scan was completing. IMO it's less fun than it might have been. also pretty sure nearly 100% of people timewarp planetary transfer but that doesn't mean the rules of time within the game are wrong, you've sort of broken the consistency of the game by having something that shouldn't logically be instant happen instantly here. * on principle... I've not actually had chance to play 1.0 yet - downloading seems throttled PS many thanks for the extra resources and constraints you have introduced in the release though I look forward to managing them when I'm done downloading.

sorry if it's already been mentioned - I did a search. I dislike the current font being used for the speedometer in the IVA view (mk 1 pod)... quite a lot. proportional spaced chars just look wrong for numeric displays IMO, I don't like the way the overall width changes depending on how wide the digits are. It's also, I feel, out of sync with the rest of the aesthetics of the mk 1 pod. I'd suggest fixed width 7 segment or (preferably) 16 segment style chars with leading zeros blanked - so that more width means more speed. If that's going to cause width problems with extreme speeds the K,M,G suffix system could be borrowed from the drum altimeter, I'm only a noob but is it ever going to be more useful to know that you're going 1234567 m/s than 1234 km/s? I'm sure it's not the biggest problem out there but I feel better for getting it off my chest... thanks for listening. j

quirk/minor OS windows 7 home premium 64b KSP 0.9.0 beta 32b unmodded The scrollbar in the mission recovery window responds to left button clicks on the scroll shaft and to dragging of the scroll box... but the scrollbars on the tech tree and contract selection screens only respond to dragging the scrollbox. I like clicking on the shaft, which is my usual way of using scroll on windows.

don't be offended... but what is your staging like, have you got some chutes in the same stage as your motors?

ps I think part of the problem I was having is that the markers on the contract orbit seem to activate their text when the mouse is at a greater range that the flight markers - you can't just move the mouse round to the other side of the pair of markers because the contract nodes always show text first (and the contract nodes show partly redundant information anyway because you can see the target ap/periasis distances by opening the contract info in the map view. afaik there's no other source of the ap/periasis heights for your flight in the map view so IMO the flight markers should take priority.

OS windows 7 home premium 64b KSP 0.9.0 beta 32b unmodded trying to match a satellite contract orbit by floating over the flight periapsis marker with the mouse to read the altitude off - text from a contract orbit market appears and collides with the flight info when the markers are close see https://www.flickr.com/photos/78401139@N06/16642073749/ this is IMO undesirable behavior and wouldn't look very slick in the final version, ideally I'd like to see text not colliding in the map view and color coded text matching the schemes used for the flight and contract orbits would also be nice. it's possible to workaround by dragging the camera and changing the zoom, at least when the markers aren't too close, but annoying when you're trying to time a burn, I'm using a mousepad which probably makes it more awkward.