Wait, what? Is this true ... are the geo/bio sites not numbered anymore? That's terrible ... how do you keep track of which ones you've been to? How do you use them as waypoints for things like meetups or planetary expeditions?
ANNOUNCEMENT January Update - Patch 1 Announcement
- Thread starter Paige Harvey
- Start date
My 2 cents worth... I've been working for software devs for over 10 years, and see that most software development (in the real world, not some hypothetical well-run Agile Sprint nirvana -- never seen one yet!) has some new features end up getting introduced after beta/testing and into production... usually this is well intentioned, and often urged by senior managers who bypass the rules they typically set for those lower down (thinking like "it's a very minor thing, nothing can go wrong" stick it into the build too"). Its just one of those things, human nature. Microsoft and Google, etc., all have these issues too. Big or small, most development is a minefield - with the more lines of code, the greater the chances of unintended consequences from even the smallest of changes.
The reason we all get it in the feels and have it rile us up so much, is that we are fans of the game, and when things don't go to what our personal expectations are we get angry. I think it's also why the Star Wars franchise is doomed, a victim of its own massive success now with toxic fandom making it very hard for the makers to do ANYTHING right in some people's eyes - and those people's voices are the loudest. We are all losing the ability to give nuanced feedback in the social media age, its always rage, rage, rage.
So my humble opinion is to chill, submit level-headed bug reports, and not just rant in comments. Peace out!
The reason we all get it in the feels and have it rile us up so much, is that we are fans of the game, and when things don't go to what our personal expectations are we get angry. I think it's also why the Star Wars franchise is doomed, a victim of its own massive success now with toxic fandom making it very hard for the makers to do ANYTHING right in some people's eyes - and those people's voices are the loudest. We are all losing the ability to give nuanced feedback in the social media age, its always rage, rage, rage.
So my humble opinion is to chill, submit level-headed bug reports, and not just rant in comments. Peace out!
Unfortunately console software update cycles are limited by the console vendors not FDEV, I feel your pain. I'm sure Fdev would love to get the same fix out to you guys today too.
Should be fine. It updates Windows it doesn't touch your software.
No one on this thread is ranting or raging or angry. The bug reports that were submitted were perfectly level-headed. Your 'humble opinion' is not a humble opinion, it is unsolicited advice and unqualified instruction justified by false assertion, and personally I think it is more likely to make players angry than an update which temporarily breaks their game is. In my opinion.
The original update did not merely fail to 'go to what our personal expectations are', it broke the game altogether. And it broke the game when it was supposed to fix the game after months of bug tracking which has put actual game development permanently on hold. And it broke the game after a public test session which was supposed to make sure it wouldn't break the game. Just saying.
Even with the prompt fix, such an obvious -up is damaging to consumer confidence and whilst players on this forum are not angry, someone in management ought to be.
And the Star Wars franchise is not doomed. It's making fortunes.
rootsrat
Volunteer Moderator
Probably better to use the confirmed issue - fdev have been closing those duplicates as they get raised
webapp
issues.frontierstore.net
StefanOS
Volunteer Moderator
Not every one did complain about commodity prices, but on the way prices are generated. the idea is to have a more "realistic" economy. The goal is fine.
In the test that was presented different ships with same amount of cargo did get different pricing...... that's not realistic,. So maybe this is a bug and has to be reported.
I also think that FD should show us more data on the economy, f.e. what the daily need of a commodity is in a station or system and if the demand is met..... f.e. this station has a demand in PAINITE of 1000 tons a day and right now 550 tons are delivered ... so after 450 tons more the pricing will go down (f.e. -10% for the next 1000 tons). Maybe this is how it is implemented right now.... without seeing the data its hard to know
In my opinion, I would expect Frontier to be doing all they could to not make mistakes. Critical posts of Frontier wont encourage them to be open with the community.
#siegementality
Unfortunately console software update cycles are limited by the console vendors not FDEV, I feel your pain. I'm sure Fdev would love to get the same fix out to you guys today too.
FD introduced changes after the beta test, and in doing so locked in a week of console disruption needlessly though. The update consoles got was essentially untested because they gambled new additions would not be a problem.
It looks to me as if they were working on a couple of different approaches to solving the resolution time problem, one where they did all of the work as soon as you jumped in there by being able to give you instant results when using the FSS, and the other was the 'likely' state approach. With resolution performed on scan as per beta. I'd guess maybe the first wasn't quite ready for the beta subsequently becoming available and they took a punt when they included it for the production release, having to roll back to the beta option (with an update to combine 'likely' state with previous wait and see full results).
Either way it shows FD are still willing to make additional changes to tested beta code prior to production release. What I'd like to see is a form of 'User Acceptance Testing' where we have a beta they provide code, when the kinks are ironed out to mutual satisfaction the change is released as is to production. With ANY modification having another UAT pass prior to release.
Either way it shows FD are still willing to make additional changes to tested beta code prior to production release. What I'd like to see is a form of 'User Acceptance Testing' where we have a beta they provide code, when the kinks are ironed out to mutual satisfaction the change is released as is to production. With ANY modification having another UAT pass prior to release.
![[DAX]](https://d2aefvhu2f0gi9.cloudfront.net/data/avatars/m/192/192803.jpg?1553527180){kind=avatar}
This is useless.
https://issues.frontierstore.net/issue-detail/80 - marked as fixed. Really - it is not, the map is still broken in the same way.
Many tickets marked as "Expired" without any actions taken. What's the point of this tracker?
rootsrat
Volunteer Moderator
Probably better to use the confirmed issue - fdev have been closing those duplicates as they get raised
webapp
I couldn't find an existing issue for this, hence I've logged a new one. Do you have a link by chance? I agree it's better to gang-vote an existing one rather than spreading votes across duplicates.
If you click the link you just quoted ...
Edit: One day they will fix those misleading snippet previews, one day
Stuttering issues while the game is still stable, playable and working is nowhere near "broke the game altogether". I play on PS4 pro and PC, and while the ps4 pro has way more stuttering than the pc version pre-patch, it's still playable without any other issues.
Thus it's not "broken".
I don't see anything broken there - the moment you selected each 'destination' the distance was updated correctly - is that not what was expected?
It should select it after the search and put the cursor on it as it was before it was broken.
It seems this was broken long enough for people to forget how it used to be...
It's not the community's responsibility to encourage Frontier to be open with them. Frontier should be open with the community in any case.
The update took a game that ran smoothly and made it stutter so as to be unplayable. You ask someone with a rail gun. Ergo the update broke the game. It broke it enough for Frontier to bring out a PC patch within hours.
I agree - looks fine, a system name was searched & the map took you there, but the previously SELECTED system was still selected, until you deliberately select the newly searched system. That's how you search the map without losing system lock. Would be a real pain if searched systems were automatically selected.
A PC patch to fix an annoying bug is nothing but normal, frontier did it numerous times before.
Again, while it hinders aiming rail guns, it's still not "broken". It's a bug, it's super annoying, sure. It's not breaking the game. You can do other things while waiting for the patch if you're on console, cause again the game is working. Not broken.
But maybe in english you use broken for things that aren't broken, it's not my native language so maybe it's just a use I don't know