Author Topic: Corona 0.41 (Maya 2016)  (Read 27384 times)

2015-09-29, 09:57:15
Reply #30

haggi

  • Moderator
  • Active Users
  • ***
  • Posts: 335
    • View Profile
In theory, this behaviour is expected with large textures and the usage of OpenImgeIO. If you do the same in Arnold, you will get a similiar slowdown. Exactly for this case the tx files should help to reduce memory demands and speed up the rendering. But I have to admit that the implementation of OIIO may not be optimal.

2015-09-29, 13:52:25
Reply #31

RickToxik

  • Active Users
  • **
  • Posts: 42
    • View Profile
Hmm...  I tried a render yesterday, after 45 mins I was not seeing the form of the building...  The thing is that in the calculation phase, the performance can go as low as 0 to 5 rays/s.  After 45 mins, the rendering phase had not started yet.  I know the textures are big, but I consider this to be a fairly light scene.  As for the textures they are mainly Arroway textures and are part of my everyday work - and specifically targeted at archviz.

Personnally I have no problem converting to tx as it is a standard procedure in vfx, but usually in archviz we work more with texture libraries...  Also, not being able at all to work with jps and pngs at 8k can be a big thing, I always considered tx files to be part of an optimisation process, not a necessary step.

Btw, for the future, I'm never criticizing, just trying to help make a better world : )
Maya 2016, windows 10

2015-09-29, 16:07:12
Reply #32

haggi

  • Moderator
  • Active Users
  • ***
  • Posts: 335
    • View Profile
You are right. The procedure is not optimal at the moment. I suppose you tried to convert the 8k textures to tx files and you did not see any speedup?

2015-09-29, 16:12:45
Reply #33

RickToxik

  • Active Users
  • **
  • Posts: 42
    • View Profile
Nope.  I will try it later today or tomorrow to see if it changes the performance, especially in terms of ray/s during the calculation phase.
Maya 2016, windows 10

2015-10-11, 00:05:11
Reply #34

Eian

  • Active Users
  • **
  • Posts: 42
    • View Profile
Hey haggi,
I just tested the new Corona plugin for Cinema4D and found out that there is a precision setting for UHD Caching. It ranges from 0 to 99 impacting performance and GI accuracy. After playing a bit I saw that when set to 0, GI is far from correct. At 1 which is the default is pretty good and after 2 there is very subtle to no difference compared to 99! Now as far as performance goes, when set to 0/1/2/3 the impact is minimal to none but when set to 50 or 99 it performs about 30% slower and also has a bit more noise for the same number of passes.
I wonder what's the default setting for this option in Maya's plugin?
From the time it takes to precalculate the same scene seems like around 10.
Now I didn't go too deep with this setting so I might be missing something but maybe a lower setting would be faster with no visual impact.
Is this option going to be there in the next version of Maya's plugin?

Regards

2015-10-11, 19:22:02
Reply #35

haggi

  • Moderator
  • Active Users
  • ***
  • Posts: 335
    • View Profile
A lot will change in the next version. The precision attribute is one of them. I have no idea which was the default in the old version, but now it is 1.0 and you can set it as you like.

2015-10-11, 19:55:51
Reply #36

Eian

  • Active Users
  • **
  • Posts: 42
    • View Profile
Good to know.. Any information on release date? :)

2015-10-12, 23:25:47
Reply #37

haggi

  • Moderator
  • Active Users
  • ***
  • Posts: 335
    • View Profile
If everyting works fine, tomorrow.

2015-10-12, 23:30:06
Reply #38

RickToxik

  • Active Users
  • **
  • Posts: 42
    • View Profile
yeepeeeeee!!!!!
Maya 2016, windows 10