Daily Build June 12 on Mac Studio

[frv]

I did a quick test with the latest build June 12:
• Files don't open made with 11 or so slow that I decided to force quit. This problem remains.
• New VFB 2.0  looks better but does not work ( well ) on a Mac Studio Ultra. Zooming in and out is a hassle to keep the image properly within the window. C4D picture viewer works well though.
• C4D crashes after quit. Not sure if this is related to CR. It also crashes after quit with 11.

Build 12 is not functional yet on a Mac Studio OSX Sonoma 14.5 and a fully updated C4D.
Downgraded back to release 11.

[frv]

I am getting a bit worried the issue with older files or files with C4D assets gets solved or not.

[frv]

Just tried to import a Maxtree asset (legacy meterials) with the daily build 12, a 9 Mb file with a few rather small jpg maps as textures.
Took about half a minute to open. The C4D project asset inspector could find all the maps. No need to relink. The maps are within a subfolder in the same folder as the file itself.

Then installed CR 11. The same Maxtree asset opened instantly. Less than a second. But the C4D project asset inspector could not link the maps even as I pointed to the exact location. Although all corona materials looked fine including the maps. Rendered fine too.

With the daily build 12 I can no longer use my assets. Importing a bunch of plants will probably take hours and eventually might even crash my system.

The problem has most likely nothing to do with the C4D asset browser. It's probably just a problem with the path to the right location of the texture maps at opening a file. It seems to me very simple to solve.

The attachment is the instantly opened file with CR11 installed with the broken links (C4D project asset inspector) that are not actually broken.

I have decided to stop using daily builds. I am getting the feeling things are going backwards.

Mac Studio M1
OSX 14.5
C4D 2024.4.1

[luis.lab]

+1

The same problem here.
Corona 12 become useless to me if this is not resolved.

[tiglat_agora]

I have the same problems as the others. Files don't open, or rather I forced the program to close because a 50mb file wouldn't open even after 5 minutes.

Greetings

[frv]

Usually the daily builds were very reliable so it's a bit frustrating those days are over. But I do understand daily builds are meant for a few hobbyists who love to try stuff to see if it works.

I am sure the Corona team will solve this issue otherwise it's the end for Corona for Cinema4D. Wonder if this is just a OSX problem.

[tiglat_agora]

It´s no osx problem, I´m on windows.

[johnnyswedish]

I have been having extremely slow load times as well and I am on Windows 11 as well. Not sure it is Corona or Maxon's INSANE asset browser since R21 or 22? Frankly, it sucks and I  don't hear anyone praising it.

[johnnyswedish]

Actually REALLY SLOW............................ closed my project by mistake and re-opened, still loading after 20min!

[Stefan-L]

here it opens fast when i deactivate all file search paths in c4d prefrences/files, when they are off the scene opens fast.
(after opening c4d is fast again when i re activate them)

i think it is related to the search paths at startup/loading a scene(and maybe material preview/editor preview)

[johnnyswedish]

Hi All,

Opened my project and takes 16:52... I have a custom built rig with a 16core AMD, 96GB fast ram, RTX 4080 Super so no slug with Windows 11 Pro. Everything works ok and stable once loaded. Like Stefan mentioned, I do think the broblem is with mat search paths. Not 100%. If you ask Maxon, they will reply that it's not their fault, you need to be using RS. I do have a hunch it is the Asset Browser causing this, but probably wrong?

[frv]

It's not the C4D asset browser. Even with a single 9Mb Maxtree resource with all maps in place in the same folder the problem persists.

[frv]

Stefan-L is right. Playing a bit with the file assets paths in C4D prefs does make all the difference. Files open instantly if you delete all paths and set them again.

Other things not working yet for me:
-C4D crash at C4D quit after render.
-New VFB 2.0 zooms in and out centering the image to the upper left corner. A hassle to move the image back in view. I would love to see the Corona VFB has a fit to window option. As in the C4D picture viewer.

I hope the RC of version 12 is all about making Coronarender a breeze to use. Not having to point to texture maps, easy viewing of the image in progress, more straightforward camera/rendersettings. A little more AI in the UI might help too.

[johnnyswedish]

Hi All,

I know this thread was specific for OSX but I have the same problem on Windows 11. Just installed the current stable version and loads instantly.

[bnji]

Hi there,

I don't mean to blame someone or to start pointing out to any specific direction, but AFAIK, Maxon have made some changes regarding C4D loading stuff (plugins, assets, etc.)
As some of you already mentioned, if you remove the previously saved location paths, C4D will work faster.
Perhaps you can optimize the use of location paths (in case you have lots of them) and reduce them to only a few of them, just trying to speed things up.
OTOH, have you had the opportunity to test the latest RC1 build?
I've been trying to reproduce this, but haven't been lucky enough reproducing the issue: however, I don't have lots of location paths saved in the C4D preferences.
I'll continue testing this trying to reproduce the issue.
I hope this helps.
Please continue providing us with your feedback.
Kind regards.