Pixel Crushers Forum

Thank you very much for this. This is great!

All right; I posted about this because I thought it might originate in 2019.2 which added the scene visibility sidebar – shifting the whole hierarchy to the right – and 2019.3 only made it more noticeable by adding the ‘selectable’ toggle. I didn't have 2019.2 installed anymore to check if I'm right...

No, no; it's absolutely fine. While I look forward to seeing this working, it can wait; especially if you currently need to focus on other things.

Speaking of 2019.2 (resp. 2019.3), I think the newly added visibility settings in the Hierarchy window might have messed up the placement of the Dialogue Manager icon which seems to be placed a bit too far to the left now.

Picture

Thank you! Those are great news.

Yep, I understand; it's absolutely reasonable not to keep the metadata in memory. Having a function to extract field data from the entries when needed would be great. Thanks again.

Hi Tony, I've noticed that while getObj() , getProp() and setProp() are supported by the Dialogue System (and I'm really thankful they are), they don't map as cleanly to DS Lua functions once you involve object references. I'll briefly explain what I was trying to accomplish to give some context. Ba...

How about SetActive() sequence for gameobjects and SetEnabled() for components?
There's also an example for queuing an explosion particle effect until you send a message to trigger it.

I'd support that.
When I read about a topic I'm currently working on, I love reading the "why" sections, or "tips" or "you have options 1, 2, 3".

I think the search bar itself might be a bit of an obstacle when you want to find something in the documentation, even if you know exactly what you're looking for. For example, let's say I'm looking for the articy:draft reference page. Search for "articy" Most of the search results are fro...

All right, thank you.