Random Thoughts – Randocity!

Is Apple’s Vision Pro worth the money?

Posted in Apple, botch, business, computers by commorancy on February 2, 2024

VisionProGogglesLet me preface this article by saying that this is not intended review the Apple Vision pro. Instead, it is intended as an analysis of Apple’s technology and the design behind the Apple Vision Pro headset. The Vision Pro’s hefty price tag also begins at $3500 and goes up from there depending on selected features. Let’s explore.

Price Tag vs Danger Target

The first elephant in the room to address with this Virtual Reality (VR) headset is its price tag. Because there is presently only one model of this headset, anyone who sees you wearing it knows the value of this headset instantly. This means that if you’re seen out and about in public wearing one, you’ve made yourself a target not simply for theft, but for a possible outright mugging. Thieves are emboldened when they know you’re wearing a $3500 device on your person. Because the Vision Pro is a relatively portable device, it would be easy to scoop up the entire device and all of its accessories in just a few seconds and walk off with it.

Like wearing an expensive diamond necklace or a Rolex watch, these items flaunt wealth. Likewise, so does the Vision Pro. It says that you have disposable income and wouldn’t really mind the loss of your $3500 device. While that previous statement might not be exactly true, it does have grains of truth in it. If you’re so wealthy that you can plop down $3500 for a Vision Pro, you can likely afford to buy another one should it go missing.

However, if you’re considering investing in a Vision Pro VR headset, you’d do well to also invest in a quality insurance policy that covers both loss from theft and damage both intentional and accidental. Unfortunately, a loss policy won’t cover any injuries you might sustain from a mugging. Be careful and remain alert when wearing a Vision Pro in public spaces.

The better choice is not wear the headset in public spaces at all. Don’t use it on trains, in planes, at Starbucks, sitting in the lobby of airports or even in hotel lobbies. For maximum safety, use the Vision Pro device in the privacy and safety of your hotel room OR in the privacy and safety of your own home. Should you don this headset on public transportation to and from work, expect to get not only looks from people around you, expect to attract thieves looking to take it from you, potentially forcibly. With that safety tip out of the way, let’s dive into the design of this VR headset.

What exactly is a VR headset useful for?

While Apple is attempting to redefine what a VR headset is, they’re not really doing a very good job at it, especially for the Vision Pro’s costly price tag. To answer the question that heads up this section, the answer is very simple.

A VR headset is simply a strap on 3D display. That’s it. That’s what it is. That’s how it works. Keep reading much further down for the best use cases of 3D stereoscopic displays. The resolution of the display, the eye tracking, the face tracking, the augmented reality features, these are all bells and whistles that roll out along side of the headset and somewhat drive the price tag. The reality is as stated, a VR headset is simply a strap on video display, like your TV or a computer monitor. The only difference between a TV screen or monitor is that a VR headset offers 3D stereoscopic visuals. Because of the way the lenses are designed on VR headset, the headset can use its each-eye-separate-display feature to project flat screens that appear to float convincingly both at a distance and at a scale that appears realistically large, some even immensely large like an IMAX screen in scale.

These VR flat screens float in the vision like a floating displays featured in many futuristic movies. However, a VR headset is likewise a personal, private experience. Only the wearer can partake in the visuals in the display. Everyone else around you has no idea what you’re seeing, doing or experiencing…. except they will know when using the Vision Pro because of one glaring design flaw involving the audio system (more on this below). Let’s simply keep in mind that all that a VR headset boils down to is a set of goggles containing two built-in displays, one for each eye; displays which produce a stereoscopic image. Think of any VR headset as the technological equivalent of a View Master, that old 1970s toy with paper image discs (reels) and a pull down lever to switches images.

How the video information is fed to those displays is entirely up to each VR headset device.

Feeding the Vision Pro

For the Vision Pro, this device is really no different than any of a myriad of other VR headsets on the market. Apple wants you to think that theirs is “the best” because Apple’s Vision Pro is “brand new” and simply because it’s brand new, this should convince you that it is somehow different. In reality, the Vision Pro doesn’t really stand out. Oh sure, it utilizes some newer features, such as better eye tracking and easier hand gestures, but that’s interface semantics. We’ll get into the hand gesture problems below. For the Vision Pro’s uses, getting easy access to visual data from the Vision Pro is made as simple as owning an iPad. This ease is to the credit of Apple, but this ease also exists because the iPad already exists allowing that iPad ease to be slipped into and then leveraged and utilized by the Vision Pro.

In reality, the Vision Pro OS might as well be an iPad attached to a strap-on headset. That’s really how the Vision Pro has been designed. The interface on the iPad is already touch capable, so it makes perfect sense to take the iPadOS and extract and expand it into what drives the Vision Pro, except using the aforementioned eye tracking, cameras and pinch gesture.

The reason the Vision Pro is capable of all of this is because they’ve effectively married the technology guts of an iPad into the chassis of the Vision Pro. This means that unlike many VR headsets which are dumb displays with very little processing power internally, the Vision Pro crams a whole iPad computer inside of the Vision Pro headset chassis.

That design choice is both good and bad. Let’s start with the good. Because the display is driven by an M2 chip motherboard design, like an iPhone or iPad, it has well enough power to do what’s needed to drive the Vision Pro with a fast refresh rate and with a responsive interface. This means a decent, friendly, familiar and easy to use interface. If you’re familiar with how to use an iPad or an iPhone, then you can drop right into the Vision Pro with little to no learning curve. This is what Apple is banking on, literally. The fact that because it’s so similar to their already existing devices makes it simple to strap one on and be up and running in just a few minutes.

Let’s move onto the bad. Because the processor system is built directly into the headset, that means it will become obsolete the following year of its release. As soon as Apple releases its next M2 chip, the Vision Pro will be obsolete. This is big problem. Expecting people to drop $3500 every 12 months is insane. It’s bad enough with an iPhone that costs $800, but for a device that costs $3500? Yeah, that’s a big no go.

iPhone and Vision Pro

