summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorCristiano Simao <40866219+CristianoSimao@users.noreply.github.com>2022-08-04 17:43:32 -0300
committerRĂ©mi Verschelde <rverschelde@gmail.com>2022-08-08 09:06:51 +0200
commit1f6709d6e33a5fc3eec0bc6d58fd3011dc5531c4 (patch)
tree850159a4905c3ea16befb1e795b373d7eccab9a4 /doc
parent335b51be70e5b45ad14c6931435cb2c24717f0e6 (diff)
doc: Clarify `MultiMesh.set_instance_color` re: white albedo color
If the user does not set the albedo color to pure white, then the multiplication with a value different from 1 will produce modulated colors. Co-authored-by: Hugo Locurcio <hugo.locurcio@hugo.pro>
Diffstat (limited to 'doc')
-rw-r--r--doc/classes/MultiMesh.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/classes/MultiMesh.xml b/doc/classes/MultiMesh.xml
index 9d8f1e1e5d..3431a3347b 100644
--- a/doc/classes/MultiMesh.xml
+++ b/doc/classes/MultiMesh.xml
@@ -54,7 +54,7 @@
<argument index="1" name="color" type="Color" />
<description>
Sets the color of a specific instance by [i]multiplying[/i] the mesh's existing vertex colors.
- For the color to take effect, ensure that [member use_colors] is [code]true[/code] on the [MultiMesh] and [member BaseMaterial3D.vertex_color_use_as_albedo] is [code]true[/code] on the material.
+ For the color to take effect, ensure that [member use_colors] is [code]true[/code] on the [MultiMesh] and [member BaseMaterial3D.vertex_color_use_as_albedo] is [code]true[/code] on the material. If the color doesn't look as expected, make sure the material's albedo color is set to pure white ([code]Color(1, 1, 1)[/code]).
</description>
</method>
<method name="set_instance_custom_data">