Linking items to photo/video dome

Beginner, so bear with me here. I was wondering how this: was achieved in babylon.js. Specifically, the little tags that are seemingly attached to the photodome. There’s a tutorial written by the fellow who made that here(, but he stops just short of explaining how to make those tags that stick to the dome.

From what I can tell you can link advanced dynamic texture to a mesh, but I don’t know where there are meshes on the domme. Thank

Hi @iblis these are Babylon.js GUI elements. See the docs here Use the Babylon GUI - Babylon.js Documentation

There’s a Playground example on that page showing exactly the technique you’re after:

Sorry but no, that is not what I’m looking for. As mentioned in the OP, I recognize that you can link an advanced dynamic texture with a mesh; in the link you sent the mesh would be the sphere. In the case of a dome I don’t see any meshes to attach to. Again, take a look at the first link in the OP to see what I mean. That is the problem I’m trying to solve.

According to the “tracking positions” part of the docs, yes you can link to a mesh or use control.moveToVector3().

In the case of tracking meshes you could create empty mesh “markers” at the locations on the surface of the dome you want to track. You’d need to convert map locations (latitude and longitude) of each point on the globe to XYZ coordinates.

You can create an empty mesh like this:

var globeMarker = new BABYLON.Mesh("globeMarker", scene);
globeMarker.position = new BABYLON.Vector3(x, y, z);

Then link your GUI control:

1 Like

Similar discussion and resolution with example here: Labeling ends of tubes

I see, I didn’t know you could make an empty/invisible marker like that, thanks.

I have another question; I’m not sure if it is possible though. Can this marker be adjusted to track through FOV changes?

playground example; if you turn around and look at woman’s face. Say I want to track her nose; the FOV multiplier makes it lose tracking. Is there some way to change the behavior of the texture to match the FOV change?

It’s because your marker isn’t actually on the surface of the dome. It’s much closer to the camera so you get a parallax effect.

1 Like

Right, I noticed that juust as I posted and was going to edit with different playground, sory. See in this example:
It’s somewhat further from camera so no parallax, but the FOV multiplier(uncomment it) induces that effect.

Unless you want to recalculate and move every marker, maybe use camera.fov instead, which should provide a similar effect?


Note, I’ve also moved your marker so it’s the same distance away as the radius of your dome, so it’s exactly on the surface and should always track perfectly.


I considered that, but I hope to use this with the webXR mode. If you have VR device or chrome mozilla webxr emulator you can see from here: that entering VR environment changes FOV back to normal.

From topics in the past it looks like FOV changes with the XRexperience helper is quite cumbersome(How to change FOV of VR Camera?) so I hope to avoid that. One message there says

I’m not familiar with how webVR becomes webXR, so I’m not sure what JCPalmer mean by that statement. Does it mean its not possible to change FOV from application-side in VR mode with webXR? Do you or anyone else have any ideas?

The fov member of camera is used to compute the projection matrix, defined in camera, called in scene, I believe.

The WebXR camera gets its projection matrices (left & right from the hardware every frame), so this field, I believe, has no effect.

1 Like

Ping @RaananW who might have a solution on the VR/XR front but yes the actual fov of the camera can only be the one of the device hence the special multiplier on the dome.

1 Like

What @JCPalmer said is totally correct - FOV is actually ignored in a WebXR camera, since the projection matrices are coming from the browser itself and not calculated by us.

You CAN calculate them yourself, but there is no guaranty as to what the results are. I haven’t tested it, but if you actually unfreeze the projection matrix of the rig cameras of the XR camera, they will be calculated by babylon and the device’s values will be overridden.

1 Like

From the other replies I’ve gathered that camera.fov changes aren’t feasible with the new WebXR, so
I think I’ll stick to the dome fov changes.

This suggests that I can somehow recalculate the marker in response to the dome fov change. I took a look at the source code of backgroundMaterial/photo dome as well but I can’t seem to pinpoint how that can be done. Any idea?