Possible to hide Block Instance materials?

[J@R]

Hi I've been running into this issue quite a lot lately, it's more of an inconvenience but I think it could definitely improve the Vray workflow for users dealing with large Block Libraries.

Would it be possible to change the default import options for Block Instances to not include the editable Material? I.e. only when you explode the block would the editable material show up in the Materials Tab.

Some of the Files I work in contain upwards of 20+ Blocks all containing multiple materials. None of these materials I actually need to control as we set these up in the original files, so it leads to a lot of unnecessary clutter in the materials tab

could this be implemented?

[J@R]

Is it possible to get a response on this?

Another alternative could be to embed an image preview into the VRscene file similarly to how a VRmat shows a preview?

The core issue is being able to preview the block/VRscene I want to import (i.e. image of person 01, person 02....), then once imported having no unnecessary clutter in the vray asset tab?

[Peter.Chaushev]

Selectively displaying referenced/imported block assets is an edge case and thus not something we are willing to implement as a global behavior. We have a couple of ideas (based on user feedback) on enhancing navigation in over-cluttered asset lists, however, cannot share any ETA or further details yet. The dev team is currently undertaking a lot of work on improving the assets UI.
Regarding the ability to preview Proxy objects (mesh / scene), our intention is to provide a geometry asset preview function which can only be called manually. This, however, is actually not as trivial as it sounds and might not be part of the initial UI update I mentioned.

I've just logged all of your feedback for further discussion. Appreciate your well-thought requests! Let me know if you have anything else in mind.

Kind regards,
Peter

[J@R]

Thanks Peter.Chaushev

I'd disagree about it being an edge case as it could be seen to be in relation to a few other Block issues...
https://forums.chaosgroup.com/forum/...lock-libraries
https://forums.chaosgroup.com/forum/...-inside-blocks

I guess I'm still unclear as to what the intended V-ray workflow is with Blocks/Proxys?

I tried adjusting my workflow to strictly use VRscene files in an attempt to streamline working with Assets/Lighting, but found it more cumbersome than linked blocks in terms of reducing file size and utilising other rhino plugins (VisualArq/Grasshopper etc.)

Apologies if I sound like a broken record but could Linked Blocks potentially read exactly like VRscenes currently do? I.e. no material conflicts/texture remapping, includes lighting
Is this a more suitable question for the folks over at mcneel?

Thanks Again,
J

[Peter.Chaushev]

You are asking in the right place. This is mainly our side, not Rhino's.
How exactly do you instance the imported .vrscenes? If you are instancing the blocks they're in, you should not see any substantial file size increase:


Furthermore, how do you imagine your ideal workflow when working with Proxy assets in Rhino and/or in relation to Grasshopper?
We will be discussing all this in early January. Your feedback is welcomed!

Kind regards,
Peter

[J@R]

cheers Peter.Chaushev

Ultimately I can't see a more ideal workflow than utilising a linked block instance, as it means the original file is still able to be edited and recognised by other Rhino Plugins and will display in Viewport as intended.
I find when using proxy's and vrscenes it can restrict my usability for other things I need to do in Rhino as they appear exploded when not in rendered mode i.e. having trees/objects that will show up cleanly in sectional 2d/make2d views.

I think what would greatly improve Vray's functionality with Rhino Blocks is as previously said being able to hide materials in the dialog to reduce clutter, and the ability to import Light Objects within blocks.
This is a massive one for me because at the moment the only way to import eg. a lighting fixture with IES file included is to export a VRscene which then removes its ability to be integrated into layers/make2d/grasshopper objects etc.

J