ricardo wrote:This is much what I figured out so far:
The MXI file keeps for each pixel an equation like this:
f(L0) + f1(L1) + f2(L2)...
.....
The pros:
...
The number crunching depends on the number of lighs involved...
...this assumption would be true only if the calculation actually starts at the lights. I take an educated guess though that the calcualtion starts at the camera, so in the end it does *not* depend on the number of lights. Lights are just stop surfaces with a spectral color so to speak. My gues is that they simply store a spectral value with high dynamic for each pixel, not some magic f(L1)
The cons:
F/stop: changing f/stop won't result in DOF changes. Better disable it.
Shutter speed: If motion blur is involved, changing it will not result in changing blur, just quit on that one also.
I have asked the same thing, however there actually *is* even a real life technic that captures and stores an image in a way which allows to set the focus
afterwards - if they would have something like this, it would be absolutely mindblowing. I don't know a solution for the motion blur problem.
I wouldn't call the absence of this feature not exactly a "con" though
Kabe
Maxwell Render Calculator 0.9.8 -
http://www.klausbusse.de/mxc/
MXM Checker 0.9.0 -
http://www.klausbusse.de/mxmchecker/
Cinema 4D R11, 2x2.66, 4 GB RAM