Following the tutorial on communicating between actors via blueprint:
https://docs.unrealengine./latest/INT/Gameplay/HowTo/ReferenceAssets/Blueprints/index.html#directblueprintcommunicationreferencing
The above tutorial, in the “Direct blueprint communication” section, is incomplete. It is confusing by not calling “fire” or “sparks” everytime you mention a blueprint, taking for granted the user knows which of the 2 blueprints we are adressing, sometimes twice in the same phrase. What is shown in 4.10 also seems different than what is shown in this tutorial, based on 4.9.
Nevertheless, I was not yet able to make my fire_effect shut down the spark_effect, any way I tried.
Just looking over the tutorial it seems in order. Notice the level of difficulty is advanced. If you were familiar with creating blueprints you would be able to follow the tutorial. I would suggest reviewing other more simple blueprint tutorials until you get the hang of it. It’s just as complex as writing out code.
As for being out of date, from time to time the documentation does get behind because of changes to the ui in favor of advancement to the engine features. While they do update them from time to time all we can do is either wait or download the engine version the tutorial was made for to learn about the feature. As you grow in your knowledge base of unreal tools it will be easier in the future to figure out what to do to make it work. It’s part of the learning process.
I agree, and I am sorry for the confusion.
I successfully made my fire emitter stop and restart my sparks emitter, not by following this tutorial (above mentioned) but by reading the “Direct Blueprint Communication” guildelines, understanding it, and making it on my own. So I guess the above mention tutorial, even followed step-by-step, is not enough to make it work, but understanding the mechanics does.
But! … I am grateful for your input.