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 have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice
New Forum User Notice Update to the Unity Editor Software Terms

Mesh.Clear() vs Mesh.Clear(bool keepVertexLayout) in 2017.2.0b4

Discussion in '2017.2 Beta' started by raoul, Aug 1, 2017.

  1. raoul

    raoul

    Joined:
    Jul 14, 2007
    Posts:
    6,630
    Hi,

    I am getting a "No overload for method 'Clear' takes '0' arguments" for Mesh.Clear() when building a dll using the 2017.2 beta unityengine.dll.

    According to https://docs.unity3d.com/2017.2/Documentation/ScriptReference/Mesh.Clear.html mesh.Clear() is still safe to use.

    When using and older unityengine.dll to build the dll "MissingMethodException: Method not found: 'UnityEngine.Mesh.Clear'" is raised in beta 2017.2.0b4 when calling mesh.Clear().

    Is this an issue with 2017.2 beta or should we use Mesh.Clear(bool keepVertexLayout) ?

    Thanks,
    Raoul
     
    Last edited: Aug 1, 2017
    raoul, Aug 1, 2017
    #1

  2. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    3,111
    Hi raoul,
    Thanks for reporting this. Sounds like a bug. Could you please file a bug report with a minimal reproduction case and reply in here with the case #?
     
    LeonhardP, Aug 2, 2017
    #2

  3. raoul

    raoul

    Joined:
    Jul 14, 2007
    Posts:
    6,630
    raoul, Aug 2, 2017
    #3

  4. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    3,111
    Good catch. Can you check b5 and see if the error persists? The fix was approved a while ago.
     
    LeonhardP, Aug 2, 2017
    #4

  5. raoul

    raoul

    Joined:
    Jul 14, 2007
    Posts:
    6,630
    I just tried b5. Unfortunately the error persists. And indeed the same error message as in my first post is raised when building the dll using the new b5 unityengine.dll.

    Should I send a bug report or has the fix not made b5 yet?

    Thanks,
    Raoul
     
    Last edited: Aug 2, 2017
    raoul, Aug 2, 2017
    #5

  6. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    3,111
    Turns out it hasn't made it in yet. It's scheduled to be merged next week, so the estimate release would be b7. A report shouldn't be necessary.
     
    LeonhardP, Aug 3, 2017
    #6

  7. raoul

    raoul

    Joined:
    Jul 14, 2007
    Posts:
    6,630
    Thank you :)
     
    raoul, Aug 3, 2017
    #7

  8. tolosaoldfan

    tolosaoldfan

    Joined:
    Sep 14, 2012
    Posts:
    78
    Still present in 2017.2.0b8
     
    tolosaoldfan, Aug 30, 2017
    #8

  9. raoul

    raoul

    Joined:
    Jul 14, 2007
    Posts:
    6,630
    This is fixed in 2017.2.0b9, available since yesterday
     
    raoul, Aug 30, 2017
    #9
    Peter77 likes this.

  10. tolosaoldfan

    tolosaoldfan

    Joined:
    Sep 14, 2012
    Posts:
    78
    Thanks for the info !
     
    tolosaoldfan, Aug 30, 2017
    #10