Pixel Crushers Forum

I think I'm getting the picture now. Your metaphor sums it up nicely! I sometimes use this feature for response menus, allowing to add a set of responses from elsewhere easily to the existing ones in the current conversation, like this: ConvJump.jpg The jump to the other group (placed in another con...

Indeed, in this kind of case it's limiting. But it's funny, how everyone may have very different ways to handle the logic behind its project. As an example, to achieve what you posted above, I could never have imagined that the dialogue system would go backwards to evaluate the group D if group A do...

Hi there :) Yes, it work as expected with the regular setting for instruction nodes! Great. I was not aware that the group nodes have a such different behavior (going forward and backwards). It may be useful, but also dangerous...let me explain it with this articy project (please download it): https...

Thank you for the scene! I think I've found the problem. The difference between your articy project and mine is the nodes evaluating the int (x == 1 etc...). I have instructions nodes (converted into groups), while you have dialogue fragments (converted into regular nodes). In your setup, it seems t...

Hi Tony, I've tried with the new package, I still have the stack overflow issue. Could you, in your articy project: - add a hub just after the start of the conversation, allowing only one pass (for me it's a simstatus check in the input pin & a simstatus set in the output pin) SimStatusCheck.jpg...

So, here are my results with the 2024/06/05 patch: Instructions as regular nodes, Reevaluate links to true, Delay evaluation to true Same result as before (the Debug log line method is never called). Instructions as regular nodes, Reevaluate links to true, Delay evaluation to false Same result as be...

Have you set the articy importer window's Instructions As dropdown to Group Entry? I tried and got a nice stack overflow, that's why I sticked to the regular mode. I guess that it's because of the jump, at the end of the conversation. It goes back just before the sim status check, which is probably...

Thank you! I've tested the patch with this configuration: - all links reevaluation options checked - instructions conversion in regular mode (with the "group" mode, my conversation creates a stack overflow, but we'll discuss that point later...) It seems that the problem has moved on. Here...

I'm also looking into providing a checkbox to disable the extra level look-ahead on Conditions. That would be great! I don't think I have something using the continue sequence, but even if it means rewriting some parts of my dialogues logic, I'm ready for it! I mean, the priority is to have this &q...

Thank you for the quick fix, there is no more warning message! Unfortunately I'm experiencing some strange behaviours :( Maybe I'm doing something wrong. My game is mainly based on randomness and replayability, that's why at certain moments I have to run conversations to handle huge pieces of logic....