Yes I understand
.
Report issues using the Issue Tracker
- Thread starter Paul_Crowther
- Start date
.@sallymorganmoore I noticed that the earliest issue I previously linked to (https://issues.frontierstore.net/issue-detail/41748) has expired, but I've also found a few more duplicates this morning - in addition to the previously reported links, I also found:
While I lack the means to verify that each of the other commanders had a bounty or fine while trying to rebuy, it stands to reason that such fines are highly likely to accompany whatever action got their ship blown up in the first place, so I'm confident that everyone reporting the scarlet krait will have that factor in common. My hypothesis is that those who did not incur any fines/bounties before attempting to rebuy their ship, also did not experience the scarlet krait, and therefore had nothing to report
As always, I hope that helps! o7
sallymorganmoore
Senior Community Manager : Elite Dangerous
Oh it really, really does. Thanks for taking the time. I'll discuss things...don't like it when there's snakes involved so we really need to iron this instance out for sure.
I've never been to a system that needed it before. I would thank you, but you seem kinda douchey about it.
So, you're an exploration virgin? Never been in a previously undiscovered system until now?
That's actually quite cool
I did all my exploring pre-FSS. Im doing it again for exo-biology!
Hey if you guys are wanting people to vote on issues as well. You need to raise the vote limit well above 6 votes. 6 simply is not enough. I know you are trying to get feedback on the issues. Gimping votes is not a good way to go about it. Imo it should be doubled at minimum. At most 20.
So what exactly are the parameters for "enough votes?"
The brand new "Buy and Store Module" feature apparently only buys one module, despite clicking it a number of times. This issue was opened on Aug 19 2021, less than a month later it's been "expired". Expired despite 13 separate people posting reproductions on the issue in the two weeks after it was opened.
Or is this "working as intended"? You need to have a couple hundred people vote on something before you lift a finger to even reproduce an issue internally?
The brand new "Buy and Store Module" feature apparently only buys one module, despite clicking it a number of times. This issue was opened on Aug 19 2021, less than a month later it's been "expired". Expired despite 13 separate people posting reproductions on the issue in the two weeks after it was opened.
Or is this "working as intended"? You need to have a couple hundred people vote on something before you lift a finger to even reproduce an issue internally?
This is one of the reasons I think the vote limit needs to be increased. Many issues are left to die simply because they can't be voted on from users having to prioritize what issue they think is more important. This is also why minor bugs like yours go years without being fixed. They don't get the attention they need.
It's counter productive. This is probably some really simple logic error in the client, that could perhaps be fixed fairly trivially. Odds on it would take more time to write the regression tests than to fix the bug. Yet, fixing "minor" things like this would go a huge way towards good will in the community. People who are bringing this up lost something like four weeks (or more) of wait time getting faction modules, and this is being implicitly devalued by "the system" (after all, someone implemented "the system").
If they were addressing every voted-on issue and actively looking for more issues to fix, I'd agree that more votes would help.
But they're not - the voted issues are stacking up faster than they can identify and fix them. More votes would only compound that issue, while giving many people the illusion that they should be fixing the issues faster than they are, leading to an even more frustrated player base.
More votes will not make the process go any faster
But they're not - the voted issues are stacking up faster than they can identify and fix them. More votes would only compound that issue, while giving many people the illusion that they should be fixing the issues faster than they are, leading to an even more frustrated player base.
More votes will not make the process go any faster
Received one 1000 fine to release the cargo near the station , the problem is the cargo was empty? bug?
update 7.01 released today.
i was doing an assassination mission and was fleeing the camp from the guards when the servers wen down... after the update i called an apex shuttle to go to the station where i have my ship parked, but the apex shuttle won't leave the place where it landed... frameshift drive cancelled it says... i don't know if it's a bug but i called another one shortly after and the same problem happened again... i'm in the Dharai A 3 planet, just outside the Franklin Mineralogic Complex... Strange thing...
i was doing an assassination mission and was fleeing the camp from the guards when the servers wen down... after the update i called an apex shuttle to go to the station where i have my ship parked, but the apex shuttle won't leave the place where it landed... frameshift drive cancelled it says... i don't know if it's a bug but i called another one shortly after and the same problem happened again... i'm in the Dharai A 3 planet, just outside the Franklin Mineralogic Complex... Strange thing...
Yea but the issue without votes tends to become expired
Suddenly unable to outfit items moved to my Fleet Carrier after Update 7. Initiated items tansfer to FC, shows up in stored items, but when I go to outfitting they do not show up and even the hardpoint diasappears (Horizons). In Odyssey the items do not even show up in stored items? Is this a new /known error/bug???
Last edited:
Ozric
Volunteer Moderator
Someone has gone through and manually expired a load of issues, around the release of Update 7, rather than the "automatic expiry after 30 days if the requirements are not met"
Of the latest cull that has taken place this is what my first page looks like. There are 8 "Expired" issues. Only 1 of them has actually expired. 1 is possibly still an issue, 3 are still issues, 3 have been fixed.
So not only are Frontier just manually expiring issues that haven't made the requirements if they're older than 30 days when they get around to doing it. They are also expiring issues that have genuinely been fixed. As a user, if I didn't know for certain those 3 issues (I know 2 for certain) had been fixed, I would think they are still an issue. All my issues except those four that are in the voting stage have been marked as "Expired". Can I really be bothered to spend ~5 minutes recreating each one of them that is still a bug currently in the game? Certainly not at the moment no.
Also as I'm here I raised this last year some time, but the Contributed issues page only shows 4 out of 48 issues, the Next/Previous buttons do nothing, and the issues displayed are ones I created not contributed to and are a couple of years old.
Of the latest cull that has taken place this is what my first page looks like. There are 8 "Expired" issues. Only 1 of them has actually expired. 1 is possibly still an issue, 3 are still issues, 3 have been fixed.
So not only are Frontier just manually expiring issues that haven't made the requirements if they're older than 30 days when they get around to doing it. They are also expiring issues that have genuinely been fixed. As a user, if I didn't know for certain those 3 issues (I know 2 for certain) had been fixed, I would think they are still an issue. All my issues except those four that are in the voting stage have been marked as "Expired". Can I really be bothered to spend ~5 minutes recreating each one of them that is still a bug currently in the game? Certainly not at the moment no.
Also as I'm here
I raised this last year some time, but the Contributed issues page only shows 4 out of 48 issues, the Next/Previous buttons do nothing, and the issues displayed are ones I created not contributed to and are a couple of years old.
Horrible AA and shimmering, would be nice if that gets fixed.
Source: https://www.youtube.com/watch?v=tnH3SK51ZZM
Nice idea but, sadly, I think this will not change the situation we are in, Bug reporting issues from the initial Alpha has made no impact as the 'bugs' are still there even after being reported as Fixed. they may seem small but like being given clearance to land BEFORE asking for it or settlement alarms NOT turning off when de-activated some actually ruin the game atmosphere. Black screen when leaving game is STILL happening. Update 7 has followed all the other updates by trying to 'firefight' issues that should have been rectified well before a 'final' release and actually succeed in creating new issues (since 7 I have had major fps issues in settlements, waiting 2-3 minutes listening to footsteps watching a black screen before being able to actually move, none of which I have encountered previously). I actually just 'fell' through the station floor after booking a taxi ( again not something I have ever had since starting odyssey).
Currently running Threat level 5 missions to re-activate settlement that do not have any threat whatsoever as no scavengers appear (I guess thats 'as intended?)
It's not my or anyone's system, well within spec for the game with up to date drivers. It's the game and if issues from the Alpha stage are still occurring after being reported then it's hardly surprising that players generally think 'What's the point?'
Not sarcasm but just a players impression of how gameplay is suffering due to a rushed release.
UPDATE : Now waiting for game to 'un-freeze' after trying to access inventory after landing (If I relog then all the lockers will be empty (what idiot thought that was a good idea?)) Oh wait even 'ESC' doesn't work, guess I'll just wait another 5 minutes till the server 'times out'.
Last edited:
Normally in a CG it takes a minute on the PS4 before it gets updated and when that doesn't work I logout and login and then I see it. It's been over an hour now and it's still not updated, wondering if this is a bug or if it's going to just be a while before it will show