C4D scenes dont open with new Daily Build from Corona 12 March 11.

[frv]

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.

[bnji]

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.

[runx]

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!!

[tuami]

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.

[frv]

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.

[frv]

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.

[tuami]

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

[frv]

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.

[John_Do]

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.

[frv]

Thanks John, love the script. Works very well. Super easy. Makes the asset browser usable again with Maxtree assets.

[bnji]

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.

[frv]

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.

[frv]

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.

[bnji]

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. 

[CambridgeCreative]

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!