Lumberyard Fatal Error

Amazon, you need to get some mechanic that if a player re-joins the game within 5-15min of a disconnect they’re at the front of the queue. I logged into at 5:30am and was online levelling for 5+hours only to get a Lumberyard (your game engine) fatal error and was kicked out. I then checked the integrity of the files (no issue), joined the 7h15m queue.

7h15min later, load into the game, recall to home to empty bags… open storage and Lumberyard fatal error… validate integrity of files (no issues) and back in a 1800+ queue. There goes my Friday gaming with my friends.

This really is not a good showing for a premium tech company wanting to make a name for it’s self and it’s game engine. please push this as urgent with the character transfer update next week.

7 Likes

Same here, first time getting this error.
Sat in 4h queue, played an hour, and now back to 6h possibly.

5 Likes

Having the same issue with random Lumberyard Fatal Errors. Got into game on Launch day right after the servers launched on the east coast, played nearly all day with no issues. Same for Launch day +1. Last two days I have had random crashes due to a Lumberyard Fatal Error and submitted the crash reports. Each time, back in 3+ hour queue times.

2 Likes

why you don’t take a screenshot of it and post it on the bug section?

In my case, the crashes create a report that I submitted each time, which I would presume they are receiving and reviewing. My main concern is not being able to immediately re-enter in to the game after a crash. Crashes happen and in a lot of games, if you log back in shortly after a crash, you are right back in to the game. In many cases, you are right back in the group/raid you were in when you crashed. My experience with crashes in this game seem to require you to sit through queue times to get back in even if you have an active character sitting in game following a crash.

2 Likes

I am able to reproduce this bug.

It happens when you cast a single heal, with targeted heal activated, and the crash happens when you circle too fast (the mouse scroll in my case) between group members.

This bug needs to be fixed ASAP because it makes the game unplayable when the healer wants to get fast to another player and heal him.

Also +1 for the queuing after a crash. We should be allowed during 2mins to come back into the game after such crashes, avoiding the queue.

3 Likes

Can verify that crash after using the mousewheel while trying to change the target, so target heals are unsable in such situation. War has to go with 49 vs 50 afterwards :frowning:

1 Like

+1 heal “lumberyard error”
+1 for the queuing after a crash

1 Like

I’ve just had this error healing in a settlement (used the scroll wheel to try and select). Fully crashed the game and now back into a queue.

Come on, why is queue protection not a thing. I restarted the game within a minute or 2 and have to go back into a 1380 queue which had just taken me 6 hours to clear. It’s a joke, please sort it out its so frustrating.

I’d only managed to play for 20 mins today and looks like im not going to be able to play at all now.

me too, Lumberyard fatal error random occurs, this time just before looting the final chest at starstone :open_mouth:

just got same while targeting a heal and looking around, I had just turned sticky heal on.

to me it happend after finishing depths dungeon

happened to me as well

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.