Kerbal Space Program

Hi gunmaster, an you please provide the affected save, your KSP.log, output_log.txt and your dxdiag hardware report.

http://bugs.kerbalspaceprogram.com/projects/prerelease/wiki

Thank you.

sal_vager wrote:

Hi gunmaster, an you please provide the affected save, your KSP.log, output_log.txt and your dxdiag hardware report.

http://bugs.kerbalspaceprogram.com/projects/prerelease/wiki

Thank you.

Roger, sorry about that.

Think that's everything you asked for, if I added the wrong thing, let me know.

Also: Running the x64 bit version (v1.1.0.1172 x64). If that helps any.

I got this too but it was only after cheating the buildings to max level.

It might occur other ways or through upgrading them normally.

I can't reproduce this. Been trying with different resolutions. Also tried a lot with fully upgraded facility buildings.

I've seen this error in build 1209 & 1215. Initially noticed it in a modded game. Behavior was more extreme though, affecting Admin Building, Control Centre, Astronaut Complex and even the Research Centre. I had no luck recreating the problem in a new stock game, until I moved my saved career to an unmodded copy of KSP. Then I saw the same behavior reported above with only the Admin Building affected.

I doubt its graphic card related as I'm running an Nvidia GTX770 which is unlikely to share much of a pedigree with Bewing's Radeon. Seems more like something the career upgrade path changes in the game to me. Never seen it occur with the Tier 1 buildings. This might also be why it is so hard to recreate on demand. I was easily 10-15 hours into my career when the problem first occurred.

I was also seeing this before, and it looked like there was a thin gap in the graphics between different elements, where it looked like the mouse position was not being captured by the building interior overlay (and was being passed to the KSC buildings).

I'm no longer seeing this either (even through the thin gap around the funds bar), in build 1230. Looking for people to give it a try (or keep an eye out) again to see if it's still happening.

This was fixed in build 1230, but now it's happening all over again in 1.1.1 (1250).

Fixed in 1.1.3, as far as I can tell. My system was very susceptible to this error, and it's not happening at all.

Woops, I tested it a lot on 1.1.3, but I still spoke too soon. It seems to be mostly fixed, but I still get it on rare occasions.

Moving to KSP as still valid

I just witnessed this bug for the first time and I actually have more input on the exact behavior.

It happens for me in the Administration building, but only when there are other UI elements in the scene, but out of view (menus, windows, craft title pins ). I attached two screenshots for clarity. In the first you will notice a craft pin near the runway, in the second image, the pin is still present, but the scene is turned so that the craft lies just out of view.

Now if I click on the administration building with the pin clearly in view, the admin building works as intended. But if I turn the screen so the pin is just out of view and then enter the admin building, that's when I see the flashing as I mouse over buttons.

My guess, is that with the pin just out of view, that puts the pin technically in the foreground, not the background, it counts as being in front of the other windows. When you mouse over a menu item in the admin building, it tries to display an element from the wrong window, because its reference point is the window in the foreground (in my case the pin).