Search Issue Tracker
Fixed in 2.4.0 - preview.4
Votes
0
Found in [Package]
2.2.7, 2.3.5
Issue ID
1176686
Regression
Yes
Cinemachine collider visualization is stuck when switching scenes
Repro steps:
1. Open attached project
2. Open the Physics Debug window and in the Physics Debug overlay panel check the "Collision Geometry" option
3. Open the "SampleScene" scene
4. Make sure you can see a sphere collider
5. Open the "SceneTwo" scene
Expected result: Collider disappears after changing the scene
Actual result: Collider is still seen
Reproducible with: 2018.4.7f1, 2019.1.14f1, 2019.2.2f1, 2019.3.0a12, 2020.1.0a1
Could not test with: 2017.4.32f1 (no package manager)
Reproducible with package versions: 2.2.7, 2.2.8, 2.2.9, 2.2.10, 2.3.5
Not reproducible with package versions: 2.2.0
Could not test with package versions: 2.1.13 (collider doesn't show)
Note: The sphere doesn't disappear when enabling and disabling the collider. With 2.2.0 it disappears after changing the scene.
Add comment
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
Resolution Note (fix version 2.4.0 - preview.4):
Fixed in 2.4.0 - preview.4