LAMBDA Crash
I have the same thing happen every time. Then I have to log in again and it successfully loads. 40% just like you
Oh, I'm a Claws/Dark scrapper. So i dont think that our character info is relevant
This has been going on for WEEKS !!!! I have started threads.. petitioned it.. bugged it.. NO FIX YET...
Do the devs have any friggin idea how annoying it is to stand around for 10-15 mnins while a team is assembled for you to only get KICKED from the lading screen back to the Login screen and then you CANNOT get back on the trial...
Seriously.. FIX THIS.. its a major issue..
The hard things I can do--- The impossible just take a little bit longer.
If numbers are so much more important than a teammate who is fun to play with, forget about the game altogether and go play with a calculator instead. -Claws and Effect-
Any info on this ??
+1. I've been using the rejoin last event button under the LFG tab and can get back in, but sometimes it takes me two tries. But with the time it takes for the game to freeze, then log out, and log back in again the trial is almost over. I've resigned myself to just not joining LAMBDA teams anymore.
+1. I've been using the rejoin last event button under the LFG tab and can get back in, but sometimes it takes me two tries. But with the time it takes for the game to freeze, then log out, and log back in again the trial is almost over. I've resigned myself to just not joining LAMBDA teams anymore.
|
3rd time does not work for me
4th time does not work for me
5th time does not work for me
league zones back.
I can run BAFs all day, every day. Ten, twenty in a row. Zero issues.
Run a Lambda? Random FPS spikes. Run a second Lambda? Crash.
Run a BAF, then Lambda? Crash. Every time.
I have not been able to get on a LAMBDA trial since last patch (does not happen in the BAF or Keys)
as the team starts to load for the trial my loading screen freezes at about 40% and crashes the game back to log in screen when I log in again and try to reload it does the same rinse and repeat.
Has anyone else had these issues ?