Search Issue Tracker
Fixed in 7.1.6
Votes
0
Found in [Package]
7.1.0
Issue ID
1170205
Regression
Yes
[Block] Some blocks no longer have a default texutre assignment and throw console errors
Repro steps:
1. Open a VFX Graph
2. Add a Vector Field Force block in Update
3. Observe the console errors:
Compute shader ([System 2]Update Particle): Property (VectorField_a) at kernel index (0) has mismatching texture dimension (expected 3, got 2)
Notes:
- The default vector field texture used to be assigned
- Not having a texture assigned did not used to throw console errors
- Same issue with Collide / Conform to SDF blocks
- Works fine in 6.9.0
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Add comment