Prioritizing Bugs in the Bugtracker

[Nightside]

1 hour ago, Anth12 said:

bug fixing DLC

I agree with what you’re saying and appreciate that others are using the bug tracker, but charging extra to fix existing bugs would annoy a lot of people.

I hope that BG will be successful enough for @SQUAD to add some staff to allow them to seriously work through the backlog, or at least clear out outdated issues.

[UomoCapra]

On 6/12/2019 at 3:06 AM, Anth12 said:

They dont seem to be listening anymore.

 

Thank you very much for sharing your feelings about the game. The KSP crew is always working hard on fixing bugs and improving the performance of the game and we try to include as many fixes as we can with every update and patch we release. For example, in our last patch (1.7.2) we included 70 bug fixes between the base game and the latest expansion.

Currently we have put more resources on QA than ever before and the team is continuously working to identify problems that could affect the experience in the game and solve them as swiftly as possible. Sometimes a few issues might go under our radar and there is where our bugtracker plays an important role and that’s how you can help us identify and prioritize bugs and issues.

Thank you for raising your concerns. We appreciate your enthusiasm and your passion for KSP, and hope we have given you some peace of mind. 

[Anth]

@UomoCapra Thanks for responding. If you need some help get in contact with me

[OHara]

On 6/6/2019 at 1:27 PM, Nightside said:

what happens to bugs reported in previous game versions that are not resolved? Do they need to be resubmitted?

A significant fraction of recently-fixed bugs were reported more than one version ago, so it does not seem that we need to resubmit. 
Some bugs get updating comments "still present in version x" (example) but that does not seem to be required (example).

Private Division seem to be going through the list over the last two weeks, trying to reproduce old bugs.  Some, they report as 'Resolved' and 'Closed' and the original poster comments to say they are not correct.  Maybe they are fixed with the forthcoming 1.7.3, or maybe we will need to resubmit those.

It is helpful when @SQUAD cites the change-log entry, or other similarly brief explanation, that gives the reason to mark a bug 'ready to test'.  Some  of the 'not fixed' bugs have the bug reporters saying "nothing changed' what am I missing?"

If anyone prioritizes by upvotes the sorting is maybe a little stale.  Bugs that were fresh when this announcement was made are still high on the list, so several involving Making History (M.H.) .  Some recently-appearing bugs are more important, and maybe easier to fix while the changes are fresh. 

Spoiler

20745  +29 Request: consistent mating diameter for 1.25m Parts
18108  +28 Landed craft (in vicinity of Island Runway) re-load far above ground
17984  +25 Joysticks not recognized under Linux
19376  +22 M.H. Structural Tubes missing config, causing drag
17912  +21 Request: unlock Personal Parachutes with a Building Upgrade
19427  +20 Landing-gear suspension oscillates forever
21278  +19 Request: switch to high-res mipmaps earlier when we zoom-in
20762  +18 M.H. Triangular Panels do not place in mirror symmetry
20346  +17 Using editor for extended periods results in performance drop
20268  +16 M.H. Round KV- pods have very high drag
19232  +15 Wheel-suspension retracts when same-craft parts are too close 
21006  +15 Request: "Warp to maneuver" button available in flight-view
20683  +15 Revamped engiens have drag unrelated to their visible shape
20423  +14 Mk2 Fuselage textures flip when the need not flip
18126  +14 M.H. Structural Tubes don't shield objects inside of them
19231  +13 Wheels too grippy (maybe resolved; 22147 says wheels to slippy)
13101  +13 Flickering orbit lines in Tracking Station
20840  +13 Revamped rocket motors have incorrect Centres of Mass
18289  +12 Landing gear bump on relaod or ending time-warp
19597  +12 EVA Kerbals can become unresponsive on console
21314  +12 Request: 1.25m Engine Plate
21915  +11 Interstage fairings now hold on to decoupled parts
20266  +11 M.H. Drag on parts node-attached to Structural Tubes (duplicate)
20513  +10 SAS orients control-point-part to point from *root* part to target

I up-voted the new inter-stage fairing bug for this reason; there are probably others that deserve more attention.

[OHara]

Several troublesome bugs have been fixed over the past few months.

Sometimes, the status of a bug becomes "Ready to Test" with a message: "We have made changes in this last release and would like your feedback please."
while the submitted craft-file or save-file shows the same behavior as when the bug-report was submitted. 

It would be helpful to say which particular "changes in the last release" are thought to be relevant, by copying the relevant entry in the change-log for example,
or mentioning some new behavior that might make the bug-or-feedback no longer a problem.

[pmborg]

Hello KSP team ( @UomoCapra ),

 

Have 1791 open bugs or 10.000 or 100.000 is the same, this is something that is not manageable, in my opinion.

The big companies normally have a minimum amount of bugs that can be in open state, before go to a next major release.

 

Probably the reasons were that until now, there was more focus on new features than solve problems, which is normally to increase the immediate sales.

But the world is not perfect, what really matters is that at least we are now, talking about correcting bugs, that might affect the sales of next releases DLC and so on.

 

 

I know that there are a lot of persons opening bugs for 1.4, 1.5, 1.6 and so on, this will lead to chaos.

From my experience the KSP team should apply the principle: "divide to conquer":

Filter the list somehow, with one criteria, for example only bugs for 1.9, all platforms and give them priority.

 

 

The past I really don’t care much, what I believe is that all community want is most of all, is to have them fixed in 1.9, before move on to next release.

 

My sincere congratulations of the work being done so far, the future can be even better!!

 

 

 

 

 

 

 

 

 

 

 

 

Edited February 16, 2020 by pmborg

[Lisias]

1 hour ago, pmborg said:

I know that there are a lot of persons opening bugs for 1.4, 1.5, 1.6 and so on, this will lead to chaos.

Alternatively, and this suggestion need a lot of thinking on their side before being really considered (how many people are still using older KSP? Why? Can we really trust the Unity telemetry without getting caught on a Survivorship Bias?), backporting some fixes as "hot patches" to these KSP versions can be a good idea, leveraging the gap between older KSP and newer, making it feasible the user reconsidering and migrate. Issuing new releases for KSP older versions (1.4.6, 1.5.2, 1.6.2, 1.7.4, 1.8.2) will be probably not cost effective, but "hot patches" may be. Microsoft did this with some success on the Windows 95 times (OSR1, OSR2, etc).

Public Bug Tracks has a P/R value, refusing bugs for older KSP may help on the technical level, but could have some backslash on the P/R one. However, I agree that the current status quo is less than effective - and in the end of the day, if you don't have a way of win the war, all that can be done is to choose the less painful way to lose it.

 

1 hour ago, pmborg said:

The past I really don’t care much, what I believe is that all community want is most of all, is to have them fixed in 1.9, before move on to next release.

The problem is that sooner than later, whatever you are doing will be the past, and so you will care for it.

Every single newbie will be a veteran soon. And if you don't care for your veterans, they leave - eroding the Community that you need to help you supporting the product. KSP has a long term gaming mechanics, I know people that play their savegames for more time than I have an account here. These guys have a huge knowledge about how things works, and even these guys being a minority around here, they are the foundations that in the past made this Community to thrive.

Of course, nothing of this makes sense on casual gaming (like Angry Birds, Happy Farm et all), where gamers happily exhausts the game potential and then wants a new release to fulfil their wishes. There's nothing wrong on this game model, but I don't think that KSP would thrive on it (do you know Space Agency for Android? Hell of a nice game, good for some playing on wait rooms or bank lines - but I never managed to like playing it on my TV using my Android setupbox).

Edited February 16, 2020 by Lisias
Of cuorse, a tyop!