Hello,
I have just given the latest build a try and have noticed much higher cook times. After a quick look at Performance Monitor, it seems like new build is triggering unnecessary shader compilations. I am using POPs where Attribute POP is setting up attributes that are used in material for shading. This workflow is just fine, but when the attribute value is animated on Attribute POP (like for example absTime.seconds), then shader complication is triggered on each frame. Hope this helps. Thanks.
Hello @monty_python
Would you be able to share a small example file that shows the issue? That would help me reproduce it on my side.
Hello @Guillaume.L,
sure, I will post some example here later today. Thanks 
I have just sent email to support@derivative.ca with example file.
1 Like
Hello @monty_python
It turns out the issue was already present in 32280 but became more noticeable in 32460, at least in your example case.
The culprit is the group POP shader is randomly recompiling when it cooks.
This is now fixed, the fix will be in the next released build.
Best,
Vincent
Hello @vincentDev,
great, thank you very much for info.
@vincentDev please may I ask if there is some workaround to prevent unnecessary shader compilation in these builds (without deleting the Group POPs)?
I am currently running 32280 and it seems to be just fine there, but since you mentioned it is happening there too, I started to worry a bit about possible frame drops. If there is no workaround don’t worry about it, I just thought I might ask. Thanks.
Unfortunately there’s no workaround, except not cooking the POP.
If you’re able to do it, moving POPs around so your inputs to group POPs are static will fix it.
Alternatively you could also rebuild things to use Delete POP and Merge POP, though these two operations are a lot more expensive than using groups.
I see, thank you once again for all information 