Search Unity

Bug CollisionMeshData couldn't be created because the mesh has been marked as non-accessible problem.

Discussion in 'Editor & General Support' started by nsxdavid, Jun 17, 2020.

  1. nsxdavid

    nsxdavid

    Joined:
    Apr 6, 2009
    Posts:
    476
    Randomly, when our headless server (Linux Unity player) spins up, many meshes report the following error:


    CollisionMeshData couldn't be created because the mesh has been marked as non-accessible.

    This is not an issue of not having the mesh marked read/write, as the issue is transient. If we kill the process and restart it, it'll generally work fine.

    This, of course, makes it nearly impossible to have a fleet of game servers (on Multiplay) as anytime it spins up one, it's like 50/50 if it's going to spin up spewing these errors or not.
     
    nsxdavid, Jun 17, 2020
    #1
    adredengaming likes this.

  2. nsxdavid

    nsxdavid

    Joined:
    Apr 6, 2009
    Posts:
    476
    NOTE: No longer an issue. This was actually caused by a problem with Multiplay trying to start servers after a deploy before all the files were updated (not Unity Engine, but... you know... still Unity since they own Multiplay now!).
     
    nsxdavid, Jul 17, 2020
    #2