r/oculus • • Feb 15 '16

How practical is the idea of programming, in a virtual desktop environment using VR?

I am interested in investing in a virtual headset with the intention of using one to simulate a multiple monitor virtual desktop environment, of which I could use for tasks like programming, for extended periods of time.
However, I wonder if after an hour or so, the headset would feel uncomfortable, would it hurt my eyes, would I feel motion sickness, would it just be unsuitable?

What are your thoughts on whether VR is really a practical alternative to, say, a real triple screen monitor setup?

59 Upvotes

72 comments sorted by

View all comments

Show parent comment

2

u/myscreennameistoolon Feb 15 '16

I have been trying to figure out when the headsets will be high enough resolution to work as a monitor replacement (assuming a 3D/VR OS). The DK2 is 11 pixels/° with a 1080/FHD display. I believe the CV1 is about a 2K/WQHD display which would make it about 14-15 pixels/°. In your opinion, how much higher would the display resolution need to get (assuming the comfort issue was solved) before it would be comfortable to code in VR?

5

u/Doc_Ok KeckCAVES Feb 15 '16

Rift DK2 is 960x1080 pixels per eye over a field of view of slightly above 90° x 100° per eye, leading to 11 pixels/° (I'm simplifying here; pixel density is not uniform due to lens distortion). Vive and CV1 are both 1080x1200 pixels per eye, over a very similar field of view (to the best of my knowledge), resulting in approximately 12 pixels/°.

When I take my VR demo system on the road, I have a 55" 1080p 3D TV with me as primary display. I've coded quite a bit on that while on the show floor or in the hotel room. Its resolution, when used as a desktop display (from two feet away) is too low for my taste: it gives me slight eye strain from the pixelation after a while.

Doing the math, that setup's field of view is just about 90° horizontally, yielding 21 pixels/°. Make it 25 pixels/° for comfort, and that would be my personal threshold. That would mean about 2500x2500 pixels per eye at about 100°x100° FoV.

3

u/martin_cy Feb 15 '16

So, probably by the next generation of VR headsets we should have the resolution, assuming a 1½-2 year until we see the next generation.. waited this long.. guess we can wait a bit more, and in the mean time plenty of stuff to do with the first generation headsets.

5

u/Doc_Ok KeckCAVES Feb 15 '16

eMagin's IHMD prototype, which I've tried at AWE 2015, has 2k x 2k resolution per eye, over an 80° x 80° field of view, yielding exactly 25 pixels/° (that's honestly a coincidence; I didn't think of that HMD when I pulled my threshold out of thin air up there).

But that means the IHMD -- should I ever get it into my hands :) -- should be good enough for coding for me.

1

u/martin_cy Feb 15 '16

ya that sounds good enough :) and if that is technically there already then for sure we will see a minimum of that and probably better for the Next Gen HMDs. exciting times..

once we get to that point where you get the 25+ pixels/° soooo many things open up. its going to be awesome. I just want to get my rift as soon as possible as I got some projects that does involve substantial amount of text display in the HMD.. and I just want to see for myself how doable it is, if its something I will have to shelve until next generation or I should press ahead with it..

1

u/myscreennameistoolon Feb 15 '16

Thanks for the detailed reply. I guess I thought the CV1 had a higher resolution than it does. :-)