ObiMeshBasedActorBlueprintEditor coludn't be created

[buscfred]

Hello,
every time i try to create a new ObiSoftbodyBlueprint surface or ObiSoftbodyBlueprint volume i get the following errors in my console:

Instance of ObiMeshBasedActorBlueprintEditor couldn't be created. The script class needs to derive from ScriptableObject and be placed in the Assets/Editor folder.
Instance of ObiMeshBasedActorBlueprintEditor couldn't be created. The script class needs to derive from ScriptableObject and be placed in the Assets/Editor folder.
UnityEngine.GUIUtilityrocessEvent(Int32, IntPtr)

Therefore I am not able to use the editor for the blueprint as shown in the documentation (I can't even press 'Generate' for my mesh).

   
   

[josemendez]

Hello,
every time i try to create a new ObiSoftbodyBlueprint surface or ObiSoftbodyBlueprint volume i get the following errors in my console:

Instance of ObiMeshBasedActorBlueprintEditor couldn't be created. The script class needs to derive from ScriptableObject and be placed in the Assets/Editor folder.
Instance of ObiMeshBasedActorBlueprintEditor couldn't be created. The script class needs to derive from ScriptableObject and be placed in the Assets/Editor folder.
UnityEngine.GUIUtilityrocessEvent(Int32, IntPtr)

Therefore I am not able to use the editor for the blueprint as shown in the documentation (I can't even press 'Generate' for my mesh).

Hi there,

Can't reproduce here, but a quick search reveals it seems to be a bug in Unity:
https://forum.unity.com/threads/custom-e...ug.579088/
https://forum.unity.com/threads/the-scri...ct.650857/

Even the "Multi-object editing not supported" message appears in your screenshot despite having only one object selected, which is indicative of the bug.

Seems to fix itself by restarting the Editor.

[buscfred]

Hi there,

Can't reproduce here, but a quick search reveals it seems to be a bug in Unity:
https://forum.unity.com/threads/custom-e...ug.579088/
https://forum.unity.com/threads/the-scri...ct.650857/

Even the "Multi-object editing not supported" message appears in your screenshot despite having only one object selected, which is indicative of the bug.

Seems to fix itself by restarting the Editor.

I restarted the editor mayn times already and this sadly didn't fix the bug.

[josemendez]

I restarted the editor mayn times already and this sadly didn't fix the bug.

What Unity version are you using?

[buscfred]

What Unity version are you using?

Unity 2019.3.1f1

[josemendez]

Unity 2019.3.1f1

We've tried 2019.2.9f1 and 2020.1, couldn't reproduce in either. Will try to test in 2019.3.1f1. Does this also happen to you when selecting any of the included softbody blueprint assets?

The error message suggests that Unity has tried to create a instance of a custom inspector script as if it were a ScriptableObject, which it clearly isn't. Also, the "Multi-object editing not supported" should not appear at all unless you have multiple assets selected (which is probably not the case).

[buscfred]

We've tried 2019.2.9f1 and 2020.1, couldn't reproduce in either. Will try to test in 2019.3.1f1. Does this also happen to you when selecting any of the included softbody blueprint assets?

The error message suggests that Unity has tried to create a instance of a custom inspector script as if it were a ScriptableObject, which it clearly isn't. Also, the "Multi-object editing not supported" should not appear at all unless you have multiple assets selected (which is probably not the case).

The same error message pops up when selecting one of the included blueprints.

[josemendez]

The same error message pops up when selecting one of the included blueprints.

Just tested in 2019.3.1f1, but sadly I could not reproduce the issue. Selecting both existing or freshly created blueprints works just fine.

I've seen some people with the same issue in other packages:
https://www.noesisengine.com/forums/view...f=3&t=1736

The Unity forums have some threads with the issue, potential solutions other people have reported:
- Reimport the project.
- Restart Unity Hub.
- Restart Unity Editor.

If none of the above work, let me know and I'll raise a bug in the Unity forums.

[buscfred]

Just tested in 2019.3.1f1, but sadly I could not reproduce the issue. Selecting both existing or freshly created blueprints works just fine.

I've seen some people with the same issue in other packages:
https://www.noesisengine.com/forums/view...f=3&t=1736

The Unity forums have some threads with the issue, potential solutions other people have reported:
- Reimport the project.
- Restart Unity Hub.
- Restart Unity Editor.

If none of the above work, let me know and I'll raise a bug in the Unity forums.

We tried all of the above thanks for your help so far. another question is it important how obi is located in our project? As shown in the image below:
   

[josemendez]

We tried all of the above thanks for your help so far. another question is it important how obi is located in our project? As shown in the image below:

As long as you don't change or rearrange the contents of the /Obi folder, you can place this folder pretty much anywhere.

Does this also happen to you if you create a fresh project and import Obi?