Forum Replies Created
-
Thank you very much!! That solved the problem.
This is very essential to know when using that function with objects that use multiple uv maps.
To close this thread: Once I applied the DataTransfer modifier everything worked from this point forward.
It must have something to do with my obj-files. When iported, blender shows the correct shading with custom normals. In verge3D they do not work… Only after my complicated workflow. Very strange. Other objects with custom normals work directly as intended. Thanks to everyone for their help!
They supported aleady from the day they was added to Blender. All custom normals will works fine in Verge3D – we have a lot of demos with split custom normals on some objects.
Yes they do work – but only with this duplicate-modifier workflow. If I have a model with custom split normals and just directly export to verge, they do not work. It least not in my tests.
The Wheighted normal modifier won’t create custom split normals data if this option is disabled. If you disable this option after adding custom split normals they won’t be applied in Blender and won’t be exported to glTF.
Well you need to use the DataTransfer modifier, not the WeightedNormal. And yes as I said, I checked that box. But: I already had that. I had to uncheck it, enable smooth shading again (it already was) und then check that box again. Now it works.
Unfortunally, animation of modifiers not supported and seems no change for this in near future.
Animating values inside the modifiers will not work because they will be baked (well at least for now). So that is obvious!
What I meant was animating the object itself with the DataTransfer modifier on it. That is what I am doing. And I have to parent the source-mesh to the export-mesh, otherwise on export the modifier will not be baked correctly into the gltf-file.So my question remains: Will there be native custom split normals support in verge3d sometime in the future? And by that I mean: Custom normals work in blender (and other 3d apps) without any modifiers. In Blender you have your 3D-model, create or import the custom normals -> smooth shading -> activate auto smooth: Done.
For them to also work in verge you need to duplicate your model, delete the custom normals on this 3d-model and then re-apply them via the DataTransfer modifier from the other duplicate (used as source inside the modifier) that still has the custom normals.Custom normals are widely used in the gaming industry -so realtime applications like verge- so being able to use them without this duplicate-modifier-pipeline would be very useful!
:)I just fixed it. All I needed to do was apply smooth-shading once more and tick the auto smooth checkbox on the export-mesh. Now everything works.
BUT: Why this “complicated” procedure? And what do we do when we want to animate these objects. Parent the source-mesh with custom normals to the export-mesh to not break the modifier? Thats not very practical…
Is there a way to make custom normals work natively on export? Those are very common in game engines so it would be nice if you could use them “natively” in verge3D.
No problem. Here are the links:
This is the app with Verge 3.9:
http://www.suedsauerlandmuseum.de/bieketurmThis with 4.0 and nothing changed, just updated and saved puzzles:
https://v3d.net/8g5Thanks for the fast replies!
Yes with Android everything works as expected.
Soooo after hours of reseach I found out that you CANT open WebXR AR-Apps on iOs through iframe at the moment. When I get rid of the iframe and put my UI inside the main-html-file than it works…
This ist very essential to know for everyone who wants to develop Web-AR with Apple hardware. In short: Its pretty much impossible at the moment. Even with dedicated apps like XRViewer…
Thanks Yuri for looking into my project files to look for the error
Next time i will develop directly on Android.Hi Yuri,
yes the render issues are gone now!
But AR still does not get detected in my app with XRViewer. A few weeks ago it still worked. I already deleted the puzzles for USDZ generation, so this can’t be the problem.
In the screenshots you see all my AR-related puzzles.
First I check if AR is available, then set the variable to true, then I set my html element with my AR button to “block” if true. But the button stays invisible.
Is the iframe a problem? I made the gui with webflow and added this:
allow="xr-spatial-tracking"to the iframe code.
Under this link you can find my project file.
I really dont know where my error is.
Hi Yuri,
thanks, that explains a lot!
But now Safari asks me if I want to download the file: AR.usdz.xml and really just downloads it. And it can’t be opened because iOs thinks that it is an xml file and not a usdz file.I am using Verge4.0 pre4 with compressed textures. Maybe this is a bug in the current pre4?
