When removing Cosmos assets from Maya, even after “Optimize scene file”, the textures are not removed from the Hyperhade, one has to select them all and delete, is there a way to improve this process in the future or include in the Optimize tool at some point?
Which scene optimization are you referring to? The Maya native “Optimize scene size” does not remove unused shader nodes from what I see. You have to go to Hypershade > Edit > Delete Unused Nodes and do it there.
Thanks for the reply Aleks yes Maya Optmize scene size and Hypershade but as you see in my image some Texture nodes are still there after “Delete unused nodes”
and this is only on 3 assets, in larger scenes the cosmos textures are together with other bunch of textures in the hypersahed and
is difficult to select them and delete.
I saw what’s happening - not all nodes are affected by the “Delete unused nodes” function, namely: VRayPluginTex, VRayNormalTex, VRayPluginFloatTex, and possibly others (all of which are unlisted in Hypershade). I logged the issue (internal bug-tracker id: VMAYA-11982) for developer investigation.
Great to hear, thanks.
Any new developments on this Aleks, the Cosmos textures are still left behind in the Hypershade after Optimise Scene Size.I’m still on Vray 5 latest build
No progress yet, I’m afraid. I’ll ask the project manager if we could bump the priority of the issue.
All right Aleks, thanks for checking again.
Hi, I just came across this today while trying to get a scene stripped down to send to chaos, ironically. Its really annoying to have all those nodes stick around when youre trying to clean a scene. If you bulk grab stuff to delete, you might delete a node you needed, and if you sift through more carefully it can take ages if you had a lot of assets. It really needs to just wipe the scene of unused vray nodes as it makes handing over files and generally keeping scenes clean really hard / or slow.
Ive actually spent a lot of time this morning trying to strip a lot of cosmos data out of scenes, also to find when I select certain nodes in the outliner, like a UVWgen node, itll freeze maya. So doubley slow trying to deal with these scenes.
I feel like after doing some tests, it might be having the hypershade open, with material preview window open when I select cosmos nodes is freezing things. That would make some sense since I cant enable “show textures” in viewport once scenes get to a certain complexity. It always freezes if there are cosmos assets (or certain cosmos assets) in the viewport. So having the cosmos textures freeze Maya in the material preview window would also make sense.
What I tend to do is select your proxy object.
Graph it in graph editor.
Select all nodes and delete.
It’s a pain but at least you get to see whats connected in one shot before deleting.
I’m having to use Cosmos assets again and this problem is still not addressed . Chaos could you please give some priority on this issue, I think is way overdue. June 13 build, Mya 2023 Vray 5. Windows 11
It would be best if we simply had the import option of referencing the asst in along with simple import.
I now save out any asset into its own scene which I reference in.
Hey Stezza, do you know a way to download a Cosmo asset but no bring in the textures into the Hypershade?
rename the folder where the textures are, Assets folder I think.
Never tried it though..
It didnt work, it automaticaly recreates a new folder “Vegetation” and the textures are again imported into hypershade. Thanks though.
ok try this as this works for me.
go to shelf Import proxy, unclick “use the new VRay Proxy node”
Then go locate it..
This brings in the proxy without textures
Nah, that’s too slow , I need to choose on the fly from the Cosmos assets I need, it takes too many steps to locate the folder.
I wish there was a checkbox “Don’t import shaders/texture”