I have a single material that freezes MAX while it is in the material browser. It can be in the scene, just not in the editor. I found and removed the raytrace, which isn’t the issue. What can cause this? I purchased the material and it has screwed up every scene I tried to use it in.
Looking into it…
Best regards,
Vlado
For me the material swatch is simply slow to update but does not cause a full freeze of the application. According to VTune, most of the CPU time when updating the swatch is spent on calculating some procedural Noise textures (see attachment). However looking at the shading network for this material, doesn’t it seems just a bit overcomplicated?
Best regards,
Vlado
Yes, it is a mess when looking at it that way. My machine freezes for several minutes and all I can do is try to remove it from the material editor before it freezes for several more minutes. I guess I’ll abandon the material.
Hi Bobby
I’m interested on how this material looks like, can you share a link?
I love a good procedural material but this seems to be overkill and or probably achievable in an easier way…
cleaning this up would take some time though. Crazy node tree!
Why is this in the docs section btw?
Maybe open a support ticket and ask for a refund, explain to them how this material crashes Max at all. Otherwise, RIP those 50 Euros
I don’t know why this is in the docs section, probably a mistake @MANUEL_MOUSIOL
At least if the material looks ok you could try to render a couple of large textures (some 100 by 100 m). This way it doesn’t completely go to waste.
Exactly what I was thinking! Could turn out to be very useful. And you can strip out the useful parts and maybe use those to build a more streamlined version.
Out of interest does the slate mode make it any quicker to ‘see’ or is it the same in either mode?
But then if you render it to a
texture the procedural benefits of the shader would be gone..