Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Bug / Crash  Path Editor not interactable.
#1
I'm unable to interact with the fields in the "Path editor" on the Obi Rope component in my scene. I am however able to edit the point placement inside the viewport.

OS: Windows 10
Unity: 2019.3.7f1
Scripting Backend: Mono
Api Compatability Level: .NET 4.x

[Image: k9H7uP]
Reply
#2
Hi,

I'm unable to reproduce this. Do you have any control points selected? (actually if you have no points selected, the GUI properties are disabled and should appear grayed out, so there's definitely something weird going on here).
Reply
#3
Yes, they grey out if I have no points selected, and these fields populate if I select one. Also, the values change if I manipulate the gizmos.

(06-04-2020, 06:32 PM)dylanrw Wrote: Yes, they grey out if I have no points selected, and these fields populate if I select one. Also, the values change if I manipulate the gizmos.

This problem persisted through a couple unity restarts, but, oddly, if I turn gizmos on and off suddenly I can interact with the fields!
Reply
#4
It's not the intended behavior, for sure, but I'm glad you got it working. Will try to reproduce and hopefully fix it. Thanks for reporting this!
Reply
#5
(06-04-2020, 07:31 PM)josemendez Wrote: It's not the intended behavior, for sure, but I'm glad you got it working. Will try to reproduce and hopefully fix it. Thanks for reporting this!

I'm finding that if I select a new point the fields aren't functionally, but then if I toggle gizmos I can edit them.

(06-04-2020, 09:43 PM)dylanrw Wrote: I'm finding that if I select a new point the fields aren't functionally, but then if I toggle gizmos I can edit them.

Also, I just updated to 2019.3.8f1 and it still persists.
Reply
#6
Hi,

Unable to reproduce on 2019.2.9f1, or 2019.3.8f1.

Are you able to reproduce this in a fresh project? Do you have any other assets installed that might make use of/modify the editor UI? Immediate mode GUI is basically a state machine, It wouldn't be the first time I've come across an asset that leaves the state corrupted, causing all sort of random issues in any GUI drawn after it. (AURA2 comes to mind, though I believe they fixed it in newer versions)
Reply
#7
Hi,

Glad you figured it out! I'm still unable to reproduce. I've created a custom tool to test this, basically copy-pasting the one in Unity's docs:
https://docs.unity3d.com/ScriptReference...rTool.html

While having this tool selected, I'm able to open and use the Path editor. Unity 2019.2.9f and 2019.3.7f1.
Reply