I don't know. Personally, I use "NaN" because I use ASE and I don't think there's an option to set the vertex position directly in clip space (I can set the local vertex position or offset)

For improved clarity (it's a bit too late to edit my posts)
About post (3/5) : Pixel shaders aren't performant in general, so if you can avoid executing it, you get better performance.
Option A (cutout) executes the pixel shader
Option B (vertex discard) doesn't

(5/5) This was something I wanted to talk about at Furality, but due to time constraints I had to cut that section. You can find the slides here: github.com/MyroG/Optimi...
What I just talked about can be found on page 74

(4/5) For worlds : You can GPU-instance "different" meshes by packing them into one mesh + UV atlas.
Create a "Tile discard" shader that uses an instanced property "tileToKeep" property, and set it via MaterialPropertyBlock.
Here, every mesh is GPU instanced, and renders in a single draw call.

(3/5)
Second image has a few benchmarks

(2/5)

www.youtube.com/watch?v=AQIJ...

Code below

The setup is basically a video player that gets rendered through the VRChat camera only

It uses assets from the prefab, but I'm not sure if I'll make it playable yet, since I made a few modifications to the base asset, and I'm not sure if anyone would want to play bowling on such a short lane.

(2/2) The "Point Light Volume" component uses a custom cookie texture showing a blurred fan. I'm rotating the point light in sync with the fan, which creates the illusion that the fan is casting a shadow, but that's not the case, AFAIK "Point Light Volume" cannot cast RT shadows yet.

Yes, we could only use dynamic bones

They seem to be synced like avatar physbones : when someone grabs the door, others can see the door being grabbed

Yep, but I forgot to mention that those bones cannot be grabbed on Desktop yet (same as with avatar physbones), so in the current state, you might need to implement separate logic for Desktop players.
(But the SDK is still in beta, things could change)

In my case, I would still need to implement some Udon code to highlight the door handle. Also, only the handle has a collider, so the door can only be pushed from the handle.
Nice update! I can think off a few interesting use cases.

(5/5) That's it! I hope my explanation was understandable and that you learned something new today.
The 300 character limit is pretty annoying, so I had to shorten some explanations...