News for hackers. Stuff that matters.
Re:Vision Pro: What we got wrong at Oculus that Apple got right by devit on Friday March 15, 2024 @10:51PM (#39722929)
To support copy&paste all you need is a common format for 3D objects, like HTML is for 2D documents; glTF might be a reasonable candidate.

The problem with the Apple approach is that there are no apps and games, and there probably won't be many given it's a 3500$ device with few users that Apple exerts its tyrannical grip over (or if there will be, they will be ports of Unity/Unreal, PC or Android VR apps, not using any of the special features that the Apple OS may have).

Re:Vision Pro: What we got wrong at Oculus that Apple got right by kevindamm on Friday March 15, 2024 @11:14PM (#39723050)
Any scene description format would work (but please not obj or stl), it would be good to see a standard emerge for this, though. USD might be it.
Re:Vision Pro: What we got wrong at Oculus that Apple got right by chris37879 on Saturday March 16, 2024 @12:04AM (#39723297)
I really hope USD is not it. Having worked with it trying to build stuff for the vision pro, it's a massive software library pretending to be a file format. It is inexorably linked to the source code that processes it to the point that making a processor for the format is a non-starter, and that seems to be by design.

The codebase is dense, hard to compile, using outdated dependencies, and doesn't play nice with anything else. Documentation is sparse, often incorrect, and severely lacking in anything like a new user guide. Everything assumes you work for Pixar already and know the ins and outs of their pipeline.

Re:Vision Pro: What we got wrong at Oculus that Apple got right by TylerE on Saturday March 16, 2024 @01:12AM (#39723548)
People have been trying to solve this problem since the VRML days in the '90s. I suspect you are underestimating the complexity of 3D data by a pretty huge extent.

3D is much, much, much more complicated than 2D, especially if you're trying to interchange between arbitrary applications that may have divergent needs.

Start with this little thought experiment.

What do you mean by 3d object?

Do you mean a set of polygons, like in a traditional triangle mesh? A volume, like voxels? A set of 3d surfaces?

Do you need to model interior details, or only the exterior envelope? Do you need to be able to split or explode it at some arbitrary level of detail? Do we need to encode sharp edges or creases in some way?

etc, etc, etc

This is before you have touched materials, texturing, lighting, any of that.

Re:Vision Pro: What we got wrong at Oculus that Apple got right by uxcolumbo on Saturday March 16, 2024 @03:01AM (#39723893)
Stupid question… isn’t all that wrapped in a container?

Like in HTML with divs? So if you have a virtual lamp you want to copy, all the various elements that make up the lamp are in a VR equivalent object markup as <div id=‘lamp’ />. If you want to copy specific elements you can, but you’d have specific actions, e.g copy color etc.

Maybe I’m missing something though and it’s more complex.

Re:Vision Pro: What we got wrong at Oculus that Apple got right by TylerE on Saturday March 16, 2024 @03:48AM (#39724050)
Don’t think about tag soup. Think about how you’d encode the geometry, and what that even means for anything but the most trivial object, like a cube.
Re:Vision Pro: What we got wrong at Oculus that Apple got right by polyomino on Saturday March 16, 2024 @03:49AM (#39724057)
Ok now, I have a few separate colored lights pointing at the lamp. What color is the lamp? How about when it’s on?
Re:Vision Pro: What we got wrong at Oculus that Apple got right by richardw on Saturday March 16, 2024 @05:59AM (#39724566)
Interesting. I assume you’d copy the object not the lighting. If you move a real object into a different room or outside you don’t expect the colour to stay the same. But if I’m pasting it into a word doc, I guess intuitively I might want it to look the same as source, but that breaks down unless I copy the whole virtual universe. A mirrored globe inside a room of mirrors is not going to look the same unless I copy the scene. People will learn this and maybe demand eg a choice of the copy scope. You might not even have rights to copy all objects. I can’t just copy your palace and paste it into mine unless you allow it (say).
Re:Vision Pro: What we got wrong at Oculus that Apple got right by TylerE on Saturday March 16, 2024 @06:48AM (#39724751)
That’s the entire crux. What exactly the hell is “the object”, and how does your target program DO anything to it, to include manipulating it, or getting it out to a GPU for rendering in some even vaguely terrible way - and you’re probably trying to render it 120 times (or more) a second with a decent level of resolution.

3D is not like tabular data. There isn’t some default resting state it naturally wants to exist in. It’s all edge cases and special logic. Also, it’s mind bogglingly vast amounts of raw data. Even a simple scene can contains hundreds of thousands of surfaces/polygons/spline patches/voxels/whatever representation.

A VR environment is essentially running a high end 3d game engine at all times.

Re:Vision Pro: What we got wrong at Oculus that Apple got right by uxcolumbo on Sunday March 17, 2024 @05:36AM (#39733106)
Isn't this already a solved problem? See 3D apps, i.e. Blender, Unity, Unreal etc. You can copy objects easily.

I don't think the intention is to copy an object with the baked in lighting at the time of making a copy. I can imagine you just want to copy the object and the behavior how it reacts to whatever environment it's placed in.

Re:Vision Pro: What we got wrong at Oculus that Apple got right by TylerE on Sunday March 17, 2024 @07:59PM (#39739156)
Not between them.
Re:Vision Pro: What we got wrong at Oculus that Apple got right by araes on Saturday March 16, 2024 @01:41PM (#39727863)
The basic math is also dramatically worse, and much more challenging for entry level participants to grasp. The basic idea of matrix math grows dramatically more complex just in terms of sheer number operations. You might be able to get away with your entire app only needing a couple mults or adds for most interaction in 2D. Basic 3D, closer to 150 mults (usually 3 [4x4] mults at 49 mults per [4x4] pair) for the default.

In 2D apps and games, you can often get away with incredibly simplistic calculations. Rarely much other than a translation. Many times 1D with naively obvious solutions. With 3D, you rapidly need to move to 4D matrices than can handle arbitrary scale, translate, rotate, perspective, clip volumes.

Nearly every 3D app anywhere has to handle the model, to world, to camera, to clip space path, which involves a lot of complex math well beyond most 2D apps. Usually, 3 different matrix mults with 4x4 matrices.

  v_world     = M⋅v_model
  v_camera  = V⋅M⋅v_model 
  v_clip    = P⋅V⋅M⋅v_model  

  v_clip   = [[P00,...,P30],[...],[...],[P30,...,P33]] ⋅ [V00...V33] ⋅
             [M00...M33] ⋅ [m00...m33]
It's one of the main reasons voxels have been the only real 3D implementation with large scale use. The amount of work necessary to develop, ... really anything that works with 3D is a large step upward in difficulty unless its totally regular and square. Otherwise, huge numbers of optimizations are no longer available. Plus, the compression cliff for normal users of effectively arbitrary 3D shape design and movement is really steep. Most first time users of an industry 3D CAD package (ProE, Solidworks, AutoCAD, Maya, 3DSMax, Blender, ect...) or similar have the "wall of difficulty" moment.

Edited: dumb math error

Re:Vision Pro: What we got wrong at Oculus that Apple got right by baby on Saturday March 16, 2024 @04:32AM (#39724241)
^ exactly this. The problem with the Vision Pro is that there is nothing to do, whereas the Quest 3 is driven by cool experiences
Re:Vision Pro: What we got wrong at Oculus that Apple got right by sunshinerag on Saturday March 16, 2024 @05:02AM (#39724355)
Tyrannical grip on users who paid 3500$? That indicates no understanding of said users.
Re:Vision Pro: What we got wrong at Oculus that Apple got right by brookst on Saturday March 16, 2024 @11:01AM (#39726528)
“This all inclusive resort has a tyrannical grip on all the poor visitors who spent $10k to travel and stay at an all-inclusive resort!”