Long time PC players vs. new console bugs

[Gaarst]

Troubleshooting an issue on the PC version of KSP is often pretty straightforward: either ask someone who knows because he has already seen this issue, or, if you're feeling confident, take a look at the game files and change some values to fix it yourself (especially for cfgs files which are easy to edit).

For console, this gets harder: no one is experienced enough on console to know what a possible console-specific bug might be caused by, and no one besides Squad or FT staff is able to "crack open" the console game and tweak some stuff down there.

I don't know a lot about console gaming (being a long time PC player, merely casual on console) but I'm pretty sure opening up a game and changing some stuff inside is at best impossible, at worst illegal. So we're ending up with an issue where now and in the future, for all new bugs, no one except Squad or FT staff will be able to help console players (whereas pretty much anyone with decent experience on PC can help anyone having an issue) which will in turn will probably cause some problem in the way bugs are handled and fixed: a large part of reported bugs on PC are already known and the community helps a lot by filtering these bugs and therefore allowing Squad staff to focus on actual new bugs that no one can solve (some bugs might actually be worked around, or even completely solved, by the community, I'm thinking about Claw's Stock Bug Fix Modules before he was hired by Squad and Slashy's help with wheels after 1.1). On console all the workload will go directly to Squad and FT with no help from the community available.

For console, even the most experienced KSP players and modders have no idea how different the game is from the PC version and some bugs that are known and can be fixed on PC might become a complete mystery on a console version (not even talking about the differences between the different console versions). So Squad and/or FT (whoever is handling bugs on console) will have a huge debugging work to do, maybe even greater than what is currently done on PC considering that console ports have chances to be at least as bugged as the PC releases.

Now, I don't claim to have a solution to this: I actually have no sensible idea on how to solve it (I don't believe releasing the console code in open source is sensible ); but I believe a discussion can be made on this and some solutions might possibly arise throughout.

Having an official and active Flying Tiger representative on the forums will probably become necessary to address these kind of issues, or to bring new elements in that kind of debate.

[Violent Jeb]

[redacted, done]

Edited August 16, 2016 by Violent Jeb

[Majorjim!]

You mean in the dev notes? Nothing in there..

 Just have a look at the console support forum here..

people are already getting refunds for the corrupting save bug and not a single word from Flying Tiger or Squad yet.