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.

Possible Error in removeEventListener (Verge3D 4.10)

Home Forums Bug Reports and Feature Requests Possible Error in removeEventListener (Verge3D 4.10)

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #85734
    Thomas Fabini
    Customer

    Hi guys,

    since I upgraded to 4.10 (which I need for compatibility with Blender 3.6 and older Projects)
    it seems that i can’t remove event listeners which were added with the ‘add event listener with callback’ puzzle.

    ‘remove event listener with callback’ puzzle seems broken.
    In function ‘removeEventListener’ ‘_pGlob.customEvents._listeners’ seems to return always undefined.

    const customEL = _pGlob.customEvents._listeners;
            if (customEL && customEL[type]) { ...

    I’ve came to check this because after updating a project, event listeners kept firing multiple times which they hadn’t in 4.9.0 (as far as I recall).

    Thanks,
    Thomas

    #85742

    Hi Thomas,
    Indeed this is a bug due to internal “_listeners” array being wrongfully exposed to Puzzles. We’re going to fix this in the upcoming Verge3D update. Thanks for the report!

    Soft8Soft Tech Chief
    Want more Verge3D updates? Follow me on X, Facebook, or LinkedIn

    #85745
    Thomas Fabini
    Customer

    Hi Alexander,
    Thank you for confirming this.

    Since 4.10 is the last version of Verge3D which is compatible with Blender 3.x could you update this version, too, keeping compatibility with older projects as the last up-to-date version for 3.x projects?

    In 4.10 you added support for unique id’s, objects and animations both, which I’m missing in 4.9.2. (there are workarounds, but having the puzzles is certainly more elegant).

    Ah – and merry Christmas and happy holidays to you and the team!
    Thomas

    #85768

    Hi and Merry Christmas,
    Unfortunately, it’s against our company policy to issue fixes for outdated releases. The only workaround I can suggest (works for both 4.10 and 4.11) is to open visual_logic.js after saving it in the Puzzles editor and replace _pGlob.customEvents._listeners by _pGlob.customEvents.t just in one place.

    Soft8Soft Tech Chief
    Want more Verge3D updates? Follow me on X, Facebook, or LinkedIn

    #85911
    Thomas Fabini
    Customer

    Hi Alexander, a happy and successful New Year 2026 to you and the Verge3D Team!

    Thank you for you reply and the workaround you are proposing.
    The company policy and the reasons for not updating an outdated version, I understand. In this particular case I’m not really happy about the repercussions, but I respect it since it’s necessary from a developers point of view.

    Regarding the workaround you are proposing – that is too risky for production and working in a team. Each single export needs to be checked, each time when saving the error creeps back in.
    I’m considering working with a modified puzzles script (which at least is a one-time change per installation) until older projects are finished and we are able to move to a current version of Verge3D.

    Thank you,
    Thomas

    #86131

    This bug has been fixed in Verge3D 4.12 pre1. Feel free to check!

    Soft8Soft Tech Chief
    Want more Verge3D updates? Follow me on X, Facebook, or LinkedIn

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