Occlusion culling is not rendering objects that are in view

Bug Reports Engine Bugs
,
1

For a few months, I’ve been having this issue where occlusion culling is not rendering parts and sections of terrain that are in view.

Here are my Streaming properties and my Camera properties.

image
image418×196 10.9 KB

image
image418×193 8.33 KB

2 Likes
2

I have experienced this occurring across multiple of our games in the past 24 hours. It has never been an issue before, but is now happening frequently (although not reliable/replicable). Occlusion culling is happening incorrectly, even when there are no objects blocking the view. We’ve confirmed with wireframe rendering that there is nothing that could possibly be blocking it. No changes to our culling settings have been made.

1 Like
3

Hi ShinyGriffin,

Is this happening in Feather Family? I tested Feather Family and didn’t get the same issues you are seeing.
Also, do you only see this in Studio, or are you seeing it in Studio and Client? If it’s only Studio, could you provide a .rbxl file that can reproduce the issue (if it’s sensitive this can be sent in a DM)?

Please also provide some info about your device (OS version, CPU, GPU)

1 Like
4

I do not see it in Studio. I only see it in live games. It happens often, but not every time I join the game. When it does happen, it happens for the entire session until I rejoin hours later. I do not change anything about my display.

I am using Windows 11. Here is my cpu and display information:

13th Gen Intel(R) Core™ i7-13700K 3.40 GHz

image
image499×313 19 KB

1 Like
5

Thanks.
You said you notice this started a couple months ago. Do you remember around when it first started happening?

1 Like
6

Unfortunately I don’t remember exactly when it started showing up, but it might have been around May or June. I have not changed anything about my monitor, graphics card, or in-game camera. I have been getting reports that this is happening to other players using Windows desktop too.

1 Like
7

I’ve also had this happen numerous times though I haven’t been able to consistently reproduce it.
I had this issue occur probably about 4 times within a week while playing Tower Defense Simulator. It always happened when a map had loaded in and I was put into the map (but not before that), though that might just be a red herring.
The area of the screen that was wrongfully occluded appeared to be different each time and it resolved after rejoining.

I’m on MacOS 15.5 with an M4 chip

1 Like