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.

export / loading fails with specific node setup

Home Forums Bug Reports and Feature Requests export / loading fails with specific node setup

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #60960
    thomasup
    Customer

    we have a very specific issue with a node setup that no longer exports in verge 4.2.0 and blender 3.4.1:

    the file did export in earlier version, but not in the current version. we narrowed it down to the nodes used by the decalmachine shader.

    i couldnt find the specific node causing the issue, but it seems to be somewhere in the parallex effect. attached file only contains the material causing the error:

    TypeError: Cannot read properties of undefined (reading 'name')
        at v3d.js:1:925848
        at _u.updateNodeGraph (v3d.js:1:925999)
        at new _u (v3d.js:1:937542)
        at v3d.js:1:1278946
        at async Promise.all (:8668/player/index 0)
        at async Promise.all (:8668/player/index 0)
        at async Promise.all (:8668/player/index 0)
        at async Promise.all (:8668/player/index 0)
        at async Promise.all (:8668/player/index 0)
    (anonymous) @ v3d.js:1
    player.js:57 Can't load the scene /sneak_peek/sneak_peek.gltf

    tested in chrome 110.0.5481.178 on windows 10

    Attachments:
    You must be logged in to view attached files.
    #60962
    thomasup
    Customer

    exporting from blender 3.3.4 LTS also does not work:

    v3d.WebGLProgram: shader error: 0 35715 false gl.getProgramInfoLog Fragment shader is not compiled.

    Edit: it does export correctly, when the file has not been opened with blender 3.4 before. so a “clean” 3.3 file works.

    #60966
    kdv
    Participant

    Fix nodes replaced by Blender 3.4.1 before exporting

    Puzzles and JS. Fast and expensive.

    If you don’t see the meaning in something it primarily means that you just don’t see it but not the absence of meaning at all.

    #60980
    thomasup
    Customer

    true, that will fix the exports. but it is hard to fix all the nodes by hand.

    we will roll back the versions, and sticking to blender 3.3 as of now, and await the next verge release!

    #60982
    kdv
    Participant

    It was the right decision )))

    Puzzles and JS. Fast and expensive.

    If you don’t see the meaning in something it primarily means that you just don’t see it but not the absence of meaning at all.

    #60984

    Thanks for reporting this! We’re going to fix this issue in the upcoming Verge3D pre-release (scheduled for the next week).

    Soft8Soft Tech Chief
    FB | Twitter | LinkedIn

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