Search Issue Tracker
Fixed in 2022.2.0b15
Fixed in 2022.2.X, 2023.1.X, 2023.1.0a17
Votes
0
Found in
2022.2.0b7
2023.1.0a8
Issue ID
UUM-12522
Regression
Yes
[VFX] Unexpected behavior with spawn context state
Modify value position in spawn context doesn't behave as expected when instancing is enabled.
Step to repro:
- Import VFX
- Try to move it in scene
Expected: follow the local position with some delay
Actual: Seems to not be able to reach previous position
Side note, it's also reproducible in our test suite with 009_ReadChaining.
Workaround: Disable instancing on this asset avoid the issue
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
Add comment