Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2017.4.X, 2018.2.X
Votes
1
Found in
2018.1.6f1
Issue ID
1058082
Regression
No
Accessing unassigned collider's material returns and sets different material than the physics manager default material
How to reproduce:
1. Open the user-submitted project
2. Click on the Cube Object and observe Its Box Collider component
3. Enter Play mode
4. Observe the Box Collider Component again
Expected result: accessing the colliders material by script changes it to the default material set in the physics manager
Actual result: accessing the colliders materials sets the material to the "default" material instead of the material set in the physics manager
Reproduced in: 2018.3.0a5, 2018.2.0f2, 2018.1.8f1, 2017.4.6f1, 2017.2.3p2, 2017.1.4p2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Add comment