1.2 scene freeze in 1.3 while rendering

[Mikhail]

1.2 scene freeze in 1.3 while rendering
 it works with all proxies hidden but the preparing proccess is still slow

Any ideas ?
I need to render it guys...it's commercial work )
Install 1.2 ?

[hubrobin]

Hi Mikhail,

we will need a bit more information in order to get this sorted. Is it possible to provide us with the scene through our private uploader? Can you capture and give us a minidump of the frozen process? In the mean time, can you give me a screenshot of the corona framebuffer when its frozen? Any displacement in the scene?

Thanks,
Robin

[Mikhail]

I don't use displasement.
Yes, I can upload scene via FTP
..............................................................

I don't know why but this morning it works better ))

Computing Secondary GI is still slow but it works...

Computing Secondary GI was much faster in 1.2 (in this particular scene)

With hidden multiscatter grass  it works almost normally.

I've attached screen with slow step (Computing Secondary GI )

[Mikhail]

Yes, the problem is Multiscatter (Grass ) with a lot of instances
May be because it use its own proxy system

I use geometry as an instance not corona proxy.

Secondary GI with this Multiscatter takes 5-10 times more than in 1.2

If Sec. GI is off - Rendering Initial pass is very slow

Using new corona proxy with multiscatter did nothing - still very slow Sec Gi step

Turning off this multiscatter(Grass) or decreasing amount of instances solves the problem !!!
But the point is that it worked in 1.2 very well

wtf guys ?
Give me my green grass back to my home : )

[maru]

We would have to do some tests. Could you start a new support ticket and send us the scene (or other scene where the problem is reproducible)?
https://coronarenderer.freshdesk.com/support/tickets/new

By the way, if it's an exterior scene, you should not use UHD as the secondary solver. PT+PT should be fine unless there are some places where secondary GI is dominating (it looks like you have a house in there so it would probably require some checking).

[Nekrobul]

We would have to do some tests. Could you start a new support ticket and send us the scene (or other scene where the problem is reproducible)?
https://coronarenderer.freshdesk.com/support/tickets/new

By the way, if it's an exterior scene, you should not use UHD as the secondary solver. PT+PT should be fine unless there are some places where secondary GI is dominating (it looks like you have a house in there so it would probably require some checking).

Maru have you noticed that that was about 3-4 reports with the same problem. And all of them are geometry overkilled exterior scenes.

By the way the solution is disable low thread priority.

And i have an idea about it, i don't know if it is pausible but when the render hits the RAM limit then LTP must be swithed off automaticaly.

[Mikhail]

!!!!! ----- Yes, "low thread priority" flag solves the problem.

It's strange but PT+PT works too...even if "low thread priority" flag is ON
Yesterday it did not work so well...may be it has become work well after rebooting ? But still 1.2 worked well yesterday without rebooting.

LOL it even works with UHD now and "low thread priority" flag is ON )))
Magic : )

It seems like when I unchecked "low thread priority" flag something changed in my system not in 3d max because I restarted it...

[Mikhail]

The problem is solved for me Maru.

Do you still need the scene for a tests ?

[maru]

We could take a look at the scene if it's not a problem for you. Checking "low thread priority" is not an official solution, sorry. It is more like a workaround. Did you by any chance run any resource-heavy app in the background? Or edited something in Photoshop at the time Corona was rendering, etc?

[Mikhail]

Ok I will start Support ticket and upload my scene.

"low thread priority" is not an official solution BUT it did work for me : )

I don't remember exactly but I think I had videoplayer opened may be photoshop with one jpeg file opened, not too much in other words

[maru]

Is it possible that the problems are related to Itoo plugins? If anyone is experiencing this too - are you using Itoo plugins?

[Mikhail]

No,I did not use it in this scene.

[Freakaz]

I have similar problem, with rendering freeze in the process of rendering with heavy scene. It renders fine for like 6-8 passes and then just render progress stops. Randomly. Once after 6 passes, then after 9 passes. I've experienced it on couple of scenes, not only exterior but interior also. No iToo plugins. No photoshop in background, only chrome with few tabs. Scene  requires ~17 gigs of RAM, but there's 32 on my workstation, so there shouldn't be a problem.
Now trying the low thread priority disabled workaround and looks like it's fine so far. 

[Ondra]

can you make a minidump when the rendering freezes? https://coronarenderer.freshdesk.com/support/solutions/articles/5000524006

[maru]

only chrome with few tabs

There was some Chrome-related fix recently. Could it be the cause?