Algodoo

The motion blur doesn't appear to work correctly when the camera follows an object (unless I am misinterpreting it). For example, select a single box and enable "follow". Then, with the grab tool, fling the box across the bounded rectangular area. You will see that the blur does not act right unless the box hits a wall and starts to spin. If you do the same thing without the camera following the object, then it seems to blur the faster it moves.

Also, I did some playing around, attempting to duplicate the motion blur effect but with much simpler code. I came up with this:

edgeBlur = {
((vel(0) + vel(1)) ^ 2) ^ 0.5 / 30
}

I take the absolute value of the sum of the x and y velocities, and reduce it down to a useable edgeBlur value.

This is MUCH simpler than your incredibly complex function which does essentially the same thing. The only difference is the fact that my method does not blur with camera motion, but for most scenes, I suspect that's Okay. What do you think about my simple script as compared to your very complicated script? Simple is better, right?

Xray,

The way I see it, BeltedRose uses all sources that might cause blur, while you choose just one. Your incredibly complex function can be simplified to

edgeBlur = {math.vec.len(vel)/30.0}

I forgot to mention that blur artifacts do appear when simply enabling "follow" on an object. This is due to the delayed response of the camera for some reason. However, if you type in the objects postStep function "(e)=>{scene.camera.pan = e.this.pos}", you will not see that artifact, since the camera's position is updated much more frequently. Furthermore, to eliminate all blur from an object (and make yourself nauseous all the while), you can also add to the function "; scene.camera.rotation = -e.this.angle". I've tried it before and it worked.

s_noonan - Yes, that's a lot simpler than my code. It will save many hours of typing next time I need that function in a scene.

Thanks
.
.
.
.

(I'm being sarcastic. LOL)

BeltedRose85463 - I've discovered over the past few years that sometimes an Algodoo glitch or artifact can be cleared up in a number of ways. One is to run the code in UpDate instead of in PostStep, and another way is to adjust the sim frequency (usually to a higher value). It just takes some playing around sometimes.

This motion blur concept of yours is a good one, and as far as I know, no one else has done this before.

Good job!