Date & Time: 22:30 BST Tuesday Aug 4th
Frequency: Prolonged Transition Screens every time I transition and a crash every few hours of prolonged play
World name: Odin
Character name: Deaxes Catperson
Retainer name: N/A
NPC name: N/A
Monster name: N/A
Class/Level: N/A
Party or solo: Both
In-game time: N/A
Area and coordinates: N/A
Housing: N/A
The steps to reproduce these issues quickest are to play in content which has a very large number of players. By far the easiest is to join a reset Tuesday hunt train on Xbox or now Switch 2.
Steps:
1. Find a community run hunt train start time and what server the train is running on
2. World travel to the appropriate server and in game location
3. Attempt to follow the hunt train
Notice the "transition" speed is significantly longer than other players. Additionally, if you attempt to follow a few hunt trains in a row, depending on how many people are there you will get an out of memory crash somewhere in the second or third hunt train.
Another way to reproduce easily right now is in the Occult Crescent in a full or mostly full instance.
Steps:
1. Join a full or mostly full Occult Crescent instance. South or North Horn both work
2. Follow the crowd moving to Fate or Critical Engagements
Notice that the "transition" from Aetheryte Shard to Aetheryte Shard is significantly longer than other players.
Xbox Series X and now Nintendo Switch 2
I am aware of this issue on Switch 2 due to it being recently confirmed on the lodestone here https://eu.finalfantasyxiv.com/lodes...fd503171baf397, however the post itself has clarified an issue I have been having with the Xbox version since its release.
My partner and I play side by side. Her on a base PS5 and me on an Xbox Series X. The Xbox version of the game launched with what is a similar issue to what is present on the Nintendo Switch 2 version of the game with what the lodestone post describes as the prolonged transition times. This was alleviated at some point via a patch to the game to a more usable level, but as me and my partner sit side by side I can easily notice that it still consistently takes me 2 or 3 times longer to get back into gameplay after a teleport. Even if that teleport is to a location in the same map, no matter the distance. I can move a couple of feet by accepting a teleport accidentally to the aetheryite exactly in the same location as I already am and I will take a significant time to get back into gameplay.
As mentioned above, an easy reproduction which is 100% consistent for me is hunt trains. There are a lot of people and you do a new load or transition every 30/60 seconds depending on hunt positions. So it can very quickly cause a lot of graphics resources to need to be cleared and reloaded into memory many many times. Eventually, depending on the number of people in the hunt train it will crash the game. I usually try and cap early on in the week so there are a lot of people on the trains. This usually means I will crash somewhere during the second train.
However, it is not the only way to cause the memory leak crash. Recently, due to the last relic step being a bit of a "Dawntrail world tour" I was queuing all the required duties for the relic step. I got multiple crashes during this time on the Xbox version while my partner never crashed. Simply because we were going in and out and in and out of duties at that rapid pace.
My overall bug report here is complicated due to the lodestone post, I am aware. The team is clearly working on the issue for the Switch 2 version which is relieving to hear. However, what spurred me to write this post is the concern that the issue will be resolved to the same level as the Xbox version is currently for the Switch 2. Where I can confidently say that the problem has not been fully solved. Or that the problem gets fully solved for the Switch and the Xbox version continues to be in this state where the issue is alleviated but not fully fixed.
I would love for this problem to get fixed for both versions so I can fully enjoy the game side by side with my partner and not have to worry and be nervous about when the memory leak crash will hit. Will it be right before the Critical Engagement I need next etc. These concerns dampen my enjoyment of a game I love. So if anything can be done to ensure this problem is gone for good on all platforms that would make me so happy.
If there is anything else I can provide to help with the problem such as my Xbox Gamertag in order to track down the crash reports on the backend or a more precise timestamp of a reproduced crash or anything else, please let me know and I can provide it.
Thank you for reading my very long bug report!
Continue reading...
Frequency: Prolonged Transition Screens every time I transition and a crash every few hours of prolonged play
World name: Odin
Character name: Deaxes Catperson
Retainer name: N/A
NPC name: N/A
Monster name: N/A
Class/Level: N/A
Party or solo: Both
In-game time: N/A
Area and coordinates: N/A
Housing: N/A
The steps to reproduce these issues quickest are to play in content which has a very large number of players. By far the easiest is to join a reset Tuesday hunt train on Xbox or now Switch 2.
Steps:
1. Find a community run hunt train start time and what server the train is running on
2. World travel to the appropriate server and in game location
3. Attempt to follow the hunt train
Notice the "transition" speed is significantly longer than other players. Additionally, if you attempt to follow a few hunt trains in a row, depending on how many people are there you will get an out of memory crash somewhere in the second or third hunt train.
Another way to reproduce easily right now is in the Occult Crescent in a full or mostly full instance.
Steps:
1. Join a full or mostly full Occult Crescent instance. South or North Horn both work
2. Follow the crowd moving to Fate or Critical Engagements
Notice that the "transition" from Aetheryte Shard to Aetheryte Shard is significantly longer than other players.
Xbox Series X and now Nintendo Switch 2
I am aware of this issue on Switch 2 due to it being recently confirmed on the lodestone here https://eu.finalfantasyxiv.com/lodes...fd503171baf397, however the post itself has clarified an issue I have been having with the Xbox version since its release.
My partner and I play side by side. Her on a base PS5 and me on an Xbox Series X. The Xbox version of the game launched with what is a similar issue to what is present on the Nintendo Switch 2 version of the game with what the lodestone post describes as the prolonged transition times. This was alleviated at some point via a patch to the game to a more usable level, but as me and my partner sit side by side I can easily notice that it still consistently takes me 2 or 3 times longer to get back into gameplay after a teleport. Even if that teleport is to a location in the same map, no matter the distance. I can move a couple of feet by accepting a teleport accidentally to the aetheryite exactly in the same location as I already am and I will take a significant time to get back into gameplay.
As mentioned above, an easy reproduction which is 100% consistent for me is hunt trains. There are a lot of people and you do a new load or transition every 30/60 seconds depending on hunt positions. So it can very quickly cause a lot of graphics resources to need to be cleared and reloaded into memory many many times. Eventually, depending on the number of people in the hunt train it will crash the game. I usually try and cap early on in the week so there are a lot of people on the trains. This usually means I will crash somewhere during the second train.
However, it is not the only way to cause the memory leak crash. Recently, due to the last relic step being a bit of a "Dawntrail world tour" I was queuing all the required duties for the relic step. I got multiple crashes during this time on the Xbox version while my partner never crashed. Simply because we were going in and out and in and out of duties at that rapid pace.
My overall bug report here is complicated due to the lodestone post, I am aware. The team is clearly working on the issue for the Switch 2 version which is relieving to hear. However, what spurred me to write this post is the concern that the issue will be resolved to the same level as the Xbox version is currently for the Switch 2. Where I can confidently say that the problem has not been fully solved. Or that the problem gets fully solved for the Switch and the Xbox version continues to be in this state where the issue is alleviated but not fully fixed.
I would love for this problem to get fixed for both versions so I can fully enjoy the game side by side with my partner and not have to worry and be nervous about when the memory leak crash will hit. Will it be right before the Critical Engagement I need next etc. These concerns dampen my enjoyment of a game I love. So if anything can be done to ensure this problem is gone for good on all platforms that would make me so happy.
If there is anything else I can provide to help with the problem such as my Xbox Gamertag in order to track down the crash reports on the backend or a more precise timestamp of a reproduced crash or anything else, please let me know and I can provide it.
Thank you for reading my very long bug report!
Continue reading...