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
- 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
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment