Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.1.6f1
Issue ID
1053595
Regression
No
Cinemachine Collider creates an empty object at the scene origin which collides with Character Controller
How to reproduce:
1. Open attached project "New Unity Project.zip" and scene "SampleScene"
2. Enter Play mode
3. Observe Scene or Game view
Expected result: Character Controller does not collide with the invisible object
Actual result: Character Controller collides with the invisible object
Reproducible with: 2018.1.7f1, 2018.2.0b11, 2018.3.0a3
Comments (1)
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
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
WeslomPo
Jun 28, 2019 09:01
So... if I understand fix correctly, fix is that:
```mCameraColliderGameObject.transform.position = new Vector3(float.MaxValue, float.MaxValue, float.MaxValue);```
But that lead to another problem, that all Physics.Raycast stop working if they not in positive/positive/positive half of quadtree. That is a very bad decision.