Chaos Corona Forum
Chaos Corona for 3ds Max => [Max] Bug Reporting => [Max] Resolved Bugs => Topic started by: Frenkkk on 2017-10-25, 16:16:01
-
i try corona 1.7 but on my complex scene the interactive render don't work
interactive render always blak screen
1.6 version work fine in same scene
-
Could you share the scene with us for our internal testing/debugging?
-
is a 600/700 mb scene with corona proxy and much more.
with corona 1.6.3 no problem, everything is faster and in real time
with corona 1.7 everything is slow, interactive render give a black screen and only after many minute give a preview,
after the first preview, interactive work fine if only i move camera , if i modify the scene the interactive give black screeen again.
it seems there is a problem with load data in iteractive render.
now i reinstall corona 1.6.3 and all is ok.
with 1.7 is impossible for me to work.
p.s.
i was a similar problem with the fisrt version of corona 1.6
-
Same problem here...Interactive rendering crash all time, When I click in stop button 3d Max keeps thinking and then close it.
I can't work with your 1.7 final release, I have to downgrade to 1.6 version.
Best regards,
-
I have got black screens with interactive too. Old/new/simple/dense scenes.
-
As Ryuu asked, if that would be possible, please share your scenes with us:
https://corona-renderer.com/upload
Otherwise we may not be able to understand the source of the issue.
-
we have had the same issues. prior to 1.7 interactive was rendering fine with scenes with lots of grass and gardens (forest packs). preliminary troubleshooting suggests it has to do with the corona camera. when we switch to Max physical camera it takes the same amount of time to engage (roughly 90 seconds) but then works as expected (even though slowly). with corona cam it seems to go into a loop of trying to refreshing the whole time even if there is no movement (spinning windows circle). we can not recover max because you have to hit stop in the split second it refreshes so we have to end task.
I have attached a screenshot of the scene to give you an idea of what we are dealing with.
Hope that helps.
-
we have had the same issues. prior to 1.7 interactive was rendering fine with scenes with lots of grass and gardens (forest packs). preliminary troubleshooting suggests it has to do with the corona camera. when we switch to Max physical camera it takes the same amount of time to engage (roughly 90 seconds) but then works as expected (even though slowly). with corona cam it seems to go into a loop of trying to refreshing the whole time even if there is no movement (spinning windows circle). we can not recover max because you have to hit stop in the split second it refreshes so we have to end task.
Hi,
what version of 3ds max do you use?
-
2017. i can see if I can replicate the problem in 2018?
-
Experienced the same black screen IR problem with a scene with 3Ml polys on 3dsmax 2018 + corona 1.7.
-
Hi,
I'd like to report the same problems with interactive rendering since updating to Corona 1.7, Max 2016.
It never took that long to load the scene into the IR window before. Now, I often have to wait couple of minutes until the image appears, even while working on small scenes.
During that time the IR window is either black or pixelised (see attached image).
-
Also not with IR, even with production render exist problem///
During production render process with resolution biggest than screen /1920-1080/ -for example 4k,
after some time VFB going to black, and only after switching between channels, for example from Alpha to Beauty or Lightmix a picture reappears, and after some time again disappears...
until the next switching channels:)
-
Also not with IR, even with production render exist problem///
During production render process with resolution biggest than screen /1920-1080/ -for example 4k,
after some time VFB going to black, and only after switching between channels, for example from Alpha to Beauty or Lightmix a picture reappears, and after some time again disappears...
until the next switching channels:)
This should be already fixed in the latest daily build. Give it a try :)
-
Also not with IR, even with production render exist problem///
During production render process with resolution biggest than screen /1920-1080/ -for example 4k,
after some time VFB going to black, and only after switching between channels, for example from Alpha to Beauty or Lightmix a picture reappears, and after some time again disappears...
until the next switching channels:)
This should be already fixed in the latest daily build. Give it a try :)
Ok,thanks:)
-
can you confirm this is fixed then?
-
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
-
can you confirm this is fixed then?
no,
the problem with slow IR is still exist.
-
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?
-
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
-
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
-
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
-
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.
-
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?
-
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
-
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.
-
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?
-
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.
-
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.
-
Oddly enough it seems it stopped doing it when I reverted back to 1.7.2.
-
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?
-
Thanks for the clarification Ondra! Haven't tried latest db. Today I was working with 1.7.2 and this specific issue wasn't present. I'll keep you posted tomorrow when I try it out.
-
any news ?
-
The main problem here is that we were not yet able to reproduce the issue, and it does not affect all users. Once we will have any findings, we will share them on the forum and over the support in related tickets.
-
The main problem here is that we were not yet able to reproduce the issue, and it does not affect all users. Once we will have any findings, we will share them on the forum and over the support in related tickets.
it seems the problem is with dual xeon !!!
-
The main problem here is that we were not yet able to reproduce the issue, and it does not affect all users. Once we will have any findings, we will share them on the forum and over the support in related tickets.
it seems the problem is with dual xeon !!!
That's just one clue.
Are you using a geforce graphics card? If so, can you try updating the drivers, or removing/replacing the card in your PC just to see if there is any difference? There was one case where Nvidia drivers would somehow collide with the Xeons, and when the card was replaced, it would go back to normal performance. But that's still just guessing.
-
The main problem here is that we were not yet able to reproduce the issue, and it does not affect all users. Once we will have any findings, we will share them on the forum and over the support in related tickets.
it seems the problem is with dual xeon !!!
That's just one clue.
Are you using a geforce graphics card? If so, can you try updating the drivers, or removing/replacing the card in your PC just to see if there is any difference? There was one case where Nvidia drivers would somehow collide with the Xeons, and when the card was replaced, it would go back to normal performance. But that's still just guessing.
hi,
my computer is : dual xeon e5 2698v4 with nvidia quadro M4000 and win 7
with corona 1.6.3 even work perfectly !!!
with corona 1.7 no !!!
the problem is in corona 1.7 !!!
because with corona 1.6.3 and the same hardware and driver, all work perfectly !!
(all my drivers are upgraded ! )
another news:
recently i have buy a new pc to use as server,
another dual xeon e5 2698v4 but with nvidia quadro P4000 and win 10
and the problem with corona 1.7 is present i new pc too.....
-
up !!!
any news ?
-
Guys i had same issue. I closed windows defender and now its okey.
-
According to our tests, there is no significant performance drop between different versions of Corona. If there is some at all, it can be explained by using different mechanisms than before (for example: adding each new feature may slightly slow down overall rendering, or rendering of specific other features). We will continue optimizing Corona to make it as smooth and fast as possible, so in case of any remaining issues (in V3 or V4), please do report them to us.