Search Issue Tracker
By Design
Votes
0
Found in
2021.3.34f1
2022.3.19f1
2023.2.8f1
2023.3.0b4
Issue ID
UUM-62408
Regression
No
GameObjects get displaced when Material with procedural movement is applied
How to reproduce:
1. Open the attached “ObjectDisplacement.zip” project
2. Open the "SampleScene"
3. Apply "Wind" Material to the "Plane A" GameObject in the Scene view (Assets > Materials)
4. Observe the GameObject
Expected result: GameObject does not get displaced
Actual result: GameObject gets displaced
Reproducible with: 2021.3.34f1, 2022.3.19f1, 2023.2.8f1, 2023.3.0b4
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Notes:
- Does not reproduce if the GameObject is at (0;0;0) position, for example “Plane A” GameObject
- GameObjects may appear as invisible, due to Culling, if the original GameObject’s position goes out of the Camera view
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Spot Light with 'Box' Shape stops working when it collides with Mesh
- Accepting Asset Store EULA endless loop in Package Manager window
- “InvalidOperationException: Sequence contains no matching element“ error when reenabling a custom Debug Draw Mode
- Prefab that contains a layout group is marked as changed by the Editor when opened
- Emission animation does not appear when the "Emission Map" parameter is set to black in a Lit material
Resolution Note:
When using shader graph, the vertex stage outputs are expected to be in object space. The Wind shader graph in the provided project applies displacement against world space position and feeds that as input.
In these situations, determining the deformation in world space makes a lot of sense. You just need to use the transform node to transform the displaced world position back into object space before connecting it to the vertex stage outputs.