The obvious design choice in a Vision Pro’s design is to marry these two devices together. What I mean by this marriage is that you’re already carrying around a CPU device capable of driving the Vision Pro headset in the palm of your hand. Instead, Apple should have designed their VR headset to be a thin client display device. What this means is that as a thin client, the device’s internal processor doesn’t need to be super fast. It simply needs to be fast enough to drive the display at a speed consistent with the refresh rates needed to be a remote display. In other words, turn the Vision Pro into a mostly dumb remote display device, not unlike a computer monitor, except using a much better wireless protocol. Then, allow all Apple devices to pair with and use the Vision Pro’s headset as a remote display.

This means that instead of carrying around two (or rather three, when you count that battery pack) hefty devices, the Vision Pro can be made much lighter and will run less hot. It also means that the iPhone will be the CPU device that does the hard lifting for the Vision Pro. You’re already carrying around a mobile phone anyway. It might as well be the driving force behind the Vision Pro. Simply connect it and go.

Removing all of that motherboard hardware (save a bit of processor power to drive the display) from inside the Vision Pro does several things at once. It removes the planned obsolescence issue around the Vision Pro and turns the headset into a display device that could last 10 years vs a planned obsolescence device that must be replaced every 12-24 months. Instead of replacing the headset each year, we simply continue replacing our iPhones as we always have. This business model fits right into Apple’s style.

A CPU inside of the headset will still need to be fast enough to read and understand the cameras built into the Vision Pro so that eye tracking and all of the rest of these technologies work well. However, it doesn’t need to include a full fledged computer. Instead, connect up the iPhone, iPad or even MacBook for the heavy CPU lifting.

Vision Pro Battery Pack

The second flaw of the Vision Pro is its hefty and heavy battery pack. The flaw isn’t the battery pack itself. It’s the fact that the battery pack should have been used to house the CPU and motherboard, instead of inside the Vision Pro headset. If the CPU main board lived in the battery pack case, it would be a simple matter to replace the battery pack with an updated main board each year, not needing to replace the headset itself. This would allow updating the M2 chip regularly with something faster to drive the headset.

The display technology used inside the Vision Pro isn’t something that’s likely to change very often. However, the main board and CPU will need to be changed and updated frequently to increase the snap and performance of the headset, year over year. By not taking advantage of the external battery pack case to house the main board along with the battery, which must be carried around anyway, this is a huge design flaw for the Vision Pro.

Perhaps they’ll consider this change with the Vision Pro 2. Better, make a new iPhone that serves to drive both the iPhone itself and the Vision Pro headset with the iPhone’s battery and using the CPU built into the iPhone to drive the Vision Pro device. By marrying the iPhone and the Vision Pro together, you get the best of both worlds and Apple gets two purchases at the same time… an iPhone purchase and a Vision Pro purchase. Even an iPad should be well capable of driving a Vision Pro device, including supplying power to it. Apple will simply need to rethink the battery sizes.

Why carry around that clunky battery thing when you’re already carrying around an iPhone that has enough battery power and enough computing power to drive the Vision Pro?

Clunky Headset

All VR headsets are clunky and heavy and sometimes hot to wear. The worst VR headset I’ve worn is, hands down, the PSVR headset. The long clunky cables in combination with absolutely zero ventilation and its heavy weight makes for an incredibly uncomfortable experience. Even Apple’s Vision Pro suffers from a lot of weight hanging from your cheeks. To offset that, Apple does supply an over-the-head strap that helps distribute the weight a little better. Even still, VR headset wearing fatigue is a real thing. How long do you want to wear a heavy thing resting on your cheekbones and nose that ultimately digs in and leaves red marks? Even the best padding won’t solve this fundamental wearability problem.

The Vision Pro is no different in this regard. The Vision Pro might be lighter than the PSVR, but that doesn’t make it light enough not to be a problem. But, this problem cuts Apple way deeper than this.

Closing Yourself Off

The fundamental problem with any VR headset is the closed in nature of it. When you don a VR headset, you’re closing yourself off from the world around you. The Vision Pro has opted to include the questionable choice of an aimed spatial audio system. Small slits in the side of the headset aim audio into the wearer’s ears. The trouble is, this audio can be heard by others around you, if even faintly. Meaning, this extraneous audio bleed noise could become a problem in public environments, such as on a plane. If you’re watching a particularly loud movie, those around you might be disturbed by the Vision Pro’s audio bleed. To combat this audio bleed problem, you’ll need to buy some Airpods Pro earbuds and use these instead.

The problem is, how many people will actually do this? Not many. The primary design flaw was in offering up an aimed, but noisy audio experience by default instead of including a pair of Airpods Pro earbuds as the default audio experience when using the Vision Pro. How dumb did the designers have to be to not see the problem coming? More than likely, some airline operators might choose to restrict the use of the Vision Pro entirely on commercial flights simply to avoid the passenger conflicts that might ensue because the passenger doesn’t have any Airpods to use with them. It’s easier to tell passengers that the device cannot be used at all instead of trying to fight with the passenger about putting in Airpods that they might or might not have.

It goes deeper than this, though. Once you don a headset, you’ve closed yourself off. Apple has attempted to combat the closed of nature of a VR headset by offering up front facing cameras and detecting when to allow someone to barge into the VR world and have a discussion with the wearer. This is an okay idea so long as enough people understand that this barge-through idea exists. That will take some getting used to, both for the Vision Pro wearer, but also for the person trying to get the wearer’s attention. That assumes that barge-through even works well enough to do that. I suspect that the wearer will simply need to remove the headset to have a conversation and then put it back on to resume whatever they were previously doing.

Better Design Choice

Instead of a clunky closed off VR headset, Apple should have focused on a system like the Google Glass product. Google has since discontinued the production of Google Glass, mostly because it really didn’t work out well, but that’s more because of Google itself and not of the idea behind the product.

Yes, a wearable display system could be very handy, particularly with a floating display in front of the vision of the user. However, the system needs to work in a much more open way, like Google Glass. Because glasses are an obvious solution to this, having a floating display in front of the user hooked up to a pair of glasses makes the most obvious sense. Glasses are light and easy to use. They can be easily put on and taken off. Glasses are easy to store and even easier to carry. Thick, heavy VR headsets are none of these things.

