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

Issue with v3d.module.js 4.8 WebGLRenderer

Home › Forums › Bug Reports and Feature Requests › Issue with v3d.module.js 4.8 WebGLRenderer

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • 2024-11-15 at 5:37 am #78771
    qiangge
    Participant

    When developing with v3d 4.8, I encountered rendering issues. When using THREE.WebGLRenderer(), the rendering works fine, but when I switch to v3d.WebGLRenderer, the rendering is incorrect. In the first heatmap example, the shader material doesn’t display, but no errors are reported. When using the Luma Gaussian model, it prompts that the shader code snippet is missing, etc.

    • This topic was modified 1 month ago by qiangge.
    • This topic was modified 1 month ago by qiangge.
    • This topic was modified 1 month ago by qiangge.
    Attachments:
    You must be logged in to view attached files.
    2024-11-15 at 5:39 am #78773
    qiangge
    Participant

    heat RightLink

    luma righLink

    • This reply was modified 1 month ago by qiangge.
    • This reply was modified 1 month ago by qiangge.
    • This reply was modified 1 month ago by qiangge.
    Attachments:
    You must be logged in to view attached files.
    2024-11-15 at 6:02 am #78784
    Yuri Kovelenov
    Staff

    Hi qiangge,

    Verge3D broke with Three.js code base long time ago so there can be many incompatibilities with recent Three.js code. We are still cherry-picking Three.js features from time to time, if we consider them really important for the Verge3D pipeline which is based around the artist. Not sure about any JS API though. :scratch:

    Chief 3D Verger | LinkedIn | Twitter

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