Unity 5.4中的ScriptableObject.ctor和LoadAssetAtPath错误
[英]ScriptableObject.ctor and LoadAssetAtPath error in unity 5.4
问题描述
I am getting these three errors each time i playing my scene. 
每次播放场景时都会出现这三个错误。 There error making no problem but i am unable to understand that why i am getting this. 有没有问题的错误，但我不明白为什么我得到了这个。
1 1
ScriptableObject.ctor is not allowed to be called from a ScriptableObject constructor (or instance field initializer), call it in OnEnable instead.
2 2
LoadAssetAtPath is not allowed to be called from a ScriptableObject constructor (or instance field initializer), call it in OnEnable instead.
3 3
UnityException: LoadAssetAtPath is not allowed to be called from a ScriptableObject constructor (or instance field initializer), call it in OnEnable instead.
1 个解决方案
解决方案1
1 2018-03-09 11:32:39
A ScriptableObject constructor should not be used for anything, unless you know exactly what you're doing and why you need to break the rules. 除非您确切知道自己在做什么以及为什么需要打破规则，否则ScriptableObject构造函数不应用于任何事情。 The reason is that ScriptableObjects aren't constructed in the main Unity thread, thus you can't really use the Unity API. 原因是ScriptableObjects不是在Unity主线程中构造的，因此您不能真正使用Unity API。 ( Debug.Log is one of the few Unity functions you can use in any thread.) （ Debug.Log是可以在任何线程中使用的少数Unity函数之一。）
Use the Awake or OnEnable functions for initialization. 使用Awake或OnEnable函数进行初始化。 If it's a MonoBehaviour , you can also use Start . 如果是MonoBehaviour ，则还可以使用Start 。 These are called automatically by the game engine. 这些由游戏引擎自动调用。
If you really can't find the offending class, you can use find/replace to change all the function calls from AssetDatabase.LoadAssetAtPath to MyDebugClass.LoadAssetAtPath . 如果您确实找不到令人讨厌的类，则可以使用find / replace将所有函数调用从AssetDatabase.LoadAssetAtPath为MyDebugClass.LoadAssetAtPath 。 Next, define: 接下来，定义：
#line hidden
public static class MyDebugClass
{
public static Object LoadAssetAtPath(string assetPath, Type type)
{
Debug.Log("LoadAssetAtPath called: " + assetPath);
return AssetDatabase.LoadAssetAtPath(assetPath, type);
}
}
#line default
This hack will show you each caller, and the message directly before the error will point to the culprit. 此hack将向您显示每个呼叫者，错误之前的消息将直接指向罪魁祸首。 (Not an elegant technique, but it will give you a fast answer. Though I can't check the syntax at the moment.) （这不是一种优雅的技术，但是它将为您提供快速的答案。尽管目前我无法检查语法。）
Note: #line hidden means this function won't show up in the stack trace. 注意： #line hidden表示此功能不会显示在堆栈跟踪中。 So the top line of your stack trace will be the line you're interested in, rather than a line inside MyDebugClass . 因此，堆栈跟踪的第一行将是您感兴趣的行，而不是MyDebugClass内的MyDebugClass 。
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.