Wearing glasses keeps the person aware of their surroundings, allowing for talking to and seeing someone right in front of you. The Vision Pro, while it can recreate the environment around you with various cameras, still closes off the user from the rest of the world. Only Apple’s barge-through system, depending on its reliability, has a chance to sort-of mitigate this closed off nature. However, it’s pretty much guaranteed that the barge-through system won’t work as well as wearing a technology like Google Glass.

For this reason, Apple should have focused on creating a floating display in front of the user that was attached to a pair of glasses, not to a bulky and clunky headset. Yes, the Vision Pro headset is quite clunky.

Front Facing Cameras

You might be asking, if Google Glass was such a great alternative to a bulky headset, why did Google discontinue it? Simple, privacy concerns over the front facing camera, which led to a backlash. Because Google Glass shipped with a front facing camera enabled, anyone wearing it, particularly when entering a restaurant or bar, could end up recording the patrons in that establishment. Because restaurants and bars are privately owned spaces, all patron privacy needs to be respected. To that end, owners of restaurants and bars ultimately barred anyone wearing Google Glass devices from using them in the establishment space.

Why is this important to mention? Because Apple’s Vision Pro may suffer the same fate. Because the Vision Pro also has front facing cameras, cameras that support the barge-through feature among other potential privacy busting uses, restaurants and bars again face the real possibility of another Google Glass like product interfering with the privacy of their patrons.

I’d expect Apple to fare no better in bar and restaurant situations than Google Glass. In fact, I’d expect those same restaurants and bars that banned Google Glass wearers from using those devices to likewise ban any users who don a Vision Pro in their restaurants or bars.

Because the Vision Pro is so new and because restaurant and bar owners aren’t exactly sure how the Vision Pro works, know that if you’re a restaurant or bar owner, the Vision Pro has front facing cameras that record input all of the time, just like Google Glass. If you’ve previously banned Google Glass use, you’ll probably want to ban the use of Vision Pro headsets in your establishment for the same reasons as the ban on Google Glass. Because you can’t know if a Vision Pro user has or has not enabled a Persona, it’s safer to simply ban all Vision Pro usage than trying to determine if the user has set up a Persona.

VisionProEyesWhy does having a Persona matter? Once a Persona is created, this is when the front facing cameras run almost all of the time. If a Persona has not been created, the headset may or may not run the front facing cameras. Once a Persona is created, the front facing LED display creates a 3D virtual representation of the person’s eyes using the 3D Persona (aka. avatar). What you’re seeing in the image of the eyes is effectively a live CGI created image.

The Vision Pro is claimed by Apple not to run the front cameras without a Persona created, but bugs, updates and whatnot may change the reality of that statement from Apple. Worse, though, is that there’s no easy way to determine if the user has created a Persona. That’s also not really a restaurant staff or flight attendant job. If you’re a restaurant or bar owner or even a flight attendant, you must assume that all users have created a Persona and that the front facing cameras are indeed active and recording. There’s no other stance to take on this. If even one user has created a Persona, then the assumption must be that the front facing cameras are active and running on all Vision Pro headsets. Thus, it is wise to ban the use of Apple’s Vision Pro headsets in and around restaurant and bar areas and even on airline flights… lest they be used to surreptitiously record others.

Here’s another design flaw that Apple should have seen coming. It only takes about 5 minutes to read and research Google Glass’s Wikipedia Page and its flaws… and why it’s no longer being sold. If Apple’s engineers had done this research during the design phase of the Vision Pro, they might have decided not to include front facing cameras on the Vision Pro. Even when the cameras are supposedly locked down and unavailable, that doesn’t preclude Apple’s own use of these cameras when someone is out and about used solely for Apple’s own surveillance purposes. Restaurant owners, beware. All of Apple’s assurances mean nothing if a video clip of somebody in your establishment surfaces on a social media site recorded via the Vision Pro’s front cameras.

Better Ideas?

Google Glass represents a better technological and practical design solution; a design that maintains an open visual field so that the user is not closed off and can interact and see the world around them. However, because Google Glass also included a heads up display in the user’s vision, some legislators took offense to the possibility of the user becoming distracted by the heads up display that they could attempt to operate a motor vehicle dangerously while distracted. However, there shouldn’t be a danger of this situation when using a Vision Pro, or at least one would hope not. However, because the Vision Pro is capable of creating a live 3D image representation of what’s presently surrounding the Vision Pro user, inevitably someone will attempt to drive a car while wearing a Vision Pro and all of these legislative arguments will resurface… in among various lawsuits should something happen while wearing it.

Circling Back Around

Let’s circle around to the original question asked by this article. Is the Vision Pro worth the money?

Considering its price tag and its comparative functional sameness to an iPad and to other similar but less expensive VR headsets, not really. Right now, the Vision Pro doesn’t sport a “killer app” that makes anyone need to run out and buy one. If you’re looking for a device with a 3D stereoscopic display that acts like an iPad and that plays nice in the Apple universe, this might suffice… assuming you can swallow the hefty sticker shock that goes with it.

However, Apple more or less overkilled the product by adding the barge-through feature requiring the front facing camera(s) and the front facing mostly decorative lenticular 3D display, solely to support this one feature “outside friendly” feature. Yes, the front facing OLED lenticular display is similar to the Nintendo 3DS’s 3D lenticular display. The lenticular feature means that you probably need to stand in a very specific position for the front facing display to actually work correctly and to display 3D in full, otherwise it will simply look weird. The front facing display is more or less an expensive, but useless display addition to the wearer. It’s simply there as a convenience to anyone who might walk buy. In reality, this front display is a waste of money and design dollars, simply to add convenience to anyone who might happen along someone wearing this headset. Even then, this display remains of almost no use until the user has set up their Persona.

