[Manuel_D]

I'm told by co-workers that the way to use VR headsets for coding is to make the text size large, but to create multiple large text panels. With VR, you essentially have low resolution virtual "monitors" but they're very large and you can have 6+ of them open at a time.

Personally, it still makes me sick when I try to use it for that.

[crooked-v]

"Large" is underselling it. Even with the AVP, about 1.5x real size is the bare minimum for me for text reading comfort, and with other headsets it's more like 2x or larger. It very rapidly gets into territory where you'll give yourself neck strain trying to keep track of everything.

[Andys]

How is it low res when the specs say 5120 × 2560?

[Manuel_D]

Because the text isn't displaying directly on the headset screen. It's being displayed as a 3d pane within the virtual desktop: https://roadtovrlive-5ea0.kxcdn.com/wp-content/uploads/2016/...

So the actual number of pixels used to display the pane containing your text is maybe 10-20% of the headset display's resolution.

I suppose you could display text directly on the headset display. But then you only have 2,560x2,560 pixels per eye, fewer pixels than a 4k display.

[two_handfuls]

Parent was talking about screen density, so pixels per degree. This headset ~~has more pixels~~ but also a wider fov, so it should feel similar.

Edit: fell for their lies, the headset is only 2k per eye. The 5k figure is "combined", i.e. a marketing number.

I'm with you though: early headsets were low resolution but these modern ones are not. We can still use more pixels though, esp. for text work.