To many issues for a Beta, more like an Alpha.
Hopefully some clarity will be given regarding remapping all my 36 ships firegroups in todays stream.... hopefully.
Supercruise News #53
Zac & Bruce deliver the final Supercruise News show of the year, including deep-dive interviews with UI Designer Henry Turner & Senior Designer Tom Kewell on the Scorpion!
DETAILS
Supercruise News #53
Zac & Bruce deliver the final Supercruise News show of the year, including deep-dive interviews with UI Designer Henry Turner & Senior Designer Tom Kewell on the Scorpion!
DETAILS
Oof, low blow but we kinda deserve it I guess
While I get the point you are wanting to make here, there is a subtle, yet huge difference that makes all the difference. PC Players have paid for Odyssey. Console commanders have not.
Ian Phillips
Volunteer Moderator
Nope. There is NO excuse for spewing abuse.
If you cannot express yourself without being abusive, then do not post.
The state of the game 7 months after release is not good enough and the progress on fixing the bugs is too slow to be satisfactory or to make me want to extend any further goodwill.
That is my constructive feedback.
That is my constructive feedback.
First time poster on the forums, after two years of playing (and loving ED). Currently I am playing on my 2nd account doing basic "trucking missions" in the Bubble as my primary exploration account is useless out in the Black. So while I am not totally dead in the water, plenty of other Commanders are.
I'm not here to blast the Community Managers or developers as I completely understand the situation in which they find themselves. Instead I question the process.
Coming from an IT world there is absolutely no way we could release a "patch/update/version" that broke so many relevant aspects of an environment. This would be a massive RPE (resume producing event) in any other environment. Can you imagine your ISP pushing out a "patch/update" that suddenly stopped all even-numbered IPs from working and couldn't link to URLs with certain letters in them (oh, say, like "am")? Or your online banking not allowing for withdrawals (feel free to keep depositing though)? And no resolution day/time was given?
I totally understand that bugs happen- hidden impacts are revealed that were overlooked. I don't have sympathy for having to work over weekend/holidays to fix things given there is a way to prevent that situation from the start (and I have lost many in weekend/holiday in 35 years of IT due to both my own negligence and others).
It was mentioned in this thread and others that proper testing before release would have prevented this. Frontier has a massive, loyal following that would gladly accept the responsibility of testing a proposed release a week before the rollout. Create a duplicate environment on a test server and pick 100/200/300 Commanders to test the new features/fixes (don't include the story lines, CGs, etc). No one knows the game like the people who actually play it. Nearly every Commander here would gladly do it for free, knowing any progress gained would be wiped when the test server is reset. It isn't a matter of that option not being technically feasible, it is a matter of building/implementing the process.
The question to Frontier becomes, is making a QA process worth the effort to make the best product available to the thousands of loyal Commanders?
Again, thank you to the Community Managers for being the "face" of Frontier and working towards a resolution.
I'm not here to blast the Community Managers or developers as I completely understand the situation in which they find themselves. Instead I question the process.
Coming from an IT world there is absolutely no way we could release a "patch/update/version" that broke so many relevant aspects of an environment. This would be a massive RPE (resume producing event) in any other environment. Can you imagine your ISP pushing out a "patch/update" that suddenly stopped all even-numbered IPs from working and couldn't link to URLs with certain letters in them (oh, say, like "am")? Or your online banking not allowing for withdrawals (feel free to keep depositing though)? And no resolution day/time was given?
I totally understand that bugs happen- hidden impacts are revealed that were overlooked. I don't have sympathy for having to work over weekend/holidays to fix things given there is a way to prevent that situation from the start (and I have lost many in weekend/holiday in 35 years of IT due to both my own negligence and others).
It was mentioned in this thread and others that proper testing before release would have prevented this. Frontier has a massive, loyal following that would gladly accept the responsibility of testing a proposed release a week before the rollout. Create a duplicate environment on a test server and pick 100/200/300 Commanders to test the new features/fixes (don't include the story lines, CGs, etc). No one knows the game like the people who actually play it. Nearly every Commander here would gladly do it for free, knowing any progress gained would be wiped when the test server is reset. It isn't a matter of that option not being technically feasible, it is a matter of building/implementing the process.
The question to Frontier becomes, is making a QA process worth the effort to make the best product available to the thousands of loyal Commanders?
Again, thank you to the Community Managers for being the "face" of Frontier and working towards a resolution.
Not the fire groups, but I wanted to update you on the targeting bug. This is EDO only and all appears to work fine in EDH.
Another observation is that either something has changed on my system, or there have been some under the hood improvements to EDH (last few updates). I get higher FPS with hardly any bad dropouts or bigger FPS drops. I've even managed to up my settings to ultra at 1920x1080 at 1.25 upscaling, I've never been running this good on wine/linux since I started playing EDH. The system is an i7-2600k with 16GB of ram and a GeForce GTX 1660 Ti.
I used to get occasional stuttering and sometimes major FPS drops and sometimes smaller FPS drops for instance around stations and asteroid belts. Now I seem to hardly go under 60FPS, though sometimes it goes down to 30/40/50 FPS. In any case maybe some good news is heartening for the team, and I'm really happy and enjoying the better performance.
I wonder how bugs like the ones we see in odyssey since launch can make it to public. I mean... they are not even playing their game? We've seen some resounding examples like pop-up stations, inverted engine trails, invisible rocks. How can they slip to public release? Just curious...
Every beta using the community slows down hotbuild development. If they beta tested on the community every patch since EDO release we would still be on patch 3. So its a toss up, hotbuild development where we got a new SRV or patch 3 where things work but 5 months of hotbuild development has not been allowed.
I prefer hotbuild development personally however you then need to have clarify given to the community that what we are seeing is hotbuild development.
I agree, there is no excuse for being abusive, and that is the problem with many of the "keyboard warriors" not only on this forum, but on the internet in general.
That being said, there are also few excuses for the hot mess that is EDO. I have been a staunch supporter of the game since Alpha, and as a LEPer I didn't actually have to pay for EDO. but I can understand the anger and frustration of many who did. The official Beta for the product was (in reality) a badly disguised Alpha test, and the released product has turned out to be an appalling mess of errors, problems and bad handling of hardware.
Each successive update seems to fix some things, but then introduces more errors and breaks more things, that then need patching, and that patch fixes some of the errors and breaks others.
After years in the IT industry myself, I find myself wondering 2 things...
- Is the COBRA engine actually fit for purpose? Has the technology moved beyond it's capabilities and the upper management are too fixed in their ways to move with it?
- Do you actually have a QA team that play the game? Because some of the fundamental things that each patch breaks really should be picked up by just simply playing the game in QA.
I would also imagine it is leading to a massive amount of frustration among the developers as they see themselves constantly chasing bugs down a rabbit hole and in a world where any one thing fixed seems to break 3 others. This, along with management pressure to get the product "fixed" and stable for release to the lucrative console market must be making for a pretty toxic working environment.
Please don't feel there is no sympathy for the situation out here in the community, but also understand where the anger and frustration is coming from. If we are (as it feels) part of the agile development process of the game, then just tell us that and let us handle it accordingly, rather than making us feel like we are unreasonable in expecting a finished product.
Cool that FDev made for us such a great Christmas present which is unplayable update (last in this year). AWESOME!
How more FD can break the game which is not final product, beta actually?
Where is QA team nor even someone is testing updates that are released? I get expression that you make static images or some pre-generated videos of the release which is not tested. Really you shoud add disclaimer at next update "Go check new things but be aware that lot of new bugs will be included! Some functionality that worked can be unplayable after update!"
Thousand commanders are upset, frustrated etc. Milions ships lost firegroup configuration... well this is bad, really bad; bugs all the time.
What will be next, what we will lose again because faith in you we lost about 7mo ago...
How more FD can break the game which is not final product, beta actually?
Where is QA team nor even someone is testing updates that are released? I get expression that you make static images or some pre-generated videos of the release which is not tested. Really you shoud add disclaimer at next update "Go check new things but be aware that lot of new bugs will be included! Some functionality that worked can be unplayable after update!"
Thousand commanders are upset, frustrated etc. Milions ships lost firegroup configuration... well this is bad, really bad; bugs all the time.
What will be next, what we will lose again because faith in you we lost about 7mo ago...
Yeah, I get that you paid for EDO and so do the CMs, but they've given an answer (though really none of us like waiting) and some folks are resorting to plain rudeness. They are working on it and the only difference really is that we know they will fix update 9 and in two weeks (my guess) this will be a faint memory, but the console community still doesn't know whether there's a future for EDO on consoles (not really the point I was trying to make though).
Not trying to make a dig at anyone really, just pointing out that this is what console's have faced for a while and, maybe, remember that when the frustration flareups happen again. I mean, this update affects EDH as well, so we're all together in this misery in one way or another.Oof, low blow but we kinda deserve it I guess
Which was that there are impatient commandos on PC and consoles? I think that must be it
No information to sell as an information is weirdWhich was that there are impatient commandos on PC and consoles? I think that must be it
That, and maybe remember your frustration now when the console community flare-up inevitably happens again. Maybe we'll get a little more understanding, a shoulder to cry on perhaps.Which was that there are impatient commandos on PC and consoles? I think that must be it
Oh we're doing this again.
I think the biggest frustration is that we have yet another update where significant things that are seemingly unrelated to the current update used to work just fine and are now broken. Couple that with the fact that we are rapidly approaching the holidays where for the most part after this week is over in three and a half days, pretty much nothing is likely to be done for another three weeks or so at least.
Not really - I don't have a lot of time for PC players that rant and rage about lack of information either ... it's very much a case of:
(so yeah, us old cynics have gotten used to the lack of info and random breaks
It is what it is )