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. Let us know your feedback about the Global Illumination changes in the 2023.2 beta.
    Dismiss Notice
  3. 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 Feedback request: Global Illumination changes Unite 2023 Registrations are now LIVE!

Problem with DLLs causing crash

Discussion in 'Unity 5 Pre-order Beta' started by TerabyteTim, Nov 19, 2014.

  1. TerabyteTim

    TerabyteTim

    Joined:
    Oct 20, 2011
    Posts:
    115
    I'm currently using Beta 13, on Windows 7. I'm attempting to utilize the new Unity UI system. It seems the crash may be at least related to initializing a new UI via C#.

    In my editor log I get the errors 'The specified module could not be found.' and 'A dynamic link library (DLL) initialization routine failed.'. This is what caused me to believe it's something related to a DLL.

    Here's a copy of the Editor.log directly after the crash:

    You'll see the crash trace at the bottom. Does anyone have any ideas what may be going wrong? I've disabled all scripts that would use plugins in the scene and it's still happening, so it may be a builtin DLL.
     
    TerabyteTim, Nov 19, 2014
    #1

  2. TerabyteTim

    TerabyteTim

    Joined:
    Oct 20, 2011
    Posts:
    115
    Weird, I'm also getting an error message when I click on any plugin to view in the inspector:

    Followed by this:

    I've completely reimported each plugin and still get the same error messages.

    EDIT:
    The above error seems to be a weird issue with paths. When I place the plugin in "Assets/Plugins/x86_64" I get the above error. But if I move the plugin to "Assets/Plugins" I get no error. I'm going to try moving all my plugins to utilize this and see how it helps with the initial error.
     
    Last edited: Nov 19, 2014
    TerabyteTim, Nov 19, 2014
    #2

  3. TerabyteTim

    TerabyteTim

    Joined:
    Oct 20, 2011
    Posts:
    115
    Aha, I solved it! Turns out it was due to something with the path location of the plugins. I moved all my plugins to just be in "Assets/Plugins" and assigned them the correct CPU types and everything works significantly better now.
     
    TerabyteTim, Nov 19, 2014
    #3

  4. TerabyteTim

    TerabyteTim

    Joined:
    Oct 20, 2011
    Posts:
    115
    Well, this solved it for about a day. Unity just randomly started crashing again with the same DLL error. I have no clue what's going wrong now.
     
    TerabyteTim, Nov 21, 2014
    #4

  5. Tomas1856

    Tomas1856

    Unity Technologies

    Joined:
    Sep 21, 2012
    Posts:
    3,658
    I think this is fixed in upcoming 5.0b14, but just to be sure, send a bug report with simple repro.

    Also, you could try deleting *.meta data file next to the plugin, this way the settings for plugin will be resetted, at least that way you won't get a crash.
     
    Tomas1856, Nov 21, 2014
    #5

  6. chrismarch

    chrismarch

    Joined:
    Jul 24, 2013
    Posts:
    463
    Do all the native plugins need to be in Assets/Plugins? Our 3rd party native plugins import to Assets/ThirdPartyCompanyName/Scripts and Assets/ThirdPartyCompanyName/Scripts/Editor.
     
    chrismarch, Nov 25, 2014
    #6

  7. Tomas1856

    Tomas1856

    Unity Technologies

    Joined:
    Sep 21, 2012
    Posts:
    3,658
    No, starting from 5.0, you can place them anywhere you want, the same goes for managed plugins.
     
    Tomas1856, Nov 25, 2014
    #7
    chrismarch likes this.