Behavior Package 1.0.12 Released!

We’re excited to announce that Behavior 1.0.12 is now available!

What we did:

  1. Dark Theme Overall & Light Theme Support
  1. Quality Of Life
  • Graph assets now generates their runtime asset on creation.
  • Tools > Behavior > Validate All Graphs now generates runtime asset if needed.
  1. Bug fixes
  • Fixed a regression from 1.0.11, nested RunSubgraph nodes causing infinite asset reimport. ( BEHAVB-333 )
  • Optimized SwitchComposite to cache enum values and eliminate redundant GC allocations when the underlying BlackboardVariable hasn’t changed.
  • Fixed WaitForAnyComposite stuck on the first frame of playmode.
  • Fixed BehaviorAssetPostProcessor processing asset during domain reload.

Changelog
You can review the full changelog here: [1.0.12 - 2025-07-29]

Your Feedback Matters
Thank you for your continued feedback - Any and all suggestions are seen and taken into consideration for upcoming releases.

13 Likes

I notice App UI is now updated to 2.0.0, can I update to this version or it’s better to stay with 2.0.0-pre.16?

Thanks for raising that point @AndreaGalet,

We were not aware of it, seems like the release went out quietly internally… Now gathering intel and will update the post asap.

The next release will most probably use the new version.

1 Like

It seems that interface got even slower, especially when dragging with MMB, takes almost a second before it starts. Does the grid have something to do with it?

Hi @DrVanillaCookie,

Are you using light mode specifically and noticed a slowdown?
Would you also be able to provide a video demonstrating the issue please?

I can take a look once I see the repro steps.

Best,
Darren Kelly

It took me a while to figure out how to record middle click (theres no option to record MMB, so I right clicked right after holding mmb)

I use dark mode as you can see. The delay was shorter on 1.0.11, I’m pretty sure. It doesn’t happen on a new graph, but becomes apparent after a few nodes added in.

There is also a delay while zooming, but not as much.

I should probably mention, shader graphs don’t have such problem on my end.

1 Like

Hi @DrVanillaCookie ,

Ah yes, we have a ticket for the middle mouse click actually. It just has not been prioritized yet.
We do not have one yet for zooming though so thanks for reporting.

This slowdown was also there before the 1.0.12 release, It’s interesting that it’s slower now though.

We should be investigating a new version of AppUI in Behavior soon to release in one of the next patches which might help, but we need to investigate. I’ll let you know if it does, if it doesn’t help, I will try to see what we can do to look into this further.

Best,
Darren

I checked zooming more and it’s quite peculiar. It will take me a while to explain :slight_smile:

So dragging have a delay before each activation, but zooming is slow only after first activation. So once I zoomed once, it’s smooth after that.

It seems that zooming delay is connected to dragging delay somehow, since once I use dragging, the next zoom activation is slow again. Hope it makes sense. I’ve no idea how it all works but seems like activating drag resets zoom caching or something.

1 Like

A few feedback developing over the week for GMTK:

  • Would be nice to add BehaviorGraphAgent to the list of AI Component.

  • NodeUI supports rich text, but search doesn’t ignore them.


  • Would be nice to have a “Create New” button on the graph agent. It’s a pain to have to do 3 click + navigate an entire list just to create a new graph.
    image

  • Would be nice to have a blackboard asset inspector from which you can see the BBV without having to open it. Also having a shortcut to copy GUID. (Yes you can do that by going into the Runtime asset directly, but it’s error prone and too much step).

  • Behavior Asset is missing asset icon next to the tab name. Same for blackboard asset.

  • When creating a BBV from a field, would be nice to have the value from the field being used as initial value.

5 Likes

See, even the thread title spells it UK Behaviour.

1 Like

Corrected! Thanks for flagging :smiley:

One bug I found while working with this version is that, properties of actions are not visible, even though I have created them using [CreateProperty]. Is there something wrong I am doing ?

Hi @Heemo2000

Only BlackboardVariable whith T being numerics, string, Vectors and UnityEngine.Object derived type are supported by the serialization. Make sure to make them public and to add [SerializeReference]attribute.

[CreateProperty] is only used for Runtime Serialization, not for editor/authoring serialization.

Thanks for informing me. I must have misunderstood [CreateProperty] functionality.

Nodes change their size when selected because of border width, this is very annoying. Maybe change selection color instead of increasing width?

Could you make Debug the same way as in Animator via “Auto Live Link” (always debug selected gameobject) instead of selecting via dropdown menu?
Also, (Outdated) is not very clear, I’ve accidentally moved the nodes during playmode and it got me confused.

Thanks for the “Auto Live Link” suggestion. Will bring up to the team.

The (Outdated) is part of the new playmode support. We haven’t had time to create a new documentation page on the topic, but you should get this message popup when editing a graph during playmode:

(Outdated) means the graph running on an agent is not up to date to the graph in the graph window.
It is still possible to attached to an outdated agent and any identical parts will still be debuggable. New or deleted section however won’t run because the agent needs to refresh its graph instance.

1 Like

That message was shown only when I tried to undo the changes.

My problem is that my mouse is so lightweight that when I click it moves the cursor slightly, resulting in this node position change

Also, please note that you can Lock Animator window to stay on last selected object, and it also doesn’t break the link when selecting object without Animator (when Lock is not used) or clearing the selection (by clicking on empty space in project for example). I’d expect the same behavior, and you can also have improvement by always showing what object is being debugged (next to debug button?) via clickable reference. Animator has the name of linked object at the bottom, but you can’t click it to focus in hierarchy.