Chaos Corona Forum
Chaos Corona for Cinema 4D => [C4D] Daily Builds => Topic started by: luis.lab on 2024-03-18, 07:58:45
-
Hi,
In the new Daily Build from Corona 12 March 11, when I close a C4D scene (saved with the new daily installed) and open it again this scene will appear 100% loaded in the C4D task manager but never open. I tested with several scenes. I could only open it again when installing back the Corona 11 last stable release.
Anyone have the same issue, so I can understand what is wrong?
Thank you
-
Good morning Luis,
I have the same problem. You have to wait forever to open a scene. I tested it with a scene created in Cinema4d 2024.3.2.
The loading time in corona 10 (hotfix2) according to the task manager built into C4D is 0:00min and in the current daily 1:17min for the same file (see attachment). If you have a big scene, it may take some time.
I think it has something to do with the Corona materials and the Corona proxies. If I delete all materials and convert all proxies, the file loads normally.
Maybe everything will work if you start a completely new project. But I don't have time for more tests.
I'm back in Corona 10 (hotfix2) because I have to constantly work with "old" files.
In general, there is currently a problem with Corona materials in cinema. As already described elsewhere in the forum, Corona materials always lose the connection to the textures when you save them in the Cinema4D Asset Browser and then reinsert them into a project.
My system: AMD Ryzen Threadripper 3970X with 128GB RAM, RTX2080 SUPER and Win11 23H2
I'm working with Cinema4D R26, 2023.2.2 and 2024.3.2
I wish everyone a good start into the week.
-
Hi there, are you able to share a test scene for us? If so, please feel free to use the link in my signature below. One note, please use the "save project with assets" option when doing so.
-
Same here, dont know its a Maxon or a Corona releated thing. We have here scenes that will load up in 1 hour. scenes that will load up before in max 30 seconds.
We did test this on a network drive with 10gbit and nvms and local on nvms, same problem.
tiglat can you try "2024.1.0" scene will load up faster here seems hotfix 2 corona 10 work here
-
Same here !
-
I could open a few months old file, 1,5Gb. I couldn't open a 3,3 Gb file from jan.
I hardly use the asset browser anymore since there are too many conflicts with CR. Although I haven't tested those for months.
Mac Studio 128Gb ram
C4D 2024 3.2
CR 12 version 11 03 2024
-
+ 1 here,
Since you mention I was having this issue but I tought it was my c4d.
-
Does anybody have an old scene we can test?
-
Hi Bengamin.
I could not send the scene file when you asked before in the previous post.
But I reinstalled the daily build again to make a test scene to send you and just before uploading I tested it and was working. So... seems if I "save with assets" and open it again, works. Like was suggested in this post already, maybe the issue is with the links from materials/proxies to the Asset Browser and/or Chaos Cosmos folder.
I still did not find time to build up a new scene with the Daily Built installed (maybe also works) instead of opening an old scene.
Best
-
Same here, since the 02.14 daily build build.
I rolled back to the January build, everything work fine.
-
i must say i have the same now on one PC, AMD Ryzen Threadripper 3970X , c4d r2024.2.
i had to revert back to january daily, feb and march build didnt open the file, i tried to let it open for more than 25min, but it seems to hang forever at 100% loading
and also manually remove chaos scatter februar version and use the one from january.
maybe that hints to something that it might be related t5o chaos scatter? (only reverting Corona itself didnt help)
EDIT: i found that it might be related to some c4d and or vray 6 materials i had in the scenes that didnt open. i still think this should not prevent the file to open in older version this was no issue. once i removed all vray and also all c4d materials the files open fast
-
any news on the slow / not loading of scenes?
this is quite a problem, on my main render server many scenes not or only very slow load (even if i delete all non corona materials).
pls try to fix that soon
THX!
-
No news sorry. I've asked twice for a test scene and no one has supplied one. I haven't been able to reproduce this issue here.
-
i try to give you one, i have to ask for permission first. the problem is is opens on one pc (dual xeon) but not the other 3070 threadripper. both same c4d, same search paths.
the same scene open sin few seconds on 2023 on same threadripper, so it must be some with corona and R2024.
my guess ti is related to shaders or materials, or missing textures(which happens in fast production scenes but normally doesnt matter).
-
Hi
As was mentioned before, maybe the problem needs to be reproduced locally. Another day I packed a scene to send you, but when I "save project with assets" and open again from there opens normally, making it no meaning to send it.
Like Stefan say, probably has someting to do with the links to Asset Browser from Proxy, material etc.
Best
-
Are these scenes also making use of scatter at all?
-
yes, here same.
my guess, or one thing at least are search paths, maybe something in Corona at start collides with thew new c4d "speed up asset search" at the beginning of opening a scene.
when rendering the search paths work fine and reasonable fast, but on first load on machines with many cores i think some collides with new r2024 features.
i started to turn search paths off, load scene and then turn them on again. this solves it often.
a killer are also 3rd party materials(c4d, rs, vray) or shaders (vray bitmap somewhere hidden)
-
Yes, also the same here
the scenes that I tried with the latest daily build before were making use of scatter.
-
Thanks, our hunch is this may be the cause. We will investigate further.
-
Can you please share the version of Scatter that you have installed? Add a scatter object to your scene and hit the info>about tab etc. Thanks!
(https://forum.corona-renderer.com/index.php?action=dlattach;topic=42282.0;attach=197207;image)
-
Hello benjamin,
the problem does exist and you were recently with us on two computers where I showed you the problem. You are welcome to come back to our computer and I will show you the problems.
Which version of Cinema 4D and Corona Renderer are you using, if I may ask, I saw somewhere that you are not using the latest versions. I hope we finally get help, I have been writing to support and here in the forum for two months, apart from the fact that they keep saying that things cannot be reproduced, it does not mean that the problems are not there and obviously there are many here who have the problems.
1. asset browser problem
2. super extremely slow opening of scenes
3. xref problem (paths of corona bitmap shaders are not converted to absolute paths.
Forgive my stubbornness on this topic, but we have to deal with this every day and I would be happy to finally get a solution to the problem.
If you have any questions feel free to contact me (privately) and I can give you more test scenes and please tell me your setup again
Greetings
Thomas
-
Can you please share the version of Scatter that you have installed? Add a scatter object to your scene and hit the info>about tab etc. Thanks!
(https://forum.corona-renderer.com/index.php?action=dlattach;topic=42282.0;attach=197207;image)
Hi!
I'm now using scatter v4, but this is because I went back to Corona 11, I think when these problems were reported I was using the March 11 version as well.
Best
Luis
-
Hello,
I've disabled my directory path with sigershaders.
-
Hi Leo3d,
Just butting in here reading your comment on Siger. I have the complete set and am having issues with scenes opening very slooooooow. Not to mention, not being able to package projects with their materials and sending to render farms which for me do not work so very limited use with their material libs. Hopefully this is something they will sort out soon, been very quiet on updates their end.
-
since i withdrew access to the siger file i no longer have any problems with opening scenes
-
Interesting, I will try this as well. Think they need to sort this out, we pay good money for their library and should work, take for example Stefan-L's amazing ones! Work flawlessly. Will send Siger another email and keep you posted... Have a good week :-)
-
Version 12 is unworkable, stalls for ever opening files. Hopefully a fix is on the way.
Just went back to Coronarender release 11. 4Gb file opens in seconds now.
Mac Studio 128Gb
Sonoma 14.4.1
C4D 2024.4.0
-
The new Daily ( 19.4.) is still UNUSABLE!!!!!!!!
-
Tried the new build released today but could not open a 4Gb file. Reinstalled CR to 11 and all was fine again. The same file opened in seconds.
-
Hi
the same here :(
-
I am actually very happy we have the daily builds. It's also really easy to install the latest stable release so I am never stuck.
Wonder though what changed recently that causes slightly older bigger files to stall. Pity I can't use the new scatter trimmer in the latest daily build. Would have like to use that in a project I have been working on for a while now.
-
Hello there,
Thank you for all your feedback.
Have any of you already tried the latest Daily build? (23.4)
Does the issue persist?
Could any of you share a previous scene so that we can use it to reproduce the issue on our end?
Looking forward to hearing from you.
Have an amazing weekend ahead.
-
Hello there,
Thank you for all your feedback.
Have any of you already tried the latest Daily build? (23.4)
Does the issue persist?
Could any of you share a previous scene so that we can use it to reproduce the issue on our end?
Looking forward to hearing from you.
Have an amazing weekend ahead.
Yes, it does!!
-
Hello there,
Thank you for all your feedback.
Have any of you already tried the latest Daily build? (23.4)
Does the issue persist?
Could any of you share a previous scene so that we can use it to reproduce the issue on our end?
Looking forward to hearing from you.
Have an amazing weekend ahead.
Is there anything new?
I already reported the error 2 months ago. Beanzvision was on my computer about a month ago and I showed him the error (plus other errors that are currently being discussed in another thread). i don't understand why they are asking for test files again. somehow there seems to be something wrong with your internal communication.
i also invited him in this thread on 2024-04-05, 12:44:06 to send test files again, that was a month ago and no one has responded. Now you are asking for test files.
i have already sent them to the support, i posted some tickets two months ago also with the reference to the corresponding forum posts and here still no connection is recognized or looked at properly. is there a programmer with whom you can contact directly?
Either the wrong configuration environments are being used or the communication with the programmer does not seem to be correct. please send me a private message if you have any questions about this or post in the thread so that others can also benefit from it.
-
Hi Tuami
did you try the latest build. I think that's what the team asked.
I did try the latest bulld and the problem of stalling files persists.
I understand frustrations with things not working but that's what daily builds are for. To test. Not for production although I often do.
I worked with Maxwell render for years and the usual practise was to have major bugs unsolved for years. Coronarender has the forum, daily builds and a properly working official release. Super happy with that.
-
I have prepared a file that does not open in CR12 current build, at least I did not wait for it. With CR 11 it opens instantly.
I will send a PM with the link. Let me know when you got it Benjamin.
I saved the file with assets and tested it on my Mac Studio. With build 11 all is fine, current build 12 not so much.
-
hello frv,
you are right that they are there for testing purposes. we lost a lot of time clearing up the problem and the error with the asset browser because we didn't know that this error existed.
i have already reported the problem several times and always tested the latest versions. i just can't listen to this “can you send us a test scene” anymore, because i have already been in active exchange with the corona team and it should be clear by now how the errors can be reproduced.
this was my last mail from march to corona team as an example
---------------
here is the summary again
Computer 1 (My computer)
On this PC is installed
Cinema 4D version 2024.2.3 (latest)
Corona 10 Hotfix 2 from September 2023
The following problems are no longer present when Corona 10 Hotfix 2 from September is installed
- Xref problem
- Long loading times when opening scenes
The following problems are still there
- Problems with Asset Browser (Corona materials are reset)
Computer 2 (computer of a colleague)
The following is installed on this PC
Cinema 4D version 2024.1.0
corona-12-c4d-daily-2024-03-11 (latest)
The following problems are no longer present when Cinema 4D version 2024.1.0 is installed
- Problems with Asset Browser (Corona materials are reset)
The following problems are still there
- Xref problem
- Long loading times when opening scenes
Forum Links
Assets Browser Problem
https://forum.corona-renderer.com/index.php?topic=41775.0
Long Loading Problem
https://forum.corona-renderer.com/index.php?topic=42282.0
Xref Problem
apparently fewer people use xref but the problem still exists
Greetings
Thomas
-
Problems with the asset browser ? I have stopped using the C4D asset browser. Maxon has made an overly complicated mess of the asset browser.
Example, I use Maxtree vegetation. For each placed Magnolia tree from the asset browser which has the same Magnolia CR material for all different Magnolia trees, C4D will still generate a new material slowing down everything.
My own libraries are much better organised than what I can do in C4D's browser with less effort without having to duplicate asset files in C4D asset libraries.
Chaos Cosmos works fine though which for me has become one of the reasons to stick with Corona for now.
I am sure the file loading problem will be solved soon as well. After which I will use the latest build for production again.
Maybe best not to spend too much time on solving issues with daily builds. That's work for Chaos.
-
For each placed Magnolia tree from the asset browser which has the same Magnolia CR material for all different Magnolia trees, C4D will still generate a new material slowing down everything.
Yeah, that's dumb but unfortunately, that's normal according to Maxon since materials are static, unlike objects which can be instantiated and linked. This kept me from building a large model library for a specific long-term project upon the AB and it's too bad since the deep level of integration is nice.
Aturtur wrote a script to merge materials sharing the same name, which is a bit unsafe since a name can be shared by as many materials as you want, even between materials from different render engines. I've modified it to run over the current material selection, which is a bit safer (also fixed a few bugs in the process). It's attached if you need it.
-
Thanks John, love the script. Works very well. Super easy. Makes the asset browser usable again with Maxtree assets.
-
Hello there,
Thank you so much for all your feedback.
We usually ask for testing files because we need to try allocating the root cause, which may differ from one user to another, from one computer to another, and so on.
The more information/files we gather, the more likely we are to find the root cause of the issue.
@frv, thank you for the project; I'm downloading it while writing this reply.
-
Treid the 15 may build.
I could open my testfile with the 15 may build, the one I send to Benjamin, in about 7 seconds on my Macbook air m1. On my Mac Studio it opened instantly with CR 11. Will try at the office how the latest build does with my Mac Studio.
I did notice that the testfile I send to Benjamin (saved project with assets) had lots of mappings missing in the exported tex folder. See attachment. On my Macbook these materials render black. I only noticed because I open this test file on my home MacBook Air. At the office on my Mac Studio I did not notice jpeg maps where missing in the export file.
Somehow Coronarender materials with a certain bitmap path don't export at saving a project with assets. That might explain as well the long opening times.
-
Just tried the current daily build (15 05). Had to go back to 11 though.
I could not open the test file or the original on my Mac Studio harddrive with the current build 12. Regardless of missing textures, with CR11 the same files open instantly. The testfile is not an older file but a project I just started a week or so ago.
-
Hello there,
Sorry for the late reply.
I've been continuously testing this trying to reproduce the "long loading times" issue but haven't had enough luck reproducing it.
Most recent test using the Corona 12 RC1: loading time = 0:12min loading the entire file provided by @frv
Some other sample files I was using for testing purposes are being loaded correctly in a short/decent amount of time (less than a minute or so).
Still, we'll keep an eye on this.
BTW, could any of you try the following and see if the issue persists?:
-Please try removing the File Assets searching paths from the C4D preferences
-Reboot C4D
-Try again opening one of your previous files (any file that was taking too long to open)
-See if the issue persists
Note: Please consider saving your folder paths stored in the C4D preferences to a separate location (screenshot, text file, etc.) so that you can save them again once the test is complete.
Please let us know the outcome.
Kind regards.
-
I have just tried Bnji's suggestion and two files that took 20 minutes each to load opened in less than 15 seconds.
I just deselected the locations of my file asset paths and rebooted Cinema 4D (R2024.4.1)
Corona version 12 daily build Apr 14
Many thanks for the tip!
-
Hi
I followed the steps mentioned above, and the files finally opened quickly. However, subsequent attempts to open the files took again forever. To resolve this, we need to remove the database from the Asset Browser, restart C4d, and re-add the databases after reopening the file. Simply unlinking the database was not sufficient; it needed to be completely removed.
Do we really need to do these steps every time we open a file?!
As previously mentioned, reproducing the issue should be straightforward, if used any materials and/or models from the Asset Browser database.
Additionally, something I noticed is even when the files open correctly, dragging material from the Asset Browser to the scene now takes much longer than before (something that used to be instantaneous).
I hope this helps.
Corona latest daily / C4D 2024 / macOS up to date"
-
About the C4D asset browser, this is not the only cause. I had the problem with Maxtree assets that I opened just by clicking the file. That problem seems to be resolved even when I leave the File path prefs as they are.
I will start a new project soon and see how and if there are still problems opening files. Maybe it's an idea to set Coronarender not to look for maps and link the maps after the file is open through the asset inspector. I used to open very big files in seconds. One of the things I like about C4D is fast opening of the app and files.
-
Are there any news, we have still problems here using latest c4d 2024.4.1 and corona db 12 RC1
-
"-Please try removing the File Assets searching paths from the C4D preferences"
if one removes this it opens fast, as i said in other post (but then it cannot render as files are missing. once loaded one can turn the file paths on again and all works good.
so the file paths make only an issue in opening/loading the scene.
older corona didnt have this issue with file paths at file open.
maybe corona can delay the file paths use until the file is open?
-
just open this scene
64 minutes!
i can gladly set up a remote access to the corona team, where the problem can be reproduced. example files are not possible, as the assets are then bundled centrally and then the problem obviously no longer occurs. just get in touch!
-
There must be a difference between 11 and 12 that causes this huge problem.
Even very large files took just seconds to open. Which is important since I open many files every hour. Release of 12 without solving this problem is not an option.
-
I went back to 11. The current RC 12 is too much hassle. I had hoped a new project in a new file would help. Then working on some displacement settings things slowed down, or stalled completely. Had to globalise filenames to open older materials and links to the mappings.
RC12 is not ready yet.
-
Have to add that I liked some features very much like the cloud density, setting for edge trimming and some others.
But now back in 11 it's all good again. Especially the general slowness of 12 would take all the fun out of using Coronarender. Not an option of course.
-
Changes in Corona 12 for Cinema 4D (Release Candidate 2) (https://drive.google.com/drive/folders/1LjPEUVYQV9hf3NvL0oK5_vkFlfRR1_ff):
VFB 2 improvements/fixes:
Changes and fixes:
Fixed slow loading of scenes when using search paths
dont work for me here. Slow loading as before.. same file, same paths, same database, etc.
___________________________
*could somebody try this, seems working when convert all corona bitmap shaders to native c4d bitmap shaders
Please try the following: Go to the Corona Converter -> deselecte everything except corona bitmap shader and click convert.
save the scene and open it again and tell me if anything has changed.
-
Hi there.
Thank you so much for your feedback.
Could any of you provide any additional scene project to test this?
I've used the last scene project provided by @frv, and everything seems to be working as expected with the latest RC (RC2), even without the need of converting the bitmap shaders.
If you have any additional scene project you can share with us, I ask you to please submit a ticket to share it with us directly.
Kind regards.
;-)
-
hi bnji,
unfortunately this is not possible - as already mentioned several times. If I export the scene including assets, the scene opens faster. I can show you the problem remotely. Just get in touch with me.
-
Hello tuami, hello bnji,
doesn't work for me either. Short test with a 9 MB file. Opens in Corona 11 hotfix2 in 4 seconds and in Corona 12 RC2 1min58sec. I see it like you tuami, if you export the file with all assets and textures, then there are no problems. The problem occurs when the databases are accessed in C4D.
I've attached a screenshot of the 9MB file of the asset inspector where you can see where the textures and materials are. Maybe it'll be helpful for you bnji and it must be possible to create such a file yourself.
best regards from Berlin
I'm on win11 and C4D 2024.4.1
-
for me this is solved in daily/RC2 from yesterday.
5gb scene opens fats now again, also with file paths etc
did you try the newest version?
-
Hi
here the problem is solved if I convert all Corona bitmaps to C4d bitmaps. Then opens fast.
But this has at least 2 huge problems.
1. Old scenes I can not open them because I need to open the scene in the first place to convert them (Corona 11 doesn't have the shader converter)
2. If I forget to convert a new used material for the C4d bitmaps before closing the scene, when I try to open it next time will be a problem.
As mentioned before by several people, I guess the problem is related to the Corona Bitmap / Asset browser links
hope it helps
-
I had just had a problem where all my Maxtree assets rendered black in 11. I globalised the texture names in the C4D asset inspector and then all was good again.
It's indeed a problem if I can only work with older files and assets if I need to open them in 12 first. That would take thousands of euros and weeks.
There has to be a proper solution to this other than constantly having to mind and hassle the texture settings and paths.
-
I have to add, that I just opened a scene in 12 RC2 without any Corona bitmap and took 1.05 min to open (with RC1 was not even possible to open).
But... in Corona 11 opens in 2 sec!
I guess the Corona bitmaps, even if slow down the loading are not the only problem...
-
hello corona team, with the latest build rc3 it seems to be going fast again :)!!!! Thanks, we will continue to test this but it looks good.
tuami
-
Great news, ty for testing and letting us know! I hope others are able to test, and I hope it also resolves their issues too.
-
Hi
Here too, so far all good with the RC3 :) Many thanks.
We keep testing.
-
Good morning,
I can only agree with the previous posters. The files are loading again as expected. Many thanks and thumbs up to the Corona team!
I wish you a good start to the week!
-
Thank you everyone for reporting and repeated testing! The Corona community is the best :) We are very glad to hear that this latest fix seems to be addressing all issues and getting everyone up and running as expected.