Quote:

---

...if only I still had a graphics card

---

Maybe we shoud buy you a new graphic card then

Quote:

---

i don't know why you would need so many textures layers though.

---

I try to explain this.

We make our levels with models. But a complete room needs many textures for floor, wall, ceiling, columns and static details.
Until now I just copied all needed textures into one big texture. But then I have to map every floor tile since I cannot tile them over the uv-space. I have to create polygons for every floor tile, for every ceiling tile and so on. This results in much more polygons for a room.

We still can copy some textures into one. But the tilable textures should have their own texture space.

We would be very pleased, if you could direct us into the right direction. Thanks in advance!

Quote:

---

Model shaders now support several skins per mesh subset, f.i. for normal maps. The skin assignments are detected automatically by the engine. Any additional skins that belong to a subset must immediately follow the skin that is assigned to that subset. For instance, let's assume that an entity has 3 mesh subsets, and the following skin assignments:

Skin1 -> assigned to subset 1
Skin2 -> unassigned (normal map for subset 1)
Skin3 -> subset 2
Skin4 -> unassigned (normal map for subset 2)
Skin5 -> subset 3
Skin6 -> unassigned (normal map for subset 3)
Skin7 -> unassigned
Skin8 -> unassigned

The 3 subsets are rendered in 3 passes, where the assigned skin is always entSkin1 and the normal map is always entSkin2. In render pass 1, Skin1 is used for entSkin1, Skin2 for entSkin2, Skin7 for entSkin3, and Skin8 for entSkin4. In render pass 2, Skin3 is used for entSkin1, Skin4 for entSkin2, Skin7 for entSkin3, and Skin8 for entSkin4. In render pass 3, Skin5 is used for entSkin1, Skin6 for entSkin2, Skin7 for entSkin3, and Skin8 for entSkin4.

---