Ignasi

Hey everybody,

Thansk for the report. We’re currently looking into this and what could be the cause.

Hey @heaventhere

Thanks for bringing this up. We’ve sent a search warrant to the Sepermeru Tax office to see if Urik has recently fled to a fiscal paradise.

Hey there,

We’re aware of this issue. It was reported recently and our team is currently looking into it.

Thanks for the report.

Hey @Exiss

If you experience this issue again without any mods installed, could you send us your game log (via private DM) so we can give it a look and see if we spot anything?
This seems to be an inconsistent issue affecting a small portion of players, and has proven to be rather difficult to reproduce internally.

Thanks in advance.

Hey there,

Please use our Zendesk platform to report official server problems, outages or infractions.
https://funcom.zendesk.com/hc/en-us

Thanks.

Hey everybody.

Just a quick update about this issue.
We sent a fix to our backend that seems to have worked for some accounts. You’ll need to relink your Twitch and game account for the items to show up on your game.
However, this is not ideal and we have been working on a way more robust solution that will come for update 2.6. We’ve overhauled the backend and our internal systems to prevent this issue from happening for this and possible future promotions, on Playstation especially, but for the other platforms as well.

Sorry for the lack of pirate Watchers stuff until then.

Hey there,

We’re still on the same block. It does seem that this was caused by some building blocks to prevent errors with NPC and fauna spawns (this seems the lesser cause in Exiled Lands), and exploit fixes. They likely won’t be reverted in that case.
Where we stand now is whether we move forward with considering an option to bypass these blocks with an admin toggle or not. Even though it would seem a no-brainer, an option like this would likely either take a lot of development time to implement properly (which would likely make it fall in the queue of likelihood of implementation), or very likely to break the game if not.

That’s where it is now. News regarding this are slow as the team that’d be in charge of considering this change is currently focused on addressing performance on consoles. That is also why we don’t have any more in-depth info about this other than the above, which is probably old news. But just for the sake of repeating it.

That kind of info can be useful too. But it’s more of a helpful guide to understand what the bug does to alter normal gameplay. We got a few reports with “it should work” as expected behavior, which…yeah. But that doesn’t help us too much narrow down the problem

Hey @KmKn

Thanks for the detailed report. We’ve sent it to our team as we’re now looking into these and other similar issues reported.
Quick note regarding the “Expected behavior” section of the bug report: it is used to describe the bug behavior to expect if following the steps and general description of the bug.

Hey there,

There seem to be three issues at hand in this thread.
First, the sheathing problem. As @Tephra mentioned, it does look like the server was crashing at that moment which made it look like the change wasn’t working, and later, that it caused the crash. So far it seemed a coincidence, but let us know if it happens again.
Second, the Orb of Nergal issue. We’re aware of it and it’s been reported recently. We’re looking to fix it for a future patch.
Third, server crashing. That could be one or many reasons. Silver lining is that each time a server crashes, a crash dump is sent to our backend where we can investigate common crashes and fix them based on number of incidences per type of crash.

Hey @Dakiara

We’re aware of this issue as it’s been reported recently. We’re looking to fix this issue for a future patch.

Then what would be the coordinates of the last screenshot you shared with us, where you could see the flying objects? (in game, Ctrl +Shift+Alt+L)

While we don’t generally discuss Zendesk related stuff on the forums, I’ll make a small exception here just to give some insight.

The automated response you received is sent to tickets that spent (under the current settings) 14 days in the backlog with no progress being done to them. The lack of progress is not neglect, but a matter of priority. Tickets are organized by priority depending on type of infraction and severity of it. While ideally, our Zendesk team would love to address every single ticket received, with the current workload that is not feasible.
However, if a ticket is automatically closed, and the issue is still causing trouble, we suggest to send a new ticket reporting it.

As a final note, while we understand the frustration when affected by an unpleasant situation when playing online, official servers are a free service offered to our players, but it is not the only way to play the game. There are many thriving communities (see our ...

Thanks for the info @HeRMaN6 and @CodeMage. It seems we at least have it narrowed down to shelves and/or stacking being involved on this. We’ve sent those instructions to our team to run some tests and see if we get any luck reproducing this.

Hey @DanQuixote

Thanks for reporting it. We’re aware of it and it is already being worked on for a future patch.

Hey there!

There’s a new thread with updated information about this issue here:

Hey there,

We’re aware of the issue. We’ve tried to also address it post 2.4.6 with a backend fix that did not reliably work for everyone. For Update 2.6, we’ve worked on an overhaul of our internal systems that should finally address this problem and ensure correct functionality in possible future promotions as well, for PlayStation especially, but also for every other platform.

Sorry for the wait!

Hey there,

We’ve sent this to our designers to see if it is AsIntended or if it is in need of a fix.
Thanks for pointing it out.

Hey @speedice

Thanks for the heads-up. W’re continuing work on optimising and stabilising performance on PS4 and Xbox after 2.5.1. Glad to hear the latest update improved performance, but as you noted, there’s still more work to do.
We’re also aware of a few graphic artifacts introduced with the update, which we’re also aiming to address as soon as possible.

Hey there,

We’ve sent a note to our team about this rippling lack of wateriness. Thanks for bringing it to our attention.