|
|
|
|
|
|
by joshstrange
871 days ago
|
|
|
After writing this I went to write a tiny new feature for my side project on the AVP. At first I couldn't get my AVP to connect to my MBP and I thought it might be because it was in clamshell mode. I opened up setting and clicked around a bit then it showed up on my AVP to connect to (I went to Control Center and clicked the button to connect to a MBP, it didn't prompt me. It did prompt me the other day when I had the laptop open). I started to write the feature but could feel the added friction and slowness. There was a little bit of input lag (moving mouse and feel like it wasn't moving as quick on the AVP), then I started getting an error from my backend in a place I hadn't touched anything. I very quickly took off the AVP to investigate with the "full power" of my MBP and external monitors. The text in the AVP is clear when you are looking at your code but moving your head "smears" the picture a bit and anything you aren't focusing on isn't clear. It would be workable and maybe I'd use it on a plane but never if I have my monitors available to me. I want to try again in the next few days but it's a decent way off from replacing my monitors. |
|
|
With regards the ‘smearing’, not sure how familiar you are with VR tech but, could you characterise it further?
Some things it may be off the top of my head:
Is it the display not switching pixel state fast enough? This was a problem with early Oculus headsets until we figured out how to strobe displays for ‘low persistence’.
Or, is it eye tracking lag, resulting in the foveated rendering not keeping up with where you are looking quickly enough? Human eyes can move extremely quickly from point-to-point (called saccades).
Be great to get your thoughts on the possible cause / tech limitations.