Once the wearer has set up a Persona, the unit will display computer generated 3D eyes on the display at times, similar to the image above. When the eyes actually do appear, they appear to be placed at the correct distance on the face using a 3D lenticular display to make it appear like the real 3D eyes of the user. The 3D lenticular display doesn’t require glasses to appear 3D because of the lenticular technology. However, the virtual Persona created is fairly static and falls rather heavily into the uncanny valley. It’s just realistic enough to elicit interest, but just unrealistic enough to feel creepy and weird. Yes, even the eyes. This is something that Apple usually nails. However, this time it seems Apple got the Persona system wrong… oh so wrong. If Apple had settled on a more or less cartoon-like figure with exaggerated features, the Persona system might have worked better, particularly if it used anime eyes or something fun like that. When it attempts to mimic the real eyes of the user, it simply turns out creepy.

In reality, the front facing display is a costly lenticular OLED addition that offers almost no direct benefits to the Vision Pro user, other than being a costly add-on. However, the internal display system per eye within the Vision Pro sports around 23 million pixels between both eyes and around 11.5 million pixels per eye, which is slightly less than a 5K display per eye, but more than a 4K display per eye. When combined with both eyes, the full resolution allows for the creation of a 4K floating display. However, the Vision Pro would not be able to create an 8K floating display due to its lack of pixel density. The Vision Pro wouldn’t even be able to create a 5K display for this same density reason.

Because many 5K flat and curved LCD displays are now priced under $800 and are likely to drop in price even further, that means you can buy two 5K displays for less than than half the cost of one Vision Pro headset. Keep in mind that these are 5K monitors. They’re not 3D and they’re relatively big in size. They don’t offer floating 3D displays appearing in your vision and there are limits to a flat or curved screen. However, if you’re looking for sheer screen real estate for your computing work, buying two 5K displays would offer a huge amount of screen real estate for managing work over the Vision Pro. By comparison, you’d honestly get way more real estate with real monitors compared to using the Vision Pro. Having two monitors in front of you is easier to navigate than being required to look up, down and left and right and perhaps crane your neck to see all of the real estate that the Vision Pro affords… in addition to getting the hang of pinch controls.

The physical monitor comparison, though, is like comparing apples to oranges when compared with a Vision Pro headset (in many ways). However, this comparison is simply to show you what you can buy for less money. With $3400 you can buy a full computer rig including a mouse, keyboard, headphones and likely both of those 5K monitors for less than the cost of a single Vision Pro headset. You might even be able to throw in a gaming chair. Keeping these buying options in perspective keeps you informed.

The Bad

Because the headset offers a closed and private environment that only the wearer can see, this situation opens the doors to bad situations if using it in a place of business or even if out in public. For example, if an office manager were to buy their employee a Vision Pro instead of a couple of new and big monitors, simply because the Vision Pro is a closed, private environment, there’s no way to know what that worker might be doing with those floating displays. For example, they could be watching porno at the same time as doing work in another window. This is the danger of not being able to see and monitor your staff’s computers, if even by simply walking by. Apple, however, may have added a business friendly drop-in feature to allow managers to monitor what employees are seeing and doing in their headsets.

You can bet that should a VR headset become a replacement for monitors in the workplace, many staff will use the technology to surf the web to inappropriate sites up to and including watching porn. This won’t go over well for either productivity of the employee or the manager who must manage that employee. If an employee approaches you asking for a Vision Pro to perform work, be cautious when considering spending $3500 for this device. There may be some applicable uses for the Vision Pro headset in certain work environments, but it’s also worth remaining cautious for the above reasons when considering such a purchase for any employee.

On the flip side, for personal use, buy whatever tickles your fancy. If you feel justified in spending $3500 or more for an Apple VR headset, go for it. Just know that you’re effectively buying a headset based monitor system.

Keyboard, Eye Tracking and The Pinch

Because the Vision Pro is affixed to your head, Apple had to devise a way to obtain input within the VR environment. To that end, Apple decided on the pinch motion. You pinch your thumb and forefinger together in a sort of tapping motion. Each tapping motion activates whatever you are looking at (eye tracking). Whenever the headset “sees” (using its many cameras) your pinching motion, it activates wherever your eyes are focused. This means that in order to open an application from the iPad-ish icon list, you must be looking directly at the icon to activate it. If your eyes flutter around and you perform the pinch motion the instant your eyes look someplace else, the app will not activate. You might even activate something unintentional.

Keep in mind that this is still considered a beta product, which weird coming from Apple. This is the first time I can recall Apple explicitly releasing a beta product for review.

That said, there are definitely some improvements that could be had with this eye tracking system. For example, the system could detect and count linger time. The longer the eye lingers, the more likely it is that the user wants to activate the thing that the eyes lingered on the longest, even if the eyes are not currently looking at it. This means that even if your eyes dart away at the moment you pinch, the system would still understand that you want to activate the icon that was lingered on the longest. As far as I understand it, the OS doesn’t presently work this way. It only activates the icon or control you are presently looking at. Adding on a fuzzy eye linger system could reduce errors when selecting or activating the wrong things.

If you need to move a window around or expand the size of it, you must be looking directly at the control that performs that action. Once you’re looking at that specific control, the pinch and move will activate the control for as long as the pinch and move continues.

Unfortunately, this system falls down hard when you want to use the on-screen keyboard. This keyboard only works if you poke each key with your forefingers on each hand. This means hunt-and-peck typing. If you’re a touch typist, you’re going to feel horribly out of place being forced into using single finger hunt-and-peck. The Vision Pro will need to make much better improvements around keyboard typing.

On the flip side, it seems that the Vision Pro may want you to use the microphone and voice to input longer strings of text instead of typing. This means that for web searches, you’re likely going to fill in fields using voice dictation. I will say that Apple’s dictation system is fair. It works in many cases, but it also makes many mistakes. For example, most dictation systems can’t understand the difference between its and it’s, preferring to use it’s whenever possible, even though the selected usage is incorrect. Same problem exists with the words there, their and they’re and several similar type words when dictating. Typing is usually the better option over dictating long sentences of text, but it also means you’re going to need to pair a Bluetooth keyboard. Then, type on that keyboard blind because the Vision Pro won’t show you your hands or that keyboard in the VR display when the keyboard is sitting in your lap. Even if the keyboard is sitting on a desk, it might not show the keyboard properly without looking down at the keyboard instead of the window into which you’re typing.

