adamabr

Ah, that is a slick solution kdv. Some of my thoughts wandered in that direction, nice to see it working. I liked how I did not need an extra object in the scene the way I did it, but it requires and extra transformation of the camera which you avoid.

Good to have options.

I like how your solution does not move the camera control object at all. I also find your solution for activating snap turn on both left and right movements in one puzzle to be cool.

Ah, good catch kdv! Moving in physical space does not move the camera control object. Rotating the camera control object causes off-axis rotation for the VR camera.

After some pondering I came up with a solution for this by offsetting the camera control object after the rotation by the difference in active camera position. Works great!

Next I’ll also add this offset to the teleport function so that the user always lands on the teleported location rather than the camera control object landing there.

Interesting, I’ll look into that. I guess I was assuming making linked duplicates creates instances meshes?

Example:

I have this bearing I want to try to optimize as much as possible.

The bearing geometry is radially symmetric, however the texture on the front cover is not.

I make a copy of the original and keep only one radial slice of the bearing. Then I instance this so I essentially recreate the whole bearing again.

Shaded mode shows the issues of seams and textures.

Adding the Data Transfer Modifier and enabling custom normals solves the normal issue.

Adding a Data Transfer Modifier and enabling UVs solves the texture issue (in Blender anyway).

So in Blender it looks like we have created a perfect copy this way. Let’s export to Verge 3D.

The normals are transferred properly but not the UVs. Adding a batch geometry puzzle brings down the render calls to the same as the original version.

A reasonable question would be if this is even relevant to do. Is it worth it? (Assuming the UVs work) Here is a comparison of file size.

Only the original exported:

GLTF: 11 KB
Bin: 40 KB
Total: 51 KB

Only the instanced version exported:

GLTF: 22 KB
Bin: 3 KB
Total: 25 KB
Savings: -26 KB (-51%)

So my take is that there are a lot of potential savings here if we can figure this out. What do you think?

• This reply was modified 3 months ago by adamabr.
• This reply was modified 3 months ago by adamabr.

I appreciate the response David! I’ll have to look into this more as I have more time but I am happy I got some input.

Interesting find!

But why does it work using the HTML overlay without clicking the fullscreen button when there is no “when clicked” puzzle?

I find this to be very odd. Does the “when clicked” puzzle affect the focus somehow?

And what workaround could I use?