Amazing! This should be great for facilitating optimization on large-scale maps. By any chance, would this also work as a step towards implementing a camera API similar to Camera: ViewportPointToRay() but that returns a boolean indicating if the model is visible from the viewport? (Not obstructed by any other parts or meshes)
2 Likes
WOOO! Gone are the days of 15 frames per second at last! Good job.
2 Likes
Is there an estimated date on Occlusion Culling being released fully?
3 Likes
Would this be an optional feature you can enable/disable for your game, or is this permanently on for all games upon release?
2 Likes
I’m finding that maps which use a lot of unions severely limit their potential for culling. When my camera is behind a union wall parts won’t cull but they do when behind a part wall, or on certain sides of a union it’s pretty weird and I don’t think thats the intended behaviour but we’ll see.
actually, its not because of the mesh shape, i have it like x, -y, -z (which makes it upside down + is the source of the bug)
Don’t know if anyone has posted about this, but I found this pretty buggy culling behavior on Project Lazarus.
2 Likes
Is that fog or atmosphere? Fog doesn’t cull objects as far as I tested, not sure however about atmosphere.
3 Likes
it might be the mesh thats infront of the character?
Transparent meshes shouldn’t cull other objects if they’re behind it.
Yes, we don’t yet support culling skinned objects, and I’m guessing your trees are skinned?
Once shipped, it will work all the time, not at specific quality levels.
2 Likes
Nope, the reason for Occlusion Culling not working on my trees is because I have Humanoid property parented under each Tree model. I do that to change trees lighting settings, as Humanoid class reduces shadow intensity and helps make it make much more realistic on trees.
Edit: it would be cool if Roblox introduced a new Class object which would adjust individual model lighting property just like Humanoid.
1 Like
Having a humanoid in a tree is just a lag machine, and from my experience, whenever I would do that, there would be 0, and I mean absolute 0 change to the shadows in both ShadowMap and Future.
1 Like
There is a huge difference in shadows, and no performance impact at all.
Humanoid trees:
Without Humanoid trees:
Without Humanoid and Shadows property disabled on leaf parts trees:
1 Like
That is almost certain that its atmosphere and not fog (this game still gets updates).
1 Like
So no humanoid made shadows better?
3 Likes
Having no humanoid makes trees look way too dark as if they are burnt.
1 Like
Oh hold up a second.
Occlusion does not work for very detailed meshes?
This would be quite inconvenient for games that mainly use meshes and very little parts.
Is it possible to approximate a size/volume for a mesh and use that as an occluder instead?
Say, you have one huge statue model, very detailed and all, but you just give it a cylinder-shaped occluder which should keep computation fairly cheap and fast in theory.
Can we perhaps even assign our own occluders to complex geometry or have a special instance that can be parented to a MeshPart or model that acts as an occluder?
Having an instance would actually be quite useful since this can also be used to just force an object to not render if you view it from a certain angle.
Some models might be too complex and have way too many parts to automatically calculate an occluder, an instance could solve this I think.
I could use an instance/object like that to hide entire parts of an level or map as well, being an more convenient way of implementing loading/unloading.
Would no longer have to parent things into ReplicatedService + physics can still simulate in invisible parts of the level.
3 Likes