i make extensive use of the max blend mtl. its simple and does all i need 99% of the time.
i see its not “supported” by vray.. what does this mean exactly? seems to work fine in the production renderer.
i assume it doesnt work in RT GPU?
i have a fiendishly complex painted brick material with many nested blend materials. its incredibly laggy in the material editor, sometimes freezing max for 5-10 minutes, particularly when browsing it in the material browser, or adding maps. ive no idea if the blend mtl is the culprit, there are many nested noises, multisubtex, and multisubobjects in there too.
it refuses to render in RT (i get blue walls instead) but i dont know if this is due to the blend material.
if so can i suggest an update to the vray scene converter that replaces blend materials with vrayblend?
yes i know about vrayblend, i also use it.. i was just wondering what the known issues are with the standard max blend? id rather not rebuild several very complex materials, but if the blendmtl is likely to be causing me issues then ill do it.
It is slow. It might not be an issue if used for one or two small objects in the scene, but if it is used a lot, rendering can be much slower. We can improve this, certainly, or we can modify the converter to convert Blend to VRayBlend…
I also preferred it as it did not look like a telegraph pole in slate editor (due all those weird duplicate slots) and therefore shading networks were a bit more neat.Well, this was an unfortunate incident due to the extra parameters being required to show the material in the Nitrous viewports (the viewport doesn’t support array parameters). I’m still hoping that one day we will be able to get rid of these duplicates.
I don’t remember getting this error longer ago, so I am wondering if Max’s Blend had always performance/compatibility issues and it’s just now printed in the log, or if some of the recent changes done to V-Ray introduced these compatibility limitations.Just the message is new. The performance issues have always been there. Like I said, this can be improved, I just never realized people used the material so much.
i have sent a max file containing the problem material to support@chaosgroup to see if you guys can figure out why it is so painfully slow .. it renders fine, not noticeably slowing the render, but in the material editor, if i click to add or modify a map or sub-material, max will freeze for 15 - 30 minutes. it also slows down work on other materials as whenever i open the material browser, its sitting in there, adding lag
i started trying to replace the blends with vrayblends, but its such a rat’s nest of a material, with many nested blends and instances all over. and with a half hour delay on each change, and no guarantee it will fix it, im hoping Chaos can shed some light before i go nuts.
