I have hard time to understand what this mode is supposed to do, since:
debug flag on can have 3 functions for each output
1. Execute - normal behaviour of the VOP
2. Pipethrough - passes through any chosen input
3. Constant - outputs just any custom constant value
but
1. what sense does execute have? simply if the debug is off, we will get the same behaviour
2. 3. there is Bypass Flag, which has Pipethrough and Constant modes as well with exactly the same finctionalities as debug (except that it actually recompiles the vop network when the flag is changed, debug on the other hand doesn't until something else forces it to recompile which makes it quite confusing because it doesn't reflect the debug setting until recompiled)
so the question is, what is the Debug flag supposed to be doing on top of other modes ? is it WIP of something in the future? (It would be nice if it can pass outputs as a temporary attributes and their visualisations directly to viewport while that vopnet is selected, like it is in Softimage ICE, that would be very nice debugging tool indeed)
I'm not able to see it's usage for now, can anybody shed some light? thoughts?
Debug Flag on VOPs?
2750 2 2- tamte
- Member
- 8885 posts
- Joined: July 2007
- Offline
- alexwheezy
- Member
- 318 posts
- Joined: Jan. 2013
- Offline
- kodra
- Member
- 373 posts
- Joined: June 2023
- Offline
I suppose the point is that in debug mode, you can choose Execute or not for each output, if your VOP has multiple output. So if you have two outputs port, A and B, you can output the normal result from A but set B to a constant.
If you use Bypass flag the node will never be executed and you cannot get the normal result.
If you use Bypass flag the node will never be executed and you cannot get the normal result.
-
- Quick Links