OK. this gets even more bizarre/confusing. So I put a trap right next to the trigger and used a variable to store and compare the action value. When these two threads are spawned at the same time, instead of creating a wait state for one thread, it simply returns a zero (or null) answer! Where you see the =?0.0 those are the times the trigger fired twice on one “press”.
WTH?!! This definitely should not be happening!
Here is the output and below is the code:
LogBlueprintUserMessages: [AC_ActorSelection] 0.176801=?11.403991
LogBlueprintUserMessages: [AC_ActorSelection] 0.154823=?18.347633
LogBlueprintUserMessages: [AC_ActorSelection] 0.14188=?0.0
LogBlueprintUserMessages: [AC_ActorSelection] 0.232479=?0.0
LogBlueprintUserMessages: [AC_ActorSelection] 0.126496=?0.0
LogBlueprintUserMessages: [AC_ActorSelection] 0.205617=?0.0
LogBlueprintUserMessages: [AC_ActorSelection] 0.104029=?21.207412
LogBlueprintUserMessages: [AC_ActorSelection] 0.257875=?31.993137
LogBlueprintUserMessages: [AC_ActorSelection] 0.106227=?58.854975
LogBlueprintUserMessages: [AC_ActorSelection] 0.260317=?0.0
LogBlueprintUserMessages: [AC_ActorSelection] 0.157265=?0.0
LogBlueprintUserMessages: [AC_ActorSelection] 0.251282=?0.0
LogBlueprintUserMessages: [AC_ActorSelection] 0.122344=?0.0
LogBlueprintUserMessages: [AC_ActorSelection] 0.233211=?93.81436
LogBlueprintUserMessages: [AC_ActorSelection] 0.126251=?48.271194
LogBlueprintUserMessages: [AC_ActorSelection] 0.867888=?108.662361
LogBlueprintUserMessages: [AC_ActorSelection] 0.199023=?110.773047
LogBlueprintUserMessages: [AC_ActorSelection] 0.199023=?0.0
