At new render setting... C4D quits

[iacdxb]

In a scene... IR is running and if create new render setting and move to that... C4D quits.

Thanks.
...

[TomG]

This is most likely because the new render setting is not using Corona as the renderer? In which case a crash or freeze would likely be expected, since now Corona is not active so the IR won't have an engine to work with?

- Steps were: simple scene, cube, CoronaSky, start IR, create new render settings (which for me uses the Standard engine by default), activate new render settings. Freeze. However, Create New Render Setting, change that to Corona, THEN swap to it, no freeze. Also, if I use Create New Child render settings, then I can swap between them, because as a child it is already set to use Corona.

- Note that swapping between two Corona-based Render Settings will not swap, e.g., Exposure to the new render settings, and will continue to display the Exposure from the Settings that were active when starting it. If you make new Settings active, THEN adjust the exposure for those Settings, IR will then update to use that Exposure.

- IR will never read adjustments to image resolution (whether you have just one or multiple Render Settings)

[houska]

Interesting what everything the users come up with that we didn't count with :-) In any case, Imran, could you please confirm that your crash was really caused by a different render engine set in the render settings?

[iacdxb]

I don't think this is caused by any other render engine.
You can give a try... a simple scene with corona render setting, run IR. create  new render setting, (it will be c4d default setting) move to that... it will quit.

It was happened when I was rendering a scene and it was very noisy...! Tried some setting but no, so then I thought to create new render setting, as I created and move to that to set Corona setting.... it was quit.

One thing can be.... before move to new default setting, first set the corona engine then move to that new setting (I mean... small white icon enable after set the corona render engine).
...

[houska]

Thank you for the information! We'll try it out and fix the crash.

[TomG]

One thing can be.... before move to new default setting, first set the corona engine then move to that new setting (I mean... small white icon enable after set the corona render engine).
...

Just so I understand, if you go to the new render setting, and change that to Corona BEFORE switching to that setting, you can then swap to it without a crash? That was my experience - thing is changing to the new setting before switching it to Corona means that IR is running, but Corona is no longer the render engine selected, which could be problematic for the IR since its render engine is no longer there :)

[iacdxb]

Yes... you are right.
safe side... it should not quit... some red screen or notify Corona is not selected.

Thanks.

p.s.
by the way...Vray Render works well with Corona material/ lights.

...

[TomG]

TY! Just wanted to be sure I understood properly :) Yes, would be nice if IR could catch that it's no longer Corona set as the render engine and stop, or in some other way exit gracefully (or at worst, crash but with a message about why, but hopefully something more friendly than that is possible - that one is over to the devs!)

[houska]

I patched the issue, so the next daily build should not crash anymore. The thing is that it might not work properly either. We will need to think about what should happen, when render settings are switched.

[iacdxb]

Thanks.
I will add in that fixing..., If Corona render is not selected and corona material used in scene... IR and PV should show some solid color view or message to understand that Corona render is not selected.

Thanks.
...