@t-studios said in After a tag is added to an object via the add tag behavior other behaviors still can’t access it by that tag.:
ior to add a tag to an object. Then, use another behavior of any type to perform an action with all objects containing that tag. It will not affect the object which you added t
I believe we've fixed this. However, your example is trying to add the tag to the same tag. No other objects had this tag so it did nothing.
This is now fixed in 1.24
You own all rights, its yours. No fees.
The only "right" we have is to use your hyperPad projects for "promotional" purposes. This usually means featuring it in the hub, or sharing on our facebook/twitter. Or if it appears in any videos we make.
Nope.
I mentioned elsewhere we are int he process of developing 3 updates.
1.24 is the one that is in the final stages and should be released soon (see announcements section if you want to join beta)
Then we can fully focus on hub again, then there will be one more focusing on lighting effects after that.
You can already turn off collisions. One way is to use the make passible behaviour https://hyperpad.zendesk.com/hc/en-us/articles/360016443571-Make-Passable
You can also make your object a scenery object.
Yup as other said, this is pretty much the entire purpose of this section :)
@supersean nothing. Just a sample promotion.
The picture is just filler content not real content.
Thanks for reporting this. Will look into it and report back if we need more info!
Very cool to see you updating this! Impressive to see how much you've learned and able to improve the performance so much.
So, I briefly spoke with @Hamed about this. It's doable, but trickier than I thought it would be.
Showing the collision editor from within the behaviour editor is currently not possible, just because of the way we manage the editors. We'd have to change how it works behind the scenes. It's possible, but requires a bit of time.
Changing the collisions using an array of points is easier, but the issue here is there is currently no point of reference for users. Meaning, it would be a lot of trial and error for you guys since you don't really know where the points are.
We'd need to tweak the current collision editor to show the point coordinates, this way you would have some sort of idea where things are if you were to enter the points manually with an array.
Soooo, It's doable, but not for a little while as we're in the middle of 3 updates.
IF this is something you guys really want and will actually use I can try to prioritize this. But I don't want to spend the time on a feature that won't be used.