Configuration :
Mac Studio M1 Ultra 128Go RAM
MacOS Sequoia v15.7.3
C4D 2023 (but same phenomenon with C4D 2026)
Corona 14 (same problem with update 1)
Hi!
Suddenly my material node editor is now very slow. It works, but every action takes a very long time (with a death balloon)
For exemple, a single right click to insert a bitmap takes 20 to 30 sec !!!
The node editor works fine if my project is empty. But more the model is heavy, more the node editor is slow.
In desperation, I decided to reinstall everything: system, C4D, Corona, etc. A clean install for the new year. But it doesn’t solved the problem.
What’s strange is that the phenomenon appeared suddenly. I really don’t understand.
To be able to work on my materials, I need to edit them individually in another empty file and then transfer my material to my main file.
it’s very restrictive.
I had the exact same issue with Corona 14 (and update1) so I went back to 13, which works much smoother.
But I’m still using R20, so I thought this is an R20 issue, but seeing your report, it looks like other versions are affected too.
Is this for you also a Corona 14 issue? Or did it happen also earlier?
Did a short test with the latest Corona release. In heavy scenes, I have to wait for many seconds after every change I do.
And for me, it is not only the material editor, but everything is much more laggy than 13.
Hi ! I understand what’s happening! I realized it while preparing the file to send to you. The file itself didn’t have any problems: the node editor works perfectly with it.
That’s because I don’t use absolute paths for my textures. I specify in C4D preferences/Files where are my textures files : it’s a very large folder with lot of sub-folders.
This saves me from having to duplicate the textures in a tex folder each time, or using absolute path which can cause problems when working with a partner.
It worked very well until now.
When I saved the file for you, I made an export with all references. It created a copy of my file with a tex folder with all the textures. And in this case, it works perfectly.
I going to downgrade to Corona 13 to see if the problem is related to Corona 14. I keep you in touch.
Same here, thanks for the input. It looks like Corona 14 (Corona 13 works fine) can’t handle absolute path. It works fine when all the textures are saved in the local tex file.
But this is not an option for me, as this needs a huuuuge ssd… And is also very chaotic…
No, not in my case, but it could be connected somehow. There are some differences between my issue and the topic you mentioned.
the issue there is long loading time when opening the scene. In my case, it does open fast.(with Corona 13 and 14)
he reported that it does happen with Corona 13. For me only Corona 14 is slow, 13 does work as expected.
he does store all data on an external server. I have everything on a local and fast M.2 SSD, but I use absolute paths.
It does work as expected, when I copy all the assets (corona proxies and textures) in the local tex file and change the paths from absolute to relative.
I’ll start with the conclusion : as lollolo invited me to do, I reinstalled Corona 13 (hotfix2), and it works perfectly ! Therefore, I encourage you to report this problem with Corona 14.
This is what I learned : - Corona 14 has trouble managing the watched folders in Settings/Files.
Copying all textures in a tex folder solves the problem. BUT for my workflow, THIS IS NOT a viable option !
NB : my watched folder is not in a distance server. It’s local.
uncheck and recheck (with restart of c4d) the watched folders path in Settings/Files → DOES NOT WORK
create un symbolic link of mu watched folder and put it in a TEX folder → DOES NOT WORK. I think it is because my watched folder has lot of sub-folders…
At the end, a simple observation : Corona 14 has an issue that Corona 13 doesn’t. Period.
So, for the moment, I downgraded to 13. But please, do something about this.
Implement new features is great. But sometimes, I’ve the feeling that corona is becoming less and less responsive…
Thanks you for your work and your attention.
Tried the latest hotfix, and it is still not really fixed for me.
I can now adjust the shaders without heavy lags, but I can’t right-click in the node editor to create a new shader or material.
In heavy scenes, right-clicks does only freeze, while not opening the tabs to add a new shader or material.
In lighter scenes it freezes for a few seconds until I can add a new shader.
The same is in the material editor (not node material editor), I can adjust shaders without lags, but get heavy lags when I want to add a new shader.
I was wondering why some scenes were extremely laggy while some others are fine, I wasn’t aware of this issue. It drives me crazy.
There is this other long standing problem that I’ve always had : if the viewport preview of the active material is higher than the very low default (from 512px and above), there is a significant lag each time the material is edited. Cinema hangs for half a second while the viewport preview is updated. It’s not a Cinema 4d issue since it doesn’t happen with other render engines.
I just downloaded the latest daily build (Corona 15, Mar 19) and tested it with a few scenes.
The issue I had before seems to be resolved. I don’t have those lags anymore.
Hi Maru, I’m not sure, if you answered me or not, because for me the issue is resolved
Nevertheless, I deactivated this option, but I don’t see a difference. It works anyway. It is as fast as it was with 13, so I’m happy with it.
Just wondering, what does “Strict thread affinity”?
By the way, before I got always an error message when I closed C4D. This is now also gone.
I just wanted to know if enabling/disabling the “strict thread priority” changes anything for you. According to your message, it doesn’t, which is also a valuable piece of information for us.
It is some very technical thing related to “core affinity locking”. It was added to check if it helps with some very specific kind of problem.
