My virtual tour is not smooth on Chrome

  • I've been having a problem for the last couple of months because my virtual tour isn't smooth on Chrome. It's very slow and stuck, and it looks like there's a problem with the graphics card.
    I installed the latest graphics card drivers, and at the same time everything works smoothly on the Mozlla browser.
    I tried to reinstall Chrome, but no changes. What could be the problem?
    Planinarenje.ba - Panorame 360°

  • Hi,

    I can reproduce that in my Chrome browser too, the browser is extremely slow.
    Firefox and Safari are fine.

    There are a lot of html elements, especially the thumbnails and that 'menu list' and it seems these make Chrome slow.

    When dynamically removing the html elements of that menu via the Chrome developer tools (Elements => select the <div> of the menu => and remove it) the browser becomes instantly faster again.

    Alternatively it would also help making the 'menu_line' <layer> invisible when not needed.
    Currently that layer is always visible, but only scrolled-out.

    E.g. just calling:

    Code
    set(layer[menu_line].visible,false);

    also makes the browser instantly faster again.
    (a visible=false results in css display=hidden)

    But that means that this is some strange problem in Chrome itself.
    It's either the high number of html elements or the size/dimension of the containing html elements.
    In any way the browser performance should got that down.

    That would be a good case for posting it in Chrome bug-tracker here:
    https://bugs.chromium.org/p/chromium/issues/list

    This is really something that should be addressed by the Chrome developers.

    Manually working around that would be possible, but that would mean a different tour management, e.g. by grouping scenes somehow to avoid showing too much thumbnails/menu-items at once.

    Best regards,
    Klaus

  • That is all in your menu_bottom.xml:
    https://planinarenje.ba/panorame360/menu_bottom.xml

    But it's not that easy to say how to modify that...

    I would say it should be added always after this call:
    set(layer[menu_outer2].state,'closed');

    and before opening the menu it should be set back to visible=true.


    But better post this example in the Chrome bug-tracker.
    A fix in Chrome itself would be better.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!