Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Does anyone else find native apps are much crisper to look at than the MacBook mirrored display. I work in text heavy apps and find the mirrored display to be average at best with heavy text. Native apps are clear and sharp.
yeah, this is certainly the case. unfortunate as I use mine for programming, but now with mouse support in visionOS it's possible that I can use something like blink.sh and a GitHub code space to do this on the device.
 
  • Like
Reactions: Mitch_T
You email them for a quote and a custom order link.

They do warn that eye tracking might not function optimally due to the prism, but for me it functions better than without the prism.
Extremely interesting, and thank you for the link. I'd searched for 3rd party lenses in the past, and tried again just now, and didn't get a single result, even indirectly--the closest was a Reddit thread that still had nothing.

I'll definitely be looking into that. It's also good to hear that the tracking seems to work fine (honestly I don't see why it wouldn't--once it gets calibrated, it should matter where your eyes are pointed relative to the screens as long as they're always pointed to the same place, which they should be.

What actually worries me about lenses that the Vision Pro doesn't know you're using (those, that is), comes from Footone 3 in John Gruber's review. He initially used the Vision Pro with the right optical inserts, but the wrong QR code, so the Vision Pro thought he was wearing different inserts. This threw off tracking a bit, which is understandable, but it also might have caused him a headache and motion sickness. I can think of a few reasons this might be, but one obvious reason is that the headset puts more detail in the rendering at the center of your view, so if there's a slight offset I could see that screwing things up in ways your brain's motion processing doesn't like.

It would be one thing for the Vision Pro to not know about your prism, but another entirely for it to not even know you've got inserts at all.

I'm already slightly prone to motion sickness with VR headsets, so with the huge price tag I'm not sure I want to risk that, even more so since my primary interest in buying a Vision Pro is to use it as "the tech guy" to explore how useful the technology really is, so I don't particularly want to hamstring it out of the gate.

If that company somehow provided some means of getting a QR code to use to tell the OS what the equivalent Zeiss inserts are so it can correct, then at least it would only be the prism that's the problem, but as-is it'd be prism, myopia, and astigmatism it'd have no idea about.
 
Last edited:
Extremely interesting, and thank you for the link. I'd searched for 3rd party lenses in the past, and tried again just now, and didn't get a single result, even indirectly--the closest was a Reddit thread that still had nothing.

I'll definitely be looking into that. It's also good to hear that the tracking seems to work fine (honestly I don't see why it wouldn't--once it gets calibrated, it should matter where your eyes are pointed relative to the screens as long as they're always pointed to the same place, which they should be.

What actually worries me about lenses that the Vision Pro doesn't know you're using (those, that is), comes from Footone 3 in John Gruber's review. He initially used the Vision Pro with the right optical inserts, but the wrong QR code, so the Vision Pro thought he was wearing different inserts. This threw off tracking a bit, which is understandable, but it also might have caused him a headache and motion sickness. I can think of a few reasons this might be, but one obvious reason is that the headset puts more detail in the rendering at the center of your view, so if there's a slight offset I could see that screwing things up in ways your brain's motion processing doesn't like.

It would be one thing for the Vision Pro to not know about your prism, but another entirely for it to not even know you've got inserts at all.

I'm already slightly prone to motion sickness with VR headsets, so with the huge price tag I'm not sure I want to risk that, even more so since my primary interest in buying a Vision Pro is to use it as "the tech guy" to explore how useful the technology really is, so I don't particularly want to hamstring it out of the gate.

If that company somehow provided some means of getting a QR code to use to tell the OS what the equivalent Zeiss inserts are so it can correct, then at least it would only be the prism that's the problem, but as-is it'd be prism, myopia, and astigmatism it'd have no idea about.
Regarding the prescription lenses, as Zeiss seems to be picky about astigmatism and other details. I am with contact lenses for now, but tested small old prescription glasses I still have and just wore them within the Vision pro. It did not even remark my glasses - clear vision. Conclusion: You might be able to insert the third party lenses without QR code, just not telling the AVP about it...
 
Regarding the prescription lenses, as Zeiss seems to be picky about astigmatism and other details. I am with contact lenses for now, but tested small old prescription glasses I still have and just wore them within the Vision pro. It did not even remark my glasses - clear vision. Conclusion: You might be able to insert the third party lenses without QR code, just not telling the AVP about it...
I might not have been clear about my concern--you can definitely do exactly that (stick the 3rd party lenses in with no QR code), as that's exactly what the company explicitly says you have to since they don't have a way to generate the QR codes.

My worry is the other way around--visionOS is definitely doing something with the information about the prescription installed, so having inserts that it doesn't know about (or doesn't know accurately what the actual prescription is) is going to throw something subtly off. The only question is just how badly.

Knowing the name of this company I was able to dig up a couple of Reddit threads with some experiences with the product. Some (not all) people reported what sounded like rather annoying behavior--repeated prompts to redo setup, Optic ID not working, eye tracking straight-up not working, or intermittent glitches with the center-of-vision rendering.

Some of these would be tolerable, but spending $4K for a head-mounted computer in which the optical tracking doesn't work right is not something I'm excited about doing, particularly since I've read at least one report of inaccurate prescription detection causing headaches and nausea, both of which I'm already somewhat prone to.

Since there's no practical way to test, and even if I could return the Vision Pro if it was wonky, I couldn't return the optical inserts, it's well out of the "eh, let's try it and see how it goes" range for my wallet.

I will add, the non-prism part of my prescription isn't that strong and well within the range of what Zeiss will make, and even the prism is fairly mild, and it's possible that some of the problems people reported with the HonsVR inserts were due to having very strong prescriptions beyond what Zeiss will make.
 
yeah, this is certainly the case. unfortunate as I use mine for programming, but now with mouse support in visionOS it's possible that I can use something like blink.sh and a GitHub code space to do this on the device.
Hoping this is corrected in future updates, it’s the only disappointing thing about the Vision Pro. Sometimes I seem to be able to get it at an acceptable level other times it’s a real strain on the eyes. The mouse support in OS2 is amazing.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.