mdkendall

I saw the same thing. I think it is a graphics glitch. Mouse-over the selections (without clicking anything) and they will highlight and then return to normal with only one showing as selected.

i7-4790K CPU (4c 8t at 3.6GHz) 32GB DDR3 at 1600MHz GTX 960 I had the graphics settings at Medium, at 1920x1080, Borderless. Performance in the VAB is not great but bearable. In flight, if there is any terrain visible it is a slideshow at about 5fps and the simulation runs at about one quarter real-time (four seconds elapsed per simulated second). If I look up at the sky, or I am in orbit and look away from the planet, it is much, much better. About 20-30fps and the simulation is approximately real-time (one second per second). In either case the GPU is pegged at 100% with about 4.4GB GPU memory allocated (2GB on the card and 2.2GB "shared"). The CPU is hardly loaded at all; less than 10% during orbit, re-entry and landing with a fairly minimal craft. The game was using about 14GB of memory.

When typing text in the description panel of a flag, comma and period still have their regular function, adjusting time-warp and pausing/unpausing the game. Other key-bindings might also still be active; I didn't check, I just noticed the time-warp because of the resulting pop-up.

More rover testing. Munfried seems pleased with the afternoon's work.

Ponoko do laser cutting and engraving of acrylic (and a lot of other things). We use them at work; they're pretty good.

Rover testing going about as well as expected.

Yes, I have that Logitech Extreme 3D Pro too. I don't use it for rockets or rovers, but for flying planes it is great. Much easier than the keyboard.

My understanding is that internal to the game a planet's biomes are represented by an image map. Different colours represent different biomes. The game decides which biome you are in my looking up your position on the map and seeing what colour that pixel is. At the boundaries between biomes, where one colour gives way to another, there can sometimes be a small fringe of an intermediate colour on the map. That is why there appears, in certain areas, to be a small fringe of tundra biome between the KSC and grasslands biomes. It happens elsewhere too. Use this knowledge wisely. It's handy for science.

After landing at the equator then driving for many days, my Ike rover has finally reached Ike's south pole. Satisfyingly, there is a small peak there.

My Ike rover landed on the equator and, for reasons having to do with accepting a contract without fully understanding how big Ike is, has been driving south for quite a while now. Today, finally, the south pole is in view. It's that flat peak on the horizon on the left. Hooray! Once it reaches the pole the rover is about two-thirds of the way to its final destination. Not quite so hooray.

I found a place on Ike I am naming "Pogo Point". I can't drive anywhere near it without being mysteriously bounced upwards.

There have been some challenges involving the island airstrip, including the Low Flyer challenge: can you fly there from the KSC and land on the airstrip while staying below 150m the whole way. There were some supplemental challenges for low mass, minimum parts count, lowest altitude on the way, etc. That was fun, but many of the craft in that thread no longer work due to ion engines being (correctly) nerfed in atmosphere now.

You don't have to wait until the mothership is directly overhead, just wait until its orbital plane is overhead. That will happen twice every Minmus day. Then launch into an orbit of roughly the same altitude as the mothership. You won't be at the same place, but it will be require little delta-V to adjust your orbit higher (to fall back) or lower (to catch up) to meet it.

One more for today; driving my newly landed rover across Duna. Props to the Camera Tools mod for the camera angle.

My set of exploratory probes has finally reached the Duna system. Successfully aerocaptured into an eliptical orbit with periapsis just above the atmosphere and apoapsis just inside Ike's orbit. Then, decouple the individual landers and put them down. The first one is safely down on Ike and the second on Duna. Rovers deployed and ready to explore. The other two remain in orbit, to be landed on Duna later.

This is fantastic. I'm amazed by how great everything looks. Really, really great. I have it running on a fresh install of 1.0.5 and the only thing I had to do was force DX11 mode. For comparison, here are two screenshots of a mining base on Minmus, one taken a couple of months ago in stock KSP 1.0.2 and one taken today in KSP 1.0.5 with the new KSPRC. It is stunning.

I made a flatbed. It flies surprisingly well.

Just typical plane testing. This one was named "Asymmetry One", and that was perhaps its downfall.

FancyMouse means a probe core facing the other way, i.e. pointing downwards when you land. When you click on the waypoint marker in the map view and choose to enable navigation, you get a marker on your navball showing the direction to the waypoint. The problem is, your ship is likely pointing upwards when you land, so you see the "sky" (blue) half of the navball, and the target is in the "ground" (brown) half, so you can't see it. One trick is to keep tilting the ship over as you come down to get a peek at the target marker. This requires you to know roughly where it is. Alternatively, if you have a probe core (e.g. the OKTO) mounted say underneath your crew cabin, facing downwards (i.e. flip it when you mount it), then before landing you can right-click on it and "control from here". The navball will flip over, showing you the brown half and the waypoint marker.

In the first one I had the Frisbee decoupler in the first stage, so everything was separated right at the start and the Frisbee was propelled by the rocket sled pushing against it. In the second one there are two stages; the Frisbee remains joined to the launcher until the rocket has burned out, then I decouple it and it flies free.

Here's another attempt. I don't know if it meets the "Frisbee must be thrown right away" rule because the thrower lets go about 1s after launch. Anyway, it gets 1.172km from the launchpad.

I don't know if this entry meets all your rules, but I got 283.6m with this rocket-powered sled launcher and Frisbee made from wheels.

Just a quick flag-planting training mission to the Mun. Pay no attention to the decoupler lying on the ground in the background, that's from a spent stage. Definitely nothing went wrong or exploded.

I think your model must use the simplifying assumption that the orbits are circular. I believe this same assumption is made by Kerbal Alarm Clock if you choose Formula Based calculation of windows, and by Olex's online window planner. This gives you a fixed time between windows based on an average value for the correct phase angle. The orbits of the planets are actually slightly elliptical, so the optimum phase angle (and hence also time between windows) varies slightly from window to window. I know of no closed-form solution that will produce the optimum phase angles, but it is possible to solve numerically. I know this was done by Matti Eiden in ksp-toolkit and the resulting table of values for the first 100 years is I think what Kerbal Alarm Clock uses if you select Modeled Data for the calculation type.