There’s no source material selected in not-working-2.png.
Hi guys,
I wanted to make my scene interactive while in game play so I started making some blueprints. I’m very new at this so I followed tutorials for guidelines. I successfully made some of my static mashes (furniture) to change color with the same pattern except one. One of the walls in the room I want to change color, but the same blueprint scripting that I used on the other meshes doesn’t seem to work in this case. I don’t know what’s the problem.
Here are some screenshots of the settings in the blueprint for the furniture…
and for the wall…
I could use some help!
Tnx
I added the source material but nothing changed!
Could you please show a screenshot of the wall material setup?
Also, put a PrintText node after F and see if it prints at all; perhaps the key input is not being sent.
The rest looks good at a glance.
Ok, so I thought something is wrong with the mesh, so I made a new blueprint for another wall, after I made the blueprint I build the lightning and restart the scene. When I opened the scene and put it in to game mode the first wall that didn’t work it stared to change color but now the new wall has the same problem. Any thoughts? Btw here a screenshot of the wall material…
My guess would be that the F key consumes input (select the F node and check details panel) and once it does, nothing else has the chance to react to the F key anymore.
If you are planning on having multiple objects react to the same action, you should place the triggering logic elsewhere; ideally some place where it can be executed globally.
For example, create a CustomEvent/Function for the objects that need to react to colour changes. Use the F key in your LevelBlueprint, get the objects you want to interact with and call their ColourChange event/function.
So sorry for the late response, I’ve checked the key input and seems ok… or maybe not… btw now it’s working, I updated the new 4.18 version and only changed the size of the box collision because it was interacting with the other box collision from different blueprint mesh. Could that be the problem?
[…]btw now it’s working
If you managed to get it to work the way you need, please consider marking the issue as resolved.