MIMO helps here to separate the spectrum use by targeted physical location, but it's not perfect by any means.
The Frame itself here is a good example actually - using 6GHz for video streaming and 5GHz for wifi, on separate radios.
My main issue with the Quest in practice was that when I started moving my head quickly (which happens when playing faster-paced games) I would get lag spikes. I did some tuning on the bitrate / beam-forming / router positioning to get to an acceptable place, but I expect / hope that here the foveated streaming will solve these issues easily.
Now I also wonder if an ML model could also work to help predict fovea location based on screen content and recent eye trackng data. If the eyes are reading a paragraph, you have a pretty good idea where they're going to go next for instance. That way a latency spike that delays eye tracking updates can be hidden too.
We’ll see in practice - so far all hands-on reviewers said the foveated rendering worked great, with one trying to break it (move eyes quickly left right up down from edge to edge) and not being able to - the foveated rendering always being faster.
I agree latency spikes would be really annoying if they end up being like you suggest.
What do you do when another device on the main wifi network decides to eat 50ms of time in the channel you use for the eye tracking data return path?
So again, you just make sure the 6GHz band in the room is dedicated to the Frame and its dongle.
The 5GHz is for WiFi.
My guess based on that is you likely dont need to totally clear 6GHz in the room the Frame is in, but rather just make sure its relatively clear.
We’ll know more once it ships and we can see people try it out and try and abuse the radio a bit.