I just attempted to do this with a script that moves the camera up and down .015 units every update to try and replicate this. But this doesn’t work because the perspective on the camera makes the movement too much up close and too little in the distance. If the camera were orthographic this could work however.
But I imagine this really needs to be done in shaderLab, and on the GPU. Is there anyway to move the actual rendered frame buffer up and to the side 1 pixel, then back, every frame?
This AA method is probably only possible on the PSP or a device that you know has a specific pixel response time or pixel ghosting. On a super fast LCD display it’s most likely just going to look like the screen is vibrating.
Wow, how times change, or not… We all moved from interlaced/fields screens to progressive scan monitors and TV’s, people forget interlace, then it’s “discovered” years later.
Anyone know the response time of the iPhone and the iPod touch? Also, would AA even be necessary on retina devices (several people say yes, others say no, and I want a definite answer on that.)
I can pretty clearly see the pixels on a retina display if there’s no AA. Although it’s much less of a big deal compared to the older displays, so it probably depends on what sort of graphics you’re using (solid colors with lots of hard edges for example).