Chaos Corona for 3ds Max > [Max] Daily Builds
Corona Image Editor feedback
mike288:
1) Yes, it is a bug we know about. It will be fixed in 1.6.
2) OK, I will look into it ASAP. Thank you.
Ryuu:
Small/heavy scene kinda doesn't matter since this tool works only on the rendered images :)
--- Quote from: PROH on 2017-03-27, 21:44:25 ---No problems so far, except from a little brain-work figuring out how to use it correct (a basic guide would be great).
--- End quote ---
Some guides/tutorials are definitely planned. You can help us by pointing out the things that are less than obvious. That way we'll know what needs better explanation and/or redesign of the UI.
Flavius:
Hi all,
I've been waiting for this since you guys have announced it! This thing is just great, and will smooth out the workflow very nicely.
What I would really really love to have is
- F-stop parameters which should work in conjunction with Bloom and Glare aaaaaaaaand :
!!! Depth of field! But if possible, I have no clue if it is, without using a Zdepth pass, but something like World Position ? would that be possible?
antanas:
Nice thing for post render lighmix tweaking for sure, now make it exportable to a self sufficient .exe gallery kind of file (like say ACDsee has) which could be sent to clients with a possibility to set some easy to set and to use buttons to specific light mix pass combos which when sent to clients those stupid monkeys could press and get different lighting and even time of the day and well, picture me VERY interested )))
@Flavius - yeah something like vfb+ or lenscare does with the help of zdepth pass but why use the "outdated crap" for that - maybe using Word position pass for that would make it possible to get blurring behind the transparent objects which makes zdepth pass based dof completely useless in such cases.
About F-stop well totally agree on that too - F-stop + aperture (I mean shape\amount of blades etc) both incamera one and in vfb\image editor one would be very handy to control both the post processing dof (if it will ever be added) and especially glare and bloom both power and shape of em.
DELETED - my overwork induced F-stop related ramble ))
romullus:
I hate to go to offtopic, but...
--- Quote from: antanas on 2017-03-28, 21:56:27 ---About F-stop well totally agree on that too but first we need to have decent working like it should F-stop in Corona itself which would behave as F-stop should - by that I mean "darkening the image" or changing the amount of light coming through it in the lenses well doing things like the real one does - for now it is only useful for rendertime dof setup and motion blur but besides that nothing else - currently it is impossible to set up cameras to match the real world camera's values without it - c'mon guys even vray respects F-stop values in it's physical camera so how comes Corona still doesn't ? And yeah F-stop + aperture (I mean shape\amount of blades etc) both incamera one and in vfb\image editor one would be very handy to control both the post processing dof (if it will ever be added) and especially glare and bloom both power and shape of em.
One thing to add to that - Ev and iso values ABSOLUTELY should work together not separately - it doesn't make any sense like it is done now.
--- End quote ---
everything you said here does not make any sense to me. F-Stop is working like it should, by changing it, you change exposure as well.
And when simple exposure (EV) is active, ISO ABSOLUTELY shouldn't affect exposure. I don't see nothing wrong with Corona's exposure control implementation, well.. except confusing controls in multiple places, but that is well known issue.
P.S. if you want to go in further discussion about Corona's exposure controls, please start new topic in general discussions board. Let's leave this topic for feedback about CIE.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version