Search Issue Tracker
Fixed in 4.11, 5.8, 6.5
Votes
0
Found in [Package]
4.7.0
Issue ID
1133922
Regression
Yes
[VFX] Deleting a block in any contextual node disconnects all nodes connected to it
Repro steps:
1. Create a new particle system
2. Assign an inline Texture2D node to the main texture slot
3. Delete any node
4. Observe how the Texture2D node got disconnected
Notes:
- Tested in 18.3 and 19.1, happens in both
- Fairly certain it is a regression as this, not sure when it was introduced
- Happens in Initialize as well, if something is connected to the bounds
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
Add comment