Yes the WebVR API access can be broken into the current release.
We are looking forward to make it in a cleaner way for the next release with the use of the latest Three.js WebVR implementation which will avoid a concurrency between the ForgeJS implementation and the Three.js one.

Sorry for the delay.
I was working on other products and I've not made any progress in this area.

Sorry for the answer delay.
So you would like to display a hotspot with a go to next scene action when a video scene media is ended?

You want to stop a video playback only or do something else?
There are also many destroy methods if you're looking after a removal.

Hi and sorry for this answer delay. You have to instanciate the editor plugin into your project like this: { "story": { ... }, "plugins": { "prefix": "../../plugins/", "engines": [ { "uid": "org.forgejs.editor", "url": &...

Is it possible to have a look to your config.json file to test it ? Thanks

Thanks for the report I open an issue and it will be verified.

Hotspots are not supported on flat view at this time.

Hi Nicolas,
I'll have a look on it asap.
In fact our HLS quick implementation based on hls.js is using the default HTMLVideoElement so it's more easier than the MediaPlayer of dash.js to access audio tracks.

The compatibility hasn't been applied yet. Only HTML5 video are ambisonics compatible for the moment. If you have an ambisonic DASH stream I can give a look on next days to see if it's possible easily. HLS has been pushed for validation today on the repository. It will be more simple to do it with i...