tyFlow Forum   ›   tyFlow Discussion   ›   Bugs and Issues   ›   problem when using multiple VDB events
problem when using multiple VDB events
Geoff
Member
Joined: May 2019
Posts: 51

#1
01-31-2021, 07:13 PM (This post was last modified: 01-31-2021, 11:06 PM by Geoff.)
Hey Tyson!
Hope you're doing well,

I still have this bug when using multiple events http://forum.tyflow.com/thread-1892.html
I use the empty birth VDB event workaround though...


But the main problem I want to point at now is the evaluation order, I don't understand how it works with VDB events.
it may be the same as standard events but It seems a bit odd with vdbs, or maybe I'm missing something...

For simple additions it's fine, but for more complex operations, with several intersections and substractions, it can be a reel pain...

For instance I'd like to patch a flow like this:    
that behave like this:    

Here's how some of my flows look like if I want a substraction to be evaluated in the right order Sad    

this file should illustrate the issue:
.max   vdb_eval_order.max (Size: 972 KB / Downloads: 264)
  Reply
tyFlow
Administrator
*******
Joined: Jan 2019
Posts: 4,560

#2
02-01-2021, 03:36 AM
Quote:I still have this bug when using multiple events

Oh, weird...I thought I fixed that one.

As for your event ordering...events are evaluated breadth-first, top to bottom. So yea...things can get tricky when you need them to evaluate in a different order due to where/when you're sending data between events.

I'll add a setting in the next build so that you can offset evaluation for any event, not merely birth events. Maybe also an "evaluation order display" or something so no guesswork is involved when specifying order values.
  Reply
tyFlow
Administrator
*******
Joined: Jan 2019
Posts: 4,560

#3
02-01-2021, 07:08 AM
Also, I tried loading the file in the other thread you linked and couldn't get it to crash. Do you have a set of steps to take to get the crashing to occur?
  Reply
Geoff
Member
Joined: May 2019
Posts: 51

#4
02-01-2021, 08:11 AM (This post was last modified: 02-01-2021, 08:13 AM by Geoff.)
That'd be a very handy addition!
I thought it was something different than breadth-first, but that make sens.
I didn't want to ask for a new feature but maybe you could consider adding a breadth-first/depth-first switch option in the flows main settings as well...
Anyway, thank you for the quick feedback.

As for the bug, this file crashes for sure (the flow is disabled) the particle to sdf op seems to be involved...
.max   vdb_crash.max (Size: 900 KB / Downloads: 275)
  Reply
tyFlow
Administrator
*******
Joined: Jan 2019
Posts: 4,560

#5
02-02-2021, 03:29 AM
Hmmm...try as I might, I can't make either file crash. I enable the flow, refresh it countless times...no crash. The VDB is initialized properly and I can see the particle mesh.

Could you send me the minidump from your crash?
  Reply
Geoff
Member
Joined: May 2019
Posts: 51

#6
02-03-2021, 03:20 PM
Hey Tyson,
You're right, the problem occurs only on my computer at home Sad
 I've send you the log and dump files...

Thanks for your time and efforts!
  Reply
tyFlow
Administrator
*******
Joined: Jan 2019
Posts: 4,560

#7
02-04-2021, 05:04 AM
Did you forget to attach? Smile
  Reply
Geoff
Member
Joined: May 2019
Posts: 51

#8
02-04-2021, 03:15 PM (This post was last modified: 02-04-2021, 03:25 PM by Geoff.)
no I've send you an email on the support mailbox, you didn't receive it?
here they are

.rar   vdb_crash_log_dmp.rar (Size: 764.6 KB / Downloads: 260)
  Reply
tyFlow
Administrator
*******
Joined: Jan 2019
Posts: 4,560

#9
02-04-2021, 03:42 PM
Nope...nothing in my inbox, but thanks for attaching here. I'll check it out when I get the chance.
  Reply
tyFlow
Administrator
*******
Joined: Jan 2019
Posts: 4,560

#10
02-09-2021, 05:00 AM
So I think I may have actually tracked this one down. Hopefully it's fixed in the next build (v0.16108)...let me know if you run into it again.
  Reply
Geoff
Member
Joined: May 2019
Posts: 51

#11
Thumbs Up  02-09-2021, 04:57 PM
That's good news, you rock!
  Reply


Forum Jump: