Anyone else having problems with being stuck in loading screens? Trying to log onto a char for the 3rd time now, nothing happens for 5 mins, then I'm back in character menu

same here. first my character got kinda stucked. buttons could be clicked but no skill was used. after restarting my computer i'm stucked in laoding screen after character window. server is tulak hord

i could locate the problem a bit. logging into a character on onderon and republic guild vessel will end in infinite loading screen. logging into character on imperial vessel does work. Edited November 4, 2019 by ultimarb

Anyone else having problems with being stuck in loading screens? Trying to log onto a char for the 3rd time now, nothing happens for 5 mins, then I'm back in character menu

 

Same Problem.

Yep, Tulak Hord is having issues, many players in guild and chat are reporting problems. It started at 5:03pm UTC (roughly 1 hour ago) when many players were disconnected from the server. Upon restart, at first I was stuck in the splash screen before character selection but I could log into other servers just fine. Then eventually, I got past character selection but the loading bar was stuck at 60% and I had to Alt+F4 out of the game. I finally was able to login on another computer but only onto a toon standing on fleet. Players are reporting issues traveling to another area. Edited November 4, 2019 by Jerba

Anyone else having problems with being stuck in loading screens? Trying to log onto a char for the 3rd time now, nothing happens for 5 mins, then I'm back in character menu

 

Same Problem.

 

same for me

Tulak Hord too, same problem.

It's the main topic on the Imperial Fleet at the moment. People can't load into FP, Chars who are on Onderon are stuck in the loading screen, GF doesn't work.

Same problem on Republic Side

Oh, and it seems (as far as fleet Chat says) that one can't exit the new duxn OP any more - because of loading sceen issues

 

As somebody on Imperial fleet-Chat just said: Please feed the hamster

 

EDIT: Chat is reporting that loading into a Yavin-Stronghold gets you stuck too

EDIT 2: Can confirm it, Yavin-Stronholds don't work, didn't even get a loading bar and had to close the game via TaskBar

Edited November 4, 2019 by Gamemaron

loading for onderon into pvp instance does work. pve not Edited November 4, 2019 by ultimarb

Tulak Hord, the same, PvP and Starfighter transitions worked as long as the toon was on the fleet; I was able to login on a char standing on Odessen, however, server lag was already 25,000 ms, when the toon was fully loaded and jumped back into the server selection at about 40,000 ms.

Tulak Hord too, same problem.

It's the main topic on the Imperial Fleet at the moment. People can't load into FP, Chars who are on Onderon are stuck in the loading screen, GF doesn't work.

Same problem on Republic Side

 

Same here

After asking in chat:

Republic fleet and Coruscant stronghold are working.

Republic guild ship and Nar Shaddaa stronghold result in being stuck in loading screen.

 

Not sure if it helps but here's a log of me trying to login to the Nathema flashpoint (after a disconnect), then being stuck in loading screen for 4 minutes before pressing Alt+F4:

