Some issues encountered with Behavior 1.0.1

Unity Engine
, , , , ,
1

I recently upgraded to start using Behavior 1.0.1 and encountered a few issues that I would like to bring to your attention (@ShaneeNishry).

  1. Duplicating a variable comparison does not correctly duplicate the operation (duplicating a “Lower” makes it an “Equal”)
  2. Sometimes when selecting a node, its fields show briefly in the inspector and then they disappear. I think a ‘drag operation’ is being initiated. I think it should either:
    a) Not initiate a drag until there is more mouse movement
    b) Ensure that after a drag, the dragged node is selected and shown in the inspector
    Or maybe both…
  3. Searching for BehaviorAgent (or t:BehaviorAgent) in the hierarchy doesn’t find objects with the component; I guess this is because the component type is a ‘BehaviorGraphAgent’, but it’s confusing when it shows up in inspector as ‘Behavior Agent’
  4. In 0.10.1, I used to be able to compare a reference variable to null (by not specifying the compare value), but now comparing equality to an empty value seems to return false when the variable has no value. I guess this may be by design, but it would be good to have some way to test if a reference was null.
  5. Sometimes UI seems to become unresponsive (can’t zoom, edit nodes, move nodes around or anything). Unity as a whole is not frozen and closing and reopening the window seems to fix it. I sometimes have a similar issue, but it only seems to affect zooming. In this case, I have tried closing just the tab and reopening it from the Open menu, but that did not help - closing the whole window and reopening by double clicking the behavior asset did. I’m not sure what triggers the issue, but I have a feeling it relates to dragging blackboard variables into slots. At least, I encountered it regularly at first (when I was dragging variables around) and seemed to stop seeing it when I switched to using the pop-up menu to select a variable instead.

Hoping these issues can be addressed soon, but apart from that, I’ve been enjoying using the updated version! Keep up the good work & progress! Kind regards,

Andy
1 Like
2

I’m off for a bit but someone else from the team will get back to you! Thanks so much for the feedback and I’m glad you’re enjoying it so far :slight_smile:

3

Thank you Andy for reaching out and bringing these issues to our attention.

Allow me to address each point you mentioned:

  1. Variable Comparison Issue: This issue flew under our radar, I have created an internal ticket and we will try to address it for the next release.
  2. Drag and Drop Issue: I have tried to reproduced it locally without success. We had some UI-related issues in Behavior 1.0.1, but they should have been addressed in version 1.0.2. We recommend upgrading to the latest version and verifying if the problem still occurs. If it does, could you provide us reproduction steps, so we can investigate further.
  3. Searching for BehaviorAgent: Good catch, I need to consult with the team about this change. I will gather more information and get back to you on this.
  4. Setting variable to null: Yes, this change was made by design. Based on user feedback, we are planning to introduce new nodes such as the Check Null condition and Reset Variable node in the upcoming version.
  5. Unresponsive UI: It appears that this issue has already been addressed in a previous release. We recommend upgrading to the latest version and checking if the problem persists. However, we are aware of a lingering issue with zoom/unzoom on the Windows platform when opening multiple graphs. The workaround for it is just as you described, closing the Graph window and reopening the asset. Could you please let us know the platform you are developing on?

Thank you again, your feedback is valuable in helping us improve the package. :muscle:

4

I have already upgraded to 1.0.2… so…:

1., 4. Good news about the upcoming fixes… thanks!
2. This seems to be fixed indeed, thanks!
3. This is not a big issue for me now I know what’s happening, so no need to get back to me, but I thought I’d bring it to your attention as it was confusing at first.
5. I’m actually developing on macOS - not sure if that rules out it being the same issue?

Cheers,

Andy
1 Like
5

Amazing, we were wondering about the bug potential being a platform specific issue as some of our engineer on Mac were not able to repo.

Could you let us know if you are still experiencing the zoom issue after the upgrade?

Thanks

6

Yes, it seems to persist on 1.0.2. I reproduced within a few clicks. I basically cleared three fields of a node using their ‘x’, then dragged one blackboard variable in to one of the slots, and then I was stuck. On this occasion, zooming still worked, but nothing else much did… at least not:

  • dragging nodes
  • dragging variables into node slots
  • clicking the link icon next to empty node slots.
  • editing inspector fields.

But closing the window and reopening fixed everything as usual. Note, this makes me all the more suspicious that it is relating to the dragging of blackboard variables, as I had not encountered this problem for a while - since precisely the time I stopped dragging blackboard variables and started using the drop down link icon/popup menu to select variables instead.

Hope that helps,

Andy

7

Thanks a lot for the detail, I’ll open a ticket to investigate the issue.