Stop and Take 5 for sanity.

Ok, so from the title, this is sounds like it is an anti-negativity thread right… No, it’s not. Don’t get me wrong, negativity makes me reach for my teddy bear and seek solace in a quiet corner, but it’s not my place to say negativity is bad and to be honest many valid points are being made in seemingly negative posts.
Righto, what on earth is this post all about. Well, it’s more about MHO on how we have ended up with quite negative forums at the moment and what we can do to improve things going forward, and I promise, I’m not going to preach to people about how they should post!!!

The perfect storm:
Going into beta 1.1 we had a number of already sensitive topics raging, shield cells, Python nerf and some concern of new content etc. Once beta dropped we had a new heat mechanic that was a bit hard to get used to, the Python nerf finally hit and collision damage went weird on us, together with some silly bugs in the community goals and cartography. My recollection is that testers were posting the issues thick and fast and were possibly quite harsh with their criticism (I re-enforce, most of the criticism was still right, it was just tainted with frustration).
I now drift to the subjective, FD developers read beta forum first few days and think, holy cow this is depressing, lets not read all this and carry on as we were and just fix the tickets we see come in. Meanwhile the community is madly comparing issues on the forums and posting videos with oodles of evidence that no-one (ok not fair, few people) is looking at. Finally tickets start being raised as we get a handle on what we are seeing. It takes FD time to collect related tickets and start seeing the picture we all saw early on in the beta phase. Beta 1.1 goes live, some of the issues are thought to be fixed because they were never understood fully and in fact aren’t fixed at all. Live players get frustrated, beta tester feel like they may as well not have been there, even the most patient CMDr is going to have some negative vibes going on ;)

Great history lesson… How do you propose we fix it then genius?

Glad you asked ;) There isn’t a simple fix, but there are thing we could do better I think

1) The beta testing has got to work better for all parties. Feedback needs to be fast and efficient. I think the following could help here
a. We could start with increasing the next beta by a week. Sure that means the live servers have to wait longer, but I think it’s worth it overall. Also, beta period needs to be judged in context of the changes. If we really are looking to judge balance changes, we need to give testers time to get a handle on new mechanics before they can truly judge effectiveness.
b. We need a mechanism to summarise what’s been going on in the beta forum so the devs can get an at a glance view and dig into issues that need looking at. Can we have a thread on the beta board that only mods can post to and have a volunteer mod to write a post every 2 days summarizing the top issues they are seeing in beta, ideally with links to example threads? I’m not a mod, but I can (temporarily at least) spend that kind of time to help the process next time round (1.2).
c. I saw that FD tried to set out what they wanted us to test in the beta forum this time out. That was great to help, I’m wondering though if we should think about having a feedback thread in the beta forum that has a fixed format, eg: You got to post and you have to select the test mission you are running, the ship etc you had and a short description of the feedback. This helps structure responses a little.

2) Community feedback by FD.
a. We currently have the weekly dev posts which are really good. However, during beta perhaps every other day a state of the beta post could be made summarizing what is being looked into and what is ticked off the list for testing in the next hot fix. Would help stem the “Talk to me devs…” threads that popped up during beta.

I have other thoughts, but this post is getting long enough as it is. People may disagree with my analysis and that’s great and all fine. I do think we can improve the way we build this game together and I think we need to look at how we can improve this for everyone next time around.

Thoughts….. (Be gentle with me, I am sensitive you know!)
 
Last edited:
The only reason to participate in a beta would be to prepare yourself for what you're going to have to adapt to when it gets released prematurely into the live game.

The track record is clear.

Anticipate the damage and be prepared to survive it.
 
Ok I inderstand what you are saying, my point is, even if it has been that way, surely we can change it to be something better? It can change can't it?
 
Wow, I wrote a whole thesis, it got one comment and disappeared off the bottom of the forum lists!! I need to think of better thread titles!!!!!
 
Can I point you to this one ? On your suggestion re beta testing, I don't think an extra week would have helped, as TitusBall has said in the thread you release when it's ready not when some oik in marketing says so.

https://forums.frontier.co.uk/showthread.php?t=112593&p=1749564&viewfull=1#post1749564

Point taken, I meant in the specific case of this Beta, my gut feeling is with an extra week FD would have had better data to make a call with. However, I totally agree that the beta should be a test of the readiness for release, meaning if it isn't ready. more tweaks and testing happen.

