I detect a problem when try to render a scene whit arnold materials and scanline standard material, and before the installation was rendered without problem
Some problem, can't render my old scenes. Freeze render production on preview pass and it is impossible to cancel without forced shutdown 3ds max
Can you guys attach the simplest possible scene reproducing the problem ?
I think I found the problem, in the old scene there are a lot of .ass proxies, if overwrite them, everything will be ok
there simple scene with 1 old .ass object, when launch prod render nothing happens. But in active shade works fine
https://drive.google.com/open?id=1Cln17W6q-HRR6zRqYt8e8CYuJwwOXSqm
The file that I´m working I can share it until next week. While I will look for another one with the same problem that I can share immediately
I can back to the previous version but I can´t find it on the Maxtoa website
I change the material and the problem persist, I think that the problem is with any complex scene, please tell me how back to the previous version
Hi! I had the same problem. the freezes stopped after I removed geforce experience app.
Hi.
I had the same problem with old scenes after update, what I did was recheck all the bitmaps in material editor and verify that all the maps was working fine (Arnold has problem with some maps and some geometry). After that I could render.
If you want you can uncheck the error in render set-up.
Yes, in general, expect issues with renders if you load old scenes, especially scenes with the "Legacy Support" switch on. You need to be able to render all scenes with that switch off to be sure you are half way there, the second half is to make sure you arnt using lights or shader types unsupported, for example OSL shaders and certain Arnold shader nodes, or sub features of nodes with mutli functionality.
Note to Foreset Pack PRO users, drop the forest color map and use an array map and inject the ID to a jitter, this way you can get leaf variation without forest color map which is not supported as it is a legacy map.
Could these problems have to do with different maps having the same name, in your scenes ?
We have just released 3.0.65. Can you guys verify if that fixes the reported problems ?
Excelent, I'll be out for a couple of days but the next week I'll check it. Thank you
Can't find what you're looking for? Ask the community or share your knowledge.