General Category > Chaos Corona for Maya - Bugs

Corona 0.41 (Maya 2016)

(1/8) > >>

Eian:
Hey Haggi,

Well done on your last release. Areal lights working properly now.
Though when I connect a texture to a to a surface through coronaLight material, I still get strange results as you can see on the image attached.
Problem occurs in progressive and bucket rendering mode as well.

Another thing I noticed with Maya 2016 is that if I save a rendered image as an openexr it wont save its gamma settings correctly.
That applies regardless of the color management setting under Maya's preferences.
Now this might be a Maya problem cause it happens with other renderer as well but I believe there might be a way you can fix it.
Only workaround I found working, is to change Colormapping_gamma to 1.000 and then save the image. And btw saving raw / color managed mode does the same thing.
So even if this is a maya problem maybe you can force a Colormapping_gamma of 1.000 just before saving the openexr image?

As you pointed out CoronaVFB is really experimental at this stage and due to constant crashes I can't say much as of now.

Keep up the good work!

Regards,
Ian

haggi:
Could you please clarify the exr problem a bit?
Do you save the rendered image directly from the renderview? Or do you mean the automatically saved image from rendering which can be found in the images directory? The rendered image will always be saved in the images directory. And if it is an exr, color correction is used, but gamma will be set to 1.0.

The image in the renderview contains gamma from color mapping. I will change the default settings for maya2016 so that by default in a new scene the gamma will be set to 1.0 what should be better because by default Mayas ColorManagement is turned on.

At the moment there is no way to save a raw - non color mapped image (except gamma). But it should be possible to implement it if needed.

Eian:
Oh I forgot to check the image output through the render settings and now that I did I see that it works just fine!

So the problem only occurs when saving through the renderview!
Though I wouldn't recommend you changing the default colormapping_gamma to 1.000 cause it will affect the quality of the rendered image which makes sense cause when a lower gamma is used the renderer will not refine the darkest areas. So when you apply the correct gamma of 2.2 you will get more noise in the darker areas.

As of now by turning off maya color management and saving through the render settings works fine.

Regards,
Ian

haggi:
Gamma does not affect the quality of the rendered image. I simply want to avoid double gamma in maya2016 what is the case if you use color management in maya what will be the default because is simply gives better results.

Eian:
Hey Haggi,

I understand you want to avoid double gamma correction and seemingly it comes to your preference what the default settings will be, they can be changed anyway.

Generally speaking, I won't post something before I test and as shown in the images attached, gamma setting (when chosen through the render settings) affects quality of the image, sometimes less sometimes more depending on the lighting.
V-ray has a setting for that as well, called "adaptation only" which allows the renderer to proceed with all its calculations as though color mapping is applied without applying color mapping so that the noise levels can be corrected accordingly.

In the images attached the one rendered with a gamma of 2.2 has less noise and was done in less time even though all the other settings were identical.
The image named "Gamma 1.0 to 2.2" is identical to the first one which was rendered with a gamma value of 1.0 and then corrected to 2.2 in post.
Difference might be small but is surely there.

Regards,
Ian

Navigation

[0] Message Index

[#] Next page