tamteHmm right makes sense, similar annoyance with Ramp VOP.
it's relative to the node that's specified in Evaluation Node Path parameter on Attribute VOP
tamteYeah for now I'll use backticks as a fix, feels hacky but works. Now... if I want access such evaluation path from a VOP with from python, that's not possible right?...
nobody can stop you from placing spare parms directly on the snippet node and pointing any Attrib VOP/Wrangle to evaluate them relative to that, but I'd not advise doing that
Thanks once again for clarifying things.