Hi,
For the above, you need to understand that this is not a simple custom mesh. It uses vertexData to compute indices and normals. And then, of course, as @labris says you can see there’s no texture in there so it will certainly not appear ‘automagically’
I guess the first question would be ‘Why would you want to use vertexData’ for your custom mesh? In which case, you will eventually need a shader and a texture sampler to apply a texture on it.
But then just why make things complex if there’s no need for it. If it’s a custom mesh you want, here’s one for you:
The Playground example is just to work out the process, what I want to create is (very) large, mathematically generated surfaces. I looked through all the meshes in the docs and none look like they will have the freedom I would like. Ribbons would probably work fine too, but it looks like these are very similar to the custom mesh, but instead of specifying every point on every triangle, Babylon calculates these for you between the longitudinal ribbons of points.
I could split my mesh up into thousands of different meshes that use a more standard mesh type for each I guess, but I don’t know if this would be as slick, or if there would be some performance drawbacks?
If I was to create each facet individually and apply colour and texture to each, is there a way I could then make them into a single mesh or a group or something, to get all/some of the benefits of having one huge mesh.
If you’re going to have very huge meshes, the best approach here would be to use Instances ( Instances | Babylon.js Documentation (babylonjs.com)) with a custom Shader or Node Material to handle the different colors/textures.
Hi. I have not had a chance to look at the customer shader or node material route, but if i ever do i will try and update this post with my findings. Thanks for your help either way.
