Players crash when trying to join a match in-progress on published islands.

General Issues and Bug Reporting
, , ,
1

Summary

Players are unable to correctly join rounds in progress on a published island if the island settings have the players spectate when joining on an in-progress round. The player will instead be met with an infinite loading screen, followed by a crash. All players are forced to queue and load at the same time.

Please select what you are reporting on:

Creative

What Type of Bug are you experiencing?

Island Settings

Steps to Reproduce

Create an Island with the settings → On Join Round In-Progress → Spectate
Have one player join the island without the other.
When the other player attempts to join, they will be unable to do so, being met with an infinite loading screen followed by a crash after about 10 or so minutes.

Expected Result

The player should join the island and load to spectate, waiting for the round to end.

Observed Result

When attempting to join a in-progress published game with “On Round In-Progress → Spectate” results in a infinite loading screen followed by a crash once the player can properly join.

Platform(s)

All

Island Code

3947-0686-4029

Video

2

Bump!

3

bumperoony

4

This is kinda game breaking, can we please get a ticket for this?

6

Additional information, and more testing has shown me more important information!

1 - If a player loads into a death barrier, this may cause the issue more frequently. I have noticed players that join in progress, despite the option being to spectate until next round, will join and die more than join and spectate. This is evident by the join message the player gets, I.E “playername is switching to spectate” when a player joins to spectate, and “playername noped out” when they die to the barrier.
Both messages cause the user to crash, but it is worth noting the setting is ignored.

2 - Players that crash are unable to join that same lobby, even if possible. They will create a new session, or get a matchmaking error.

10

Ws!

12

FORT-1078199 has been ‘Closed’. We’re unable to reproduce this issue.