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

Problem with model display under Windows

Home › Forums › Graphics / Blender › Problem with model display under Windows

Tagged: 

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • 2022-04-22 at 10:17 am #51271
    danielbruno
    Customer

    Hello.

    I am developing a product configurator and before launching it I’ll be doing tests on the maximum number of platforms I can have access to. I’m using Verge 3D for Blender 3.91 under MacOS and I had success on MacOS with Chrome, Safari and Firefox. It also performs well under iOS (iPhone and iPad) and Android.

    The problem arises when I use a real Windows machine. Although it is a laptop with dedicated 3D graphics card and with “good performance” as stated by WebGL System Report page, the model doesn’t show (only metallic parts appear although not correctly textured). Curiously, when I test the configurator under a real Windows 10 installation through BootCamp on my MacBook everything works well. Attached you can find the correct expected result and the problematic one under real Windows. Could you please help me with this issue?

    Thanks a lot!

    Daniel.

    Attachments:
    You must be logged in to view attached files.
    2022-04-29 at 9:59 am #51488
    Ivan Lyubovnikov
    Staff

    Hi,

    From the second picture it looks like it may be a shader crash. Can you check the browser console to see if it shows any errors?

    Co-founder and lead developer at Soft8Soft.

    2022-04-29 at 12:41 pm #51494
    danielbruno
    Customer

    Hi Ivan. Here is the output at Chrome’s console:

    Verge3D 3.9.1 for Blender (Trial, WebGL 2.0)
    v3d.js:352 — Verge3D Performance Profile (1s) —
    v3d.js:352 Scene Loading Time: 2888ms
    v3d.js:352 Asset Compression: yes
    v3d.js:352 FPS: 49
    v3d.js:352 Render Calls: 22
    v3d.js:352 Triangles Rendered: 170026
    v3d.js:352 Geometry Buffers: 22
    v3d.js:352 HDR Rendering: no
    v3d.js:352 Viewport Resolution: 766×700
    v3d.js:352 Pixel Ratio: 1 (current) / 0.8333333730697632 (device)
    v3d.js:352 Image-Based Lighting: Light Probe + Cubemap 512px
    v3d.js:352 Lights: 1
    v3d.js:352 Reflection Probes: 0 (cube) / 0 (plane)
    v3d.js:352 Post-Processing: Render,Copy/Other
    v3d.js:352 Shadow Map: N/A
    v3d.js:352 Materials and Shaders: 8
    v3d.js:352 Material_0 – MeshNodeMaterial – 3.4ms
    v3d.js:352 01 – Alpine White – MeshNodeMaterial – 0.7ms
    v3d.js:352 14 – minau – MeshNodeMaterial – 0.3ms
    v3d.js:352 metal pés – MeshNodeMaterial – 0.1ms
    2v3d.js:352 Verge3D_Environment_EasyHDR – MeshNodeMaterial – 0ms
    v3d.js:352 BackgroundCubeMaterial – ShaderMaterial – 0ms
    v3d.js:352 System Material – ShaderPass – 0ms
    v3d.js:352 Total Render Time: 4.5ms
    v3d.js:352 Textures & Render Buffers: 10
    v3d.js:352 Wood017_2K_Color.png.001 – Texture – 1024×1024
    v3d.js:352 Material_0_normal.jpeg – Texture – 1024×1024
    v3d.js:352 Material_0_baseColor.jpeg – Texture – 1024×1024
    v3d.js:352 Material_0_metallicRoughness.png – Texture – 1024×1024
    v3d.js:352 cayley_interior_1k.exr – Texture – 1024×512
    v3d.js:352 N/A – WebGLRenderTarget – 1024×1024
    v3d.js:352 EffectComposer.rt1 – WebGLRenderTarget – 766×700
    v3d.js:352 EffectComposer.rt2 – WebGLRenderTarget – 766×700
    2v3d.js:352 N/A – WebGLRenderTarget – 512×512

    Thank you.

    2022-05-07 at 2:52 pm #51794
    Nurgeldi Dovletov
    Staff

    Hi!
    It will be better to use Verge3D 4.0 pre4 or you can also wait for the official release of Verge3d 4.0.

    Verge3D Developer

    2022-05-14 at 9:24 am #52048
    danielbruno
    Customer

    Hi Nurgeldi.

    The display issue under Windows was solved using 4.0-pre version.

    Thanks for the tip!

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