release 0.34

[haggi]

And another one:

This release contains an updated corona core. The old releases will expire in January.

release 0.34:
- fixed shader assingment via Assign New Material... #125
- fixed cameras ui in renderGlobals #151
- should now run on windows8

[Hamburger]

Thanks Haggi - It's very comfortable to use Corona these last few versions.

Unfortunately I am still struggling with producing a physical sun with sharp shadows - maybe I'm missing something? I have uploaded a simple test scene for reference.
(Also - I noticed a crash when I put the sun size multiplier to .010. )

[haggi]

Indeed, the lower limit should be 0.01, but for some reason the value should be not lower than 0.055.
Your skylight is brigther than your sunlight. That's the reason why you do not see the sun shadow. Increase the sun brightness and you will see a sharp shadow. I'll check if I can make this values a bit more appropriate to avoid confusion.

[Hamburger]

Thanks Haggi - yes out of the box settings would work I think. Although I'm not sure how you could deduce physically accurate sun+sky intensity settings.

[Hamburger]

Is batch render supported yet?

I tried a few command line, but couldn't get anything to render via batch;

render -r Corona

just returns "Cannot open renderer description file "CoronaRenderer.xml"".
Corona is installed though the way it is specified in the manual - I guess Maya can't find it without the GUI because Corona is running as a module?

[haggi]

Well, I didn't update the xml file since a long time because noone needed it.
And maya needs the xml file either on a location which is defined by the env variable MAYA_RENDER_DESC_PATH. Unfortunatly this has to be defined outside of maya. Or it has to be placed in the maya/bin/rendererDesc directory.
I will put it on my to do list. In a future version it will be installed autmoatically.

However, starting a batch rendering from within maya should work.

[Spiketer]

Hi everyone finally I got to you. My problem is not working your render. I have Maya 2015 Ext 1. All made by written but the plugin Serano not connected
"// Error: line 1: The specified module could not be found.
 (mayatocorona) // "

[haggi]

Did you install the redistributables for VisualStudio 2013?

[Spiketer]

Yes everything is installed VisualStudio 2013 version 12.0.21005 х86-х64

[haggi]

Could you write me a email, then I'll send you some infos to track hopefully the problem. (haggi at haggi.de)

[Spiketer]

Keep my address spiketer@rambler.ru

[Spiketer]

I understand this application Dependency Walker shows the lack of the necessary DLLs. Then the question is it possible to specify the path to missing dll file mayatocorona.mll and as it to make. Of course waiting for your solution

[Spiketer]

In your assemblies found a strange phrase. Why file mayaStart catalogue mayaToCorona_2015\ressources have a copy set PATH=C:\Program Files\Autodesk\Maya2014\bin;%PATH% and no set PATH=C:\Program Files\Autodesk\Maya2015\bin;%PATH%

[haggi]

You are completly right, that's wrong. I wasn't aware that someone uses this script to start maya. I'll correct it in the next release. Of course the path should point to Maya2015.

[Hamburger]

Strange, on my home computer .34 works, but at work .34 does not work.

When rendering it will crash because it is now 2015.

[haggi]

Strange. The limit depends on the corona_release.dll. Can you examine that the corona_release.dll in the mayaToCorona/bin directory is from 30th of December?

[Hamburger]

Yes, it is most definitely .34 downloaded from the link in the email.
The files are from 31st december 2014.

I deleted the old folder so there was nothing left, then unzipped the new folder to the Autodesk folder, so there is no overlap either.

[Hamburger]

Solved it.

A few months ago when i first installed corona, I accidentally unzipped it to the maya root directory. Even though I eventually installed it the proper way as a modeul, there was an old left over Corona_Release.dll in the root maya bin folder. Deleting this fixed it. Sorry for any issues Haggi.

[haggi]

Ahh, that's good to know. Thanks for letting me know.