Frame in/out set correctly, still same errors. Julik Were you getting these same errors where it's looking for completely different frames than the frame your updating?
Thx Ari Sent from my iPhone > On Dec 2, 2013, at 7:07 PM, Julik Tarkhanov <[email protected]> wrote: > > Use geo holds. When I had to use OBJ sequences (which I didn’t enjoy for a > second) I used this script > to auto-bracket my readgeo with frameholds. Obviously Nuke-7 only. > > https://gist.github.com/julik/6089831 > > >> On 03 Dec 2013, at 01:03, Ari Rubenstein <[email protected]> wrote: >> >> Is there a workaround to the incessant ReadGeo ERROR's where Nuke is always >> looking outside the obj frame range and returning a "No such file or >> directory" error ? >> >> For instance, say I'm on frame 140 and nuke produces this error saying it >> can't read geo for frame 80 (the .obj sequence is from 101-190. >> >> This happens with great frequency under many scenarios. > > -- > Julik Tarkhanov | HecticElectric | Keizersgracht 736 1017 EX > Amsterdam | The Netherlands | tel. +31 20 330 8250 > cel. +31 61 145 06 36 | http://hecticelectric.nl > > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
