Search Unity

Native DLLs are not loaded correctly when Burst 1.2.2 is used to build a client

Discussion in 'Burst' started by sebas77, Feb 11, 2020.

  1. sebas77

    sebas77

    Joined:
    Nov 4, 2011
    Posts:
    1,642
    sebas77, Feb 11, 2020
    #1

  2. Carpet_Head

    Carpet_Head

    Joined:
    Nov 27, 2014
    Posts:
    258
    having the same issue, had to roll back to 1.2.1
     
    Carpet_Head, Feb 11, 2020
    #2

  3. xoofx

    xoofx

    Unity Technologies

    Joined:
    Nov 5, 2016
    Posts:
    417
    Our apologize, this is a regression that went through in 1.2.2 and also in our 1.3.0-preview.1.
    We have a fix that we hope to release today.
     
    xoofx, Feb 12, 2020
    #3

  4. xoofx

    xoofx

    Unity Technologies

    Joined:
    Nov 5, 2016
    Posts:
    417
    This regression was not caught because we didn't have any integration tests in Burst that would involve native plugins as well. We are adding a test for that case to track that we won't regress anymore.
     
    xoofx, Feb 12, 2020
    #4
    nicolasgramlich, elcionap, Carpet_Head and 1 other person like this.

  5. Slarti-42

    Slarti-42

    Joined:
    Jul 1, 2019
    Posts:
    49
    I would so like to use ECS, but I cannot as all the packages are using their own .dll and I have my own. I need my system.runtime.compilerservices.unsafe, but collections are using its own and there is no easy way to fix this unless I have overlooked it. What I found is, that quite many people are complaining about this.

    Wouldn't it make sense to create a shared user/package .dll folder and each package is installing it's .dll in that folder and when the .dll is already present, checks the version and keeps the latest?
     
    Slarti-42, Feb 13, 2020
    #5

  6. xoofx

    xoofx

    Unity Technologies

    Joined:
    Nov 5, 2016
    Posts:
    417
    The team responsible for collections is working on fixing this. I don't know the details but they will remove the need for unsafe and/or avoid assembly conflicts.
     
    xoofx, Feb 13, 2020
    #6
    Slarti-42 likes this.

  7. Slarti-42

    Slarti-42

    Joined:
    Jul 1, 2019
    Posts:
    49
    Awesome - is there an eta - approximatively? Just for my own planning. Can be a ballpark figure, but it makes a difference if it will be Q2, or Q2'2021 ;)
     
    Slarti-42, Feb 13, 2020
    #7

  8. xoofx

    xoofx

    Unity Technologies

    Joined:
    Nov 5, 2016
    Posts:
    417
    We just pushed Burst 1.2.3 which should fix the issue with native plugins.
    Burst 1.3.0-preview.1 is still affected by this issue, we hope to release a new version tomorrow.
     
    xoofx, Feb 13, 2020
    #8
    nicolasgramlich likes this.

  9. xoofx

    xoofx

    Unity Technologies

    Joined:
    Nov 5, 2016
    Posts:
    417
    Update: Burst 1.3.0-preview.3 is also released with the fix for native plugins issue.
     
    xoofx, Feb 13, 2020
    #9
    nicolasgramlich likes this.

  10. Slarti-42

    Slarti-42

    Joined:
    Jul 1, 2019
    Posts:
    49
    Hi Xoofx, while I appreciate this very much, it is in the collection package as well. :( can't use ECS
     
    Slarti-42, Feb 16, 2020
    #10

  11. tertle

    tertle

    Joined:
    Jan 25, 2011
    Posts:
    3,759
    We have no issue with collection / entity packages since updating burst.
     
    tertle, Feb 16, 2020
    #11

  12. Slarti-42

    Slarti-42

    Joined:
    Jul 1, 2019
    Posts:
    49
    Well depending on what external .dlls you are using.
     
    Slarti-42, Feb 17, 2020
    #12