Motion blur is entirely in the eye because you don't see in frames per second - your sight is a continuous, real time chemical reaction to the exposure to light. The less time an image is exposed to your eye, the less it persists in your vision. This is why CRTs have basically no "motion blur" relative to their FPS - they refresh in strobes, the actual image is only exposed to your eye for only a small amount of time (which is why they flicker and cause eye strain). It's like a prehistoric version of Lightboost/ULMB (Ultra Low Motion Blur).
When you have inadequate pixel response times, you get ghosting, an entirely different problem. You get the "ghost" of previous frames in the current frame because the pixels can't keep up with the color transition, and are continuously in the middle of transitioning by the time the next frame appears, causing trails of improperly transitioned colors to appear behind moving objects.
http://www.overclock.net/t/1430257/what ... r-monitors
When you have inadequate pixel response times, you get ghosting, an entirely different problem. You get the "ghost" of previous frames in the current frame because the pixels can't keep up with the color transition, and are continuously in the middle of transitioning by the time the next frame appears, causing trails of improperly transitioned colors to appear behind moving objects.
http://www.overclock.net/t/1430257/what ... r-monitors