Page 1 of 1
what is this error message & how do you correct it?
Posted: Mon Apr 21, 2008 7:04 am
by Gary
I got this error message:
"camera.setcutplanes invalid znear/zfar planes"
This message came up on all my existing views out of nowhere when I send a file to mxcl (mxcl never opens, the error comes up in formz after hitting maxwell render).
The only workaround I came up with was to cut and paste the model and the views into another file.
Can anyone offer any insight.
Gary
Posted: Mon Apr 21, 2008 10:45 am
by zak
Hi
Try to delete ALL your views and make a render with only one name. which should be short - like "v-A1" f.ex.
Sometimes It get f.... up, if there is one view that conflict - I have not been able to recreate it - but it happens now and then.
Best Regards
Jesper

Posted: Tue Apr 22, 2008 12:36 pm
by juan
Hi,
It is strange, this message appears when formZ sends znear/zfar values out of range. These values are sent to MAxwell only when "clip Hither/Yon" is enabled. Are you using a perspective camera? Do you have clip Hither/Yon enabled? When did you start to have this issue? was it after upgrading something?
Thanks,
Juan
Posted: Tue Apr 22, 2008 4:45 pm
by Gary
Hello Juan:
Nothing changed in my file, and the error message starting displaying in all existing views. No recent updates, yes perspective camera, no clip hither yon. No recent upgrades....
I have striped out all of the geometry from the formz file and it still has the error with all old and new views. I have uploaded the form z file to the same location as the last file I sent you Juan. let me know if you need the address again.
Thanks,
Gary
Posted: Fri Apr 25, 2008 1:02 pm
by mojo
when i get this message, i copy the complete geometry into a new file and create new views again...
that works for me
Posted: Tue May 27, 2008 4:54 am
by Gary
Hello Juan:
Any news on correcting this bug. Had it reappear on a large file. Many views.
Happy to provide more info if it is needed.
Thanks,
Gary
Posted: Fri May 30, 2008 11:57 am
by juan
Hello Gary,
It should be fixed in the next update. We were about to release it but it needs more testing.
Regards,
Juan
Posted: Tue Jun 24, 2008 5:59 pm
by Gary
Hello Juan:
Can you confirm if this bug has been corrected in 1.8?
Thanks,
Gary
Posted: Tue Jun 24, 2008 6:25 pm
by juan
Hi Gary,
It should work fine now with 1.7.
Regards,
Juan