Login | Register 

[2018.41570] - Copy SOP stamp references cook unnecessarily

Report bugs so we can squash them!

[2018.41570] - Copy SOP stamp references cook unnecessarily

Postby tetkin » Tue Nov 27, 2018 10:40 pm

I'm not sure if this is a new issue, but a reference to a stamped value upstream from a Copy SOP will cause whatever is referencing the stamp (and everything downstream) to cook on every frame, even if nothing in the Copy SOP's dependencies is changing. It appears to only do this when the value of that stamp is determined by an expression that references "me.copyIndex"

Example setup:
- Create a Circle SOP
- Feed that into a Primitive SOP and make a reference to a stamp in one of its parameters (e.g. the Red color attribute as "fetchStamp('foo', 0)")
- Feed that into a Copy SOP and add a stamp parameter (e.g. "foo"). The value of this stamp can be an expression that references "me.copyIndex".
The Primitive SOP will cook on every frame.
(4.57 KiB) Downloaded 11 times
User avatar
Posts: 340
Joined: Thu Mar 08, 2012 6:32 pm
Location: Los Angeles, CA

Re: [2018.41570] and 23700 - Copy SOP cook unnecessarily

Postby archo-p » Thu Dec 06, 2018 3:57 pm

I have come across this now as well, but in the stable 23700 build. Definitely a hangup for a current project!
User avatar
Posts: 474
Joined: Thu Nov 19, 2009 3:03 pm
Location: Los Angeles

Re: [2018.41570] - Copy SOP stamp references cook unnecessar

Postby adellelin » Thu Dec 06, 2018 3:58 pm

im seeing something similar today. also with the Copy SOP
Posts: 1
Joined: Tue Jan 14, 2014 9:35 pm

Re: [2018.41570] - Copy SOP stamp references cook unnecessar

Postby bradonwebb » Fri Dec 07, 2018 12:30 pm

I'm getting an infinite loop on the copy stamp as well, seems to be an unnecessary cook.

The fetchstamp upstream is causing the copySOP to re-cook, re-sending the stamp causing the channel fetchstamp to re-cook, and so on.
Posts: 1
Joined: Wed Jan 10, 2018 10:44 pm

Return to Bugs

Who is online

Users browsing this forum: No registered users and 9 guests