Thanks for linking to Titus's post, I don't disagree with anything said really, I'm just focusing on what we the community can do constructively and examples of how maybe we can create better comms with the devs. Maybe I'm way off base, it just seems if something doesn't change, we may lose a game which has so much promise for reasons that don't justify the consequences if that makes any sense!!
 
What is FD's Go/No Go procedure I wonder? By what criteria are they judging the readiness of their code? Because If you read the beta forum a lot of the problems we are all experiencing were reported during the beta period.
What is the point of a 2 week beta period anyway. Thats nowhere near enough time to identify and eliminate bugs.
 
Have not had chance to play 1.1 yet, but i was watching the beta forums.

It strikes me that this was not the way to run a beta, but hindsight is a wonderful thing of course :)

It looks as though some of the live issues are there in the beta, so FD made a decision to ignore the feedback and go ahead anyway, thats how it looks anyway. More worrying is there seem to be changes and their effects which are not listed in the patch notes, that might suggest the patch notes are not complete or are a synthesis of reported issues with their change log fix, they shoudl really be othe other way roundl ALL changes in the change log with their associated reported issue - I realise that is potentialy a much larger list and harder to manage, but how else would you test effectively? I am only guessing with that.

It feels like a week long beta was a hard goal and quite possibly the first big patch since post live has quite a lot of eyes on it, it looks like the devs were pretty well engaged in the beta forum, not in all cases, but they were certainly not asleep at the wheel. Did the devs really need more time for this one? Its inevitable that issues will get through, no matter what. FD need to recognise them, say that they agree and then fix asap, it would be helpful to beta testers if FD also pointed out why the issue was not picked up in the beta forum/test.

I wonder if FD need to change their beta access and allow more people to test rather than just those who were previously beta backers. This is, one would hope, a fairly light patch in the face of what is to come, 1.2 will be bigger I think, and probably beta over a longer period, FD shoudl be doing a wash up over 1.1 and hopefully providing us some feedback on the process and what, if anything, needs to change.
 
This isnt really a beta at all is it.. Its just early access to the next release version - which is fine as long as they actually took more note of what was broken
 
Have not had chance to play 1.1 yet, but i was watching the beta forums.

It strikes me that this was not the way to run a beta, but hindsight is a wonderful thing of course :)

It looks as though some of the live issues are there in the beta, so FD made a decision to ignore the feedback and go ahead anyway, thats how it looks anyway. More worrying is there seem to be changes and their effects which are not listed in the patch notes, that might suggest the patch notes are not complete or are a synthesis of reported issues with their change log fix, they shoudl really be othe other way roundl ALL changes in the change log with their associated reported issue - I realise that is potentialy a much larger list and harder to manage, but how else would you test effectively? I am only guessing with that.

It feels like a week long beta was a hard goal and quite possibly the first big patch since post live has quite a lot of eyes on it, it looks like the devs were pretty well engaged in the beta forum, not in all cases, but they were certainly not asleep at the wheel. Did the devs really need more time for this one? Its inevitable that issues will get through, no matter what. FD need to recognise them, say that they agree and then fix asap, it would be helpful to beta testers if FD also pointed out why the issue was not picked up in the beta forum/test.

I wonder if FD need to change their beta access and allow more people to test rather than just those who were previously beta backers. This is, one would hope, a fairly light patch in the face of what is to come, 1.2 will be bigger I think, and probably beta over a longer period, FD shoudl be doing a wash up over 1.1 and hopefully providing us some feedback on the process and what, if anything, needs to change.

I'm not sure I 100% agree. Yes FD were present in the forums, but I'm not sure proper communication either way was going on. If the issues were truly understood by FD then they must have known the call to release it live was pretty flawed. There were so many videos on the collision damage issue that I can't believe they watched them and then released with no fix. Now maybe they thought they fixed it but didn't have time to release a beta hotfix for test. This is where my minimum 2 week beta comes from. Time to check for issues. If we experience nothing in 2 weeks we should be good. If we experience something, there should be time to make a call on if the release date is held.
 
I'm not sure I 100% agree. Yes FD were present in the forums, but I'm not sure proper communication either way was going on. If the issues were truly understood by FD then they must have known the call to release it live was pretty flawed. There were so many videos on the collision damage issue that I can't believe they watched them and then released with no fix. Now maybe they thought they fixed it but didn't have time to release a beta hotfix for test. This is where my minimum 2 week beta comes from. Time to check for issues. If we experience nothing in 2 weeks we should be good. If we experience something, there should be time to make a call on if the release date is held.

