Crash with Edge Trimming - C4D 2024.1.0 and Corona 10 (HF2)

[d4l1]

Hi,

as mentioned in the topic name, grass assets that have edge trimming active in the Opacity slot are crashing the render right at the start. This is new in 2024.1 and / or Corona 10 (HF2). Unfortunately I can't test it with C4D 2023.2.2 and Corona 10 (HF2), only without the hotfix. About ~ 1 year ago today I'd kind of the same problem with crashes while Edge Trimming is active and I'm not really sure what solved the problem. Did some trail and error to get rid of that crash but I guess it solved itself over time. But now the problem happens with a newer version, still working with 2023.

Could it be a bug or should I wait it out? :)

Thanks for the great work!

[Beanzvision]

Hi there, are you able to share a test scene at all?

[d4l1]

Preparing a test scene is always a great way of troubleshooting.

Got to the point where I would say, the grass assets created with Forester will crash while using Edge Trimming. Once converted, it renders without any problem. Looks like that thread was opened a little bit too fast and I'm off to the other support site now. :)

Thanks anyway!

[Beanzvision]

Can you also test this with the latest V11 daily build and let me know if it still crashes for you?
https://drive.google.com/drive/folders/1AMdDmYkftsDZelYVFHRTF84oVgEhs9ny

Also, can you share the bug reports from the previous crashes?

[d4l1]

Installed the Daily Build, but still crashing.

Attached are both bug reports.

[Beanzvision]

Thanks for the files, I will add them to our internal bug report. Can you also try this with a Corona material instead of using a standard C4D material and also another grass asset from our Cosmos browser?

[d4l1]

Yes, but I've left work already and will not be back until next Monday. But I'll share that outcome asap!

[Beanzvision]

Thanks!

[d4l1]

Back again. Replaced the material with a Corona Physical Material and the Edge Trimming in the Opacity slot. Still a crash after I start rendering. Bug Report attached.

[Beanzvision]

Okay, thanks for testing and letting me know. I will log the report. Also, does it crash if using a grass assets from the Cosmos browser?
(Internal ID=1240086686)

[d4l1]

With an grass asset from the Cosmos Browser (RayGrass004, still unconverted, as a proxy mesh) it works.

[Beanzvision]

Okay, thanks for testing and letting me know.

[d4l1]

A quick update to that problem from 'the other side', the Forester Support. Not quite sure if I could update the Support ID / Internal ID in a different way than this. :)

Hello,

We could reproduce the bug. However, it’s not a Forester or MultiFlora bug.

The bug needs to be resolved on the Chaos side.

It’s best to email them with a simple scene (plane + Forester MultiFlora simple grass + chaos scatter) and have them take a look at it.

The bug is only visible in 2024 as far as we can tell. So that makes it easier to track down.

[Beanzvision]

A quick update to that problem from 'the other side', the Forester Support. Not quite sure if I could update the Support ID / Internal ID in a different way than this. :)

Hello,

We could reproduce the bug. However, it’s not a Forester or MultiFlora bug.

The bug needs to be resolved on the Chaos side.

It’s best to email them with a simple scene (plane + Forester MultiFlora simple grass + chaos scatter) and have them take a look at it.

The bug is only visible in 2024 as far as we can tell. So that makes it easier to track down.

Thanks for the update. I believe we are currently looking into this and may have it resolved.

[d4l1]

Great, nice to hear! Thank you for your support!