Buttons not working in carrer mode

[Silverwood]

Hello

Ok I have a slight issue  - as I was having issues with the admin building bug, I updated to the beta version, the admin bug is fixed - but three things have happened - 1. A windows bug which caused the Pc to shut down and restart - may be nothing to do with KSP, then after playing for two days whilst in game the buttons for options from the crew (cre report etc) stopped working and , finally at the same time the add manoeuvre button stopped working. But after loading the save, they worked ok again.

Playing the previous version had no issues apart from the admin bug.

Any ideas?

Keith

 

[diomedea]

To be honest, no idea at all; but I also doubt anybody may identify what caused the issue from only the information provided in the opening post.

Let's start with one thing: sometimes we find what can be called "intermittent bugs", weirdnesses we are unable to identify the cause and, trying to reproduce in the same situation, don't show every time (or even never again). There is no chance to diagnose bugs unless reproducible, so these intermittent ones are very hard to squash.

The above brings to consider one of the most important pillars with testing: reproducibility. Who has to examine the issue has to know the correct situation to make the bug appear. Among KSP testers, the consolidated procedure to report an issue is to provide a detailed explanation of the situation, possibly a savegame that leads to the appearance of the issue, KSP settings if appropriate to the issue, a detailed list of steps to perform to arrive at the bug, criteria to identify the bug occurrence (e.g. what is expected against what is produced by KSP).

Another pillar with testing is appropriate documentation of the issue, e.g.: showing pictures (or even better, videos) while the bug is occurring; making tests of your own and providing results showing when the bug shows or not; if appropriate, external references providing evidence about the expected results. Plus of course the KSP logs as proper: often times logs provide information about KSP workings, showing if something went wrong (e.g. the various exceptions being logged with output_log.txt). Plus, mandatory information about the KSP version installed and the OS used (sometimes corroborated by further details, e.g. GPU brand, screen resolution, input devices used...).

Final and very important pillar: no add-ons if trying to isolate a stock KSP bug. Actually, even better to run a virgin KSP install and try if the bug shows on a brand new game, rather than one you may have running (and could somehow have been corrupted).

Most of the above is described in the guidelines for stock support & bug reporting. Should your bug be reproducible on your side, best you could do is to actually use the official bugtracker and fill all available information as suggested above. This forum section may give you help about fixing what may be wrong with your game or KSP install; but won't solve any real KSP bug: those have to be reported with the bugtracker.

[Silverwood]

Ok thanks. I am not intending to be a tester for the beta, I have only had the game a week, I installed it to stop the other bug. I have tried the same save and neither issue has happened - so perhaps it was something else. However if it happens again, I will follow your suggestion on reporting, etc.

I only post the issue in case anyone else had a similar issue.