New Update breaks Mesh Renderer Bounding boxes; relying on if the mesh is in view
complete
Smash-ter
As of the VRChat beta build 1385, mesh renderers behave differently than previous updates. In the past I normally use a small quad with big bounds to reproject what I have on my avatar's camera into the corner of the screen. It's if as though the mesh is getting culled from my POV even though I have Dynamic Occlusion disabled on the mesh. Either the player's POV is deliberately occluding the small mesh or the bounds of the non skinned mesh are not working properly. the image in the corner will only pop up if:
- you are previewing the model in the main menu
- the world has your model duplicated and you can look at it (possibly in mirrors but the shader in this case has a parameter to exclude mirrors)
- your avatar is in an obscure position
If the mesh is a skinned mesh renderer with a similar bounding box the result will replicate what's on top of the first image, otherwise if it's not a skinned mesh renderer it will result in the bottom of the first image.
Log In
StormRel
complete
Smash-ter
Patch is now live
This post was marked as
available in future release
StormRel
tracked
StormRel
Merged in a post:
[1386] Using Any Constraints to the head bone does not behave properly on local copy
Smash-ter
I was trying to see what i can do to possibly fix some of my models in the Open Beta that use buffer particles but since the new update went out yesterday, and is still apparent after the recent open beta patch, constraints that are anywhere near the headbone, regardless if they are parented or scale constrainted. I tried my best to summarize the issues here: https://twitter.com/Smash_ter/status/1730354376831607247
d
d4rkpl4y3r
I can reproduce the MeshRenderer on my avatar loosing their bounds for frustum culling for remote players.
The way it happens for me is if I have a prop toggled on and then a remote player does hide and show my avatar, the mesh renderer now culls for them like its bounds size is 0. other mesh renderers on my avatar that werent enabled still have correct bounds. the only way for ppl to fix my avatar seems to be rejoining the instance to load the avatar from cache/server again.
StormRel
Hello! Can you provide an example avatar ID for us to see this issue?
Smash-ter
StormRel: I made an updated post but here's a sample model I made to show the problem a bit
avatar ID: avtr_ab79d677-7d98-4911-bb88-d782f0e964af