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

[luis.lab]

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"

[frv]

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.

[tuami]

Are there any news, we have still problems here using latest c4d 2024.4.1 and corona db 12 RC1

[Stefan-L]

"-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?

[tuami]

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!

[frv]

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.

[frv]

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.

[frv]

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.

[tuami]

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.

[bnji]

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.
;-)

[tuami]

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.

[tiglat_agora]

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

[Stefan-L]

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?

[luis.lab]

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

[frv]

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.