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.

EXTURE_CUBE_MAP_POSITIVE_X level 0 is incurring lazy initialization

Home Forums Bug Reports and Feature Requests EXTURE_CUBE_MAP_POSITIVE_X level 0 is incurring lazy initialization

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #21977
    GLiFTeK
    Customer

    Error: WebGL warning: generateMipmap: Tex image TEXTURE_CUBE_MAP_POSITIVE_X level 0 is incurring lazy initialization. v3d.js:1:533735
    Error: WebGL: No further warnings will be reported for this WebGL context. (already reported 32 warnings) v3d.js:1:533735
    TypeError: asm.js type error: Disabled by debugger

    i just finished a pretty challenging scene setup.
    figured out how to select only specific values of a vertex color..
    i had previously set up a system where one object had certain parts vertex colored 100% red, 100% blue etc.. and i could change opacity of those parts based on that.
    but being limited to 3 groups (colors) was too little.

    so i set this scene (attached) where you can set whatever decimal space value of one color of vertex paint.
    ie: there are 3 blue boxes in this scene.. one with all of it’s vertexes at 0 red, 0 green and 0.3 blue, the next box is 0.6 blue, next 0.9.

    using the color ramp node, and selecting just those values.. i was able to control the boxes visibility
    pretty cool!
    i was so psyched that i had come out victorious after hours and hours of trying different things (greater/less than) etc…
    so excited to implement it into my project which i’d made it for…
    but yeah…
    no dice…
    won’t work in verge3d

    the scene shows up.. just the opacity doesn’t work for some reason.
    bummer.

    anyway.. those are the error messages i got, up there.
    the blend file is attached.
    (also i typed “vector paint” i meant “vertex paint”

    all the nodes in this pic are supported. i don’t know what went wrong.
    s

    • This topic was modified 2 years, 8 months ago by GLiFTeK.
    Attachments:
    You must be logged in to view attached files.
    #21981
    GLiFTeK
    Customer

    woops this is just background messages.. i have them in another project.. doesn’t have anything to do with the opacity issue.

    i’m experimenting with doing the same thing with UV’;s.. working but not with one material over many objects. (must click 3 times for the 3 objects.)

    #22243

    Hi! Sorry for slow reaction. So is there an issue for us to look into, or everything works just fine?

    Chief 3D Verger | LinkedIn | Twitter

    #22462
    GLiFTeK
    Customer

    Hi! Sorry for slow reaction. So is there an issue for us to look into, or everything works just fine?

    i always get the TEXTURE_CUBE_MAP_POSITIVE_X level 0 is incurring lazy initialization.
    error message like 16-32 times per project.
    have come to ignore it.
    this was a confusion of that with something else..
    nothing concerning what i originally thought in this post.

    #22465

    i always get the TEXTURE_CUBE_MAP_POSITIVE_X level 0 is incurring lazy initialization.
    error message like 16-32 times per project.

    got a mini-blend file to look into?

    Chief 3D Verger | LinkedIn | Twitter

    #51487
    yogyog
    Participant

    I’m getting a lot as well.

    Is this a resault of using cubemaps?

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