Spawned Interactable Components are broken since 39.00

[X_TyFighter_X (TrickTyger)]

Summary

Preplaced entities with interactable components work fine but if you spawn an entity with an interactable component then it doesn’t fire any of the events (Succeeded event but I also tested Started)

Please select what you are reporting on:

Verse

What Type of Bug are you experiencing?

Verse

Steps to Reproduce

Make a prefab with an interact component
Place one in the level
Spawn one when the game is started

Expected Result

Both fire the “Success” print

Observed Result

The spawned prefab doesn’t fire the Success print

Platform(s)

All

Upload an image

Video

2025-11-30 17-09-27.mp4

Additional Notes

The 3 cubes you can see are preplaced prefabs - you can see the “Success” print in the top left corner

I spawn in the prefabs from the trigger - the Success doesn’t print

[zkz-nito]

Verified broken in my projects as well and also in a quick test project. Prefabs added in outliner seem to work, any Entity created at run time does not.

[HimboHouse]

Also is happening in my project, weirdly enough SOMETIMES if I spam the interact button a ton of times it eventually will fire once. Also it appears to only work with some meshes so I assume the mesh’s collision matters

[RickF1234]

Also broken in my project after V39 update. I am spawning the entity in with a intractable component and it never fires.

[SGSensei]

Mine seem to still be working perfectly fine after 39.0.0. Was investigating with Trick, and we seem to be led to believing that attaching it to the SimEntity directly is now whats causing issues. I personally attach my components to a different entity that is already existing and attached in the Simulation, and have 0 issues post 39.0.0. Still trying to narrow down specifics for replication, but this is what we’ve managed to find so far.

[X_TyFighter_X (TrickTyger)]

Worth saying that i’ve tried attaching to a different entity in scene but it doesn’t work for me but does for Sensei so who knows haha!

[HimboHouse]

I’ve been trying to find a workaround all afternoon because this bug completely breaks a game I’m working on. I’ve found that some meshes sort of work, they never register the first time, but if you hit the right spot or angle after around a hundred attempts, they eventually respond. Once a mesh does accept an interaction, that specific instance can then be interacted with normally from that point on. I’ve also found that other instances of the same mesh asset start working as well once a single instance has successfully registered an interaction.

[spankysully1 (spankysully)]

Also having the same issue

[zkz-nito]

very jank work around is I used Scene Graph ray cast object collision with players lookat if it’s a entities with interactable_component I register a Input Trigger for Interact and then call the interactable_component Succeed … this was the simplest solution I’ve found until Epic fixes the issue. Tried using Prefabs in the outliner and ran into a bunch of issues registering buttons, meshes, and general inconsistencies. Hopefully Epic fixes quickly.

[WhooptyFN]

Im having the same issue in my projects. It completely breaks my game.

[Uxibeo]

I found the root cause of the problem: instead of inheriting interactable_component, I had to retrieve it from another component. But doing it this way means we lose control over filtering which agents can interact with the entity, and we also lose the ability to customize the interaction text.

Working component

working_component<public> := class<final_super>(component):
    OnSimulate<override>()<suspends>:void=
        if(Component := Entity.GetComponent[interactable_component]):
            loop:
                Agent := Component.SucceededEvent.Await()
                Print("Clicked by Agent")

Broken component

broken_component<public> := class(interactable_component):
    OnSimulate<override>()<suspends>:void=
        loop:
            Agent := SucceededEvent.Await()
            Print("Clicked by Agent")

[X_TyFighter_X (TrickTyger)]

This doesn’t fix the issue for me unfortunately

[AtAshTag]

This is probs why when you inherit the interactable comp you cannot Enable() after it starts as Disabled in the editor

[dcuadevhouse (LynDevhouse)]

Encountering this issue on my side as well - can confirm that spamming the interact button sometimes allows the interact to go through though!

Only issue is that it takes 100-200 interact button presses for the interaction to go through/

[Jpt96]

Has broken 2 of our games in development and will block them from being able to be published until resolved.

[HimboHouse]

More details found about the bug here: Problems With interactable_component

I just tested it and my intractable_components now work when set to 0,0,0. It still completely breaks my game, but does give some more info on the nature of the bug lol

[HimboHouse]

Ok I did some more testing, it appears that interactable_components work within ~10 meters of where the entity they are attached to was initialized. (when constructing the transform_comp of the entity include a local transform and add that component before attaching to the Simulation Entity)

My game is still completely broken because the entities they are attached to need to be able to move, but adding this info to help the devs find the source of the bug and to help any FNC devs who maybe don’t need to move the entities the interactable comp is on

@X_TyFighter_X @Oni_Stoney

[Unreal_Rider1983 (Charles_Owen)]

It seems to be the same issue: once an Entity is spawned, it can be interacted with normally as long as it doesn’t move. However, if the Entity moves, the interaction functionality stops working

[Flak]

Thanks for the detailed reports, everyone. The team is checking into this.

[Flak]

I’ll be dropping this in the known issues thread. Thanks all!

We’re investigating an issue where entities spawned at runtime with an interactable component are not behaving as intended. We’ll let you know when we have more information or a fix.