News for hackers. Stuff that matters.
Re:Coding in Vision Pro by larrysalibra on Friday February 16, 2024 @06:15PM (#39404317)
It ranges from okay to not that bad. It’s not as good as the “retina” screens in Apple’s other products.

I can definitely see pixels on the device if I’m wearing contacts unlike what most of the early reviewers claimed.

But it’s not so bad as to be unusable and you don’t really notice them in most contexts - the main place I notice pixels is using it as a screen for macOS. VisionOS apps are rendered very large by default so the resolution deficiencies aren’t as apparent.

Overall it is very impressive but there’s also much room for improvement in resolution.

Re:Coding in Vision Pro by drcode on Friday February 16, 2024 @07:29PM (#39404911)
I don't know, if I need to use my macOS laptop, it sounds a lot easier to just use my laptop, instead of using a helmet and then doing the connection dance to get a single ok-ish screen anyway
Re:Coding in Vision Pro by veec_cas_tant on Friday February 16, 2024 @10:50PM (#39406194)
A single screen that is much larger than a MacBook screen, that is the advantage. And the connection dance is really just...tapping the connect button?
Re:Coding in Vision Pro by kllrnohj on Saturday February 17, 2024 @09:48AM (#39409869)
But with the same "resolution" such that you can't fit any more content on it and with much worse density.

Why would I actually want that? You've been able to do this for decades by hooking a TV up to your laptop and while that certainly has space challenges that limit the number of people that'll try it, it's not like tech bloggers were flocking to hook up 65" TVs to their macs and lovingly wax poetic about the productivity gains, either.

Re:Coding in Vision Pro by ninkendo on Saturday February 17, 2024 @10:31AM (#39410341)
The virtual resolution is adjustable and you can fit a lot more contents on the screen than you can with a real monitor. It basically allows one more setting past the maximum “more space” mode you normally get from macOS. It does render a little bit blurry, though, if you crank up the virtual resolution to the max.
Re:Coding in Vision Pro by bed99 on Friday February 16, 2024 @06:36PM (#39404495)
I don't think it is possible to see the pixels, they are the size of a red blood cell. But maybe you can see antialiasing or noise from the cameras.

Personally I can't see any pixelation. It's even better than reality. That being said passthrough cameras' resolution do suck but it's not what it's important and probably the easiest problem to solve.

Re:Coding in Vision Pro by hatsix on Friday February 16, 2024 @11:29PM (#39406366)
sure, they're small, but some of them are closer to your eye lense than your retina. The pixels per degree are lower than any Apple product in the past 10 years
Re:Coding in Vision Pro by ribosometronome on Friday February 16, 2024 @06:28PM (#39404424)
For non-text content, I think it's pretty good, actually. Watching content in Disney+ or Max's theater modes is really satisfying despite those virtual screens being sub-4k.
Re:Coding in Vision Pro by euroderf on Friday February 16, 2024 @06:38PM (#39404514)
Now there is a topic. How does it work with contacts ?

Does it obviate the need for the 149$ Zeiss add-ons ?

Do you blink enough in the environment ?

Re:Coding in Vision Pro by robterrell on Friday February 16, 2024 @06:51PM (#39404621)
I have been using contacts and just got the zeiss lenses today. So far it's roughly equivalent. I think there is a touch more distortion (chromatic aberration along the edges) with the inserts. But my contacts are progressives and kinda sucked for this, single vision would probably be great.
Re:Coding in Vision Pro by astrange on Friday February 16, 2024 @11:47PM (#39406461)
The purchase path in the online store will ask what kind of contacts you have, and if they're compatible will recommend using them instead of inserts.

The main advantage is that it's less crowded in there, I suppose.

Re:Coding in Vision Pro by euroderf on Saturday February 17, 2024 @09:35AM (#39409750)
I wonder what are the criteria for compatibility...