Search Issue Tracker
Duplicate
Votes
0
Found in
2017.3.0b7
Issue ID
964379
Regression
Yes
Crash in PhysicsManager::SetColliderTransformChangeInterest after importing second project into unity
This has happened in 3 separate instances whild performing Asset Store Bash:
Repro :
1. Import 1 project with 3d physics- In my case was Republique Tech Demo. a smaller one would be Ultimate Survival.
2. Load up main scene
3. Exit play mode and import a second project with 3d physicsfrom the asset store (in my case, it was Tanks)
4. Try to load up a scene from the second project, and notice the crash.
Again, this has happened for my colleagues, with totally different asset store projects. The pattern seems to be the fact that both projects have physics.
stack:
0x0000000140974C83 (Unity) PhysicsManager::SetColliderTransformChangeInterest
(see more in the log attached).
Reproduces in 2017.3 0b7, b5, b3
No able to reproduce in 2017.2 f3, 2107.3 a2, 2017.3 a3, a7, b1
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
This is a duplicate of issue #958230