if you have the new rendern monkey 1.62 then you can get the motionblur from it
you must export it almost to a fx file.

eh, not sure about this. It will, like anything else, only work for models. Being said, rotating the view quickly would not blut the object if it were still. This soley depends on the objects velocity.

As said, it might not work well for complex models, but reading through the shader, since it stretches by the surface normal, it might actually be fine with complex models...

i think it would be best for object-based motion blur though. you couldn't use that example for motion-blur of animated models because polygons are definitely going to intersect with each other a lot, particularly with complex hands, fingers, etc.

on second thought, the blurring would make the intersections a non-issue. i was thinking about it at school, and thinking that a closed fist has normals in lots of different directions, pointing towards and away from each other. very fast-moving fists would have a lot of intersecting polygons, but it shouldn't look too bad if everything is blurred and smoothed.

it would work with rotating models of the relative velocity was vertex-based, not object-based (which would be required anyway for blurring animations). each entity could remember their own camera-relative vertex positions in an array (may be easier with lite-c if you have global structs that point to an entity and contain an int[array] with relative camera positions for each frame).

i haven't learned how to pass extra info (such as an array) to a shader yet (i'm very fresh at this), but i will in a sec after i do some experiments for a school project.

julz

NVidia uses a very similar method as what I did, but they used 16 frames instead of 4. 3DGS materials are limited to 4 textures though, so without a DLL, no luck

They also used a different mixing method (which I will look into) that adds a sort-of "bloom" effect to it, which in turn, blurs the image for better mixing. I'll have to give this a try...