Hi Jordi, Thanks for the reply, but I'm not sure I follow on using resetsensor - what's the flow after the onclick event? thanks! Edit: Well, I tried using webvr.resetSensor( {next scene's starting view point} ) but what still ends up happening is the current pano switches to the next hlookat before the transition.

I've tried applying the following flags for my WebVR experiences, KEEPVIEW|MERGE, but when I transition from one scene to another, the view is defaulted to what is set in the <scene> hlookat and vlookat. I made a custom orientation function that has the proper linkedscene vertical and horizontal position, but when I use that, the orientation changes happens before the transition starts. Meaning, the current view changes to what would be the correct orientation in the next scene. Is this the expe...

I noticed that when the navigation to the next scene is triggered, the krpano element collapses before the next scene is loaded causing the flash/flicker effect.

When I navigate from one scene to another, there is flash or flicker of black before the blend mode transition happens. I've found this to only happen in Chrome, but not in Firefox. I am using krpano 1.19 r3 and only the HTML5 viewer. Here's the scenario: Click next scene button > Screen goes black > Fades out > Previous scene still viewable then fades to new scene I'm using the sample vrtourskin.xml with the following skin settings: <skin_settings maps="false" maps_type="bing" maps_bing_api_key...