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.
It may be that the node group consists of nodes that are not yet supported (or not fully supported) by Verge3D. You could try to simplify that shader by removing / replacing unsupported nodes.
Can’t it be that the path to Verge3D is specified incorrectly? Please note that the repository path should end with “addons”, not “addons/verge3d”. To make sure you might try to remove the repository and add it again.
We got an older Samsung Tab S7 – the demo plays smoothly, except when one tries to interact with the scene, it flickers because of touch event causing the video to reload. Or is it flickering even without any interaction?
The First Person mode that is enabled for the camera is simplistic and only uses a navigation mesh. To implement sliding on a surface you would need to use the physics Puzzles. See our Blender Snowballs VR demo for a working example. For sliding, you would need to adjust the friction value for the sliding surface with the apply body param puzzle.
I guess 3 hours export is not what we intended for the Verge3D user I strongly recommend rethinking your pipeline / application design since such big models are not friendly to web-based real-time 3d graphics, bugs or not. Please see this guide for more details.
Please note that the repository path should end with “addons”, not “addons/verge3d”. To make sure you might try to remove the repository and add it again.
I strongly recommend rethinking your pipeline / application design since such big models are not friendly to web-based real-time 3d graphics, bugs or not. Please see this