Search Issue Tracker
Fixed in 10.1.0
Votes
0
Found in [Package]
5.2.0-preview
Issue ID
1232867
Regression
No
[VFX Graph] Node rendering is corrupted when a binary Point Cache Node is connected
Steps to reproduce:
1. Open the attached project (case_1232867.zip)
2. Double-click on "case_1232867-MeshTest" Visual Effect Asset in the Project Browser
3. Connect "AttributeMap : position" from Point Cache Node to "Attribute Map" in Set Position from Map Node
4. Connect "AttributeMap : normal" from Point Cache Node to "Attribute Map" in Set Velocity from Map Node
Expected result: No visual changes
Actual result: Rendering breaks for several related and unrelated Nodes and their properties become unreadable
Reproduced in: 5.2.0-preview (2019.1.14f1), 7.3.1 (2020.2.0a5), 8.0.1 (2020.1.0b4)
Not reproducible in: 4.10.0 - preview (2018.4.20f1)
Note:
- The issue does not reproduce with an ASCII-formatted pCache
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (fix version 10.1.0):
Fixed in VFX Graph 10.2.0