Author Topic: release 0.30  (Read 6435 times)

2014-11-22, 17:29:17

haggi

  • Moderator
  • Active Users
  • ***
  • Posts: 335
    • View Profile
Hi,

the new version is online. Still no Winodws8 support for OSL, sorry.
Some features have changed and a several settings are disappeard from render globals.
At the moment I'm trying to match the 3dsmax version. A lot of work has to be done, but I wanted to give you the possibility to play around with the passes and other features.

What has changed:
- transparency in VP 2.0 fix #105
- corrected normal mapping (I hope)
- set dudx, dudy to 0.0
- fixed component connections like facingRatio->ramp.uCoord #106
- fixed strange shadow colors in maya lights #108
- removed ward bsdf
- removed gamma for exr files
- made attributes visible in corona surface shader dragndrop
- corrected defaults for IOR
- added missing anisotropic rotation
- OSL: added reverse node
- added multipliers for coronaSurface color values #121
- added passes rendering, no multilayer exr yet #100
- removed brdfType from coronaShader
- removed acceleration structures from render UI
- fixed tinted maya and swatches lights #111
- fixed incorrect maya light calculation

The new highlight is passes rendering. On vimeo there is a small video showing passes in action:
.

2014-11-25, 04:54:45
Reply #1

Hamburger

  • Active Users
  • **
  • Posts: 84
    • View Profile
Thanks Haggi.

It's a solid update, although unfortunately during testing it seems Corona kills the Maya render view.

"// Error: file: C:/Program Files/Autodesk/Maya2015/scripts/startup/colorManagementRenderViewUtilities.mel line 192: renderWindowEditor: Object 'renderView' not found. //"

I recorded a video showing that if Maya launched with Corona plugin preloaded, render view will break.  If Maya launched without Corona plugin, render view will be fine. I don't know why this is or how it got to be, but if you're interested I can PM you the video link showing what happens.

The solution of course is to load Corona after Maya is launched.

If this doesn't happen to anyone else I'd say my preferences have corrupted.
Maya 2016
Windows 10

2014-11-25, 08:03:28
Reply #2

haggi

  • Moderator
  • Active Users
  • ***
  • Posts: 335
    • View Profile
That's a strange one. Yes, a video would be nice.

2014-11-25, 10:09:17
Reply #3

Ludvik Koutny

  • VIP
  • Active Users
  • ***
  • Posts: 2557
  • Just another user
    • View Profile
    • My Portfolio
I've got the same error when tried to initialize IPR :)

2014-11-26, 01:12:17
Reply #4

Hamburger

  • Active Users
  • **
  • Posts: 84
    • View Profile
I've got the same error when tried to initialize IPR :)

Try setting Corona to NOT autoload with Maya (in Plug-In Manager), then try adding this to your usersetup.mel

Code: [Select]
string $corona = ("if(!`pluginInfo -query -l -n mayatocorona`) loadPlugin \"mayatocorona\"");
scriptJob -runOnce true -idleEvent $corona;

This worked for me 100%, no more errors with the render view.
Maya 2016
Windows 10

2014-11-26, 08:27:50
Reply #5

Ludvik Koutny

  • VIP
  • Active Users
  • ***
  • Posts: 2557
  • Just another user
    • View Profile
    • My Portfolio
Well, i assume throwing error when launching IPR is kinda expecten since IPR is still not supported AFAIK.

2014-11-26, 16:14:07
Reply #6

haggi

  • Moderator
  • Active Users
  • ***
  • Posts: 335
    • View Profile
Indeed. But it should trow an error and not screw up anything else. I'll check it.

2014-11-26, 20:30:57
Reply #7

haggi

  • Moderator
  • Active Users
  • ***
  • Posts: 335
    • View Profile
Okay, I tried everthing, but I as completly unable to recreate the same behaviour. Could you please check by renaming the preferences directoy if this is a prefs thing once again? My mayaToCorona is set to autoload and it is set as preferred renderer in the prefs and everything works fine.

2014-11-26, 23:57:28
Reply #8

Hamburger

  • Active Users
  • **
  • Posts: 84
    • View Profile
I agree I think it is corrupt preferences too and not a bug.

I removed "maya\2015-x64\prefs" but the problem still happened, however I then removed the "maya" folder and let it rebuild everything and that was fine, so yes - corrupt preferences it is!

Quote
But it should trow an error and not screw up anything else.

Yes, it happens exactly like this for me - there doesn't seem to be any extended issues with IPR. It's fine. I thought Rawalanche meant that the render view ui was not being drawn properly.
Maya 2016
Windows 10

2014-11-27, 10:35:22
Reply #9

Ludvik Koutny

  • VIP
  • Active Users
  • ***
  • Posts: 2557
  • Just another user
    • View Profile
    • My Portfolio
Sorry for the confusion. I just meant that i am getting same message "Object 'renderView' not found.". Not that it kills my render view. It does not. I just thought it may be IPR related.

2014-11-27, 11:15:40
Reply #10

Hamburger

  • Active Users
  • **
  • Posts: 84
    • View Profile
No problem! :)

haggi, I was curious if you possibly had anytime to have a look at the physical sun? I couldn't remember if you had confirmed it or not. After playing with Corona .30 today, I still could not achieve a sunny day with sharp shadows 1:00pm blue sky type render.

I think the materials are very nice now and much easier to control, the swatches are obviously fixed of the yellow tint too which also helps. Render passes work nicely.

Maya 2016
Windows 10

2014-11-27, 17:25:34
Reply #11

haggi

  • Moderator
  • Active Users
  • ***
  • Posts: 335
    • View Profile
No, I didn't had a look at the physical sky and sun. I concentrated on the materials. Sorry.