Re: [Nuke-users] Smart Vector error

STMaps definitely should be more bulletproof too - Smart Vector was working awesome, then caused issues when pushed, using multiple nodes in a comp. On 10 August 2016 at 16:02, Michael Garrett wrote: > Right. That makes sense doesn't it, and it's something I had

Re: [Nuke-users] Smart Vector error

Right. That makes sense doesn't it, and it's something I had considered, as it does some crazy matrix lookup to calculate the reference frame on the fly. I actually naively thought I may be able to get around the issue by baking out an stmap. Well, I'll try snipping up the input into smaller

Re: [Nuke-users] Smart Vector error

Smart Vector has always worked but only used on < 250 frame IIRC. On 9 August 2016 at 06:44, Michael Garrett wrote: > I'm getting an error when using VectorDistort with pre-rendered smart > vectors, stating "reference frame is outside the valid frame range", when > it

[Nuke-users] Smart Vector error

I'm getting an error when using VectorDistort with pre-rendered smart vectors, stating "reference frame is outside the valid frame range", when it isn't. It seems pretty arbitrary on what frame it decides to error out on. Has anyone else seen this and know of a fix? This is using Nuke 10.0v3