Chaos Corona Forum

Chaos Corona for 3ds Max => [Max] Bug Reporting => Topic started by: Light&Bit on 2017-12-21, 18:59:31

Title: 1.7 slower than 1.6
Post by: Light&Bit on 2017-12-21, 18:59:31
Hi chaps,

I have noticed that Corona interactive render 1.7 is slower than 1.6, is it just me or what?

Best

Dan
Title: Re: 1.7 slower than 1.6
Post by: cecofuli on 2017-12-21, 22:20:32
Can you show us some video screen-capture of file running inside the two versions?
And can you give us more info?
Title: Re: 1.7 slower than 1.6
Post by: Frenkkk on 2017-12-25, 13:50:01
Hi chaps,

I have noticed that Corona interactive render 1.7 is slower than 1.6, is it just me or what?

Best

Dan


me too !!!!

1.7.2 is slower than 1.6.3.
is impossible for me use 1.7, is TOO SLOW ( i have a dual xeno e5 2698v4)

now  I reinstalled  the old  1.6.3


i opened this topic : https://forum.corona-renderer.com/index.php?topic=17989.0
and one month ago I opened a ticket on Corona Renderer Helpdesk, where i upload scene and screenshot,

but nothing happened....


I hope this is not the prelude to what will happen to corona render after the acquisition of chaos group. !!!!!
Title: Re: 1.7 slower than 1.6
Post by: maru on 2018-01-03, 12:21:39
and one month ago I opened a ticket on Corona Renderer Helpdesk, where i upload scene and screenshot,
I sent you this message and never heard back:
"Meanwhile, if you would like to check this, there is one more idea: go to system tab > system settings and change the "# of threads override" from the default -1 to -2, -3, or -4. You can also try with higher values."
So does it change anything?

Quote
I hope this is not the prelude to what will happen to corona render after the acquisition of chaos group. !!!!!
How could this be related to Chaos Group?
Title: Re: 1.7 slower than 1.6
Post by: Frenkkk on 2018-01-04, 12:10:17
and one month ago I opened a ticket on Corona Renderer Helpdesk, where i upload scene and screenshot,
I sent you this message and never heard back:
"Meanwhile, if you would like to check this, there is one more idea: go to system tab > system settings and change the "# of threads override" from the default -1 to -2, -3, or -4. You can also try with higher values."
So does it change anything?


no, nothing,

Title: Re: 1.7 slower than 1.6
Post by: maru on 2018-01-04, 13:20:58
Thanks for checking.
Title: Re: 1.7 slower than 1.6
Post by: dcode on 2018-01-04, 20:12:27
Also the same for me here, I revert back to 1.6 and significantly quicker.
I also discovered that instanced group of lights were not displaying however they worked perfectly once I reverted back to 1.6.
Title: Re: 1.7 slower than 1.6
Post by: maru on 2018-01-05, 09:59:12
Also the same for me here, I revert back to 1.6 and significantly quicker.
What is your processor model?

I also discovered that instanced group of lights were not displaying however they worked perfectly once I reverted back to 1.6.
Can you explain this? It sounds like a different issue.
Title: Re: 1.7 slower than 1.6
Post by: dcode on 2018-01-08, 23:36:02
Hi Maru,

Sorry for delay reply, I am using a dual Xeon  E5-267W 3.1GHz. on Win 7.

Yes you are correct the grouped lighting which was mirrored but not rendering in a refreshed IR view is a separate issue.

Cheers
Title: Re: 1.7 slower than 1.6
Post by: maru on 2018-01-09, 10:06:22
Sorry for delay reply, I am using a dual Xeon  E5-267W 3.1GHz. on Win 7.
There were some fixes regarding IR in our latest daily build. Could you test it? https://coronarenderer.freshdesk.com/support/solutions/articles/5000570015

Quote
Yes you are correct the grouped lighting which was mirrored but not rendering in a refreshed IR view is a separate issue.
It would be best if you could describe it well and report here https://corona-renderer.com/bugs/
Title: Re: 1.7 slower than 1.6
Post by: Frenkkk on 2018-01-10, 17:42:06
Sorry for delay reply, I am using a dual Xeon  E5-267W 3.1GHz. on Win 7.
There were some fixes regarding IR in our latest daily build. Could you test it? https://coronarenderer.freshdesk.com/support/solutions/articles/5000570015


i have tested the latest daily build but

the problem is still exist :(