this post was submitted on 10 Mar 2025
746 points (97.5% liked)
Greentext
5764 readers
2042 users here now
This is a place to share greentexts and witness the confounding life of Anon. If you're new to the Greentext community, think of it as a sort of zoo with Anon as the main attraction.
Be warned:
- Anon is often crazy.
- Anon is often depressed.
- Anon frequently shares thoughts that are immature, offensive, or incomprehensible.
If you find yourself getting angry (or god forbid, agreeing) with something Anon has said, you might be doing it wrong.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Maybe I'm misunderstanding you but isn't that screen tearing?
I mean just from persistence of vision you'll see multiple copies of a moving object if your eyes aren't moving. I have realized tho that in the main racing game I use motion blur in (beamng) I'm not actually reaching above 80fps very often.
here, I copied someone's shader to make a quick comparison:
with blur: https://www.shadertoy.com/view/wcjSzV
without blur: https://www.shadertoy.com/view/wf2XRV
Even at 144hz, one looks smooth while the other has sharp edges along the path.
Keep in mind that this technically only works if your eye doesn't follow any of the circles, as that would require a different motion blur computation. That's obviously not something that can be accounted for on a flatscreen, maybe in VR at some point though if we ever get to that level of sophistication. VR motion blur without taking eye movement into account is obviously terrible and makes everyone sick.
Someone else made a comparison for that, where you're supposed to follow the red dot with your eye. (keep in mind that this demo uses motion blur lengths longer than a frame, which you would not have if aiming for a human eye-like realistic look)
https://www.shadertoy.com/view/7tdyW8
Okay now I got it from your explanation, thanks!
By the way, the first two Shadertoys aren't working for me, I just get “:-( We either didn't find the page you were looking for, or there was an internal error.”. The third one works, though...
Oh I guess I set it to private instead of unlisted on accident. It should be fixed now.