Search Issue Tracker

Fixed in 2022.2.X

Votes

2

Found in

2021.2.0a9

2021.2.14f1

2022.1

2022.2

Issue ID

1409430

Regression

Yes

"This Mesh Collider is attached to GameObject but doesn't have Read/Write enabled" error when creating a mesh without vertices

Physics

-

Reproduction steps:
1. Open the user's attached "MeshTest.zip" project
2. Open the "SampleScene" Scene
3. Enter the Play mode
4. Observe the Console window

Expected result: The error tells the user that they are trying to set a mesh with 0 vertices.
Actual result: "This Mesh Collider is attached to GameObject at path 'TestMesh' with Mesh '' in Scene 'SampleScene' but doesn't have Read/Write enabled. Only colliders that have default cooking options, are not scaled non-uniformly, and their meshes are not marked dirty can leave this disabled." error message appears

Reproducible with: 2021.2.0a9, 2021.2.15f1, 2022.1.0b12, 2022.2.0a8
Not reproducible with: 2019.4.36f1, 2020.3.36f1, 2021.2.0a8

  1. Resolution Note (fix version 2022.2):

    Fixed in 2022.2.0a12

Log in to vote on this issue

Comments (2)

  1. kobyfr

    Nov 04, 2022 14:54

    my project was started as a 2021 project.
    my prefab has an empty object that was added a mesh collider.
    Even though I set the mesh collider to "cook everything", it seems not to set that option properly.

    MeshCollider:
    m_ObjectHideFlags: 0
    m_CorrespondingSourceObject: {fileID: 0}
    m_PrefabInstance: {fileID: 0}
    m_PrefabAsset: {fileID: 0}
    m_GameObject: {fileID: 1391453082}
    m_Material: {fileID: 13400000, guid: 9e79fd23270d43e488214eac3126c892, type: 2}
    m_IsTrigger: 0
    m_Enabled: 1
    serializedVersion: 4
    m_Convex: 1
    m_CookingOptions: 0
    m_Mesh: {fileID: 5032453918844749008, guid: 1ced72a21e301354ab9612efc3caa845, type: 3}
    --- !u!1 &1000010996348880

    Once I moved to the 2022 Unity version, created a new mesh collider component on top of a new object, and copied the values to the original mesh collider component, was it set to its proper values.

    MeshCollider:
    m_ObjectHideFlags: 0
    m_CorrespondingSourceObject: {fileID: 0}
    m_PrefabInstance: {fileID: 0}
    m_PrefabAsset: {fileID: 0}
    m_GameObject: {fileID: 1391453082}
    m_Material: {fileID: 13400000, guid: 9e79fd23270d43e488214eac3126c892, type: 2}
    m_IncludeLayers:
    serializedVersion: 2
    m_Bits: 0
    m_ExcludeLayers:
    serializedVersion: 2
    m_Bits: 0
    m_LayerOverridePriority: 0
    m_IsTrigger: 0
    m_ProvidesContacts: 0
    m_Enabled: 1
    serializedVersion: 5
    m_Convex: 1
    m_CookingOptions: 30
    m_Mesh: {fileID: 5032453918844749008, guid: 1ced72a21e301354ab9612efc3caa845, type: 3}
    --- !u!1 &1000010996348880

    I believe this to be a problem with porting of a 2021 project to a 2022 project format.

  2. kobyfr

    Nov 04, 2022 14:17

    bug reproduced in 2022.2.0b13, by adding a mesh collider to an object, a mesh that is taken from the "Low-Poly Spaceships Set", which is free in the asset store.

    Mono path[0] = 'C:/dev/pq/games/2d_space_shooter/builds/windows/My project_Data/Managed'
    Mono config path = 'C:/dev/pq/games/2d_space_shooter/builds/windows/MonoBleedingEdge/etc'
    Found 1 interfaces on host : 0) 192.168.1.113
    Multi-casting "[IP] 192.168.1.113 [Port] 55000 [Flags] 2 [Guid] 3434088012 [EditorId] 3010125751 [Version] 1048832 [Id] WindowsPlayer(2,LEGION-KF) [Debug] 0 [PackageName] WindowsPlayer [ProjectName] My project" to [225.0.0.222:54997]...
    Initialize engine version: 2022.2.0b13 (458a6ada3646)
    [Subsystems] Discovering subsystems at path C:/dev/pq/games/2d_space_shooter/builds/windows/My project_Data/UnitySubsystems
    GfxDevice: creating device client; threaded=1; jobified=0
    Direct3D:
    Version: Direct3D 11.0 [level 11.1]
    Renderer: NVIDIA GeForce GTX 1050 (ID=0x1c8d)
    Vendor: NVIDIA
    VRAM: 4019 MB
    Driver: 27.21.14.5749
    Begin MonoManager ReloadAssembly
    - Loaded All Assemblies, in 0.135 seconds
    - Finished resetting the current domain, in 0.002 seconds
    <RI> Initializing input.

    New input system (experimental) initialized
    Using Windows.Gaming.Input
    XInput1_3.dll not found. Trying XInput9_1_0.dll instead...
    <RI> Input initialized.

    <RI> Initialized touch support.

    UnloadTime: 1.211500 ms
    This Mesh Collider is attached to GameObject at path 'Hovercraft/Collider' with Mesh '5.3' in Scene 'TestScene' but doesn't have Read/Write enabled. Only colliders that have default cooking options, are not scaled non-uniformly, and their meshes are not marked dirty can leave this disabled.

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