3 ms·
Mind blown. Indeed: - when I move my head to (+30, +45), my brain reports viewport.LeftTop =(0,0), and, - when I move my eyes to (+30, +15), my brain reports
by numpad0 4y ago
Mind blown. Indeed:
- when I move my head to (+30, +45), my brain reports viewport.LeftTop =(0,0), and,
- when I move my eyes to (+30, +15), my brain reports viewport.LeftTop = (30, -15).
But our eyes are built in such way that the whole lens and sensor assembly rotates, rather than having sensor fixed to the head and lens rotating, so it makes no sense. Framebuffer should always span from (0,0) to (size.x, size.y).
Perhaps the framebuffer always covers the full viewing range, and DMA start addresses are dynamically determined by current eye positions, or perhaps even by feature matching?
- MereInterest 4y agoIt gets even weirder when you consider blind spots. The hardware has a pretty big design flaw, that the signal wires are routed in front of the active sensors instead of behind. As a result, there's a big bundle that needs to pass through the sensor array, resulting in a blind spot. This is fixed in software, by interpolating nearby inputs before presenting it to the user (i.e. your conscious mind). Saccades also present a hardware limitation. During rapid movements, the eye can't focus correctly. To improve the overall UX, we throw away those frames entirely, reconstruct them with a linear interpolation of the next few frames, and call it a day. It does introduce some lag, but the user-level process is usually lagging behind anyways, and doesn't notice the input lag so long as we backdate the timestamps.
- Someone 4y ago> To improve the overall UX, we throw away those frames entirely, reconstruct them with a linear interpolation of the next few frames Do we know that interpolation is linear? If so, in what coordinate system? Head? Single eye? One including gaze direction? One including what one is attending to (whatever that is)? I find it hard to believe it would be linear. Wouldn’t that mean that it would seem a rolling ball stops rolling during saccades? I wonder what kind of experiment could be used to research that.
- yojo 4y agoThe time stamp thing is especially crazy, and you can see it break down if you saccade to a ticking clock. This twitter thread made the rounds a while back, which lays it out in a nice incredulous rant: https://mobile.twitter.com/foone/status/1014267515696922624 https://mobile.twitter.com/foone/status/1014267515696922624
- psd1 4y agoThe hardware is designed completely iteratively, so it's - predictably - a mass of ossified hacks. The product team has no strategic vision: it's generally conservative, but sometimes a completely random idea gets into production. They do A/B testing but completely half-ass it, often they never deprecate the old version, and deciphering serial numbers requires a degree in microbiology. You'd think the environment would be perfect for disruption, but this actually is the new arrival and it's repeating all the mistakes of the incumbents! How the fuck this scales to billions I have no idea. The sysads must be getting overtime.
- lagrange77 4y agoRight. And after the CEO exit scammed without any documentation, we can't even ditch the whole codebase and rewrite it from scratch, as would be mandatory.
- psd1 4y agoThe hardware is designed completely iteratively, so it's - predictably - a mass of ossified hacks. The product team has no strategic vision: it's generally conservative, but sometimes a completely random idea gets into production. They do A/B testing but completely half-ass it, often they never deprecate the old version, and deciphering serial numbers requires a degree in microbiology. You'd think the environment would be perfect for disruption, but this actually is the new arrival and it's repeating all the mistakes of the incumbents! How the fuck this scales to billions I have no idea. The sysads must be getting overtime.