We have just released Shapespark 3.6.0 with the following improvements:
HDR sky textures can now be used as a light source when baking a lightmap.
Added procedurally generated clouds for the Hosek-Wilkie sky model.
Easier interaction in VR: controllers are now visible and can be used to point and interact with the scene.
Added collisions in VR when moving with a controller’s thumbstick. Controllers will also vibrate when they or the camera collide with the scene geometry.
When viewing the scene on a VR headset, VR mode starts automatically.
Added the SwitchScene extension, which allows for easy switching to another Shapespark scene.
Reduced Z-fighting artifacts when viewed in Chrome on PCs.
Fixed mesh collisions not being updated after changing their visibility from external code.
Fixed materials dragged onto objects having broken UVs after upload.
Added a vertical offset parameter for the sky horizon.
Improved draft baking performance on larger scenes.
Improved the appearance of reflection material ball previews.
Improved initial camera positioning on imported scenes.
Hi, does the reflection probe update work with custom html yet? I was trying today and couldn’t seem to get it to work with Material.baseColorTexture changing. when I do Viewer.requestFrame(), do I need to add in a Viewer.updateReflectionProbes() or some command to get the reflection probes to update?
Hi,
Currently, reflection probes are only updated when materials are changed through the MaterialPicker extension or when objects are switched using the ObjectSwitch extension.
ViewerAPI has a function setMaterialForMesh(material, mesh), which when called for a specific mesh, should trigger a reflection probe update for all probes visible from it. However, this behaviour is not officially supported. If you write custom code that relies on this function, it might break in a future update.
We are planning a new ViewerAPI, which will be more comprehensive and should also officially include what you’re asking for. But we cannot provide an ETA for its release at this time.
The [BoundingBox] switch in [ReflectionProbes] isn’t working. Even when I turn the switch off,
it always appears as if it’s ON in the scene. I wonder if this changed in update.
Indeed, there is a bug involving reflection probe bounding box switch introduced in 3.6.1 .
We will fix it in the next release.
For now the simple workaround is to set bounding box min & max coordinates to very large numbers (like -9999 for min and 9999 for max). It should have the same effect as disabling the bounding box altogether.
3.6.1 was already released, on 18th May.
This problem which you mentioned will be fixed in 3.6.2 or 3.7.0.
Unfortunately I can’t say right now when we will release the next version.