Ok so the enviro preview node is becoming a pain, is it really needed? can it be hidden or better yet not created at all? For example.. Have 10 scenes referenced, all 10 have duplicate nodes of the enviro preview. I have also run into it causing name clashing because its always in there... Anyone have suggestions?
Announcement
Collapse
No announcement yet.
VrayEnvironmentPreviewTM - is this really needed??
Collapse
X
-
You should clean your references. I create two custom buttons on my shelf. One is called EXPORT, the other is IMPORT. What you do is select something, then go export selection to c:\temp\temp.mb
Then copy that mel and call that export. Now you do import c:\temp\temp.mb and have that mel command as import button.
Now when you are creating an object you use for a reference, you select it and hit export button. Then you go new scene, hit import and save it. It will do a good job at keeping a clean reference and you won't have those files added up.
-
Originally posted by Resin View PostOk so the enviro preview node is becoming a pain, is it really needed? can it be hidden or better yet not created at all? For example.. Have 10 scenes referenced, all 10 have duplicate nodes of the enviro preview. I have also run into it causing name clashing because its always in there... Anyone have suggestions?
Best regards,
VladoI only act like I know everything, Rogers.
Comment
-
Originally posted by Resin View PostHi Vlado, could you direct me to where that node is created in the settings so we can disable it, even after a export selected we get an unknown foster parent node come in that is the vray env preview. Cheers
Best regards,
VladoI only act like I know everything, Rogers.
Comment
Comment