Barriers that have a player added to the ignore list now start to show the barrier material to the player.

Just adding my voice - it’s frustrating to keep running into the same issues without resolution.

In a quick test, it looks like barriers now disappear at a relatively short distance. And when they come back into render range, the material is visible even if the player is on the ignore list, which shouldn’t happen.

Really hoping this gets fixed soon. I also hope the other issue I reported doesn’t get swept under the rug again. It was marked “needs more info” - even though I provided clear instructions, simple repro code to add all players to the ignore list, and a video showing the bug from multiple perspectives. It was 100% reproducible on Xbox Series X, PlayStation 5, and PC, yet was closed as “unable to reproduce.”

I can confirm this too, barriers are awful now. Don’t render well, materials don’t hide, ignored agents don’t take effect sometimes.. They’re weirdly buggy this update.

1 Like

FORT-920720 has been ‘Closed’. We’re unable to reproduce this issue.

This is a mistake clearly ?

1 Like

My other bug report was closed like this as well. :confused: Doesn’t make any sense.

This is an unbelievable response. What’s the point of reporting a bug? They just closed it without even asking the creator directly…

1 Like

My current workaround is to trigger added to the ignore list twice in a row — it’s effective so far.

Really? This bug is happening on a regular basis. It is just not happening immediately, you as the Player have to move away from the Barrier and then get back to it for the bug to appear. So if someone tried it only from a short distance, he would not be able to reproduce it. This is such important function of the Barrier device, that if this thread can not be reopen, it is needed to create new one with more details about how to reproduce it.

1 Like

I just tried to call a function twice in a row in one of my maps and it still doesn’t fix it, at least not in Edit Session. I didn’t use a Trigger device.

1 Like

There might also be environmental differences causing the results to vary.
Until this is fixed, we’ll have to use some rather odd workarounds—haha.

            BARRIER_Start.AddToIgnoreList(Player) 
            BARRIER_Start.AddToIgnoreList(Player)

This topic has been closed, so it may need to be reported again under a new thread.