Some node inspectors do not appear after importing Odin about monobehaviourtree

[Qriva]

Hello, could you provide a little bit more details?
Does this problem encounter when odin is used in node inspectors or by having odin imported in the project? By nodes you mean graph nodes or their inspector?

I am not in possesion of odin right now, but in any case it would be good to have some reproduction steps. My wild guess is that odin tries to enforce some custom inspector and it breaks how things are displayed.

[corpvs2]

I found that many nodes cannot be displayed, such as root and wait node
however IsSetCondition.cs Node Can displayed,
I tried to create a new leaf node with only one int variable, and it seems that it can't be displayed

[Qriva]

In this case I think the problem appears on all nodes without custom inspector, but it's hard to say if this is fault of my code or just odin is broken in some way. Please check if you odin version is not too old.
Anyway I will try to do something to investigate this problem - please give me odin version used in your project.

[corpvs2]

Hi odin version is 3.0.13

[Qriva]

I contacted odin devs on discord and I think 92d8753 should fix this problem.
Asset store version will come later (it requires approval anyway), so you can test if everything works by adding package via upm: https://github.com/Qriva/MonoBehaviourTree.git#upm

[Qriva]

Fix landed in asset store: https://assetstore.unity.com/packages/tools/ai/monobehaviourtree-213452#version-current

[corpvs2]

hi Thank you very much. I'm going to use him to make some AI

…

------------------ 原始邮件 ------------------ 发件人: "Qriva/MonoBehaviourTree" ***@***.***>; 发送时间: 2022年8月12日(星期五) 晚上11:21 ***@***.***>; ***@***.******@***.***>; 主题: Re: [Qriva/MonoBehaviourTree] Some node inspectors do not appear after importing Odin (Issue #4) Fix landed in asset store: https://assetstore.unity.com/packages/tools/ai/monobehaviourtree-213452#version-current — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>