VertExmotion [Released]

Hello!
Is there a setting for inertia to stop objects from deforming when in uniform motion like in elevator?

 

You could try to add the inverse motion vector to the sensors. There's a custom world force in the sensors' parameters.
There's different samples using custom forces by script in the package.

 

Hi, I used vert exmotion on the skin mesh, the effect is good when the scale value is 1, but when I set the scale of the character larger at runtime, vert exmotion has no effect, how can I solve this problem? Thank you!

 

Unity version: 2022.1.8 vertExmotion vertion:1.10.2

In your demo scene to adjust the scale value of those characters, the effect is good, but using my own characters, scale larger will have no effect

 

Hello.

I tried applying it to poiyomi as per page 22 of the document, but I can't paint on the vertices.
gradient doesn't seem to work either.

Is there any solution?

 

What is your version of unity?
Do you use the latest version of Vertexmotion ?

 

I am using unity 2020.3.30f1
The version of vertexmotion uses the latest 1.10.2

 

Does the model has the Read/Write parameter enabled in the import settings?
If it doesn't work, could you send me your model and your invoice number (contact@kalagaan.com)
I'll help you to fix it.

Note : With Unity 2021 you can use the Vertex Buffer mode, so you don't have to convert the shader.
You'll have to download the package again using the package manager in Unity 2021.

 

Hi, kalagaan

Could you upload a scene example for this script! Thanks a lot!

 

@kalagaan Hi, I'm running Unity 2022.1.17f1, HDRP, with your latest update. Is there a way to show the entire mesh when painting with the vertex buffer mode? It seems to disappear when orbiting around in the scene view. GPU Compute Skinning is enabled.Thanks.

 

I found that the hdrp vert lit shader was giving an error and doing the same thing because it calls vertmesh that was looking for vertexmotion.cginc down one folder when it was actually down two. So I changed the shader to look for it like this.

#include "../../VertExmotion.cginc"

 

Unity 2021.3.11f [ VertExmotion implementation in Amplify Shader Editor].

When i add the additional directive for Vertexmotion.cgnic, i get a redefinition error for _Time.

I don’t know HLSL so i don’t know what to do.
//EDIT - upgraded to 2021.3.13F - problem still exists.

///EDIT

Shader error in 'VerExmotion/Basic_AmplifiedVersion_Converted': redefinition of '_Time' at 2019_4/2021.3.13f1/Editor/Data/CGIncludes/UnityShaderVariables.cginc(40) (on d3d11)

I notified Amplify shader team but they are busy with other things.

 

Oops, I was really busy these months and I didn't see this notification
I'll have a look, thank you for the feedback

 

Thank you, for the feedback!

 

I'll check that!

 

Getting this error with the Unlit URP shader:

invalid subscript 'normalOS'
Compiling Subshader: 0, Pass: DepthNormalsOnly, Vertex program with <no keywords>
Platform defines: SHADER_API_DESKTOP UNITY_ENABLE_DETAIL_NORMALMAP UNITY_ENABLE_REFLECTION_BUFFERS UNITY_LIGHTMAP_FULL_HDR UNITY_LIGHT_PROBE_PROXY_VOLUME UNITY_PBS_USE_BRDF1 UNITY_SPECCUBE_BLENDING UNITY_SPECCUBE_BOX_PROJECTION UNITY_USE_DITHER_MASK_FOR_ALPHABLENDED_SHADOWS
Disabled keywords: DOTS_INSTANCING_ON INSTANCING_ON SHADER_API_GLES30 UNITY_ASTC_NORMALMAP_ENCODING UNITY_COLORSPACE_GAMMA UNITY_FRAMEBUFFER_FETCH_AVAILABLE UNITY_HALF_PRECISION_FRAGMENT_SHADER_REGISTERS UNITY_HARDWARE_TIER1 UNITY_HARDWARE_TIER2 UNITY_HARDWARE_TIER3 UNITY_LIGHTMAP_DLDR_ENCODING UNITY_LIGHTMAP_RGBM_ENCODING UNITY_METAL_SHADOWS_USE_POINT_FILTERING UNITY_NO_DXT5nm UNITY_NO_FULL_STANDARD_SHADER UNITY_NO_SCREENSPACE_SHADOWS UNITY_PBS_USE_BRDF2 UNITY_PBS_USE_BRDF3 UNITY_PRETRANSFORM_TO_DISPLAY_ORIENTATION UNITY_UNIFIED_SHADER_PRECISION_MODEL UNITY_VIRTUAL_TEXTURING


