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.

ERROR: 0:2440: 'node_vect_math_dot_product'

Home Forums Bug Reports and Feature Requests ERROR: 0:2440: 'node_vect_math_dot_product'

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #21543
    GLiFTeK
    Customer

    Browser CONSOLE ERROR message(S):
    ” v3d.WebGLProgram: shader error: 1282 35715 false gl.getProgramInfoLog Must have an compiled fragment shader attached. ERROR: 0:2440: ‘node_vect_math_dot_product’ : no matching overloaded function found ”

    ” v3d.WebGLShader: Shader couldn’t compile. ”

    ” v3d.WebGLProgram: shader error: 1282 35715 false gl.getProgramInfoLog Must have an compiled fragment shader attached. ERROR: 0:2507: ‘node_tex_musgrave’ : no matching overloaded function found ”

    Browser/operating system: e.g. Chrome 73 / Window 10, Safari / iOS 12
    Firefox 70.0.1 (64-bit) Windows 8.1
    Version 2.17.0pre1
    Blender 2.81

    What steps will reproduce the problem?
    using Dot Product in Math Node(?)

    What is the expected result?
    the copper metal texture should show as usual

    What happens instead?
    object with material does not show, error message in console appears

    NOTE: i’ve never voluntarily used “Dot Product” as a math node on my own.
    It IS, however, a node in a group node setup i use in a few materials which i downloaded from BIS (Blender Interplanetary Storage) https://b3d.interplanety.org/en/bis-online-blender-material-storage/
    I use these materials often, with no problem.
    not sure why it may be causing a problem.
    (maybe this is not the source of the problem?)

    EDIT: tried it in blender 2.80 and verge 2.16
    same problems.

    • This topic was modified 2 years, 12 months ago by GLiFTeK.
    • This topic was modified 2 years, 12 months ago by GLiFTeK. Reason: verge / blender versions
    • This topic was modified 2 years, 12 months ago by GLiFTeK.
    • This topic was modified 2 years, 12 months ago by GLiFTeK.
    #21554

    Hi,

    this issue has been fixed in 2.17 pre1. Make sure you have updated the engine runtime to 2.17 for your application (by clicking the update button in the App Manager).

    Chief 3D Verger | LinkedIn | Twitter

    #21560
    GLiFTeK
    Customer

    Hi,
    this issue has been fixed in 2.17 pre1. Make sure you have updated the engine runtime to 2.17 for your application (by clicking the update button in the App Manager).

    Fantastic.
    All fixed.
    thanks!
    :good:

    #21588

    great!

    Chief 3D Verger | LinkedIn | Twitter

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