corona 1.7 interactive render problem (SLOW)

[denisgo22]

can you confirm this is fixed then?

I can confirm that problem with black VFB in production mode render is gone:)
but still exist problems with slow IR, as previously reported by the guys:)
Thanks

[Frenkkk]

can you confirm this is fixed then?

no,
the problem with slow IR is still exist.

[Ondra]

can you confirm this is fixed then?

no,
the problem with slow IR is still exist.

can you upload the scene for us, so we can take a look at it?

[Frenkkk]

can you confirm this is fixed then?

no,
the problem with slow IR is still exist.

can you upload the scene for us, so we can take a look at it?

i sent the scene 22 days ago
here the tiket : https://coronarenderer.freshdesk.com/support/tickets/9019

i have the problem in all my scene : the interactive render in 1.7.2 is slow slow slow (impossible to work)
while in 1.6.3 it is very fast.

i use 3dsmax 2015, win7 with 64 gb ram dual xeon 2698v4.

please help me !!!!

thanks

[Ink Visual]

Hi guys,

I'd like to report again that I still face the same bug. I was hoping that the Hotfix 2 will resolve the issue however the IR is still super slow. Every scene (small, big, with scattered objects, without...) is much slower compared to 1.6.3. Really annoying black screen while reloading the view.
Please could you confirm that somebody is working to fix it?

My setup is dual Xenon E5 2680 v0, 32GB RAM, win7, MAX 2016

Thank you,
Michal

[maru]

i sent the scene 22 days ago
here the tiket : https://coronarenderer.freshdesk.com/support/tickets/9019

@Ondra - The issue is logged in our internal tracker as "9019 - 1.7 IR slowdown" with the sample scene attached.

I'd like to report again that I still face the same bug. I was hoping that the Hotfix 2 will resolve the issue however the IR is still super slow. Every scene (small, big, with scattered objects, without...) is much slower compared to 1.6.3. Really annoying black screen while reloading the view.
Please could you confirm that somebody is working to fix it?

My setup is dual Xenon E5 2680 v0, 32GB RAM, win7, MAX 2016

So far it seems that there are some issues with dual xeons.

Here are some (pretty random) ideas what you could try:
-Everything from here: https://coronarenderer.freshdesk.com/support/solutions/articles/12000011479
-Going to System > System settings and under "interactive rendering" changing "# of threads override" from the default -1 to something like -2, -3, or -4

[Dalton Watts]

I'm also facing this kind of issues since the beginning of 1.7. As soon as I launch IR window on my second monitor, if I go back and just hover the mouse over the viewport... BOOM!! IR constant refresh. It only stops refreshing if I force it clicking on IR window.

Max 2017, latest Corona_2018-01-04 and Dual Xeon 2696 v3.

[maru]

I'm also facing this kind of issues since the beginning of 1.7.

Have you tried the ideas from my previous message, and also disabling the Views > Viewport configuration > "Improve quality progressively" option?

[denisgo22]

I'm also facing this kind of issues since the beginning of 1.7.

Have you tried the ideas from my previous message, and also disabling the Views > Viewport configuration > "Improve quality progressively" option?

Seems it help:)
-----------------------
Sorry:(
Make some tests on simple interior scene----its NOT HELP :(((
With /render hidden/ checkbox in Max and - for example -- one unhidden object in veiwport IR refreshing constantly with moving cursor from VFB to viewport and viсe versa/
/Improve quality progressively/ is OFF for all viewports///

Also with one render object, without /render hidden/--while moving the cursor to viewport and leave this on viewport--- exist constant flashing buttons /Stop/ and /Render/ in VFB tab///
DB 4 2018/max2017

[Dalton Watts]

I'm also facing this kind of issues since the beginning of 1.7.

Have you tried the ideas from my previous message, and also disabling the Views > Viewport configuration > "Improve quality progressively" option?

Thank you for the suggestions maru but none of the solutions works. Disabling "Improve quality progressively" or changing the thread number under system settings didn't solve it.

Edit: Forgot to mention I'm using Corona Camera.

[Dalton Watts]

IR was the major advantage Corona had (and still has) over vray. This was precisely what made me change to Corona. Will this be addressed by the team in the near future?

[NicolasC]

So far it seems that there are some issues with dual xeons.

Hi Maru,

Would you please mind elaborating a bit about these issues, if you can ?

Thank you.

[Frenkkk]

IR was the major advantage Corona had (and still has) over vray. This was precisely what made me change to Corona. Will this be addressed by the team in the near future?

nice question.

[Dalton Watts]

Oddly enough it seems it stopped doing it when I reverted back to 1.7.2.

[Ondra]

The restarts were caused by recent "reset xform" fix. We had to improvize since this operation was not sending us correct notifications. And the improvization broke something else. This is common pattern in 3dsmax, especially in interactive rendering - fixing one hole opens another hole.

It is OK now, with the latest daily?