- Tue Apr 10, 2012 2:58 am
#354669
Doing so would not somehow automatically introduce motion blur -- for that, the camera needs to be written (remember that all other factors aside, rendering always takes place within the context of a single MXS file) with two or more physical positions; the engine then interpolates between those to produce blur. The implication, then, would be that you would need to go through all the cameras, record their positions in a list, then go through the list again, where for each camera, you write an MXS which has a camera built using the position of that camera, and the positions of cameras (depending on where and how long the blur is supposed to be) preceding and following it. I'm not sure whether you can do this with a script or not, but you could do it with python.
Next Limit Team