Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We’re making changes to the Unity Runtime Fee pricing policy that we announced on September 12th. Access our latest thread for more information!
    Dismiss Notice
  3. Dismiss Notice

[Physics.PhysX] QuickHullConvexHullLib::findSimplex: Simplex input points appers to be coplanar.

Discussion in 'Physics' started by ArchCodeEmbodyRomance, Feb 20, 2020.

  1. ArchCodeEmbodyRomance

    ArchCodeEmbodyRomance

    Joined:
    Jan 5, 2017
    Posts:
    1
    I create a Quad, and set its Transform as follows:
    position (306.2141, -94.32835, 378.1256)
    rotation (31.305, -86.606, 90.394)
    scale (11.69272, 100.1775, 15.23574).
    When i check “Convex“ propertie on Mesh Collider Component,it is no error.
    Then i change "Cooking Options" on Mesh Collider Component and check “Convex“ propertie on Mesh Collider Component again, editor pring two error:
    1.[Physics.PhysX] QuickHullConvexHullLib::findSimplex: Simplex input points appers to be coplanar.
    UnityEngine.GUIUtility:processEvent(Int32, IntPtr)
    2.Failed to create Convex Mesh from source mesh "Quad". An internal unspecified error has occured that could mean the Quickhull algorithm found the input mesh topologically challenging.
    UnityEngine.GUIUtility:processEvent(Int32, IntPtr)
    Final I change Rotation or Scale and check “Convex“ propertie on Mesh Collider Component again, The error disappear.
    My Unity version is 2019.3.0f5.
    I would like to know the reason for this problem and how I should tell the artists to avoid it

    I`m so sorry about my Englis.
     

    Attached Files:

  2. raitoryuukuu

    raitoryuukuu

    Joined:
    Jan 21, 2020
    Posts:
    7
    did you ever found a solution ?
     
  3. DevDunk

    DevDunk

    Joined:
    Feb 13, 2020
    Posts:
    4,220
  4. A5Xyck

    A5Xyck

    Joined:
    Jan 25, 2020
    Posts:
    1
    Had the same Error

    Recreating the parent object, which had weird rotations and scalings, did it for me.
    Guess it has something to do with parent-child transform relations.