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

General Issues and Bug Reporting
, , ,
46

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.”

48

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
50

This is a mistake clearly ?

1 Like
51

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

52

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
53

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

54

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
55

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
56

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.

57

Yeah, that doesn’t work. Barriers are completely borked right now. And this visual glitch is just one of several issues. I was going to file more bug reports, but after seeing mine - and others like it - rejected for no good reason, I’m done with them. I built my own replacements for a new map, and they work. Now I’m just hoping the solution I came up with doesn’t get broken and ignored in the future too. Fingers crossed.

58

Yes, that should not have been closed. Apologies all around! The team is on it!

4 Likes
61

Hi,
Is there any update on this?
I couldn’t see anything in the update patch notes

62

what was your solution if you dont mind me asking

63

This was not fixed.
Barriers still shows when they shouldn’t.

This should be a higher priority bug, because maps are relying on this to work. there isn’t any good workarounds for this either.

3 Likes
64

I hope it gets fixed soon

1 Like
66

For whatever reason, barriers are working better with the 37.30 update, but they still have some bugs. From quick testing, everything seemed fine for player #1. However, sporadically, some barriers still didn’t display the correct visual state for player #2 (as per the ignore list). I haven’t had a chance to test further yet.

67

FORT-920720 is ‘Closed’ as ‘Fixed’. The issue will be addressed in 38.00.

3 Likes