Skip to content
TheChatArchiveThe Chat Archive
Geminigemini-2.5-pro-exp-03-25-grounding· GoogleHugging Face LMArena Search Arena 24K

I am working on a UEFN project in which I need an npc's head to track a player. To do…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Perplexitysonar-reasoning’s answer.
  1. User

    I am working on a UEFN project in which I need an npc's head to track a player. To do this, I need to know if you can expose a players position in Verse as a 3 vector (this is definitely possible) and capture it and make it available inside of the control rig blueprint. Focus your research around what can be connected from verse to the Control Rig. Keep in mind UEFN is different from Unreal Engine. Do NOT guess or make ANY assumptions in your response. If you can't find a conclusive answer, simply respond with "Inconclusive."

  2. Gemini Assistant

    Based on the available search results, here's what can be determined about connecting Verse to Control Rig in UEFN:

    1. Getting Player Position in Verse: Yes, you can get the player's position and transform using Verse scripting in UEFN. This is often done using functions like GetPlayspace().GetPlayers()[INDEX].GetFortCharacter[]?.GetTransform()[1].

    2. Direct Verse to Control Rig Variable Connection: There is no direct, documented method shown in the search results for Verse to directly set variables within a Control Rig Blueprint graph. Standard Unreal Engine methods involving getting variables via Animation Blueprints[2][3][4] or accessing controls via Blueprint components[2][4] might not translate directly or easily to the UEFN + Verse workflow.

    3. Indirect Connection via Props/Actors: Several sources demonstrate using Verse to move a creative_prop or another actor, and then having the Control Rig follow that prop[1][5][6].

      • Verse code can get the player's transform and use MoveTo or TeleportTo on a creative_prop[1][5].
      • A Control Rig component is added to a Blueprint Actor (often containing the skeletal mesh the rig controls)[1][6].
      • Within the Control Rig graph, nodes are used to get the transform of an external actor (the prop being moved by Verse) and apply it to control the bones/controls of the rig[1][6].
      • In the Blueprint Actor containing the Control Rig component, the "User Defined Elements" section is used to map a Control Rig element (like a root control) to a "Reference Actor" (the prop being moved by Verse)[1][5][6]. This effectively makes the Control Rig track the Verse-controlled prop.
    4. Control Rig Smoothing: Control Rigs are noted for running client-side and providing smoother motion compared to just using Verse's MoveTo or TeleportTo for visual updates, as Control Rig updates can happen per-frame (tick) rather than being limited by Verse's rate[1][5]. This is a common reason for using this Verse -> Prop -> Control Rig workflow.

    Conclusion:

    While you can definitely get the player's position (as a transform, which includes the Vector3 position) in Verse, there isn't a straightforward, documented way to directly pipe this Vector3 variable from Verse into a variable inside the Control Rig graph itself.

    However, the established UEFN workflow is to use Verse to move a helper creative_prop based on the player's position, and then configure the Control Rig (via its Blueprint component and internal graph) to track the transform of that helper prop[1][5][6]. This achieves the goal of having a Control Rig (like an NPC's head rig) follow or react to a player's position, driven indirectly by Verse.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.