Summary
We are receiving multiple reports from players via email and direct messages stating that they are unable to join the island and that the game crashes when they attempt to do so.
All affected players appear to share the same root cause: they are using the newer Xbox model, the Xbox Series S.
To investigate the issue, I mistakenly purchased an Xbox One S (an older and lighter version of the console) instead of an Xbox Series S. However, the game runs smoothly on this device, which suggests that the issue may not be related to pure hardware limitations.
The map also runs smoothly on the smartphone version of the game, although I am not sure if this information may be helpful.
The map is not heavy in terms of resources, textures, or code, and it has been optimized in every possible way.
We would greatly appreciate your help in investigating and resolving this issue so that all Xbox players can access and play the map. Many players are currently waiting for this to become possible.
Thank you very much for your support.
Please select what you are reporting on:
Creative
What Type of Bug are you experiencing?
Stability
Steps to Reproduce
Join island 7578-0076-3430 with specific console model “Xbox Series S”
Expected Result
Fortnite client crashing upon joing island 7578-0076-3430
The player is brought back to Xbox home screen.
Observed Result
Fortnite client crashes upon joing island 7578-0076-3430
The player is brought back to Xbox home screen.
Platform(s)
Xbox (only model Series S)
Other Xbox models, also older ones with less performant hardware have no issues.
Island Code
7578-0076-3430
Additional Notes
We attempted to isolate the problem using a bisect method, removing roughly 50% of the map at a time. Unfortunately, we were not able to identify the exact cause of the issue.
The only scenario in which players with that console were able to join successfully was when we removed almost everything from the map, leaving no elements.
We repeated this process following different elimination paths, but the element whose removal allowed players to join was never the same. This leaves us puzzled about the root cause, since the triggering factor appears to change each time
The first elements we removed in every test were all Creative devices and any code-related components, so we are confident that the issue is not related to Verse code.
The root cause appears to be hidden somewhere within the map resources themselves. However, without proper client/server logging, we are currently unable to determine what exactly is causing the crash.
As a result, we cannot identify which specific asset or resource is triggering the problem on that particular console model.
Current memory usage:
