New daily build crashes c4d

[CJRenders]

Installed the new daily build and it crashes c4d and wont stay open.. cool

[TomG]

https://help.c4d.corona-renderer.com/support/solutions/articles/12000033461-how-to-report-issues-c4d

Be sure to include the bugreport.txt, whether it's every scene, what version of C4D, etc. Thanks!

EDIT - and which OS as well :)

[CJRenders]

cant include bug reports when none are made. The program doesnt get that far. I found that it didnt delete the previous installations so I had to manually do it and reinstall the build

[bnji]

It would be better if you create a support ticket or send an email to support@corona-renderer.comIf you can't include a bugreport file, please send screenshots and screen recordings if possible.
Also, include hardware and software specs.

Don't forget to include a list of step-by-step of how to reproduce the issue.
Regards.

[rafaz]

Hello all,

I'm also having the same issue, once installed tried open it crashes. I noticed the last 2 builds were like that, the only one that works right now is the 2021 - 02 - 17 build. Once I delete the corona folder c4d comes backup and running again. It wont generate bug report

I'm on:

Mac Big sur 11.3.1 - M1 model
Cinema 4d R23

[mmarcotic]

Hello,

sorry that you're having issues. We will definitely look into this, but it would be super helpful if you could somehow extract the screenshotted log.

Thanks in advance,
Jan

[rafaz]

Hello,

sorry that you're having issues. We will definitely look into this, but it would be super helpful if you could somehow extract the screenshotted log.

Thanks in advance,
Jan

I have attached a txt file containing the whole report, screenshot won't fit the whole thing.

[mmarcotic]

Thank you very much,

we will prioritize this for (hopefully) the next daily build.

Thanks,
Jan

[AndyPi]

Hi,

I am on Big Sur 11.4.1 Beta and every version of the Daily build crashes same as above.

Will there be support when the public release comes out?

I have a attached the crash report anyway but I am running a Hackintosh with a 3950x so you wouldn't officially support my machine. However under previous versions of Big Sur Corona has run perfectly for me.

[rasputin1963]

Yep,  the new daily build is consistently crashing the whole C4D program.   This crashing phenomena started immediately after I installed the new May 17th daily build.  The crash happens when the AFB renderer reaches its first or second pass.    A Corona Error Message pops up (see screencap),   and the whole C4D software is frozen and rendered useless,    and has to be terminated via the Windows Task Manager.     The error message is just a white screen and has no verbiage on it.

I'm using Maxon Cinema 4D R20.

[mmarcotic]

Yep,  the new daily build is consistently crashing the whole C4D program.   This crashing phenomena started immediately after I installed the new May 17th daily build.  The crash happens when the AFB renderer reaches its first or second pass.    A Corona Error Message pops up (see screencap),   and the whole C4D software is frozen and rendered useless,    and has to be terminated via the Windows Task Manager.     The error message is just a white screen and has no verbiage on it.

I'm using Maxon Cinema 4D R20.

Is it possible to quit C4D via LSHIFT+RSHIFT+DEL ? That would provide us with some tangible information about the error.
Did you try uninstalling and reinstalling the daily build? I have tested it in R20 and it does not crash for me. Also I would recommend updating Nvidia Drivers (if applicable), as we have updated Optix Denoiser in the latest daily.

Thanks,
Jan

[rafaz]

Hello all,

I just noticed the new Corona Renderer 7 for Cinema 4D (Daily Build 2021-06-05) release, I don't see any mention on either this thread issue got fixed or not. Or maybe it would be the

•Fixes of macOS build for legacy CPUs ?

[BigAl3D]

@AndyPi Why on earth are you using a Beta version of Big Sur, when it was released almost a year ago? Just seems odd. If indeed you are using it, then having an error with another pre-release software is not a fair complaint.

[mmarcotic]

Hello all,

I just noticed the new Corona Renderer 7 for Cinema 4D (Daily Build 2021-06-05) release, I don't see any mention on either this thread issue got fixed or not. Or maybe it would be the

•Fixes of macOS build for legacy CPUs ?

This fix for legacy CPUs also included some M1 fixes, we unfortunately do not have an M1 available to us presently, so we hope that this fixed your issue.

Thanks,
Jan

[rafaz]

Hello all,

I just noticed the new Corona Renderer 7 for Cinema 4D (Daily Build 2021-06-05) release, I don't see any mention on either this thread issue got fixed or not. Or maybe it would be the

•Fixes of macOS build for legacy CPUs ?

This fix for legacy CPUs also included some M1 fixes, we unfortunately do not have an M1 available to us presently, so we hope that this fixed your issue.

Thanks,
Jan

Hello, I just tried the new release and it's not crashing on start up, therefore, it is crashing when i Hit render.
i've attached the bug report this time.

Latest daily, Mac M1, big sur 11.4

 

[BigAl3D]

Just a guess here, but I thought Corona is not yet able to run native on M1 chips, no? Assuming it cannot, there a thread about a trick to get Corona to run on M1 chips. Here's that specific post:

"Corona plugin isn't fully ported yet to natively work on M1 processors, but you can still run it using Rosetta.

First, please install latest daily build of Corona v7 if you don't have it already.

Then, you need to make sure Rosetta 2 is installed. You should be asked to install it any time you try to open any application that is compiled for Intel processors, so there is a good chance you already have it on your system. The quickest way to check it is to try to open Corona Image Editor - it should either open directly, meaning you already have Rosetta installed, or ask you to install Rosetta.

Afterwards, you can just switch your Cinema 4D to start using Rosetta so it can load Corona plugin. To do this, find Cinema 4D in you Applications folder, right click (or ctrl+click) its icon, select "Get Info" and check "Open using Rosetta". After this you should be able to open Cinema 4D as usual and Corona should load normally.

We realize this is not perfect and we are already investigating native support of M1 processors."

@Ales

[rafaz]

Just a guess here, but I thought Corona is not yet able to run native on M1 chips, no? Assuming it cannot, there a thread about a trick to get Corona to run on M1 chips. Here's that specific post:

"Corona plugin isn't fully ported yet to natively work on M1 processors, but you can still run it using Rosetta.

First, please install latest daily build of Corona v7 if you don't have it already.

Then, you need to make sure Rosetta 2 is installed. You should be asked to install it any time you try to open any application that is compiled for Intel processors, so there is a good chance you already have it on your system. The quickest way to check it is to try to open Corona Image Editor - it should either open directly, meaning you already have Rosetta installed, or ask you to install Rosetta.

Afterwards, you can just switch your Cinema 4D to start using Rosetta so it can load Corona plugin. To do this, find Cinema 4D in you Applications folder, right click (or ctrl+click) its icon, select "Get Info" and check "Open using Rosetta". After this you should be able to open Cinema 4D as usual and Corona should load normally.

We realize this is not perfect and we are already investigating native support of M1 processors."

@Ales

Thx for the response but, unfortunately its not the case. Rosetta is installed since day one, and all the steps are checked.

The only version that works so far is the 7 Daily Build Fev 17, all the others after that has been crashing on start up or like the last one when I click on render. It's kinda sad that dev team doesn't even have a machine to test on, which means NATIVE support is even further away... I've been with corona since early v2 versions and maybe it's time to look for a new render :/ 

[BigAl3D]

I know, that sound bad for developer to say "we don't have a machine to test on" even though they are taking money from people using that platform. Doesn't seem right.

[mmarcotic]

Hello all,

I just noticed the new Corona Renderer 7 for Cinema 4D (Daily Build 2021-06-05) release, I don't see any mention on either this thread issue got fixed or not. Or maybe it would be the

•Fixes of macOS build for legacy CPUs ?

This fix for legacy CPUs also included some M1 fixes, we unfortunately do not have an M1 available to us presently, so we hope that this fixed your issue.

Thanks,
Jan

Hello, I just tried the new release and it's not crashing on start up, therefore, it is crashing when i Hit render.
i've attached the bug report this time.

Latest daily, Mac M1, big sur 11.4

Thank you for this bugreport + additional information, I will update our internal task.

Thanks,
Jan

[ChrysMacZ]

Hello all,

I just noticed the new Corona Renderer 7 for Cinema 4D (Daily Build 2021-06-05) release, I don't see any mention on either this thread issue got fixed or not. Or maybe it would be the

•Fixes of macOS build for legacy CPUs ?

This fix for legacy CPUs also included some M1 fixes, we unfortunately do not have an M1 available to us presently, so we hope that this fixed your issue.

Thanks,
Jan

Hello, I just tried the new release and it's not crashing on start up, therefore, it is crashing when i Hit render.
i've attached the bug report this time.

Latest daily, Mac M1, big sur 11.4

Hi all,

Exactly the same for me, this daily now don't crash C4D but crash when I clic render or try to create Corona material. (Fresh Clean Install and update of Mojave 10.14.6 - Radeon RX 580 - C4D R24.037 and Corona 7 Daily 2021-06-05 nothing more was installed).

Thanks,

Chrys

[CJRenders]

Has this thread become a go to spot to report crashes? lol

[mmarcotic]

These crashes were pretty much identical (M1 chip under Rosetta)

Feel free to try out the release candidate build! It doesn't crash for us anymore internally.

Thanks,
Jan