We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.

Ok, I Agree

Debugging

Home › Forums › Programming › Debugging

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • 2019-08-13 at 8:48 am #17799
    loom
    Customer

    Hi,

    do we care about this error in chrome console ?

    v3d.js:1 [Violation] Added non-passive event listener to a scroll-blocking ‘wheel’ event. Consider marking event handler as ‘passive’ to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952

    just wondering if we could ignore it ?

    Cheers,
    Chris

    2019-08-13 at 11:52 am #17804
    Yuri Kovelenov
    Staff

    Hi,

    Can this error be seen in some of Verge3D demos as well?

    Chief 3D Verger | LinkedIn | Twitter

    2019-08-13 at 12:20 pm #17806
    Yuri Kovelenov
    Staff

    I see them now – you must have enabled Verbose level in Chrome console. Nevertheless, I think it is worth looking deeper into those warnings. Thanks for heads up!

    Attachments:
    You must be logged in to view attached files.

    Chief 3D Verger | LinkedIn | Twitter

    2019-10-08 at 10:19 am #19958
    mugga
    Participant

    I also got this warnings in chrome and the wheel event doesnt work for me. Is there a workaround?

    Update:
    It is working but not when scrolling/zooming in webgl. How can I fire and event when zooming? The “each frame” function is producing to much overhead for me, I would like to execute some functions when zooming.

    2019-10-08 at 2:35 pm #19967
    Yuri Kovelenov
    Staff
    mugga wrote:

    The “each frame” function is producing to much overhead for me

    you can possibly only check the distance to the camera every frame, and perform other operations only if the distance changed

    Chief 3D Verger | LinkedIn | Twitter

    2019-10-08 at 3:28 pm #19972
    mugga
    Participant

    Ah okay, yeah this should work.

    2020-04-01 at 10:33 am #25220
    web
    Customer

    I’m in the middle of trying to optimize performance for animation of geometries etc. And also came across the “non-passive event listener” warning and also “setTimeout handler took <N>ms”.

    Did you already worked on the event listeners optimization?

    2020-04-01 at 2:39 pm #25233
    Yuri Kovelenov
    Staff

    Hi,

    these are ‘normal’ warnings which relate to blocking the main thread by 3D rendering.

    Here is some advice on boosting the rendering up
    https://www.soft8soft.com/docs/manual/en/introduction/Optimizing-WebGL-performance.html

    Chief 3D Verger | LinkedIn | Twitter

  • Author
    Posts
Viewing 8 posts - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.