So I got a very simple test case that causes a runtime crash with WebGL in Unity 5 Release Candidate 1, hopefully this will help you diagnose / narrow down the cause.
So a brief description of the code. I have my custom class which derives from MonoBehaviour. I also have a serialised BB Variable for this class (CollectibleObject.cs)
I have two actions, NullGameObject which calls BBObject.value = null;
and NullCollectibleObject which calls BBCollectible.value = null;
There is one gameobject in the scene with the BT, it has a blackboard variable of type UnityEngine.Object. This is then further specified (via custom Preferred Types) to be of type Collectible.
If I call BBCollectible.value = null then it will crash on that provided variable, however if I just call BBObject.value = null then it will not crash (you can test this with both actions). Hope this makes sense, I’ve also attached a screenshot of the tree to this post. But it may be more self explanatory to check out the project directly. Thanks.
Ah interestingly, so this project was failing consistently in Unity beta 18,
Now with RC1 it crashes identically in NodeCanvas if Player Settings -> Exceptions is set to None, however if exceptions is set to any other value, it doesn’t crash.
Hello and sorry for such a late response, but Im overwelmed lately due to version 2 🙂
I didnt yet have time to take a look at WebGL, but I will as soon as v2 is out.
Thanks for the provided info, I will bookmark the post and take a look again after the fact.
Cheers!
Join us on Discord: https://discord.gg/97q2Rjh
Author
Posts
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic.
Login
Register
By registering on this website you agree to our Privacy Policy.