2019-11-04T18:16:19.682264 02451B68 INFO Login user: Jerba shardaddress: @:: [Client.Startup](playerclient.cpp:PlayerClient::Login:1954)
2019-11-04T18:16:27.047768 02451B68 INFO Renderer using 24-Bit Depth Buffer. [Client.Renderer](dx8cs_services.cpp:`anonymous-namespace'::RendererLogMessageHandler:571)
2019-11-04T18:16:37.336768 02451B68 DEBUG Constructed with desired state [CS_SHARD_CONNECTED] [Connect.firestorm.client.ConnectionObject](connectionobject.cpp:ConnectionObject::ConnectionObject:42)
2019-11-04T18:16:37.336768 02451B68 DEBUG [OMEGACONNECT] Starting login: Jerba : @he4001n01.swtor.com:8995:castlehilltest [Connect.firestorm.client.ConnectionObject](connectionobject.cpp:ConnectionObject::beginConnection:148)
2019-11-04T18:16:37.374746 02451B68 DEBUG setState changing state to [CS_LOGGING_IN] [Connect.firestorm.client.ConnectionObject](connectionobject.cpp:ConnectionObject::setState:63)
2019-11-04T18:16:38.206888 02451B68 INFO [Client] Active area load complete [Client.AreaManager](bwaareamanager.cpp:bwa::AreaManager::_onActiveAreaLoadComplete:932)
2019-11-04T18:16:39.014793 02451B68 DEBUG Game launch reply address = ie1poolf1n1015.swtor.com:20063 [Connect.omega.appframework.ServerProxy](serverproxy.cpp:omega::ServerProxy::ReplyGameLaunch:183)
2019-11-04T18:16:39.315370 02451B68 DEBUG HandleInitialize completed. [Firestorm.firestorm.client.OmegaClientApp](omegaclientapp.cpp:OmegaClientApp::HandleInitialized:413)
2019-11-04T18:16:39.315370 02451B68 DEBUG setState changing state to [CS_APP_INITIALIZED] [Connect.firestorm.client.ConnectionObject](connectionobject.cpp:ConnectionObject::setState:63)
2019-11-04T18:16:39.315370 02451B68 DEBUG setState changing state to [CS_CONNECTING_REPOSITORY] [Connect.firestorm.client.ConnectionObject](connectionobject.cpp:ConnectionObject::setState:63)
2019-11-04T18:16:39.315370 02451B68 DEBUG setState changing state to [CS_REPOSITORY_CONNECTED] [Connect.firestorm.client.ConnectionObject](connectionobject.cpp:ConnectionObject::setState:63)
2019-11-04T18:16:39.315370 02451B68 DEBUG setState changing state to [CS_CONNECTING_COMPILERS] [Connect.firestorm.client.ConnectionObject](connectionobject.cpp:ConnectionObject::setState:63)
2019-11-04T18:16:39.315370 02451B68 DEBUG setState changing state to [CS_COMPILERS_CONNECTED] [Connect.firestorm.client.ConnectionObject](connectionobject.cpp:ConnectionObject::setState:63)
2019-11-04T18:16:39.315370 02451B68 DEBUG setState changing state to [CS_CONNECTING_SHARD] [Connect.firestorm.client.ConnectionObject](connectionobject.cpp:ConnectionObject::setState:63)
2019-11-04T18:16:39.315370 02451B68 DEBUG [sHARDCONNECT] Starting shard server connections [Connect.firestorm.client.ConnectionObject](connectionobject.cpp:ConnectionObject::ScriptCompilersConnected:301)
2019-11-04T18:16:39.510518 02451B68 DEBUG [sHARDCONNECT] All connections for shard connect have fully connected. [Connect.firestorm.client.ConnectionObject](connectionobject.cpp:ConnectionObject::connectionsOpen:109)
2019-11-04T18:16:39.510518 02451B68 DEBUG Connection Object connected to Omega shard [Connect.firestorm.client.ConnectionObject](connectionobject.cpp:ConnectionObject::ConnectedToOmega:326)
2019-11-04T18:16:39.510518 02451B68 DEBUG setState changing state to [CS_SHARD_CONNECTED] [Connect.firestorm.client.ConnectionObject](connectionobject.cpp:ConnectionObject::setState:63)
2019-11-04T18:16:40.305677 02451B68 INFO [Client] Active area load complete [Client.AreaManager](bwaareamanager.cpp:bwa::AreaManager::_onActiveAreaLoadComplete:932)
2019-11-04T18:16:40.664457 02451B68 DEBUG TellCharacterSummaries [Firestorm.firestorm.OmegaWorldObject](omegaworldobject.cpp:OmegaWorldObject::TellCharacterSummaries:429)
2019-11-04T18:17:07.389033 02451B68 DEBUG TravelPending: nathema_flashpoint : 4611686358368677004 : 4611686358368677004 : 3 : \world\areas\4611686358368677004\area.dat [Firestorm.firestorm.OmegaWorldObject](omegaworldobject.cpp:OmegaWorldObject::TravelPending:290)
2019-11-04T18:17:09.644637 02451B68 INFO [Client] Active area load complete [Client.AreaManager](bwaareamanager.cpp:bwa::AreaManager::_onActiveAreaLoadComplete:932)
2019-11-04T18:21:24.998252 02451B68 INFO RemoteRenderer process shutdown complete. [Client.Shutdown](dx8_basic.cpp:OSShutDown:2602)

Edited November 4, 2019 by Jerba

confirm. tulak hord having issues. got kicked from server. needed two attempts to log in again. will quit the game for today, just in case. server repair or something

confirm stuck in onderon log in

Server Tulak Hord. Can't log into my characters, which are in my yavin 4 stronghold. All the others are fine. Naturally, all my high level chars logged out on yavin 4 😔😔😔😔

From the other thread:

Hey folks,

 

We are going to be restarting Tulak Hord to address the issues you are experiencing. It is happening shortly.

 

Thanks, I will let you know when it is live again.

 

-eric

Connection issues still not solved even after server restart...