Search Unity

Burst 1.1 GUID change

Discussion in 'Burst' started by tertle, Jul 8, 2019.

  1. tertle

    tertle

    Joined:
    Jan 25, 2011
    Posts:
    3,761
    The burst asmdef GUID changed from

    b92ff8b696eb46a4b90382b319e963fe in 1.0.4
    to
    2665a8d13d1b3f18800f46e256720795 in 1.1.0 (preview 3)

    which is a bit annoying and breaks packages.

    Any particular reason why?
     
    tertle, Jul 8, 2019
    #1

  2. recursive

    recursive

    Joined:
    Jul 12, 2012
    Posts:
    669
    I'm also dealing with this, on 2019.3a8
     
    recursive, Jul 9, 2019
    #2

  3. Hyp-X

    Hyp-X

    Joined:
    Jun 24, 2015
    Posts:
    438
    +1

    Also the preview 4 package is broken:
    Code (CSharp):
    1. Cannot perform upm operation: shasum check failed for C:\Users\hyp-x\AppData\Local\Unity\cache\npm\packages.unity.com\.tmp11860IFojrsGAJdTF\tarball\package.tgz
    2. Expected: 83f9f4fb1b5f1869662103fa61362ac0def8b338
    3. Actual:   2a81c789c325423b67457b3d1bc1c1c961c7fcdb [NotFound]
    4. UnityEditor.EditorApplication:Internal_CallUpdateFunctions()
    Also 1.0.4 doesn't compile:
    Code (CSharp):
    1. Library\PackageCache\com.unity.burst@1.0.4\Editor\BurstAotCompiler.cs(638,32): error CS7036: There is no argument given that corresponds to the required formal parameter 'exceptionType' of 'BuildReport.AddMessage(LogType, string, string)'
     
    Hyp-X, Jul 9, 2019
    #3

  4. fabrizio_unity

    fabrizio_unity

    Unity Technologies

    Joined:
    May 3, 2018
    Posts:
    47
    Hello,
    Thank you for reporting this issue.

    We had an issue during the burst release process that was generating wrong GUIDs and this issue has been resolved before starting releasing 1.1.0 preview packages. Moving forward this issue will not occur and the correct GUID to be used to reference Unity.Burst assembly is 2665a8d13d1b3f18800f46e256720795.

    We apologise for any inconvenience it may cause.

    @Hyp-X
    The issue you see with the 1.0.4 version of the package is due to a change in the editor that came after we released our package and the compatibility has been restored in 1.1.0 preview packages.
    We are not able to reproduce yet the issue you are experiencing with preview.4, can you provide the editor version you are using and the steps to reproduce it?

    Thank you very much and sorry for the inconvenience,
    Fabrizio
     
    Last edited: Jul 10, 2019
    fabrizio_unity, Jul 10, 2019
    #4
    eterlan likes this.

  5. fabrizio_unity

    fabrizio_unity

    Unity Technologies

    Joined:
    May 3, 2018
    Posts:
    47
    Hello,

    The issue involving the preview.4 burst version showing

    Code (CSharp):
    1. Cannot perform upm operation: shasum check failed for C:\Users\hyp-x\AppData\Local\Unity\cache\npm\packages.unity.com\.tmp11860IFojrsGAJdTF\tarball\package.tgz
    2. Expected: 83f9f4fb1b5f1869662103fa61362ac0def8b338
    3. Actual:   2a81c789c325423b67457b3d1bc1c1c961c7fcdb [NotFound]
    4. UnityEditor.EditorApplication:Internal_CallUpdateFunctions()
    was due to an issue in the packages registry and our Package Manager team managed to fix it.
    No changes are required on your side.

    Please note the fix can take up to 1 hour from now until is completely functional.

    Please do not hesitate to let us know if you encounter the same issue again.

    Thank you,
    Fabrizio
     
    fabrizio_unity, Jul 10, 2019
    #5
    recursive likes this.