Render region hangs up.

[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)