Material Contacts
in progress
Fax
Allow contacts to write directly to shader properties.
If enabled on a receiver, you select up to four target MeshRenderer components that will then have the full world-space transform matrix of each of the receiver’s four nearest contacting senders written to their material properties, in addition to the transform of the receiver component itself.
Learn more in our Aug 27 Developer Update.
Log In
Aonodensetsu
Please also allow sending a little additional data along with the transform, could even be packed into the last row of the transform matrix if there's a technical limitation against otherwise.
While position allows for proximity based effects (and workarounds), it leaves a gap for contact 'property' based animatable effects. The tag system will likely be abused for workarounds regarding this, but I think allowing even just a few animatable floats along with the position will lead to significantly more possibilities and less abuse of other properties of existing systems.
Smash-ter
The thing I'd honestly ask is if there'd be more mesh slots, as I feel 4 is a tad restrictive (unless there's a chance to get the
_Self
function to be a dedicated component)Smash-ter
This has a lot more potential than many realize, especially given that the contact has a local to world matrix for shader authors to utilize. This indirectly fulfills one of my most wanted requests with regards to the shader aspects https://feedback.vrchat.com/avatar-30/p/components-that-take-transform-values-and-output-them-to-custom-shader-propertie
Fax
updated the status to
in progress