Search Issue Tracker

By Design

Votes

0

Found in

5.4.0p2

Issue ID

825135

Regression

Yes

Switching the graphics API creates 155 errors in the "Multistory Dungeons" asset

Editor - Other

-

Switching the graphics API creates 155 errors in the "Multistory Dungeons" asset

1. What happened

Opened the "Multistory Dungeons" asset from the asset store, changed the graphics API (e.g. Metal -> GLCore, or vice versa) and noticed 155 errors in the console window. The project seems to be working fine.

2. How we can reproduce it using the example you attached

- Download and open the attached project (Demo_01 Scene);
- Go to Player Settings and change the graphics API and see the 150+ errors in the console window.

Error message: "This MeshCollider requires the mesh to be marked as readable in order to be usable with the given transform."
Log in to vote on this issue

Comments (2)

  1. Elideb

    Dec 02, 2016 10:34

    If this is the same issue that affected our project, it is caused by using a MeshCollider in a GameObject with negative values in its scale. If that's the case, Unity now requires the mesh asset to be imported with Read/write enable set to true.

    I've created a script to help identify prefabs presenting this problem. It can be adapted to look into scenes, too.
    You can chek it here:
    https://github.com/Elideb/UnityInvertedMeshColliders/

  2. Jens_Restemeier

    Oct 21, 2016 12:09

    Ok, then, "Resolved by Design", what IS the design? What was the problem? How is it resolved?
    We have this on colliders that are never read other than by the collision system so shouldn't be readable.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues