Behavior: Event Channels NOT Initialized when Start Node is run (BUILD ONLY)

Unity Engine
, , ,
1

Empty Event Channel- Variables Create Instances On Start.
Triggering a Message on Start will not work, because the channel instance is created after the Send Event Message node (in this case).

image
image669×676 23.9 KB

This Error is BUILD ONLY. I use Unity 6___23.f1

This fixes it:

image
image710×400 13.5 KB

Best regards,
Nixon

2

I UPVOTE THIS! SHOULD BE FIXED ASAP! otherwise we can not use this package. please someone from unity save us.

3

Morning folks,

I’ll bring this one to the team and we’ll get right on it.

Thanks for the report.

4

Hi,

Would you be able to provide a repro project for this?

Thanks,

5

Thanks for reporting the issue!

From the screenshot I assume you had the repro from the Demo project.

We created a public ticket (should be visible in the coming day) and will work on it for 1.0.7 (as we are already locked for 1.0.6).

Sorry for the inconvenience :bowing_man:

6

Repro Project not yet, since it is our steam game website working on. repro steps sure:

  1. create an event channel & a blackboard variable for it
  2. Don’t create a scriptable object instance, but rather let behavior graph create its own instance.
  3. On start send the event message
  4. Build the Game

Result: in build, event message will not be sent, because the instance is not created at that time.

7

Hi @Aroboss

Could you confirm the package version you were using?
We could not reproduce the issue on Unity 6.0.23f with both 1.0.5 and 1.0.6.

We had a related issue at release and we provided a fix for that on 1.0.4:

  • Fixed not assigned EventChannels not generating local instances by BehaviorGraphAgent when the BlackboardVariable was part of a BlackboardReference.
    > Changelog 1.0.4

Could you confirm that the issue is still happening on your side on latest version?

Thank you

8

Hey @Aroboss , I hope you’re doing well. Can you confirm for Morgan’s message above please? Thank you! :slight_smile:

9

Hey,
Sorry for the delay. Totally right - When I reported this, v 1.0.5 was the newest one (Nov 20), since v 1.0.6 came out Nov 21. Issue is fixed. =)!
Best!

10

No worries! Thank you very much for confirming. It’s really us who took time to respond for some reason :sweat_smile: