Our PC build runs OK but when we try to run a Web Player build, which works OK pre 5 Beta, we get a bunch of different “TypeLoadException: Could not load type ‘’ from assembly ‘’” messages. Some examples are:
‘UnityEngine.UI.Navigation’ from assembly ‘UnityEngine.UI, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null’
‘UnityEngine.UI.Toggle’ from assembly ‘UnityEngine.UI, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null’
‘UnityEngine.EventSystems.EventSystem’ from assembly ‘UnityEngine.UI, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null’
‘UnityEngine.Vector3’ from assembly ‘UnityEngine, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null’
‘FaceFXTriggerEntry’ from assembly ‘Assembly-CSharp, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null’
as well as:
MissingMethodException: Method not found: ‘UnityEngine.AddComponentMenu…ctor’.
and then a bunch of messages about:
“The script behaviour ‘’ could not be instantiated!”
“(Filename: C:/buildslave/unity/build/Runtime/Mono/MonoBehaviour.cpp Line: 1506)”
The WebGL build also doesn’t run but I’m not sure if it’s having the same issues since I don’t know where to find its log.
Anyone have any ideas? I saw another post about TypeLoadExceptions that seemed similar but there were no answers. I’m guessing it’s either a setting or somehow my build and Unity WebPlayer are out of sync.
It turns out that converting our project from 5.0.13b to 5.0.14b created the issue, at least with regards to the Web Player. I was going to try it with 5.0.16b but I couldn’t even get our 5.0.14b copy of our project to load anymore. Unity would eventually just close on its own without any sort of pop up to let me know there was a problem and the Editor log file had a lot of the same messages as the Web Player build when I tried to run it. I could still open it just fine with 5.0.14b. Fortunately I still had a copy of the project that we tried 5.0.13b on and when I copied that and tried 5.0.16b on it that allowed me to load the project. I then did a Web Player build which mostly runs though there are some sound issues and it seems that you have to set a script generated AnimationClip as legacy before you try to call SetCurve on it, which you don’t have to do when testing through the editor.
I still can’t get the WebGL version to run and haven’t found the information on debugging it or finding its log file.
Hey Guys, I’m having the same issue here with 5.0.B16 It was working great for a few days and somehow I got this issue now. It wasn’t a problem before (with the same build).
Any idea what causes it or how to solve it?
I just ran into this again under 5.0.16b. At first I thought it was because I had deleted my Library directory to see if some corruption was causing our Web Player build to not load sounds. What appears to have done it though was that I had selected “Development Build” and “Script Debugging” in case those could help track things down if sounds were still not loading. After doing a build with those checked it went back to not knowing what Vector3s and all the other stuff was. I rebuilt things with those unchecked and I can run again (still without sounds). Hope this helps get you going again.
Well OK, now I’m back to not knowing what’s going on again. I just ran the version that was working a couple hours ago to get the sound error messages so I could see if anyone else ever had the same problem and that version is now running into the same errors again. This is getting really old. I don’t know if it’s because I did a WebGL build afterwards or what but, like you, it’s the same build (sorry, I missed that the first time I read your post). Going to reboot my machine and see if that makes Unity happy again.
Well this has been interesting but I think I’ve figured it out. Since both hernaez build and mine hadn’t changed and we still had problems this meant some external force was a factor. After the standard reboot and all that sort of thing I was still having the same problem and had the feeling it wasn’t some issue with my computer itself. Then I remembered that when you run a web build it contacts the Unity site to see if any sort of update is needed. So I did a build that could be run offline. I tried that but the problem still happened, but I noticed it was still connecting to the Unity site so I pulled the power to my switch and was able to run three times in a row. I plugged the switch back in, waited to make sure I was connected to the net again, and the problem returned. It seems like at least sometimes they’re not realizing the version we’re trying to run and having us running the wrong one.
OK, so checking the log files with the version that runs I have “web: player version 5.0.0b16”, “Initialize engine version: 5.0.0b16” and my libraries and other data are coming out of …“/AppData/LocalLow/Unity/WebPlayer/player/Stable5.x.x-Development/”…
For the version that doesn’t run I have “web: player version 5.0.0b17”, “Initialize engine version: 5.0.0b17” and my libraries and other data are coming out of …"\AppData\LocalLow\Unity\WebPlayer\player\Beta5.x.x-Development"…
I should be building with 0b16 and haven’t installed 0b17 yet.
With the references to 5.0.0b17 I had the feeling that would be the case. I really hope this doesn’t keep happening. I’m glad everything is working for you now.