|
|
|
 |
Reply From: |
Cogan |
MeshInstance3D.mesh.material.albedo_color = color
I’ve created a scene to demonstrate this.
Sorry Cogan, I downloaded it, unzipped it, and tried importing it - twice, but nothing. I am on a crappy old Chromebook, although that shouldn’t make a difference, right?
Curiously99 | 2023-05-26 21:30
Ok then I’ll show you all the necessary things.
First Add a StandardMaterial3D as the material property in your mesh.
then, if you’re changing the color from a script attatched to the MeshInstance3D:
mesh.material.albedo_color = color
If you’re changing it from another object:
MeshInstance3D.mesh.material.albedo_color = color
Definitely closer, but a couple of things.
Firstly, if I run colorpicker without any script, it puts the color console within the game window itself. That’s not what I want long-term. What I’m after is an expression to assign color that I can then use in a broader ‘if something is touching then change color’ statement.
Secondly, and sorry about needing to be spoonfed this, but now the color element itself is causing problems. The closest I’ve manged is this:
The node tree is: StaticBody3D>MeshInstance3D>CanvasLayer>ColorPicker
extends ColorPicker
const BLUE = Color(0, 0, 1, 1)
func _ready() → void:
- indent - MeshInstance3D.mesh.material.albedo_color = BLUE
But ‘invalid get index ‘mesh’ on base MeshInstance3D’, and so the game window was just empty grey. The crazy thing is, on the viewport, the damn thing turned blue!!
(I found ‘draw_mesh()’ in the docs and thought I had it for a moment, but it looks like it’s only available in 2D.)
Curiously99 | 2023-05-27 05:54
OK, so forget about it turning blue in the viewport, I can’t seem to replicate that now.
Curiously99 | 2023-05-27 06:11
Ok then I’ll try to explain this better. The color picker and canvas layer nodes are not necessary. This function can be called from any script, including a script attached to the mesh instance itself.
If it’s being called by a script attached to the mesh instance it’ll be really easy. you just type this
const COLOR = Color(0, 0, 1, 1)
mesh.material.albedo_color = COLOR
In this case (remember this is only if it’s a script attached to the MeshInstance3D that is changing color) COLOR represents a color. It could also be a variable or even just a hard coded value. Mesh is the value of the mesh variable in the mesh instance 3D node. This will give you the mesh that is assigned to the mesh instance 3D node. The period means that it’s a value of the given object, so material means the material of the mesh of the MeshInstance3D that the script is attached to. If the material is a StandardMaterial3D, it will have the property albedo_color. The second line sets that property to color. Also I’m sorry for the wall of text, I’m just really trying to help you understand this.
If you’re calling the function from a script attatched to a different object, it’s gonna work almost exactly the same, but first you’ll need a variable that defines the MeshInstance3D (that has the mesh that has the material that has the albedo_color property) so if you’re calling from a separate object it would look something like this (mesh_instance is a variable that can have a different name if you want as long as it’s a mesh instance with a mesh with a material with an albedo_color property)
const COLOR = Color(0, 0, 1, 1)
mesh_instance.mesh.material.albedo_color = COLOR
I see how the ‘…instance.mesh.material.albedo…’ path essentially mirrors the location of albedo in the user interface, that’s good to know. Probably works in lots of other contexts.
Here’s the screenshot:
https://drive.google.com/file/d/1-hDrYTIIacM3KrdcOd6TwjfaG5h4yNss/view?usp=sharing
It’s basically showing the same error I’ve been describing, is it saying that the color value it’s returning is null?
Curiously99 | 2023-05-27 09:47
Your code looks fine. Could I see the MeshInstance3D in the inspector with the mesh clicked like in that one screenshot I sent? Not the script the node.
… but the color’s not changing from the inspector either!
I need to experiment with the inspector. I hadn’t seen the material color, I’d been using the surface material override. That must be interferring with the material color.
Leave this with me, I’m going to figure this out.
Curiously99 | 2023-05-28 05:38
It looked like you didn’t have any lighting nodes in the screenshot you sent. Try adding lighting and tell me if it works then.
edit: Also scripts don’t run in the viewport unless they have “@tool” on the first line (even before the line that says “extends SomeObject”
Also also, unless you wanna change the color during the game, you can just change the albedo color in the material settings without code.
Cogan, I’ve done it!
Here’s the celebratory screen shot:
https://drive.google.com/file/d/106pza6q1zWHhr1Ti38b7783r3dI-gqTf/view?usp=sharing
(Impressive right?)
I did have lighting nodes, they were just hidden away on other nodes. Good to know about the @tool, I did always wonder about how people viewed updates within the Viewport.
The main thing is, I had been using surface_material_override, not mesh.material in the inspector. The inspector settings were conflicting with my code.
Cogan, I’ve learned from this exchange, I really appreciate your help.
Curiously99 | 2023-05-28 10:45
