We’re planning on removing the “resolution” property from Web3DOverlays and changing how their “dpi” property works so that they match web entities. If you are using Web3DOverlays, it is likely that this change will affect their dimensions. You should be setting the dimensions of the overlay (in meters, as per usual), and then fine tuning the dpi as desired. If you change the dimensions of the overlay and want the web surface to scale accordingly, you’ll need to update the dpi, too.
This change will be made in this PR, but we wanted to give you a heads up: https://github.com/highfidelity/hifi/pull/11847
Currently, the way these properties work is:
- dpi does not actually affect the resolution of the surface. Instead, a higher dpi will just make the overlay smaller.
- resolution both changes the actual resolution of the surface and the dimensions of the overlay.
- the rendering bounds of the overlays do not properly match their visual bounds. This means that sometimes a web overlay will disappear while it is still in view.
After the change:
- resolution is removed
- dpi correctly corresponds to “dots per inch.” If an overlay is 1 inch x 1 inch with a dpi of 30, it will be 30 pixels x 30 pixels.
After the change, by setting the dimensions and dpi of a web overlay, you’ll still have full control over the pixel resolution of the surface.
I know Fluffy and HumbleTim were experimenting with web overlays, but I am not aware of any other content that uses them. If you have any questions or concerns about this change, let us know!