It sounds like you are trying to make a multi/sub-object texture(one bmp for part of the mesh and another for another part of the mesh in the same channel, ie:diffuse color), which I don't think you can do.
The multiple texture capabilities are for applying different maps and shaders in different channels on a mesh, not for applying it to different parts of a mesh.
Join us in the Irrlicht chatroom:
[url]irc://irc.freenode.net/irrlicht[/url]
I love deadlines. I like the whooshing sound they make as they fly by. -D.Adams
You have to access the different mesh buffers which are part of the mesh. Each one has its own material and you have to assign the proper textures there.
hybrid wrote:You have to access the different mesh buffers which are part of the mesh. Each one has its own material and you have to assign the proper textures there.
Can you please give out some examples( showing some code is better...) to explain how to do the mapping?
Thank you very much!!!
What Using a 3d modeller is almost the only way to do proper UV texture mapping. If you have a more complex mesh thn a cube you'll like fail to add textures manually.
BTW: You simply have to guess which mesh buffer is the corret one for your texture. It heavily depends on the loader etc. how this will work. And if your mesh does not contain separate material definitions you cannot add separate textures at all.
The best way is that use one model one texture.
bitplane's hint covers this problem mostly. thank you very much.
complex mesh has to using 3d modelling program maybe.
and need to learn more mesh buffers.
my program is that client receives meshes/textures from server. and don't want clients save meshes/textures in their HDD. it's just temporary data. All process must be executed in memory.
Why not a temp dir you clean after the programm ends?
And why clutter the internet with traffic when its better buffering the data on the users HD?
Just look how GuildWars does it. Some nice protected container format, reminds me a bit of the old BAM format cbm disks have. *g*
You would just need to edit Irrlicht itself so that it reads from said container format and not from normal filespace and you dont even need to release your "ultra high confidental" scrambling system. Irrlicht is zLib licenced