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. Thx Ari Blue Sky_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
