Narrative
I’ve been working on a number of in-network examples lately to share with other users. In many cases I include COMPs in network that are intended for small in-network user interaction. This may be something like a button that’s used to turn on a data simulation, or to swap between different textures. These are largely cases where my in-network UI elements are set-up as display false. Generally speaking, I like to save networks like this with the COMPs viewer active set to true - this makes it easy for a user to quickly interact with the UI element (which is also generally easier for beginners).
I’ve noticed that in some cases when I’ve saved a network with COMPs whose viewer active flags are on, they appear initially like default COMPs until selected.
Issue
- Operators that are saved with a their viewer active state behave as if their viewer active state is false until selected.
- This seems to occur when two operators
.nodeXdistance is 10,000 network units or greater. - Operators will return to expected viewer active state when selected by the user.
Steps to Reproduce
- In a new TouchDesigner network add any two operators.
- Separate operators by 10,000 TouchDesigner network units
- Make both operators viewer active
- Save and close TOE file
- Open TOE file
- Operators will display as though their viewer active state is false until selected by the user
Example File
Attached are two example files
Two constant CHOPs - in this case both ops are viewer active. Another with a mixture of ops whose viewer active states are true and false.
simple-test.toe (3.5 KB)
Only the Button COMPs are actually viewer active.
viewer-active-ops.toe (19.4 KB)
After thoughts
After thinking about this more, I can imaging that this may actually be zoom level. Hopefully this is enough to help track down the issue here.