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. Unite 2023 Registrations are now LIVE! We are thrilled to announce that Unite 2023 Registration is now live and open for all!
    Dismiss Notice
New Forum User Notice Unite 2023 Registrations are now LIVE!

Bug algo.decimateTarget: prints "Should not happen"

Discussion in 'Pixyz' started by mgear, Oct 9, 2023.

  1. mgear

    mgear

    Joined:
    Aug 3, 2010
    Posts:
    8,988
    Tested decimateTarget in one model (cannot share the model),
    but just posting here just for into that is printed those "Should not happen" few times..
    (pixyz 2022.1 update 2 r7)

    *process was bit slow it was cancelled,
    so cannot confirm if it would had finished normally, even with those errors, probably would.

    [2023/10/09 12:04:16] executing command algo.decimateTarget
    [2023/10/09 12:04:16] occurrences: [2]
    [2023/10/09 12:04:16] targetStrategy: ["ratio", 80.000000000000]
    [2023/10/09 12:04:16] UVImportance: algo.UVImportanceEnum.PreserveSeamsAndReduceDeformation
    [2023/10/09 12:04:16] protectTopology: False
    [2023/10/09 12:04:16] iterativeThreshold: 5000000
    [2023/10/09 12:04:16] Current triangle count (20673251) is above the iterative threshold (5000000) => run iterative method
    [2023/10/09 12:06:13] Using a max error of 10200.7 at iteration 1/10
    Should not happen
    Should not happen
    [2023/10/09 12:08:54] 18726413 triangles remaining after iteration 1/10
     
    mgear, Oct 9, 2023
    #1

  2. AxelJacquet

    AxelJacquet

    Unity Technologies

    Joined:
    Oct 18, 2021
    Posts:
    13
    Hello @mgedikoglu
    Thank you for this new message.
    Without the model, it will be indeed hard to replicate and potentially fix...
    It's an unhandled case that can happen in some complex local topology cases.
     
    AxelJacquet, Oct 10, 2023
    #2