mayaToCorona 0.47

[haggi]

Only two small updates:

- reimplemented dump and resume renderings. You can now activate it from render globals and push a button to save/load framebuffer for resume
- changed the roundCorner connection from messate to point. Before the attribute was grayed out for what reason ever and it was not possible to simply connect a roundCorners. Not you should be able to connect a roundCorners via drag'n drop.

[max45]

Now roundCorners not working

[haggi]

Arrrgh... you are right, I forgot to update a part with the correct attribute, I'll post a new version tomorrow.

[haggi]

Shoud now work again. Bugfix release is ready for download at the usual location.

[max45]

Now with roundCorners node working but that with attribute "roundCorners"?

Waiting chackbox animation in Render View. Very need.

And performance... Max A6 faster near 10-15%. Especially with textures

[haggi]

I implemented round corners the way it now works for the other 3d packages. There will be no roundCorners attribute like in the old shader. I suppose there will be a object set attribute sometime in the near future.
Now with the noOSL textures, I don't have very much influence in the speed any more. It is all pure Corona unless you use OSL shaders.
I only implement a animation option in the render view if more than only one person needs it. I personally do not like it, and it is the first thing I turn off in vray. The goal is to be as interactive as possible and this is not the case any more if you do animations. And if you are not interactive any more you can do batch rendering with one mouseclick.

[max45]

I only implement a animation option in the render view if more than only one person needs it. I personally do not like it, and it is the first thing I turn off in vray. The goal is to be as interactive as possible and this is not the case any more if you do animations. And if you are not interactive any more you can do batch rendering with one mouseclick.

I need 5-10 frames sequence. 2-3 hours per frame.
it is better to see the problem in a buffer.
Very hard implement this checkbox?

[haggi]

Implementing a checkbox is not a problem. The main problem is that it is error prone. Normally you fire off a rendering and you can continue to work. But as soon as you start a sequence, you should not change the scene any more because this can cause problems if the next frame is rendered.

So what you need is not to be able to render a sequence directly in the UI, but you need a standalone viewer for a batch rendering which shows the render process. Even if it is the plan to implement such a standalone viewer, it will take some time, at least a few months.

[jpatton]

The render settings do not load.  I get this error:

# Error: line 2: MelError: file C:\Program Files\Autodesk\Maya2016\Python\lib\site-packages\pymel\core\language.py line 906: Error during execution of MEL script: line 2: KeyError: file C:\Program Files\Autodesk\Maya2016\Python\lib\site-packages\pymel\core\system.py line 543: renderData
Script:
  CoronaCommonGlobalsCreateTab

any ideas?

[haggi]

Do you have installed Mtoa or Vray on your system?

[jpatton]

Hey Haggi, I have vray installed.

[haggi]

Yeah, that's a problem. The reason is that maya does not have a built in way to overwrite the  commonGlobalsTab. There are different ways to approach this problem, either you recreate the whole thing from scratch, that's the way Arnold and myself is doing it, or - the vray way - you overwrite the system mel files. In other words, I cannot guarantee that the plugin works with together if other other plugins are loaded. That's the simple conclusion.

[RickToxik]

Hi j(eff?)patton and haggi,

  I also had the same problem in the past with many other renderers.  Usually the render settings window was opening but one tab was missing, just changing tab was helping to recreate the problem.  But I guess if you post that you just can't access any render setting at all...

  I had this kind of problem with arnold and especially with octane.  Octane was creating objects custom attributes that were interfering heavily with other renderers or could mess up the scene when you did not have octane loaded or available on your system.  The problem was so bad in my case that I stopped using octane in big part because of this - it was crashing scenes and preventing me tu operate maya without octane installed or loaded!...

  Anyway, trying to be not too long, vray creates custom attributes too, so if you're shading a scene in corona that was originally in vray, you might have some custom attributes on your objects that conflict with corona...  And this could mess up your render settings - I've seen this in Arnold.

  So, what I mean to say is that there is a chance that you cannot resolve this issue if you are interacting with objects that have been previously loaded in another renderer, maybe because of objects custom attributes that corona cannot deal with.  Maybe this is not the case but I have seen this before : )

[Eian]

Hey Haggi,

The batch rendering doesn't seem to work in this version..
I also get a crash when I try to go to a different frame while IPR rendering..

"About Corona" gives me the following error
"# Error: IndexError: file C:\Program Files\Corona\mayaToCorona\scripts\Corona\menu.py line 36: list index out of range # "
Not important I know but thought I should let you know anyway.

Using maya 2016 on the latest version of windows 10 (64Bit) btw.

Regards

[haggi]

Thanks, I'll have a look.