Thanks @Flak, appreciate it
2 Likes
Any timeframe of when this issue is resolved?
1 Like
Hey everyone!
Issue still hasn’t resolved, but we came up with a workaround for our project if you need to unblock yourself:
- Create a new input_trigger_device that takes a Creative Input Action, that action being Creative Input Custom 6 (Interact), then subscribe to the device trigger with a placeholder function.
- Create a custom component that has a mesh_component that can detect overlaps with your actor/component of interest.
- Add some detection and registration/unregistration logic for when your actor/component is in your radius as well as some VFX or other UI/UX elements to tell the user that the actor/component can currently be interacted with.
- Hook up your filtering and interaction logic into the input_trigger_device event subscription’s placeholder function!
2 Likes
Ok this is wild. The just rebuild interaction from scratch method lmao ![]()
2 Likes
Pretty much lmao, but it got the job done for now at least!
Currently Still Broken in 39.10
Yep, can confirm that unfortunately…
FORT-1025748 is ‘Closed’ as ‘Fixed’. The issue will be addressed in 39.20.
39.20v
Why are my test results only successful a few times, with most still failing?
We are on 39.11
2 Likes
Okay, I thought yesterday’s update would upgrade to version 39.2.
@WinterWins1 Thank you.