Thread for publicising your issues that are otherwise expiring due to lack of votes/confirmation

Maybe only few of us do reactivations these days. Orthrus farming seems to be more interesting...
It’s definitely more of a niche issue, but annoying for those of us who do like to run the missions. Especially now that there is the added risk factor of the Banshee in some of the settlements. And, since this is an issue as a direct result of a fix from Frontier, I’d like to see some kind of standards. If only in accountability, at least.

Sitting at 9/10 now by the way.
 
It’s definitely more of a niche issue, but annoying for those of us who do like to run the missions. Especially now that there is the added risk factor of the Banshee in some of the settlements. And, since this is an issue as a direct result of a fix from Frontier, I’d like to see some kind of standards. If only in accountability, at least.

Sitting at 9/10 now by the way.
What I meant was, there might just not be as many CMDRs doing reactivations at the moment, so only few can report/confirm. BUT you have my vote.
 
What I meant was, there might just not be as many CMDRs doing reactivations at the moment, so only few can report/confirm. BUT you have my vote.
I’d have figured a few were to see what got added for them in U17, with the Thargoid Goliath knockoff roaming about.

Anyway, that did it and it can now be voted for. (Thanks) Whatever use that may be at this time… hopefully they’re already aware anyway.
 
Having been quite critical of Frontier's Issue Tracker in the past, I think it's only right that I mention a recent change which I think is very positive: since about 1 November it looks like someone has been going through the newly raised issues and any which are "should have been a support ticket" are getting converted to support tickets. It also seems like there's been an increased effort to proactively clean up duplicate reports.

This is going to both significantly reduce the number of open unlikely-to-be-confirmed bugs (making it easier to see the rest of them) and give much better responses to the people raising those issues through the "wrong" channel. It probably will also help Support pick up on patterns in requests which are due to an underlying bug that's not reasonably identifiable and confirmable from an individual player perspective, and hopefully get those into the fix queue more efficiently.

Big (y) to the staff working on this.
 
Having been quite critical of Frontier's Issue Tracker in the past, I think it's only right that I mention a recent change which I think is very positive: since about 1 November it looks like someone has been going through the newly raised issues and any which are "should have been a support ticket" are getting converted to support tickets. It also seems like there's been an increased effort to proactively clean up duplicate reports.

This is going to both significantly reduce the number of open unlikely-to-be-confirmed bugs (making it easier to see the rest of them) and give much better responses to the people raising those issues through the "wrong" channel. It probably will also help Support pick up on patterns in requests which are due to an underlying bug that's not reasonably identifiable and confirmable from an individual player perspective, and hopefully get those into the fix queue more efficiently.

Big (y) to the staff working on this.
That's a thumb, right? ;)
 
Getting the Cutter DC on a FC fixed and correcting the alignment to the docking ports were a pleasant and unexpected surprise.

Floating rocks are still a thing.

Station approaches in SC still feels a bit different than Legacy, but I haven't been in Legacy for so long that I'm not sure about that anymore.

Kudos to FD for fixing the most aggravating things that I found irritating.
 
Last edited:

Now that invasions are starting to come back into swing, I figured I'd get this back on the radar - getting a "murder bounty" because you hit an AX NPC with a beam laser for less than a second but apparently that counts as "murdering" them like you weren't trying to shield strip the Hydra or Medusa currently massacring things in the instance(and which killed that idiot AI you were trying to help).

Someone remind me why crime reports are active in a war zone. Like accidental friendly fire when you're attacking one Hydra and the other has decided to make you its target doesn't happen. Not like it even discourages those who would deliberately shoot down defenders...

Note : I didn't create a duplicate report but rather searched and found this one, then added contributions.
 
The turreted flak issue has been broken for LITERALLY YEARS. Would really appreciate it if people would upvote it before it expires!

Basic issue: When a Multicrew Gunner uses turreted flak, they do not get the UI or noise to tell them when they are near their target, making hitting impossible.

 

A pretty minor one but could be incredibly unpleasant for someone actually in the dropship at the time - at one particular settlement layout the frontline vultures can get stuck on the settlement geometry.
 
The turreted flak issue has been broken for LITERALLY YEARS. Would really appreciate it if people would upvote it before it expires!

Basic issue: When a Multicrew Gunner uses turreted flak, they do not get the UI or noise to tell them when they are near their target, making hitting impossible.



A pretty minor one but could be incredibly unpleasant for someone actually in the dropship at the time - at one particular settlement layout the frontline vultures can get stuck on the settlement geometry.
I’ve added both to the OP and I’ll add some confirms when I get a chance 👍
 
The turreted flak issue has been broken for LITERALLY YEARS. Would really appreciate it if people would upvote it before it expires!

Basic issue: When a Multicrew Gunner uses turreted flak, they do not get the UI or noise to tell them when they are near their target, making hitting impossible.



2-3 more confirmations needed to the issue with Flak turrets in multicrew (which are useless due to the bug) - so it does not expire and maybe gets some attention from FDev
 

2-3 more confirmations needed to the issue with Flak turrets in multicrew (which are useless due to the bug) - so it does not expire and maybe gets some attention from FDev
Looks like one of the contributions doesn’t have a “view reproduction details” tab which probably means it doesn’t count towards the total, so 4 more Confirms should do the trick - and I just might be able to help with that…😁

Edit: …aaaand done. Vote away, folks 👍
 
Last edited:

2-3 more confirmations needed to the issue with Flak turrets in multicrew (which are useless due to the bug) - so it does not expire and maybe gets some attention from FDev

Looks like one of the contributions doesn’t have a “view reproduction details” tab which probably means it doesn’t count towards the total, so 4 more Confirms should do the trick - and I just might be able to help with that…😁

Edit: …aaaand done. Vote away, folks 👍
Awesome! Thanks so much guys! I'm really looking forward to getting my Multicrewsader going again!
 
Does anyone know if NPC pilots still run from Thargoid fights, taking the mothership along with them? I'm considering doing some bug hunting with an NPC crew member but don't want to set all that up only to have them high-tail it out.
 
Just a few days left to go with AX pilots giving you a bounty when it would make more sense for their “report crimes” flag to be off - another 4 confirmations should keep the report from expiring.
or for the zone to just be lawless regardless of crime reporting flags the same way non-thargoid zones are, since they already have the "no system link" warning

or for no-system-link areas to become blanket lawless, I can dream damnit
 
Back
Top Bottom