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.

Issue with server side rendering

Home Forums Bug Reports and Feature Requests Issue with server side rendering

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #30223
    Yorick
    Customer

    Dear Verge,

    We are running into problems implementing Server Side Rendering with Verge3D.
    The model is running fine locally and in our application online.
    But when running on our server (both private hosting and on Amazon EC2).
    Some aspects of the model are not shown correctly.

    You can see an example where it goes wrong here:
    https://drive.google.com/file/d/1kfqS9FKZYj6vWeV6dioZKjSN8XkXLeAh/view?usp=sharing

    This video is taken on an Amazon EC2 instance with GPU (https://aws.amazon.com/blogs/aws/now-available-ec2-instances-g4-with-nvidia-t4-tensor-core-gpus/).
    The result of chrome://gpu is attached as a PDF. No clear errors in the console.
    Version of verge: Verge3D 2.17.1 (WebGL 2.0)

    Our 3D engineer will share the used files in a couple of hours.
    Please advise on how we can get this working correctly.

    Attachments:
    You must be logged in to view attached files.
    #30225

    Hi,
    Have you considered a Z-fighting issue? Perhaps your surfaces are located too close to each other or you have a large camera distance range (try to increase camera near and/or decrease camera far distance).

    Verge3D’s Tech Chief
    FB | Twitter | VK

    #30232
    dragosburian
    Customer

    Hello Alexander,
    Here is the blend file used for exporting the scene Yorick presented, regarding Z fighting, I did try changing the camera range and even increasing the thickness of windows significantly(50 times) in order to eliminate that possibility. The issue persisted, I am also attaching another example of how the image gets warped, where not just faces close to each other fail to render properly. Please let me know if you need anything else, we are really looking forward to fixing this.
    https://drive.google.com/file/d/1AfkcHHTFoXJ2CMlqo9R0PHnIesvbxGZS/view?usp=sharing
    Dragos

    • This reply was modified 1 year, 3 months ago by dragosburian.
    Attachments:
    You must be logged in to view attached files.
    #30237

    Thanks for the file. I still believe it can be z-fighting issue. I’ve reproduced it on my computer with Nvidia GPU. Try to increase your camera near distance to 1 meter.

    Attachments:
    You must be logged in to view attached files.

    Verge3D’s Tech Chief
    FB | Twitter | VK

    #30248
    Yorick
    Customer

    Thanks for the hint Alexander, we’ll look into it.
    But how come this happens on our servers and not locally? Should they not render the same?

    Could it have something to do with Rasterization that is on that server “software only” in chrome?

    #30253

    No, the most important line in your GPU report is “WebGL: Hardware accelerated”, while rasterization is used to draw various HTML elements on the page.

    Most frequently, such difference occurs because various hardware has different depth buffer precision (the WebGL/OpenGL spec allows such situations).

    Verge3D’s Tech Chief
    FB | Twitter | VK

    #30478
    Yorick
    Customer

    Thanks, great support Alexander!

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