Initiating a Conversation with a Player in Air At Start of Game Breaks Their Game (Have to Close Client)

Summary

If you initiate a conversation with a player via verse InitiateConversation(agent) while the player is jumping, the player’s game will break.

The player’s cursor is freed, but no conversation HUD is shown. The players cannot control their character or pause. They have to close their client.

Please select what you are reporting on:

Creative

What Type of Bug are you experiencing?

Assets

Steps to Reproduce

  1. call InitiateConversation() on a player that is jumping
  2. observe player’s game becomes stuck

Expected Result

Can still initiate conversations with jumping players. If not, their game should not break.

Observed Result

Cannot initiate conversations with jumping players. If you do, their game breaks.

Platform(s)

ALL

If you initiate a conversation immediately after a player joins the game, the conversation HUD will not show on the players screen.

Trying to re-initiate the conversation will also fail, until the player respawns. Once the player has respawned, initiating the conversation will work again (it is possible that manually hiding the conversation would also allow the conversation to be shown)

If you Sleep for ~2s after player joined event, and then initiate the conversation, the HUD will reliably show. Sleeping for less time works for some platforms, but Xbox requires the longest amount of time to load.

There is something happening with showing HUD too soon after player join in progress, and i think this issue is being caused by automatic show settings as well

@OohWowow could I get an island code from you so we can repro this here?

Thank you!

One more ping for @OohWowow

1 Like

sorry for the delay! trying to find some time to get this together for you guys, on my list :smiley:

@Flak I am going to try to get you guys a code today!

here is the code for repro-ing the behavior! 5409-7387-4563

this teleports players into the air on spawn, and initiates a conversation with them

this behavior ONLY occurs in private codes, not in edit session

all you need to do is load into this island code, and the verse will fire on its own

you will have to close the Fortnite client, pausing does not work so you cannot leave the game

@Bug-Reporter pls dont close this :smiley:

verse code for reference:

using { /Fortnite.com/Devices }
using { /Verse.org/Simulation }
using { /UnrealEngine.com/Temporary/Diagnostics }
using { /Fortnite.com/Characters }
using { /UnrealEngine.com/Temporary/SpatialMath }

player_manager := class(creative_device):
    @editable Spawners: []player_spawner_device = array{}
    @editable DebugConversation: conversation_device = conversation_device{}

    OnBegin<override>()<suspends>:void=
        for(Spawner:Spawners):
            Spawner.SpawnedEvent.Subscribe(OnPlayerSpawned) 

    OnPlayerSpawned(Agent:agent):void=
        if(Player:=player[Agent], FortChar:=Player.GetFortCharacter[]):
            PlayerT:= FortChar.GetTransform()
            if(FortChar.TeleportTo[PlayerT.Translation + vector3{Z:=10000.0}, rotation{}]){}
            DebugConversation.InitiateConversation(Player)

I was also able to confirm that

CanInitiateConversation
IsAgentInConversation

functions ALWAYS fail, even if an agent IS in conversation, or can initiate conversation

It looks like this behavior only occurs when initiating the conversation immediately at the start of the game.

If a player is jumping/falling/slide kicked while in a conversation, that conversation is cleared. Since the conversation HUD fails to show when the conversation is initiated immediately, I imagine it fails to clear this HUD, leaving the player in this broken state

The player’s experience is only broken if they are in air when this occurs. If they are on the ground when the conversation is initiated immediately on game start, the HUD shows and behaves normally.

we see this behavior inconsistently for JIP players.

in the repro project (which is mostly empty) i do not see this issue

in larger projects where more devices are setting up at game start/initing on player join, we do see this issue. to me this suggests a timing issue depending on the load the verse server is under

along the lines of these timing issues: Stat Creator UI Widget Does Not Show For Players Who Join In Progress - #43 by OohWowow

Thank you! Ignore the Bot Reporter status, we’ll be reopening and rechecking with your latest information.

1 Like

Thanks for your patience here, @OohWowow - we have a repro and will pass it to the proper team.

1 Like

No worries, super happy you guys were able to repro :smiley: thanks for following up!

FORT-869946 has been ‘Closed’. This issue won’t be fixed—please see examples of why this may be the case.

@Flak still ignore the bug reporter? or has it been closed