Can we say that the Meta Quest 3 is the ultimate device? I would say that the new Apple toy can keep it to themselves; a crazy price for an unknown user base, almost non-existent application fields. For example, you can get by with not just a Quest 2, but even a Quest Go (irony aside, some customers still use the Go and continue to deliver virtual training on it).
As for this Meta Quest 3? Let’s start with the information you need; you don’t have to change anything. You can use the SDKs you have set up on Unity, and you and your team can rest assured, even more so. Let’s say that at the end of the ride, you can put your product on the Store and benefit from the performance boost of the Meta Quest 3. However, I suggest starting to think about a qualitative setup for the incoming device.
Let’s try again
Maybe we can afford a few more shadows, a reflection here and there, not bad. Instead, the novelty is mixed reality, much more performant, not at Pro levels (which none of us have bought), but I would say very satisfying. A small reflection, perhaps Quest 3 will really bring mixed virtual training to a level of renewed confidence? Will it be easier to put on a headset than to learn the process itself?
Because the problem is always the same, like hand tracking, cool, but not even on the Meta Store does the user base seem very interested. In fact, the advice we give ourselves is to continue using the controllers even where a more Matrix-like solution might seem to fit better. The reason? The user sees the controller as a convenient and versatile support rather than a limitation in their virtual simulation. Big news, the controllers have greatly improved, convenient even to provide to individuals not technologically educated; let’s hope they don’t break them.
Technical fancy words
Technical specifications? What can I say, very simply, it has a 50% improvement in performance, it has a new generation SnapDragon 2, and the lens resolution has increased. However, at the fair, we must follow these guidelines, namely, continue developing for Quest 2 as the performance target, remembering that at some point we should introduce a way to increase graphic performance in case a Quest 3 is used (perhaps self-configuring?), and forget about Apple’s nonsense; we don’t have all the time in the world