Node Material to Legacy Material

[vockC3F3P]

Hello together

Is there a way to convert Node Material back to Legacy material or has anyone a script? I need to convert a lot of Materials back to Node.

Standard Shaders with bitmaps (Color, Roughness - Specular, Normal, Bump, Ramp, SSS,...)

Thx a lot.

[peter_horvath]

May I ask why do you need to convert them back? It's not supported officially, because the legacy node system is deprecated and will be removed in a future release, so we want to encourage people moving to the Node system and not back to the old one.

[vockC3F3P]

The reason is that we have performance problems and a lot of crashes. often it's the ai.dll error. But also if we have the asset/TX Manager open and relink a texture Cinema freezes when baking the texture in the materialmanager. To switch off the preview and back on again after the textures are replace is a huge timeloss and not an option. Maybe this is a known issue?

Update:

This is also a crash we encounter a lot.

[peter_horvath]

No, not a know issue. Can you send me that bugreport file shown in the dialog?

[peter_horvath]

Could you please tell me more about the performance issues?

[vockC3F3P]

this should be the report.

[vockC3F3P]

sure,

it's very slow. Loading images from a NAS to the Nodeeditor takes from 1min to 3min. Connecting a node to the standardnode takes up to 2min until cinema/arnold reacts again. Loading a szenefile (our standardsize +/- 1.8 to 3GB need 5min sometimes more. viewportbaking takes very long. The moste crashes are when the viewprort is baking. With the legacy material we have less crashes but the loading of the images also takes long. We encounter that problem since R23 i belive...

[peter_horvath]

Actually, sorry, in the same folder where you had the _BugReport.txt file, should be a file called minidump.dmp. Could you please send me that file as well?

[peter_horvath]

About the performance issues, it sounds like a networking issue. Probably the Node Material wants to read the textures more often, as it renders more previews. Although the textures should be cached, so it should not be an issue. Are those textures on the network drive Tx textures? I'm wondering if it's something to do with auto tx generation.

[vockC3F3P]

voila. I had to make a zip for *.dmp was not allowed to upload.

[vockC3F3P]

yes. they are all tx. maybe one or two are not because they haven't been rendered. I have the auto tx on rendering.

All textures are as absolut path loaded and made to tx when rendered.

[peter_horvath]

Thanks for the minidump, it helped me identifying the problem. This crash will be fixed in the next release.

I'll also investigate the performance issues.

[peter_horvath]

I'm wondering if you have the same delay when you render to the Picture Viewer. If this is a networking issue, then it should happen with every render, at least the first time. If so, can you share an Arnold debug log?

[vockC3F3P]

i will try. I am currently out of office for 3 weeks:)

[peter_horvath]

Crashes should be fixed now in C4DtoA 4.7.5. Please try this build if you can and let me know how it works. I don't expect the performance issue to go away, I still think that's something more genetic and related to the local network.