For example, I would never attempt to blog an article this long using a VR headset. Not only would the headset eventually become too uncomfortable on my head, dictating everything by voice would get to be a pain in the butt because of all of the constant corrections. Even Apple’s active correction system leaves a lot to be desired, changing words from what you had actually wanted into something that doesn’t make any sense after you read it back. These problems will immediately be carried into the Vision Pro simply because these systems already exist in Apple’s other operating systems and those existing systems will be pulled into the Vision Pro exactly as they are, warts and all.

What Apple needs to create is a psuedo Augmented Reality (AR) keyboard. A keyboard where the VR system uses AR to pick up and read what you’re typing. Sure, the keyboard could be connected, but the AR system could simply watch the keys you’re pressing and then input those key presses via camera detection rather than via Bluetooth. In this way, the on-screen keyboard can still present and show which key is being typed in your vision, yet give you the option of touch typing on a keyboard.

Pinch Motion

The Apple chosen VR pinch motion seems like a fine choice and might become a sort of standard across the industry for other VR headsets and applications. Many VR headsets have struggled to produce a solid standardized input system. The pinch is a relatively easy, intuitive control and it works well for most use cases in the Vision Pro, but it’s definitely not perfect for all use cases. The cameras around the Vision Pro unit seem sensitive enough that you don’t have to hold your hands directly out in front in an awkward position like many VR headsets require. Instead, you can sit comfortably with your hands in your lap or on a desk and the unit will still pick up your pinch taps. You will need to move your hand(s) around, though, to activate resize and movement controls as well as when typing on the on-screen keyboard.

However, I do think it would be great for Apple to offer a lighted wand or other physical object that can supplement, augment and/or replace the pinch control. For people who don’t have access to fine motor controls with their hands, an alternative control method using an external device could be ideal for accessibility purposes.

VR Motion Sickness

One thing that cannot be easily overcome is VR motion sickness. It doesn’t matter what headset manufacturer it is, this problem cannot be easily overcome by software. Apple has done nothing to address this issue with the Vision Pro. If you have previously encountered VR sickness while wearing a headset, you’re likely to encounter it with the Vision Pro eventually. The transparent effect of showing you your present surroundings might help reduce this problem. If you replace your present surroundings with a forest or beach scene or some other fantasy environment, your body will be at odds with what your eyes are seeing.

VR motion sickness is typically exacerbated by rapid movements, such as riding a VR roller coaster or riding in a high speed car chase in VR. These are situations where the mind sees motion, but the body feels nothing. This disparity between the physical body sensations and the motion the mind is experiencing can easily lead to VR motion sickness.

If you stick to using the Vision Pro strictly for computer purposes, such as an extended monitor or for other productivity or entertainment purposes, you might not experience sickness. If you wish to get into full 3D virtual gaming, the reason most people want to purchase a VR headset, then you’re inviting motion sickness.

Keep in mind that VR motion sickness is not the same as real motion sickness. I can ride on planes, boats and even buffeting roller coasters, all without any sickness or issues. However, the moment I strap on a VR headset and begin riding a VR roller coaster or ride around in a fast VR car, the VR sickness begins to kick in. When it arrives, the only solution is to take off the headset and let it subside. It also means exceedingly short VR sessions. When the VR sickness comes on, it comes on rapidly. Perhaps even as fast as 5 minutes after experiencing a lot of motion on the VR screen.

If you’ve never bought into or tried a VR headset in the past, you should make sure you can return the headset should you experience VR sickness while using it.

Overall

The Vision Pro is a pricey VR headset. While the Vision Pro is not the most expensive VR headset on the market, it’s definitely up there in price. The question remains whether the Vision Pro is a suitable or efficient alternative to using a keyboard, mouse and monitor when computing. This author thinks that the presently clumsy, slow input systems utilized in VR headset systems (yes, that includes the pinch), when compared to a mouse and keyboard input, doesn’t make a VR headset the most efficient product for computing.

The best use cases for 3D stereoscopic VR headsets is for immersive 3D virtual gaming (assuming you can get past the motion sickness) and consuming movies and TV shows. The floating large screens in front of your vision are ideal for presenting flat and 3D movies as well as TV shows which make you feel like you’re watching entertainment in a theater environment. This aspect is actually quite uncanny. However, for consuming music, a VR headset is a fail. You simply need earbuds, such as Apple’s Airpods for that. You don’t need to spend $3400 to listen to music, even if the Vision Pro is capable of layering reverb and echo effects onto the music to make it sound more spatial.

Personally, I want to hear the music as it was crafted by the musician. I don’t want third party added effects that are more likely to detract from and muddy the final music product. If a musical artist as recorded a Dolby Atmos version of their music, then playing that version back exactly in its original recorded spatial form is perfectly fine, but devices shouldn’t layer anything else on top.

Overall, the Vision Pro is a fair addition to the VR headset space. However, it’s no where near perfect and it needs a lot of nuanced tweaking in subsequent models before it can become a real contender. This first released model is both overkill and naive all at the same time, adding bells and whistles that, while interesting, add to the hefty price tag without adding substantial benefit to the final product.

The built-in main board M2 computer ensures that the unit will become obsolete in 1-2 years and need to be replaced, adding yet more computer junk to our already overflowing landfills. Apple needs to firmly grasp and get behind product longevity in this product rather than planned obsolescence every 12 months. Decoupling the main board and placing it into the battery case would go a long way towards longevity AND allow for easy replacement of that battery and main board. This change alone would enable a Vision Pro headset’s display to remain viable for years to come, all while simply replacing an obsolete computer and battery that drives it. This one is a big miss by Apple’s design team.

Rating: 2.5 out of 5 (Apple tried to do too much, but actually did very little to improve VR. Apple’s design increases landfill chances; not a green product.)
Recommendation: Skip and wait for the next iteration

↩︎

Running / Installing Mac OS X (Snow Leopard) on VirtualBox

Posted in Apple, Mac OS X, VirtualBox, virtualization by commorancy on June 21, 2010

