Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - ringas

Pages: [1]
1
[Max] I need help! / Re: Z Depth Values / CoronaBackground
« on: 2015-06-26, 00:06:57 »
Thank you very much!!!

In case anyone is interested, to do the same thing in Nuke, one has to invert the zdepth so that white is far, then use a multiply(math) node to make the white correspond to the value in front of the camera and finally copy zdepth.red channel to depth.z for use use with a zdefocus. Not as accurate as with Vray but if it looks right...

Tassos Ringas

2
[Max] I need help! / Z Depth Values / CoronaBackground
« on: 2015-06-24, 22:42:37 »
Hi all,

I have been trying Corona and I have a little problem/question regarding the values in the zdepth Render Element:

Being used to the way Vray handles zdepth, I expected a zdepth in which values correspond to the distance in front of the camera (Nuke uses that and it's very intuitive and useful to know where an object is just by sampling the red channel of zdepth with a colour picker). To do that in Vray, I just put 1 in the max value and Vray enters a special mode outputting the distance value.

Now, in Corona, the values don't correspond to the distance, no matter if the clamp option is either ON or OFF, or I use the camera option. I was wondering if it's at all possible to force Corona to output distance values instead of float numbers. I could use some more involved ways to achieve that in Nuke but it would be much better to avoid that.

As a side note, would it also be possible to have a separate CoronaBackground Render Element, showing only the background with the rest being black?

Hope this makes sense,

Tassos Ringas

3
I am also using Nitrous, but in Realistic Mode with Scene Lighting and everything's black.

4
Thank you all for the replies!!!

Maru, this is exactly what I meant, but it's not really a problem as I am always grading in half-float in Nuke.

Coming from a photography and architecture background, what I have found during all these years of using advanced rendering programs is that they are so well designed that I can apply my old and trusted "Sunny 16" rule and I am always getting what I expect. It would be nice to be able to do the same thing in Corona sometime, I know we are half way there, as there is already an aperture setting used for DOF, so it now misses ISO and speed...

This is so exciting, reminds me of the thrill of the early Ghost days, when we used to shape what actually became Brazil!!!

Happy to be on board and kudos to you all :)

Tassos Ringas

5
Hi,

Are there any guidelines to setting those?

When using Vray, I had gone through a detailed metering procedure, using grey, non-reflective materials and setting the camera's ISO and speed so that the value of the rendered image at the brightest spot is similar to the value of the diffuse component of the material. Once I got close enough, I started using those values as a starting point for the cameras. I am pretty happy with the results and haven't changed anything for a couple of years.

Now, I think there isn't a specific Corona Camera, where I could do something similar (I wish that we have one someday).

I could just not mess with anything and do heavy post in Nuke using full float EXRs, but it would be nice to have a starting point.

Any thoughts?

Tassos Ringas

6
Hi,

I really like the Mask Render Element, it seems so much more powerful than Vray's Multimatte.

What would make it even better is to be able to assign an arbitrary MatID override per material. That way we can use more than 15 MatIDs (Max's default number).

Tassos Ringas

7
[Max] Resolved Bugs / Render Elements bugs
« on: 2013-03-20, 13:41:35 »
Hi,

It seems that in the autosave files these two bugs pop up:

The Corona_Alpha Render Element gets renamed to "other" in Nuke.

Also, the two Zdepth elements are not saved in the exr.

When saving using normal 3dsmax dialog all is fine

Tassos Ringas

8
[Max] Resolved Feature Requests / Autosave Padding
« on: 2013-03-20, 13:11:39 »
Hi,

It would be nice to have a padding setting and a start value for the autosave feature, the way it is set at the moment makes it difficult to import into programs such as Nuke which start with a frame value of 1.

Thanks in advance,

Tassos Ringas

9
Thanks for the reply,

It seems it is a bug with alpha 4, it was fine with alpha 3

Tassos Ringas

10
Hello everyone,

This is my first post here, so I would like to first say "WOW!!!!!!!". This is one damn fine renderer!!!

I started using it yesterday and I came upon a very annoying bug:

When the daylight system is set to CoronaSun (or with a plain CoronaSun) is set to "From Sky" the viewports are practically non-usable, they crawl to a halt. Using "Direct Input" or "Kelvin Temp" makes this go away.

I am using Corona Alpha v4, in Max 2012 64bit, Win7 64bit with 16GB RAM, Nvidia 670.

I hope this makes sense,

Tassos Ringas

PS. BTW, why can't I access daily builds?

Pages: [1]