I’m working on converting our project from NC 1.6 to NC 2, and I noticed the BBParameter editors aren’t behaving like they did before (when they were BBVariables). I have a set of GlobalBlackboards that I keep on the scene at all times. In NC 1.6, if I created a Check Enum condition task (for example, but something similar seems to happen to all the Check X conditions), and assigned Value A to something on one of those global blackboards, Value B would turn to a dropdown of all the possible options for the enum I selected. Instead, I see a string that just says “Object”.
Stepping through the editor draw code, I see that neither Value A’s refType or blackboard gets set when I assign the variable reference like I described above. Am I doing something wrong? Is there a different way that I should be referencing GlobalBlackboards than just keeping them on the scene?
This is a very special case with Enum tasks used with Global Blackboards. I cant seem to reproduce any other error using other similar Check/Set tasks.
The errors stems from the fact that the Enum tasks use a non type safe BBObjectParameter which is used within NC very rarely.
A good solution to your issue would be to use CheckVariable and select the enum you want to check (since I suppose you have already added that enum in the Type Configurator Window).
Meanwhile I am fixing the CheckEnum, although to be honest I was realy considering removing it since in v2 we can use generics like CheckVariable and SetVariable amongst the others.
Let me know,
Cheers!
Join us on Discord: https://discord.gg/97q2Rjh
Author
Posts
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic.
Login
Register
By registering on this website you agree to our Privacy Policy.