Render region hangs up.

[vermu]

Hi,

I have annoying little problem with corona 5. It happens almost in every scene at some point. I can render just fine but when I use render region rendering hangs in preparation phase when you green dots. Does anyone else have this problem?

[romullus]

Sounds like bug. Maybe try to collect minidump and send to the team for investigation. https://coronarenderer.freshdesk.com/support/solutions/articles/5000524006#crashes2

Moving topic to bug reporting board.

[rowmanns]

Hi,

Please can you provide the Corona, 3ds Max and Windows versions which you are using?

A minidump and the scene would also be helpful, instructions on how to do this are in my signiture.

Thanks,

Rowan

[Neiko]

Hello,
we are experiencing the same issues while rendering regions of animation frames in backburner. Rendering freezes for hours during the GI calculations.
It's happening randomly on various nodes but not on every single frames, about 20% of them are freezing. We are using the Max region option in render setup and not the Corona region in the Frame Buffer. Trying out the latter right now to see if that could temporarly solve the problem. I'll update you on our progress.
Issued a ticket to the technical support as well.
Any idea why this happens? thanks

[vermu]

Hi,

Please can you provide the Corona, 3ds Max and Windows versions which you are using?

A minidump and the scene would also be helpful, instructions on how to do this are in my signiture.

Thanks,

Rowan

I am using max 2019, corona 5 and win 10. I can't provide minidump cause when the corona hangs up I have to kill max session from task manager. I don't get autodest crash message.

[TomG]

Actually, the page linked to https://coronarenderer.freshdesk.com/support/solutions/articles/5000524006-how-to-report-issues-3ds-max tells you how to get a minidump from a frozen Max that doesn't actually crash ;) Scroll down to "2. Crashes, Errors, Freezes - Collecting the Minidump File if Autodesk Error Report Window is not Available"

[vermu]

Hi,

Please can you provide the Corona, 3ds Max and Windows versions which you are using?

A minidump and the scene would also be helpful, instructions on how to do this are in my signiture.

Thanks,

Rowan

I sent the minidump through support portal.

[rowmanns]

Hi,

Thanks for sending through the minidump. Would you also be able to provide your scene so we can test it here?

Thanks,

Rowan

[Frood]

Same for a mate here: region + GI calc -> freeze/hang, not to cancel.

Uploaded "1575887167_Corona-V5-Render-region-GI-Calc-Dump.7z" with another dump if it helps. (Corona v5 | Max 2016 | Win 10)


Good Luck

[rowmanns]

Hi Frood,

Are you also able to get hold of the scene? It would be a big help for us.

Thanks,

Rowan

[vermu]

Now I know when the hanging occurs. It's always happening when I convert vray scene to corona scene with scene converter. If the scene is original corona scene it works ok. But if it's converted scene it's never working. But it was working ok in corona 4. This is a bit of a problem for me now.

[Frood]

Hi Rowan,

It would be a big help for us.

I know, but cannot. If you want me to check something specifically in the scene, just tell me.

It's always happening when I convert vray scene to corona scene with scene converter.

Scene was build from scratch, but there might be converted assets inside. But if so, everything would have be prepared externally and then merged. Additionally mate claims that it happens frequently to him (personally I rarely use region).


Good Luck

[rowmanns]

Hi Frood,

Can you confirm that your colleague is using Max render regions or Corona regions?

Thanks,

Rowan

[Frood]

Native Max region. Thx and

Good Luck

[alexyork]

Same here. Not every scene but several - using max region = just sits there calculating secondary bounces forever. Can't send scene though, sorry!

[maru]

(Internal ID=432923875)

[maru]

We received a scene related to this issue, called "....E_region_hang". I was not able to reproduce any issues there, but please make sure that:
- all your plugins are updated to the latest versions (forest pack and vray are definitely used there)
- you are NOT rendering from a vray camera

[vermu]

Hi,

Scene used vray camera. I created corona camera but it didn't help. Same freeze in computing sec. GI

[rowmanns]

Hi,

What is the specification of your computer?

Thanks,

Rowan

[alexyork]

Uploaded scenefile: 1576754518_Crash-scene.zip

[GeorgeK]

Uploaded scenefile: 1576754518_Crash-scene.zip

Had a quick look at this, it's really bizarre, i was able to recreate the hanging and apparently unticking 2.5D, rendering (all good with old disp.), and re-tick it again it solves the hanging issue even with 2.5D on.

Also removing the multi map from displacement, but it works normally after the above process. (3ds max 2020.3)

[alexyork]

Uploaded scenefile: 1576754518_Crash-scene.zip

Had a quick look at this, it's really bizarre, i was able to recreate the hanging and apparently unticking 2.5D, rendering (all good with old disp.), and re-tick it again it solves the hanging issue even with 2.5D on.

Also removing the multi map from displacement, but it works normally after the above process. (3ds max 2020.3)

We also found that on one workstation if you delete the (useless) phoenix water object in that scene and hit render it's fine. But then doing the exact same thing on a different workstation with identical software results in max hanging forever during calculation stage of rendering... very very weird.

[Frood]

Any news here?

Meanwhile I have discovered that Max2016 | 2018 + Native Max Region + Caustic solver=Corona crash. I wonder if this one here is related.


Good Luck

[rowmanns]

Any news here?

Meanwhile I have discovered that Max2016 | 2018 + Native Max Region + Caustic solver=Corona crash. I wonder if this one here is related.

Good Luck

Hi Frood,

This one is still under investigation by the devs. It's not related to the other issue that you found with the Max regions and caustics solver.

Thanks,

Rowan

[Frood]

Ok, thanks again Rowan, also for updating the changelog.


Good Luck

[rowmanns]

This is fixed in the latest v6 DB. (2020-06-18)