Map icons cannot be toggled

[Renegrade]

I've noticed that ever since the little map icon buttons (hidden at the top of the screen in the Map view whilst in space) gained the ability to remember their state, they sometimes become unresponsive to clicks and can't be toggled.

KSP Version: KSP 0.90.0 build 705, x86/32-bit version on Win 7 x64

What Happens: Map icon toggles are unresponsive to mouse clicks

Mods / Add-Ons: All Stock

Steps to Replicate:

1) Launch any craft

2) Go into map view (default key is 'M'), try to enable or disable a map icon (example, flags) via left mouse button

Result: Nothing happens. Flags are unresponsive and do not highlight. Everything else works fine. No unusual locks seen in the input lock stack.

Fixes/Workarounds:

- alt-tab to another application and back

- check the input lock stack in the debug menu - this clears the issue for some reason without showing any usual locks

Some notes:

- I always play in windowed mode.

- It doesn't always seem to happen (it's frequent though)

- It sometimes resolves itself spontaneously

- This bug predates 0.90, it started when the icons were updated to remember their on/off state (0.25 I think?)

I've confirmed it with an absolutely pure, brand-new stock install.

Here's what I mean by "map icons", in case it isn't clear:

[DeMatt]

It's something to do with the way KSP handles being alt-tabbed out and back in. Alt-tabbing out of KSP (and back in) causes the bug; alt-tabbing out (and back in) a second time fixes the bug.

[Renegrade]

It's something to do with the way KSP handles being alt-tabbed out and back in. Alt-tabbing out of KSP (and back in) causes the bug; alt-tabbing out (and back in) a second time fixes the bug.

A start with no alt-tabbing at all results in the bugged state. Alt-tabbing (or simply clicking out of the window) and back only clears the issue. Temporarily. Switching to a new ship jams it up again. :/

Oddly enough, looking at the input stack also clears the issue.

It's not a critical issue to begin with, and there ARE workarounds, but it's quite annoying and came in with 0.25...

[vexx32]

This is a very weird one, because I honestly can't say I've ever run into it. Could you get an output_log.txt file from a session where this has occurred?

We'd probably appreciate being able to look at your DxDiag and a screenshot of Task Manager showing all running processes at the time of the occurrence. And... just to cover all our bases, a screenshot of your video settings, please.

[Renegrade]

This is a very weird one, because I honestly can't say I've ever run into it. Could you get an output_log.txt file from a session where this has occurred?

We'd probably appreciate being able to look at your DxDiag and a screenshot of Task Manager showing all running processes at the time of the occurrence. And... just to cover all our bases, a screenshot of your video settings, please.

Here they are:

http://alpha.renegrade.net/images/ICONS-VideoSettings.png

http://alpha.renegrade.net/images/ICONS-dxdiag.txt

http://alpha.renegrade.net/images/ICONS-output_log1.txt

http://alpha.renegrade.net/images/ICONS-processlist.png

Special note is that I run in 1900x1000 windowed mode, which is a custom resolution I set up in the nVidia control panel (so I don't have to edit settings.cfg all the time). I don't use it fullscreen at all, it's just for windowed mode (1900x1000 leaves enough space for the taskbar and a bit extra, and also means I don't have to perfectly align the window to see everything and only lose 20 measly pixels).

Pretty much the only things changed are:

- Texture resolution set to full (it likes to half itself after the first run)

- Res to 1900x1000

- Ground scatter turned on

- Stage control changed from space to tab

An extra special note is that I have to move the window sometimes, as Windows likes to stupidly tile things, which results in the bottom being hidden by the taskbar, so I generally move it up a few pixels with every launch. (Good job, Bill Gates!~) I did not otherwise alt-tab or switch windows for the output log presented.

Also it's ONLY the map icons when really in space (launch a craft->press M->these icons), not the Tracking Center. The TC icons ALWAYS work. Also, when the icons aren't working, their hover-over tooltip doesn't work either, it's like they're not even there.

0.25 had this issue too (as I said, ever since the icons started remembering their state, which is especially terrible because that feature is otherwise very, VERY welcome).

Note if zipping or jpegging is required of the above things, let me know.

Oh and for that output log, I started KSP, went into the VAB, loaded R5 MunLand II, and hit launch, and immediately went to the map to check the icons - they were dead. It's a pure stock game.

Edited January 12, 2015 by Renegrade

[vexx32]

Hmm. That's... quite odd, really. Not really sure where that could be coming from, nothing in the logs or anything.

Can I ask you to see if it'll still happen in one of the standard resolutions? Also, could you try running KSP with the -popupwindow option? Just trying to isolate variables, I guess, haha.

[Claw]

I was able to duplicate this. I use maximum resolution in the "-popupwindow" frameless window mode (edit: was also able to dupe with full screen). I was able to launch a craft from the SPH, go to map view, and the buttons did not work. As you said, doing ALT+TAB cleared it up. Pressing ALT by itself did not do anything. Nor did clicking on any other buttons in the display in both stage view or map view. I also tried the NAV ball up and down and that didn't fix it either.

I was able to get the buttons to work by ALT+TAB and back, or ALT+F12, then hovering over the debug window. If I didn't hover over the debug window, I still couldn't click on the buttons.

Incidentally, I was able to look at the input lock stack with the problem and without, and no, there's no difference in the bit mask.

Strange I didn't notice this before...

Edit: Okay, new information:

- Launching without a control part led to the situation above (where I couldn't control the buttons in any way without ALT+Tab away and back. Also, having the NAV ball open didn't help.

- When launching with a crewed capsule, bringing up the NAV Ball also allowed the buttons to be clicked on. Closing the NAV Ball caused the buttons to lock out again.

- I didn't try with probe cores.

Cheers,

~Claw

Edited January 13, 2015 by Claw

[wibou]

I confirm I have the exact same issue more or less often.

I don't think it is related to alt-tab although alt-tabbing out/in sometime fixes it. Otherwise I just switch to KSP and then back to the ship.

I really thought it was a Linux related bug (I use Kerbal under Linux), I'm kind of glad it's not.

[vexx32]

I guess that explains why I never see it, then -- the first thing I always do when changing to Map mode is to bring the navball back up. I'll have another go at it when I get back later today. For now, though, marking this one as a definite [bug].

[Renegrade]

Can I ask you to see if it'll still happen in one of the standard resolutions? Also, could you try running KSP with the -popupwindow option? Just trying to isolate variables, I guess, haha.

Still does, with or without the popupwindow thing (which was a terrifying borderlerss window :S ), and also in fullscreen mode..

Actually I saw something interesting while testing the above; I can see the altimeter briefly while trying to bring down the map icons sometimes

I was able to confirm that bringing up the navball also unjams the icons, by either pressing the little button for it, or by pressing the 'del/.' key on the numpad.

(As a note, I only bring up the navball if I'm about to maneuver, I ignore it otherwise)

[Sonny_Jim]

Still happening in v1.0 :\

I don't have to alt-tab for the bug to occur. Just launch a ship, switch to map view (which starts with the navball hidden) and try to click the filter buttons. If I unhide the navball it lets me click the filter buttons properly.

Edited April 28, 2015 by Sonny_Jim

[Renegrade]

Still happening in v1.0 :\

I don't have to alt-tab for the bug to occur. Just launch a ship, switch to map view (which starts with the navball hidden) and try to click the filter buttons. If I unhide the navball it lets me click the filter buttons properly.

Confirmed here too.