Haylee Schäfer

This actually isn't about having different materials for each of the instances, rather the ability to properly being able to use e.g. cubes. The default THREE Mesh allows you to...

> Did you try it out? Yep, works just as intended :) (You can try it yourself https://nbtviewer.inventivetalent.org/)

>I dont have those types of files. e.g. https://github.com/InventivetalentDev/minecraft-assets/blob/1.13.2/data/minecraft/structures/end_city/ship.nbt

Source of the rendering code is at https://github.com/InventivetalentDev/MineRender/blob/master/src/model/index.js#L825

>Nothing happens :( That's what it renders (at least for me o.O)  as you can see, there are different textures on the left and the right face. The THREE.CubeTextureLoader...

Fixed some stuff to keep the behavior of non-array argument the same as before. Tested with cubes with multiple materials: https://codepen.io/inventivetalent/pen/MZpxWX and torus with single texture: https://codepen.io/inventivetalent/pen/dwvrzM

> Why does the torus look all green? Because the material is green :p

Well, cubes with different textures are my particular use case, which is why I added it. The reason the toruses all look green is because it only uses a single...

yep, because toruses don't support the cube mapping ^^

I'm just trying to add the same thing the native THREE Mesh class already has. *whose only use case is different materials on different sides as well btw