Last modified August 1, 2020: Follow redirects in vrm_applications (f504c33)
Update order for BlendShape-related components
As described in https://github.com/vrm-c/vrm-specification/blob/master/specification/VRMC_vrm-1.0_draft/README.md#update-order, it is recommended to update as the following order:
Integrate with LookAt
To reduce the processing order problem of LookAt and BlendShape,
VRMLookAtBlendShapeApplyer have been integrated into
BlendShapeClip’s exclude functions
For example, when
blink are applied at the same time, there are models whose eyes become weird.
To address this issue, a function that can disable
blink when applying
fun is created. As of vrm1.0, there are three types of exclude functions:
SetValue and Apply
UniVRM-0.X there are two systems
BlendSahpeProxy.SetValue + Apply. In
BlendShapeProxyy.SetValueImmediate has been removed.
ignoreBlink, etc. functional, it is necessary to accumulate the rest of the included blendshape values and then process them at once. (Initially it was designed to be stored and applied by the application side)
The timing of using Apply function
Apply explicitly on the user application side.
Apply is called in VRMBlendShapeProxy.Update.
Note that it is better to use VRMBlendShapeProxy.Apply when the necessary blendshape values are set.
Apply is called in VRMBlendShapeProxy.LateUpdate.
When fine controlling is not required.