Search Issue Tracker
By Design
Votes
1
Found in
2018.1.0b7
Issue ID
1005448
Regression
No
Transform position gets corrupted after destroying and instantiating objects multiple times when TransformAccessArray is used
To reproduce:
1. Open repro project(link in edit)
2. Open and play 'FontXR_Calibrator' scene
3. Move mouse cursor through the pink gameObject while holding LMB
4. Press B key a couple of times('Object Instantiator' child objects will be destroyed and re-initialized )
5. Move mouse cursor through the pink gameObject while holding LMB
Expected: result in 3rd and 5th steps should look identical.
Actual: in 5th step, we can see that transform positions are incorrect
Reproduced: 2018.1.0b1, 2018.1.0b12, 2018.2.0a5
Could not reproduce on earlier versions, because of editor crashes
Note: The first time an object is dynamically instantiated and its transforms are moved via TransformAccessArray correctly
Workaround:
comment line 594 in DynamicBoneThreaded.cs and uncommenting m_ParticleJobHandle.Complete() and ApplyParticlesToTransforms() methods
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Add comment