From 1ab268d7751e95f0ee4ec32d6bec6a1c712926f6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Matja=C5=BE=20Lamut?= Date: Thu, 13 Apr 2023 19:46:23 +0000 Subject: [PATCH] Documentation - more information on COLLADA texture paths --- ...pipeline-blender-collada-static-models.rst | 22 ++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/docs/source/reference/modding/custom-models/pipeline-blender-collada-static-models.rst b/docs/source/reference/modding/custom-models/pipeline-blender-collada-static-models.rst index 8d598f10cb..d52c952b3d 100644 --- a/docs/source/reference/modding/custom-models/pipeline-blender-collada-static-models.rst +++ b/docs/source/reference/modding/custom-models/pipeline-blender-collada-static-models.rst @@ -158,8 +158,28 @@ Texture Paths Textures will show properly in OpenMW when the path in the exported COLLADA file is as follows ``textures/the_barrel.dds``. The exporter detects the ``data/textures`` part of the texture's path in Blender and truncates the rest. -The texture path can also be set manually in the exported COLALDA file. +The texture path can also be set manually in the exported COLLADA file. +Textures Not Visible +==================== + +If a texture doesn't show on the exported model in OpenMW-CS or in-game, it's likely +the file path to the texture is incorrect and OpenMW can't find it. +To fix this you can open the exported ``.dae`` file in a text editor and check +the texture's filepath. In the example of this barrel model it's found on lines 13-17. + +.. code:: + + + + textures/the_barrel.dds + + + +A path to a texture must always start with ``textures/`` and then continues with +whatever subfolders the texture is in. It's a common issue that the path can start +with ``../textures/`` in which case you can manually remove the ``../`` +and the textures should then show. Collision Shapes ****************