Updated 8/2/2011

Lion Update

With the recent release of Lion, there is a push to get a Lion version working on VirtualBox.  At present, there is yet no boot loader capable of booting Lion on VirtualBox. So, for now, Snow Leopard is still it for a standalone MacOS on VirtualBox.  I will update this article as necessary to address a working installation of Lion as it progresses.  Stay Tuned.

Nawcom Mod CD

There is a new CD image from Nawcom (http://blog.nawcom.com/?p=306) that makes installation of MacOS X much easier on VirtualBox (instead of using Prasys’ EFI boot CDs).  And yes, I’ve tried it.  The Nawcom EFI CD is much faster for installation because it does some very clever things, including installing the boot loader at the end of the install.

So, I am now recommending you to download and use the Nawcom ModCD instead of the Prasys EFI boot CDs listed below.  Although, I will leave the information for the Prasys Empire EFI CDs available should the Nawcom CD not work for you.  Alternatively, you can try the tonymacx86.com iBoot or iBoot Legacy CDs if all else fails.  Even using the Nawcom ModCD, you will still need to follow the instructions on changing the resolution of the screen as documented below as this CD doesn’t change that part of the installation process.

Go!

Let’s start by saying this. Support Apple by legally buying your copy of Mac OS X.  Don’t pirate it.

Note also that buying a retail packaged disk from the Apple store prevents a lot of headaches during this process.  A Mac OS X Install Disk that comes bundled with any Mac system will only install on the hardware with which it came bundled.  For example, if you try to install from a bundled DVD media that was shipped along with a MacBook Pro, it will not install on Virtualbox and you will see the error ‘Mac OS X cannot be installed on this computer’.  Save yourself the headache and get a retail disk from the Apple store.

Before getting started, if you are wanting to run Mac OS X on VMWare Player 3 instead, then check out Randosity’s Running Mac OS X on VMWare Player 3 article for details.

Apple’s Stance

Apple wants you to buy and run Mac OS X (desktop edition) on a MacBook Pro or other similar Mac hardware. While I think that’s a grand notion to sell the hardware, the hardware will sell regardless of the operating system. Further, if you are a hardware company, why sell the operating system separately anyway? I mean, if it’s the hardware that matters, how is it that you can buy Mac OS X separately both desktop and server editions. I digress.

Because Apple wants you to buy into their hardware platforms, they would prefer you not run Mac OS X on Virtual Environments. I personally think, however, that this idea is both socially and ecologically irresponsible. For a company that tries to tout itself as Green and Earth-Friendly, by not allowing virtualization of Mac OS X (any desktop version), this prevents people from using the hardware they already have and instead forces us to buy new hardware that will eventually fill landfills. Using existing hardware that may work just fine, although not made by Apple, at least keeps the hardware out of the land fill and they are still making money off selling the operating system.

Supported vs Non-Supported CPUs

Note, these boot CDs support specific types of CPUs.  If your CPU is not listed (i.e., Atom processor), you will need to download and use the CDs labeled with the word ‘Legacy’.   These CDs may or may not work for your CPU, but these are the only CDs that have a chance of working on non-supported CPU types.

Let’s get started — items required

  • A recent PC hardware config (within the last 3 years) installed with 64 bit Windows 7 or Vista or Linux 64 bit
    • Note, the faster the PC is, the better that VirtualBox will work.
  • A recent processor (Intel core i3, i5, i7, i3m, i5m, i7m, AMD Phenom or similar 64 bit processor)
  • Enabled VT-x (for Intel Processors) or AMD-v (for AMD processors) in the PC BIOS
  • Retail version of Mac OS X Snow Leopard.  (If you try any other version other than the retail package, it probably won’t work!)

As stated above, you will need hardware capable of VT-x / AMD-v (BIOS level virtualization support passthrough). Without this hardware configuration, you will not be able to install Mac OS X. Most recent dual and quad core processors support this technology. Although, you may have to enter the BIOS to enable it. So, check your BIOS for ‘Virtualization’ settings and enable it.

Pick your host operating system. You can run Windows 7, Vista, XP, Linux (Ubuntu, Redhat, etc) or Solaris. Whichever operating system you choose for the host, make sure it’s a 64 bit edition. I recommend Windows 7 64 bit edition as XP 64 bit edition can be somewhat of a bear to work with and Vista isn’t readily available at this point. If you’re looking for the least expensive solution, then I would choose Linux. I personally use Windows because I also need Windows 7 for other tasks as well. If you are currently running a 32 bit OS edition, you will first need to upgrade the host to 64 bit to operate Snow Leopard. Snow Leopard is mostly 64 bit now and, thus, requires a 64 bit host OS to function.

Note that this tutorial was tested using Mac OS X 10.6.3 (Snow Leopard). OS X may install using 10.6.4 or later, but Apple may also make changes that could prevent it from working. If you have an older install disk than 10.6.3, the installation may fail. I recommend using 10.6.3 or later.

What is EFI?

One other thing to note about Macintosh computers and Snow Leopard… Macintosh computers require an EFI BIOS to boot. What is EFI? EFI stands for Extensible Firmware Interface and was developed by Intel for the Itanium platform in the mid-90s. This ‘BIOS’ replacement is designed to allow direct 32 and 64 bit addressing right from the firmware unlike the PC BIOS which only allows 16 bit addressing during boot operations.

Apple integrated EFI into the PowerPC and later the Intel Macintosh line to boot Mac OS X. Because this boot system is not compatible with PC BIOS, it requires the standard PC BIOS to boot an EFI boot system first. Then, the EFI boot system can then boot Mac OS X. So, the boot system goes like this:

  • PC BIOS boots EFI
  • EFI boots Mac OS X

Yes, VirtualBox has an EFI boot system within, but this EFI system will not boot Mac OS X (probably on purpose). Instead, the Empire EFI boot ISO is necessary to boot Mac OS X (both the Mac OS X install media and the actual operating system once installed).

Focus on Windows

With this post, I will focus on using Windows as the Host and Mac OS X as the guest. You can utilize this guide if you want to use Linux, but you will need to determine how to get certain steps done with Linux (i.e., creating and/or mounting ISO images). So, let’s get going.

Items you’ll need

Steps to get it working

  • Install VirtualBox on Windows
  • Open VirtualBox and click ‘New’. This will start a Machine build Wizard
  • Name this machine ‘Mac OS X’
  • Set the Type to Mac OS X + Mac OS X Server (if it isn’t already) and click Next
  • Set memory to 1024 (or whatever you want to give it) and click Next
  • Under Boot Hard disk, either create a new HD or select an existing HD file* (at least 20GB), click Next
  • If Creating new, continue onward. Otherwise, skip down to ‘Readying VM for First Use’
  • In the New HD Panel, choose Dynamic Expanding Storage, Click Next
  • Click the Folder icon to choose where this disk is to be stored (C not recommended)
  • Set the size to 20GB (type in 20GB), click Next
  • Click Finish to exit HD creation and click Finish again to exit VM creation

Readying VM for First Use

Now you have a new VM for Mac OS X set up, it’s not to use ready yet. So, Let’s ready it for use:

  • Click to select the Mac OS X machine
  • Click the ‘Settings’ button
  • Click the System settings icon
  • Uncheck ‘Enable EFI’ (we will use EFI, just not VBox’s built-in version**)
  • Under Processor tab, leave it at 1 CPU and enable PAE/NX if it isn’t already
  • Under Acceleration, Enable VT-x/AMD-v (must be enabled). Without this setting, you can’t run Mac OS X in VBox.***
  • Under Display, set the Video Memory to 128 and Enable 3D Acceleration
  • Under Storage, IDE controller type must be ICH6
  • Also under Storage, click ‘Empty’ cdrom drive and set the Empire EFI disk to this drive using the Folder icon****.
  • Audio Driver is Windows Directsound + ICH AC97
  • Network should be Bridged Adapter (NAT may work)
  • Click ‘OK’ to save these settings

Now you’re ready to start the install process. Click the ‘Start’ button to start the Mac OS X virtual machine. Once the Empire EFI screen has loaded, eject the Empire EFI ISO image by unchecking it from the Devices->CD/DVD Devices Menu and then locate your Mac OS X Install ISO and select this. If you have the original media and want to create an ISO, go to the ‘Creating an ISO image with ImgBurn’ section below. After the Mac OS X install ISO is selected and you’re back at EFI, press the F5 key. The screen should refresh to show the newly inserted Mac OS X install media. Once it shows the install media, press the enter key to begin installation.

Note, if you start this process using the Empire ISO image, then you must use a Mac OS X Install ISO. If you want to use the physical media, then you’ll need to burn the Empire ISO to a CD and boot from the physical media drive in VirtualBox. You can then eject that media and insert the Mac OS X install media. You cannot mix and match ISO to physical media. I was not able to get mixing ISO and physical media to work in Empire EFI.

Installation of Mac OS X

Once you get the Mac OS X Installer going, I’ll leave it up to you to finish the full install process. However, I will say this about the hard drive. The VBox HD is blank. So, you will need to prepare it with ‘Disk Utility’. Once the Mac OS X installer starts and you get to the first screen with a menu bar, choose Utilities-> Disk Utility. It will recognize the Disk is there, but it cannot be used until it is partitioned and formatted. Choose the VBox disk and click the ‘Erase’ tab. Under Erase, choose Mac OS X Extended (Journaled) and then name it ‘Hard Disk’ (or whatever you want to call it) and click the ‘Erase’ button. It will confirm that you want to do this, so click ‘Erase’ again. Exit Disk Utility and continue the installation. It will probably take 30-40 minutes to install Mac OS X depending on various factors.

Mac OS X Installed — What’s Next?

If you’ve installed from the Nawcom ModCD, then skip this part and go directly to Final Steps + Increasing screen resolution.  If you’ve installed from tonymacx86.com’s CD, you may still need to install MyHack.  If you’ve installed from Prasys’ Empire EFI CD, you will need to install MyHack.  So, continue on.

Ok, so now that Mac OS X is installed, the system still won’t boot up without the EFI disk. So, reboot after the install with the Empire EFI ISO in the drive. Choose the new bootable ‘Hard Disk’ in the EFI menu and boot into Mac OS X. Once Mac OS X is loaded, open Preferences and set the ‘Startup Disk’ to your new bootable installation. Now, open Safari and search Google for ‘MyHack’ or locate this Randosity article in Safari and go to this site: MyHack. The download will be a package (.mpkg) file and needs to be downloaded on Mac OS X. Once downloaded, double-click the package to install. Click through the Wizard until you get the screen with the ‘Customize’ button. Click Customize and enable PS2Controller (keyboard and mouse) and disable SleepEnabler (doesn’t work with later OS X versions). Click to finish the installation process.

After MyHack is installed, you can eject the Empire EFI media and your Mac OS X installation will now boot on its own.

Final Steps + Increasing screen resolution

You’ll notice that the resolution is fixed to 1024×768. You can change this resolution, but it has to be done in two files. First on Mac OS X, there’s the /Extra/com.apple.Boot.plist file. This file describes the resolution for the Mac to use. Before you edit this file, install Xcode from the Mac OS X media (insert it into the drive with the Mac running). Open ‘Optional Installs’ folder and double-click ‘Xcode’ and follow the installation instructions. Note, it takes about 2.3GB of space. Plist files are easier to edit when the Property List Editor is installed from Xcode. Otherwise, you will have to hand edit these files with TextEdit.

Also note that the /Extra folder is at the root of the Hard Drive volume.  It is not inside your local user profile folder.  You will also note that after a default install, Mac OS X doesn’t show hard disk icons on the desktop.  To turn this icon on, from the top menu, select ‘Finder->Preferences…’.  Then, put a check next to ‘Hard Disks’ under ‘Show these items on the desktop’.  Once you open the Hard Disk icon, you should see the Extra folder.  If you still don’t see the Extra folder, be sure that you have installed MyHack or used the Nawcom ModCD.  If MyHack hasn’t been installed, there won’t be an /Extra folder there.  The Extra folder gets installed as a result of installing MyHack.

Also, there can only be one available resolution in Virtualbox and on the Mac at a given time. I wish it supported more resolutions at once, but it doesn’t. Note also that because VirtualBox doesn’t support Mac OS X fully, there are no machine additions. To enable the resolution, on the PC side of VirtualBox (on the VirtualBox host), you will need to run the following command from a command shell (cmd):

VBoxManage setextradata "Mac OS X" "CustomVideoMode1" "1920x1080x32"

The “Mac OS X’ label is the exact machine name in VirtualBox. The “1920x1080x32” setting is customizable to your needs (and video card capabilities). However, both this setting and com.apple.boot.plist (on the Mac) must match for the screen resolution to take effect.

The ‘VBoxManage’ command is located in the Program Files\Oracle\VirtualBox folder or wherever you installed VirtualBox. You can add this location to your PATH variable so you can use this command without typing in the full path each time.

In the com.apple.Boot.plist file, you will need to add the following properties (if not already there):

Graphics Mode - String - 1920x1080x32
GraphicsEnabler - String - y

(The resolution value should match the above VboxManage command). If you want to change resolutions later, you will need to edit both places again and reboot your Mac.

If you reboot and the screen hasn’t changed or has changed to 1280×1024 and not the resolution you expected, double check that both com.apple.boot.plist and the CustomVideoMode1 setting match and are active. Both of these settings must match for the resolution to work.

Updating com.apple.Boot.plist

It’s easiest to edit this file with the Property List Editor tool. So, install Xcode before managing this file. In order to edit this file, you cannot edit it directly. Instead, copy the file and paste it to your desktop. Edit the file on your desktop. Then, once done editing, drop the file on top of the /Extra folder. Click “Replace File” when asked and supply your account password. Once the file is replaced, you can reboot to see if the resolution change has taken effect.

Audio Support

Update: On my HP quad core system, I am unable to get the AC97 sound driver to work on 10.6.4 (as have others). I have uninstalled and reinstalled this kernel extension, but it simply will not activate. I am still working with this setup to see if I can get it working, but so far no luck. I should point out, then, that the AC97 sound driver may not work on all systems and may not work with 10.6.4. So, you may not want to update to 10.6.4 until this issue is resolved if you need sound.

Mac OS X does support audio output with an AC97 audio driver in Snow Leopard up to 10.6.3. It does not appear to support audio input. I will say, however, that the audio driver is, at best, under performing. That means, it breaks up, it doesn’t always work and it generally sounds crappy. That said, if you want to hear the various insundry noises that the Mac can make for bells, you can install the driver. The AC97 driver can be found in this Virtualbox Forum Thread.

Note, if the supplied installer does not properly install the driver, download the .zip file and install the AppleAC97Audio.kext Extension the into /Extra/Extensions folder. Then follow the instructions below on rebuilding the Extensions.mkext file.

Kernel Extensions — Rebuilding .mkext cache files (Kernel Extension Cache)

Mac OS has always been known for its extensions. Well, Mac OS X is no different in this respect. In the original Mac, you simply drop the extension into the Extensions folder and it works. Well, unfortunately, it’s not quite that simple with Mac OS X. If you want to drop in a .kext file (extension), you will need to rebuild the Extensions.mkext database. This database is what helps Mac OS X find and work with installed extensions. To rebuild these cache files, you will need to use the following Terminal.app as root:

# kextcache -v 1 -t -m /Extra/Extensions.mkext /Extra/Extensions/ /System/Library/Extensions/
# kextcache -v 1 -t -m /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext /System/Library/Extensions/

Running these commands will rebuild the cache files necessary to activate newly installed extensions. So, if you need to install any new extensions, you will need to run the above commands to recreate the extension cache files.

Creating an ISO image with ImgBurn

To create an ISO image using ImgBurn, you will first need to download and install it. Once it’s installed, start it up. Now click ‘Create image file from disc’. Insert the Mac OS X CD. The CD will be labeled ‘Boot Camp’. This is fine as this is the only partition that Windows is able to see. As long as it sees the ‘Boot Camp’ partition, the image will be created correctly. Click the CD icon at the bottom of the Window to create your ISO image. Once the image has been created, you can continue at your previous step.

Rebooting the Mac

As a side note about rebooting. With some hardware, rebooting Mac OS X in VirtualBox doesn’t work. Sometimes it seems to hang, sometimes it gives a banner telling you to power off the machine. Basically, there isn’t really a resolution to this issue. Simply use shutdown, then when it appears all disk activity has stopped, close the Vbox window (making sure to power it off). Then click ‘Start’ again to start it up. This is really more of an inconvenience than anything, but it’s manageable.

Updating Mac OS X

As new updates get released by Apple, you may be tempted to install them immediately.  While this shouldn’t be a problem on a real Mac, it is possible that a security or full update from Apple could break VirtualBox installations accidentally (or, more likely, intentionally).  Since Virtualbox offers snapshot capabilities, I recommend taking advantage of this and do the following:

  • Cancel any updates
  • Shutdown Mac OS X
  • Take a snapshot of your Mac OS X Guest in the Virtualbox console
  • Start up Mac OS X
  • Update OS X

If the update causes your system to stop booting, stop working or in any way become broken, you can revert to the snapshot and not update.  On the other hand, if the update works perfectly, then I recommend you delete the snapshot once you feel comfortable that the update is working as expected.  If the update doesn’t work, you may need some updated components such as the Chameleon boot loader or an updated boot disk to handle the new OS update.

Notes

* I suggest using a VMDK HD image as there are more tools for VMDK format files than VDI files. Though, your choice. If you want to use a VMDK file, go to vmcreator.com and have them make you a file to download.

** VirtualBox’s EFI works, but not with Mac OS X. Whether that’s intentional is unknown. Instead, you need to use the Empire EFI ISO disk to boot Mac OS X to install it.

*** You may have to enable VT-x/AMD-v in your machine’s BIOS.

**** Click the ‘Add’ button in the Media Library window to locate your ISO image, then make sure this file is selected and click ‘Select’.