Forum Replies Created
-
AuthorPosts
-
danielbrunoCustomer
It’s indeed there. But the way it is, it looks like the v3d namespace is already defined in the parent doc. I’d like to suggest that the full process is added to the docs.
Thank you!
- This reply was modified 1 year, 1 month ago by danielbruno.
danielbrunoCustomerThanks a lot, @kdv
You saved my day!
Am I wrong or this exact method
v3d.puzzles.procedures.PROC_NAME
is not explicitly detailed on the documentation?Daniel.
danielbrunoCustomerHi Nurgeldi.
The display issue under Windows was solved using 4.0-pre version.
Thanks for the tip!
danielbrunoCustomerHi 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×512Thank you.
danielbrunoCustomerJust uploaded it via wetransfer and send the link to info@soft8soft.com
Many thanks!
danielbrunoCustomerThanks, Yuri!
Surely I can send you the files. Please tell me to where I can send them to you.
danielbrunoCustomerHi Yuri. Thanks for your reply.
Sorry but I’ve uploaded to v3d cloud a version with these huge texture files. I have already tried with way smaller versions of any of the textures and the problem with Windows persisted. You can check it here.
Thank you.
danielbrunoCustomerdanielbrunoCustomerHello.
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. 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 where 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 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.2021-04-23 at 11:43 am in reply to: Blender 2.93 Geometry Node export to Verge3D is now possible! #40458danielbrunoCustomerSuper cool!
Thank you so much for sharing this.
Daniel
danielbrunoCustomerThanks for your reply, Simone! I got the point.
I will return to Shape Keys.
-
AuthorPosts