Well Duh!
Report issues using the Issue Tracker
- Thread starter Paul_Crowther
- Start date
Duh, thanks. Think I have been at the grind too long.........Nah.
Just repassing by forums after 1 month to see what the remaining players still expect for FDEv, it's just crazy how people still continue to do beta testing ( work that should be done by the company not the players ) and discovering bugs and submitting them expecting that FDEv will actually manage all those bugs , if they had to fix all the bugs you guys fairly report to them , with the team they have at hands with the game would take them more than 1 year just for that.
Not to mention new features ....
You people continue to believe on whatever you think you believe , FDEV and Frontier on my opinion does not deserve half of the effort you are doing , nor they really seem that much afraid about the community feel, just watch some of those B's streams they do with community manager (not to personally attack any CM, i understand they are doing their job , but part of that job is also transmitting what players feel , and not only what is filtered and selectable just for the benefit of the company)
I just wonder when they finally have to put out the plug on Horizons and merge all to the consoles what will happen then ... and when really ?
Good luck reporting those issues, keep you faith in them if you want people, but sincerely from my point of view , everyone just should stop reporting and letting them decide what they want to do going forward.
At this point I just think they should release to consoles and merge all into Odyssey, and stop wasting resources on this game as it is.
If ED wants to live up to the future a new complete game need to be build from scratch and hopefully with a new pragmatic way so that community boa more involved in decisions , even if that takes more years to accomplish.
Sincerely , as a long time developer myself and team and project manager experience this is just my personal view on things.
As a player also myself for along date , I already aconplished all I ever wanted in ED with 1800+ h coming from initially XBOx then to PC, i started this game over 2x did same things 2x and sincerely liked it during that time , but enought is enought and it's time for the game to evolve to a new level or just be there make the affirmation that the game is has completed it's cycle and is as it is .
Not to mention new features ....
You people continue to believe on whatever you think you believe , FDEV and Frontier on my opinion does not deserve half of the effort you are doing , nor they really seem that much afraid about the community feel, just watch some of those B's streams they do with community manager (not to personally attack any CM, i understand they are doing their job , but part of that job is also transmitting what players feel , and not only what is filtered and selectable just for the benefit of the company)
I just wonder when they finally have to put out the plug on Horizons and merge all to the consoles what will happen then ... and when really ?
Good luck reporting those issues, keep you faith in them if you want people, but sincerely from my point of view , everyone just should stop reporting and letting them decide what they want to do going forward.
At this point I just think they should release to consoles and merge all into Odyssey, and stop wasting resources on this game as it is.
If ED wants to live up to the future a new complete game need to be build from scratch and hopefully with a new pragmatic way so that community boa more involved in decisions , even if that takes more years to accomplish.
Sincerely , as a long time developer myself and team and project manager experience this is just my personal view on things.
As a player also myself for along date , I already aconplished all I ever wanted in ED with 1800+ h coming from initially XBOx then to PC, i started this game over 2x did same things 2x and sincerely liked it during that time , but enought is enought and it's time for the game to evolve to a new level or just be there make the affirmation that the game is has completed it's cycle and is as it is .
Please correct the unreadable text, it is very disturbing to play (
And another bug: In some settlements, people periodically stop walking and patrolling. They still react if you shoot at them, but they stand still and just spin. Also, items are not loaded into containers, yesterday I was in 2 settlements where there were not even first-aid kits and batteries.
At least a couple of the expired bugs I've reported recently have been reproduced by other commanders and they've contributed to the bug reports. Yet still, they expire. Sigh.
It's really disheartening when I vote on bugs, contribute with my own bugs and generally play the game with an eye on improving it where it isn't quite right only to see those contributions expire, especially when I know other CMDR's have/see the same issues :-(
If other commanders can reproduce the issue, why would they ever expire?
Surely where a bug has been reproduced, it'd be better to acknowledge the bug, put it on a backlog and mark it as low priority rather than let it expire. For the bug reporter, it'd at least give us the feeling that contributions matter.
If they're left to expire because they're a duplicate, then mark them as potential duplicates.
Also, another feature to add could be when issues are coming up to expiration, give the reporter the ability to confirm if the issue is still active and if it is, extend the expression date.
It's really disheartening when I vote on bugs, contribute with my own bugs and generally play the game with an eye on improving it where it isn't quite right only to see those contributions expire, especially when I know other CMDR's have/see the same issues :-(
If other commanders can reproduce the issue, why would they ever expire?
Surely where a bug has been reproduced, it'd be better to acknowledge the bug, put it on a backlog and mark it as low priority rather than let it expire. For the bug reporter, it'd at least give us the feeling that contributions matter.
If they're left to expire because they're a duplicate, then mark them as potential duplicates.
Also, another feature to add could be when issues are coming up to expiration, give the reporter the ability to confirm if the issue is still active and if it is, extend the expression date.
@sallymorganmoore @Zac Cocken I've figured out the cause of the Scarlet Krait error when trying to rebuy a ship at Inter Astra, as reported in:
and duplicated in:
Basically, trying to rebuy your ship while you have outstanding fines (only possible post-Odyssey, since the player is no longer guaranteed to be destroyed with the ship) causes the scarlet krait - paying off the fines first allows the rebuy to succeed without having to relog into Horizons (thereby avoiding being relocated to the nearest jail, as well)
I'm not sure if this is related to a reported (and confirmed) crash to desktop in similar circumstances, but it's worth looking into this one as well:
and duplicated in:
Basically, trying to rebuy your ship while you have outstanding fines (only possible post-Odyssey, since the player is no longer guaranteed to be destroyed with the ship) causes the scarlet krait - paying off the fines first allows the rebuy to succeed without having to relog into Horizons (thereby avoiding being relocated to the nearest jail, as well)
I'm not sure if this is related to a reported (and confirmed) crash to desktop in similar circumstances, but it's worth looking into this one as well:
sallymorganmoore
Senior Community Manager : Elite Dangerous
Thanks so much for this! Noted. Lovely when all teh links are just....THERE. Thanks millions for helping me be as fast as freaking lightning!
There's an odd bug when trying to bookmark (engineer?) planetary bases in ODY, which I'm just flagging here as it appears to have multiple expired tickets for the same issue, and has clearly persisted through a number of patches:
Latest ticket - https://issues.frontierstore.net/issue-detail/42090
Same issue - https://issues.frontierstore.net/issue-detail/39660
Expired:
Latest ticket - https://issues.frontierstore.net/issue-detail/42090
Same issue - https://issues.frontierstore.net/issue-detail/39660
Expired:
Hello,
I have a small problem, the codex entry of the supermassive black hole of Sagittarius A still does not validate, after 5-6 visits, and this since the start of the game and a recent visit.
best regards, Cmd Walt71.
I have a small problem, the codex entry of the supermassive black hole of Sagittarius A still does not validate, after 5-6 visits, and this since the start of the game and a recent visit.
best regards, Cmd Walt71.
I'm having an issue that I'm trying to find on the issue tracker before making a ticket.
I am scanning systems that show X amount of bodies,
But as you can see the system map doesn't show 25 bodies. Also, "loading simulation" is stuck, it doesn't load ever.
They don't show in the navigation panel either, so I can't target them here either.
This is a bug right? Does anyone know of the issue already on the tracker or should I make one?
I am scanning systems that show X amount of bodies,
But as you can see the system map doesn't show 25 bodies. Also, "loading simulation" is stuck, it doesn't load ever.
They don't show in the navigation panel either, so I can't target them here either.
This is a bug right? Does anyone know of the issue already on the tracker or should I make one?
Do you know abut the FSS? ... seems maybe not. Google knows.
Please,
MAKE THE SUGGESTIONS FORUM MATTER.
This is how FD should treat a future feature subset... i.e. have the suggestions forum moderated fully and treated to bug tracker type rank voting and then having focused feedback forum on the top 1-5 and then coming back to the community with Dev feedback and producer/ David Braben feedback.
Why vote for bugs? Prio should be based on impact to the game and number of players affected, but not just popularity.
Votes to involving the community in the long-term dev of the game, and making the Suggestions Forum actually mean something, yes.
I've never been to a system that needed it before. I would thank you, but you seem kinda douchey about it.
I've never been to a system that needed it before. I would thank you, but you seem kinda douchey about it.
Hi I had a problem with srv reloading high-grade ammo. After reload it won't fire? I found a ticket for this bug but it was expired. This problem is only in EDO . Should I open a new ticket?
@sallymorganmoore is it possible that issue tracker specifies when a ticket was fixed? e.g. i'm revisiting tickets that i know are still issues in v6.01, and they got marked "fixed" at some point. there's no indication what the fix was, or which version does the fix apply to, or when it was marked fixed.
So it raises questions such as "is this fixed in the internal dev build, or is this considered fixed in the current public release?". Having clarity on this would help a lot.
I've also had a number of created or contributed issues expire, despite other contributions. I implore you to not let issues with confirmations expire. Please understand that a lot of us take out time from our days to file these tickets and supply evidence etc., not to mention draw attention to them on forums or discord groups. So it's a massive waste of everyone's time to have such tickets expire. It also discourages any future constructive feedback or participation. I hope you understand, doing my own job and then doing frontier QA work is already enough without having it all go to waste, and then the expectation that someone would ever repeat the process...
So it raises questions such as "is this fixed in the internal dev build, or is this considered fixed in the current public release?". Having clarity on this would help a lot.
I've also had a number of created or contributed issues expire, despite other contributions. I implore you to not let issues with confirmations expire. Please understand that a lot of us take out time from our days to file these tickets and supply evidence etc., not to mention draw attention to them on forums or discord groups. So it's a massive waste of everyone's time to have such tickets expire. It also discourages any future constructive feedback or participation. I hope you understand, doing my own job and then doing frontier QA work is already enough without having it all go to waste, and then the expectation that someone would ever repeat the process...
We evidently need an option to reraise issues, as they've been marked "fixed" without actually being fixed. One simple example of this was the inability to trade materials at the bartender (still a huge what) when the storage was full; it was poked at in the UI layer but still broken in the database layer, so we were happily told it was "fixed" when it changed from a broken error message to an outright disconnection.