invalid subscript 'normalOS'
Compiling Subshader: 0, Pass: Unlit, Vertex program with <no keywords>
Platform defines: SHADER_API_DESKTOP UNITY_ENABLE_DETAIL_NORMALMAP UNITY_ENABLE_REFLECTION_BUFFERS UNITY_LIGHTMAP_FULL_HDR UNITY_LIGHT_PROBE_PROXY_VOLUME UNITY_PBS_USE_BRDF1 UNITY_SPECCUBE_BLENDING UNITY_SPECCUBE_BOX_PROJECTION UNITY_USE_DITHER_MASK_FOR_ALPHABLENDED_SHADOWS
Disabled keywords: DEBUG_DISPLAY DOTS_INSTANCING_ON FOG_EXP FOG_EXP2 FOG_LINEAR INSTANCING_ON SHADER_API_GLES30 UNITY_ASTC_NORMALMAP_ENCODING UNITY_COLORSPACE_GAMMA UNITY_FRAMEBUFFER_FETCH_AVAILABLE UNITY_HALF_PRECISION_FRAGMENT_SHADER_REGISTERS UNITY_HARDWARE_TIER1 UNITY_HARDWARE_TIER2 UNITY_HARDWARE_TIER3 UNITY_LIGHTMAP_DLDR_ENCODING UNITY_LIGHTMAP_RGBM_ENCODING UNITY_METAL_SHADOWS_USE_POINT_FILTERING UNITY_NO_DXT5nm UNITY_NO_FULL_STANDARD_SHADER UNITY_NO_SCREENSPACE_SHADOWS UNITY_PBS_USE_BRDF2 UNITY_PBS_USE_BRDF3 UNITY_PRETRANSFORM_TO_DISPLAY_ORIENTATION UNITY_UNIFIED_SHADER_PRECISION_MODEL UNITY_VIRTUAL_TEXTURING

 

I'm trying to use VertExmotion along with HBAO, but the HBAO post process is producing a strange outline which shows the mesh both before and after deformations from VertExmotion. Any idea how I can work around this?

Was wondering if it could be something simple like an ordering issue, but tried setting HBAO higher in the script execution order and no luck.

There seems to be an incompatibility between the two assets. I contacted the HBAO developer and he replied with a tidbit of information that may be useful to you.

"Like most SSAO solutions, HBAO require 2 inputs: depth and normals textures that Unity provides to shaders"

Any idea how I can work around this?

 

I tried out Amplify Occlusion since I saw another post saying it is compatible, however it has the exact same issue as HBAO, the strange ghosting between the mesh before and after VertExmotion deformation.



The only way around this that I can find is to set the "Per Pixel Normals" to "None," but unfortunately this leaves the mesh looking pretty bad without normals in the AO calculation.

Any ideas?

 

On the latest version of Unity you can use the vertex buffer mode instead of the shader mode,
it will work with any shader.

 

Hello,
Did you try the Vertex Buffer mode ?

 

Where do I find Vertex Buffer mode?

Edit: Found it, and it works perfectly!


Thanks! This will make my life a lot easier since I no longer need to manual update my custom shaders.

 

Hi @kalagaan, this looks like an incredible asset, and I'm super impressed that you've maintained it since 2014! I'm currently evaluating it for use in a game about cells, where I was going to represent the cell membranes as softbodies to give them some fluidity and deformability. One other critical requirement is to be able to merge other small softbodies (vesicles) with this membrane, or pinch them off. Your push and pull interactions look promising, but does your asset provide a way to actually "merge" two softbody meshes into one, or split one apart?

 

VertExmotion doesn't modify the original geometry, it's a way to deform existing meshes.
The sensors are spheres (or cylinder) where you can modify the vertices with some settings (offset, inflate, jiggle...)
You can share them between different objets, so if the vertex density is the same, both surfaces could be modified in the same way in worldspace.
Not sure that it will feet exactly what your need, but it could help to have nice interactions.

 

Cool, thank you for clarifying. Looks like I'll need to find a good asset for combining meshes or write something crude myself. VertExmotion should be great for the fluidity part though. Thanks again!

 

Hi @kalagaan, this asset is really nice. Is there any tutorial for collisions?
For example at this demo(http://www.kalagaan.com/VertExmotion/Demos/Collisions/) and in general for simple collisions can be done only with sensors or there's a script needed? If there's a script needed do you have a tutorial or example?

 

A default collision system is included in the sensor's settings, there's some informations in the documentation.
https://www.kalagaan.com/VertExmotion/Doc/VertExmotion_doc.pdf

There's some examples in the package for using the collision system and some scripts for advanced collisions based on procedural sensor spawn and control, it really depends of the effect you need.

 

Thank you very much!

 

Does this asset work with HDRP and also with Skinned Meshes that use/manipulate Blendshapes at runtime?

 

Yes it works with all render pipelines and blendshapes.

 

Thought I would just share this small bit of info here as I was struggling with syncing up my character mesh soft body with attached clothing and couldn't find any solid answers in this thread. What ended up working best for me was to programmatically copy the sensors and sensor links from the VertExmotion component on my character to the one on my clothing item. The important part was copying the sensor LINKS as well as the sensor itself.

This + ensuring that the vertex painting on your base mesh and on your attachment/clothing is similar (in my case I just fully painted (red) the animated areas on my base mesh and clothing) and you can get it basically 100% accurate. I have a extremely thin, tightly wrapped bandage on my characters leg which is now simulating perfectly.