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.
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.
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.