Staging can overlap the exit icon in the editor

[Daveroski]

When enough stages are on a vehicle to require scrolling through staging, the topmost stage can overlap the exit icon requiring the user to scroll the staging to be able to see the icon properly and activate it.

[Bilfr3d]

Please read this thread and provide a bit more info

Including screenshots, KSP version and build and also graphical settings such as what resolution you are running KSP at.

Cheers,

ToTheMun

[Daveroski]

Please read this thread and provide a bit more info

Including screenshots, KSP version and build and also graphical settings such as what resolution you are running KSP at.

Cheers,

ToTheMun

Here's an idea... Why don't you try it for yourself then get back to me if it happens on your screen too. I find that increasing the size of the UI makes it more noticeable.

[vexx32]

This is a known issue, and has been around for several versions. It's perfectly possible to click through the staging display; the buttons will still function, as far as we can tell.

However, in future, we do request that you follow the posted guidelines (see the stickied thread ToTheMun kindly linked) when starting a thread in the Support forums. The more information that is available, the faster a problem can be resolved.

[Daveroski]

So for every bug I come across, I should post a screen shot, which means opening an account elsewhere because I can't upload screenshots directly and I should find my logs and do the same for those.

And after doing all that, you get to tell me, 'it's a known issue..'

How about I do what I've been doing, find a bug, get told it's a known issue, job done?

If someone says.. Ooo that's new! then, I can go and do the extra work and help the developers with whatever they need.

But do all that for every bug, the vast majority of which are already known... not gonna happen. If it comes to that and the red tape is more important than getting the game fixed, I'll just let 'em get on with it. Instead of spending game time without a single mod, trying to reproduce bugs so I can report my findings

[Master Tao]

Often we can't tell whether it's a new issue until we have good information. You can also read the appropriate threads for Known Issues:

• Known Issues & Self-Help, which links to:
  
  • Cross-Platform Issues
    
  • Windows 64-bit Issues
    
  • Mac OS X Issues
    
  • Linux Specific Issues
    

  [*]How to Get Support (modded installs)

  • The Other Linux Thread
    

The staging list overlap issue is actually mentioned in the Cross-Platform Issues thread – before 0.25, it caused worse issues than not being able to click the exit button.

Also, websites like Imgur do not require an account to upload images – only if you want to edit, remove, or reorganize them later.

[vexx32]

Also, for uploading files, you can use any number of sites that do not require registration. http://www.imgur.com/ is a popular and pretty easy to use website for uploading pictures, and we tend to recommend http://www.pastebin.com/ for log files (although there are many similar websites out there you may choose to use instead).

And as Tao mentioned, while we can sometimes recognise an existing issue right away, often we can't be sure without the additional information.

[Claw]

So for every bug I come across, I should post a screen shot, which means opening an account elsewhere because I can't upload screenshots directly and I should find my logs and do the same for those.

And after doing all that, you get to tell me, 'it's a known issue..'

How about I do what I've been doing, find a bug, get told it's a known issue, job done?

If someone says.. Ooo that's new! then, I can go and do the extra work and help the developers with whatever they need.

But do all that for every bug, the vast majority of which are already known... not gonna happen. If it comes to that and the red tape is more important than getting the game fixed, I'll just let 'em get on with it. Instead of spending game time without a single mod, trying to reproduce bugs so I can report my findings

And as Master Tao pointed out, a few of us have spent many hours collecting known issues. Many of your problems you've been asking about (that I've responded to) are also linked in my signature as well as stickied at the top of this forum. And as Vexx pointed out, I've even listed free places to post the information we ask for, which don't require email address, accounts, or money in the bug report thread here.

Also, please bear in mind that if you didn't know it's already a known issue, then it's likely that someone who is trying to help you might not know it's already a known issue. If someone doesn't know it's already a known thing, then please don't fault them for asking for more information. We all want to help, but don't forget that we are KSP players just like you. Getting upset at people asking for clarification on a problem doesn't help anyone fix it.

Cheers,

~Claw

[Bilfr3d]

So for every bug I come across, I should post a screen shot, which means opening an account elsewhere because I can't upload screenshots directly and I should find my logs and do the same for those.

And after doing all that, you get to tell me, 'it's a known issue..'

How about I do what I've been doing, find a bug, get told it's a known issue, job done?

If someone says.. Ooo that's new! then, I can go and do the extra work and help the developers with whatever they need.

But do all that for every bug, the vast majority of which are already known... not gonna happen. If it comes to that and the red tape is more important than getting the game fixed, I'll just let 'em get on with it. Instead of spending game time without a single mod, trying to reproduce bugs so I can report my findings

You want the bugs resolved, don't you? Then:

follow

what

support

helpers

are

telling

you

to

do!!

If you can't put up with following those steps to resolve a bug, or provide more information to diagnose a bug, then the bug is unlikely to be resolved/diagnosed. Additional information such as screenshots and logs are required as to diagnose what is happening in your game, what mods (if any) you are using (in which case if you are using mods, the thread will be moved to modded support), what you are doing in your game for that log/scene, crash reports for that log/scene, and also to visually see what the bug is as the bug is not ALWAYS replicable on other systems. It depends on the users specs, what renderer they are using and a bunch of other variables.

[Daveroski]

You want the bugs resolved, don't you? Then:

follow

what

support

helpers

are

telling

you

to

do!!

Don't

answer

any

more

of

my

posts

you

are

rude

patronising

and

annoying

While I am seriously trying to help the devs sort out the game, you just keep showing up with annoying remarks and patronising attitude.

You have annoyed me to the point where nothing you say is relevant any more.

If you had taken a moment to see that you had annoyed me and made some effort to apologise, I could have let it go But this post was the last straw.

So I'm asking you in front of the whole forum.

Will you please stop answering my posts?

[Commander Jebidiah]

I think this thread has gotten a bit out of hand and you should all get back on topic.

[sal_vager]

Known issue, worked around by scrolling the stage list downwards with a mouse wheel or the page down key, very low priority.

Thread is devolving into unnecessary arguments.

Closing.