cedar jungle
I am converting my Mesh's to InstancedMesh's, and it looks like the Instanced version is using the full texture, not its "subsection" of the texture
I believe this is called Texture Atlas'ing (correct me if im wrong) - packing up a bunch of textures into one png file, and having my models only map to a subsection of that larger png file
When I convert these to instancedmesh's, it no longer appears to be doing its "subsection" mapping
Here's my platform before InstancedMesh 👆
Here's that same platform after InstancedMesh 👆
Is it not possible to do that type of texture atlasing when using the instanced approach? Do I need to get these textures all separated out into their own texture file?
cedar jungle
possibly relevant?
slow forge
Here is a (very basic) example of texture atlas using instanced mesh. I hope it can help you. The trick is to pass a THREE.InstancedBufferAttribute containing a Float32Array to a custom shader using these values for UV offset.
There is not much difference with the 2018 answer aside it's using more up-to-date version of three (r153)
live demo:
https://raw.githack.com/Oxynt/three-instanced-uv/main/index.html
cosmic zealot
Agreed with previous answers, you'll need a custom shader if you intend to use different parts of the texture atlas on different instances.