Update 17.01 | Update Notes

fairly easy to reproduce and fix
I'm an avid bounty hunter who has made billions in bounties and massacre missions. I've done a lot of hunting in RES-s since update 17 and I've seen this bug where system authorities or powerplay agents go hostile on me and won't stop shooting me I think 3 times. It's quite rare and not that easy to reproduce. In any case, they don't pose a serious threat to a properly built warship, being more of an amusement than anything. Sooner or later they either jump out or get destroyed in a fight with some pirate, or you can just jump to SC and drop back into the RES to get rid of any hostiles.

The "accidental" pulse laser fire while an NPC is scanning me is more common, but frankly, it's no big deal at all, maybe taking 1% off of my ~800MJ biweaves.
 
I'm an avid bounty hunter who has made billions in bounties and massacre missions. I've done a lot of hunting in RES-s since update 17 and I've seen this bug where system authorities or powerplay agents go hostile on me and won't stop shooting me I think 3 times. It's quite rare and not that easy to reproduce. In any case, they don't pose a serious threat to a properly built warship, being more of an amusement than anything. Sooner or later they either jump out or get destroyed in a fight with some pirate, or you can just jump to SC and drop back into the RES to get rid of any hostiles.

The "accidental" pulse laser fire while an NPC is scanning me is more common, but frankly, it's no big deal at all, maybe taking 1% off of my ~800MJ biweaves.
I have not been affected by this bug ever, but I witnessed it a few times on team members. Honestly, I could not make heads nor tails of how people were supposedly dying to random NPCs on this grand a scale... Until the terms "Type-10" and "AFK" were added to the discussion...
 
Dont worry I bought my 10 year old nephew a Star citizen account, when he retires he'll be able to see if its completed by then 😁
Seriously... lets hope we dont have to sing my favourite programming song when starting elite (updating now)

Bill

All together now

99bugs in the code
99 bugs in the code
take one down
patch it around
127 bugs in the code

PS. I am a professional programmer by trade, and have that sign above my desktop :geek:
That's really not the cutting remark that you think it is. If Star Citizen was so great then there wouldn't be so many ex-elite players lurking on Elite forums etc, trying to reassure themselves that their $1000 ship jpg purchase was a great investment while watching the nth 30k for the also nth bugged reason. Happy to play Elite and don't need others' reassurance to know that I make the right choice every time I load up the game if I happen to think about it, which frankly I don't, but I'd imagine that's not so much the case for someone sunk costed into Star Citizen.
 
Actually Jack, go read the defect to see how many non AFK problems this bug has caused.
Well of course it ought to be fixed, apparently they tried and didn't manage it in time for this release.

Still it seems rather rare and hasn't really caused me much trouble, at least for me far from game breaking. Of course I haven't played all loops so it might break some other part of the game badly.

Personally I thought the the bug (with hostile ships not turning red) we had over xmas a year or two ago was worse. Still I learnt being more aware of surrounding ships and who is attacking me.
 
1: I did not see his post. If I had I would not have brought it up.
2: I'm sorry they are having a difficult time. This has nothing to do with fixing defects.
3: I'm not sure this should have even been brought up. I don't play those other games. Are you saying they've reduced the number of employees working on ED bugs to build these other games?

The bug was introduced in Release 17. 30 years of Software Validation tells me this clue should make it fairly easy to reproduce and fix, unless the code is like the spaghetti of X86 BIOS. HOWEVER since it has been publicly acknowledged I will cease and desist, and assume it will be fixed in the next release.

I'm really only upset because I spent over 500M building the Type 10 for Massacre Missions, only to be presented with the rebuy screen returning from the bathroom after 20 minutes of play. The ship can't be touched by pirates in the Low RES. I went from 100% to rebuy in less than 5 minutes.
Hindsight: Never go to the bathroom until you go offline. Whoda thunk?
Peace.
A useful tactic in update threads is to go to the first post and then click on the dev post label at the top right which will take you through all the dev posts in order that way you can see all the official stuff without wading through all the rubbish we players post.

Just because they know the bug exists doesn’t mean an acceptable fix is going to be found and available soon.
 
A useful tactic in update threads is to go to the first post and then click on the dev post label at the top right which will take you through all the dev posts in order that way you can see all the official stuff without wading through all the rubbish we players post.

Just because they know the bug exists doesn’t mean an acceptable fix is going to be found and available soon.
I appreciate the tip!
 
Now, this isn’t a “Someone lit the Necronomicon on fire and one of the Elder Gods is about to take offense at it” problem, but it’s still a bit… miffy, if I’m using that word correctly.


Particularly since the issue came up with U17 itself attempting to fix these missions not failing properly if your local party with Revenants resulted in a few burns and bruises.
Maybe I'm wrong, and I have a tendency to be cynical, but I assumed that the main reason for the update was the changed Orthrus behavior in which they scoot when people shoot -- presumably to slow down the money printing a bit.
I more think the scenario was not playing as intended - by allowing (mostly) liberal use of Guardian weapons in something that was likely not meant to have them be an option. Seeing how the main defense mechanism of the Orthrus, aside from its shield, is the Guardian neutralizer field*. It might also make those Basilisks and Medusas dropping by to defend the spires a threat worth considering by several players.

*That presumes they fire off their shutdown field when disturbed during the scanning loop. I’ve not been too active around the spires and haven’t visited one yet after the update.
 
*That presumes they fire off their shutdown field when disturbed during the scanning loop. I’ve not been too active around the spires and haven’t visited one yet after the update.

They shoot both EMP and AGF instantly if attacked anytime. In multiplayer mode, sometimes AGF canceled (maybe bug).
 
Last edited:
So in summary, the fixes in the release notes have fixed all the things, and the other problems mentioned in this thread have been acknowledged both on the Tracker and by a comment here from Paul, so basically, nice job!

If anyone replies to this with their favourite paper-cut claiming it's a game-breaking issue and it turns out it's not even on the Tracker I will happily spend the fuel on towing them to scoop height and simply letting go.

On a more serious note "someone" (which I assume is either Paul or whoever Paul has shackled in the meeting pod until they do better) really is using that issue tracker now and stuff is getting into the fix list and getting fixed and to me that's even better news than the smattering of bugs fixed in this release so THANK YOU.
 
So pleased you have fixed the cargo transfer to FC. Especially as I have just started loading 20,000 tons of tritium for my next journey!
 
This is a known issue we are investigating but is not resolved in this particular update.

With apologies for lacking the energy to confront the Issue Tracker and attempting to pass a hint here instead, all of my observations in Hazardous RES scenarios point to the attacks being a fire groups problem, as if they have scanners and weapons in the same group and on the same trigger. I would give it a quite high chance that comparing the intended fire groups to the actual fire groups would discover the cause!

Many Commanders report this issue as "being attacked", but lack the subtle observation that the attacker is not actually fighting them, just attempting to scan!
 
Many Commanders report this issue as "being attacked", but lack the subtle observation that the attacker is not actually fighting them, just attempting to scan!
It seems that there are two completely different issues that get conflated. One is the laser burst at scan, which does seem to be a firegroup problem as you point out. The other, much rarer IME, glitch is a system authority/powerplay agent going full offensive on player for absolutely no reason. I've had it on a few times, and I've been squeaky clean every time—no bounties, no fines, no illegal cargo, no friendly fire incidents from my part.
 
Last edited by a moderator:
Back
Top Bottom