Status:
Vuo version:
Fixed in Vuo version:
OS version:
- OS X 10.10
Steps causing the bug to occur:
- Set up some layers and an "is point within layer" node and some way to react on it.
- Publish the "Rendered Layers" input port(s).
- Connect layers to "Combine Layers With Transform" node.
- Publish layer output from "Combine Layers With Transform".
- Store to node library
- Create a new composition
- Use the newly created node from the library, and connect it to a "Render Layers to Window" node.
- Observe high resource usage through the activity monitor.
How did the result differ from what you expected?:
High resource usage.
Have you found a workaround?:
Connect "Rendered Layers" output port from "Render Layers to Window" to a "Hold" node before connecting to desired input port in custom node.
Other notes:
Publishing layers directly without the use of a "Combine Layers With Transform" node will warn about a feedback loop, and prevent connection without the hold node.
Compositions:
Attachment | Size |
---|---|
![]() | 1.37 KB |
![]() | 1.66 KB |
Comments
Could you attach your Check
Could you attach your
Check Layers
subcomposition? (You can find it in Tools > Open User Modules Folder.)Yep
Yep
MartinusMagneson.checkLayers.vuo
Thanks. I see the problem,
Thanks. I see the problem, though I'm not yet sure what the solution should be. I've marked this bug report accepted, and I'll discuss with the team.
In the meantime, using
Hold Value
outside the subcomposition is a good workaround.In the meantime, using Hold
Or, better yet, use
Receive Mouse Moves
instead ofCheck Mouse Status
, like in the attached composition.MartinusMagneson.checkLayers.vuo
Thanks, is there also a
Thanks, is there also a difference in using "receive mouse buttons" to the "check mouse status" one? With this loop in place Vuo crashed quite frequently.
This issue, where infinite
This issue, where infinite feedback loops could be created through subcompositions with internal trigger ports, has been fixed in Vuo 2.0 beta.