fair points, it does look like Michael has 'fessed up that the collision damage bug was supposed to be fixed between the final beta and live but somehow slipped through, which I think confirms your point about it not being a beta test (in the professional sense) and just a preview early access with some feedback, for me a beta is only complete when you have a beta deployed you are not going to change anymore, no 'we can fix that between now and live', unless its a really trivial system with few consequences and not hard to fix later if it goes wrong - colision damage would not, to me, seem to fit that description ;)
 
Seen this before... Why go live with this total balls up... people have weeks of gameplay and have lost a lot because FD and the devs haven't addressed the issueses or programs within the environment. They shown little or no regard to their player base.

Disgraceful. :mad:
 
Last edited:
1) The beta testing has got to work better for all parties. Feedback needs to be fast and efficient. I think the following could help here
a. We could start with increasing the next beta by a week.
b. We need a mechanism to summarise what’s been going on in the beta forum
c. I’m wondering though if we should think about having a feedback thread in the beta forum that has a fixed format,

Thoughts…..

I asked about a bug feedback thread in the BetaForum since this is the way to get the most feedback.
The answer was a long the line: "No we have our ticket system and want you to create tickets" or in other words they want to educate the player to create the tickets for them. That works when the ticket system is an integrated part of the game .. simple and easy to use but it wont when this is not done and especially nto when most made the experience that their tickets are not processed in resonable time.
-
So eighter they have to create that user friendly report system or they should generate a Forum thread and YES one on FD side has to read this thread and create Tickets out of it since FD want to work with tickets only.
-
Seeing how they are present and responding in the Forum to a number of burning topics (see the non working background sim) my impression is that they welcome to get lesser bug/trouble reports. No ticket no work for them. Broken releases..so what?
-
But obvious users have ticked the issues we see in v1.1 (read in various thread). So it's not even that it wasn't reported but their ticket system is so inefficient that they missed the important feedbacks.
 
Last edited:
I asked about a bug feedback thread in the BetaForum since this is the way to get the most feedback.
The answer was a long the line: "No we have our ticket system and want you to create tickets" or in other words they want to educate the player to create the tickets for them. That works when the ticket system is an integrated part of the game .. simple and easy to use but it wont when this is not done and especially nto when most made the experience that their tickets are not processed in resonable time.
-
So eighter they have to create that user friendly report system or they should generate a Forum thread and YES one on FD side has to read this thread and create Tickets out of it since FD want to work with tickets only.
-
Seeing how they are present and responding in the Forum to a number of burning topics (see the non working background sim) my impression is that they welcome to get lesser bug/trouble reports. No ticket no work for them. Broken releases..so what?
-
But obvious users have ticked the issues we see in v1.1 (read in various thread). So it's not even that it wasn't reported but their ticket system is so inefficient that they missed the important feedbacks.

Thanks for that feedback, I did not know you had suggested a similar thing before. For me, there is some solace in the speed with which issues were addressed with the live version, but still, I firmly believe the beta was somehow a missed opportunity that should be fixed in the future, no matter if it's via my suggestions or something completely different.
 
I feel utilising something like BugZilla, publicly, would address a lot of the problems.

I'd also like to see FD publish their test scenarios we can then fill in the gaps with a community test-pack or set of smoke tests.

I suspect I'm not the only person who plays this game that deals with this sort of thing as a day-job.
 
OP you've stated the thoughts I've had many times.

I don't expect the Devs to get involved with the threads in the forum, that could turn into a testosterone contest I would not want to read.

But a general feedback on the acceptance of specific problems, identifying the good ideas that will, or will hopefully be, included into future builds would be greatly appreciated.

Let us know that what we say is read, understood and being considered.

A good ask.
 
Looks to me like the devs operate in a scrum environment and have sprints (most big business use this).

The problem is when you fix the timescale of the sprints and release regardless of the bugs outstanding so you can start the next sprint.

The sprints have to be able to cope with problems (waterfall approach would help!) and they really shouldn't be releasing a patch when they know the patch is broken. The major problems were widely reported in beta by beta testers so there is no way they can say they didn't know. They just didn't factor in the time required to fix it before the sprint ended.
 
Back
Top Bottom