frankmci wrote:I'm guessing it's because units of time are an artificial, arbitrary human concept, but most software does not treat it as such. For most render engines, exposure wise, there is no such thing as a unit of time that truly lasts more than one frame. I think to get the effect you want you will need to not just increase exposure, but reduce the number of frames per second, too. If you want a 0.25 second exposure, you will need to render your animation at no more than 4 fps.
Ok, I think it's a lead I haven't explored yet. I need to see what I can do with this information and if it helps. Thank you for the suggestion anyway.
skientia wrote:There is only a thin correlation between a real photography and a renderer. The concept of exposure differs between the two — exposure time is non-existent in a renderer, "exposure" is arbitrary.
I understand that but renderers like Arnold and Redshift, for example, are following the photography conventions pretty well in language and effects, mimicking the behavior of real photography really well. Octane is pretty good at this too, except this particular case which I can't crack yet.
skientia wrote:One way to yield this result in a physically plausible manner is by accurately (enough) animating the object and/or camera and facultatively via a double exposure method, akin to real photography, for more control. The emphasis is on the animation being the most challenging and fundamental part (the accumulations of all the imperfect movements, shaking, twisting).
I'm not familiar how to do the double exposure technique with Octane. Where can I learn more about it?