Re: Loading Screen froze with only one character.

by proxos666
Reply

Original Post

Re: Loading Screen froze with only one character.

★★ Apprentice

@proxos666

yep, here you go.

 

Spoiler
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>tracert www.google.com

Tracing route to www.google.com [64.233.184.147]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 68 ms 130 ms 94 ms wa-in-f147.1e100.net [64.233.184.147]

Trace complete.

C:\WINDOWS\system32>
Message 51 of 80 (437 Views)

Re: Loading Screen froze with only one character.

@TheSkiv

 

That looks like some sort of firewall block

 

You are in Italy yes ?

 

I tested from Milan to www.google.com , your ping should be similar if in Italy yet yours is not stable, may need to ascertain why

 

If you do the following command how much is the ping changing up and down after say 30 seconds ?

 

ping -t 64.233.184.147 

 

Router: Milan
Command: ping count 5 64.233.184.147


PING 64.233.184.147 (64.233.184.147): 56 data bytes
64 bytes from 64.233.184.147: icmp_seq=0 ttl=45 time=34.499 ms
64 bytes from 64.233.184.147: icmp_seq=1 ttl=45 time=34.381 ms
64 bytes from 64.233.184.147: icmp_seq=2 ttl=45 time=34.375 ms
64 bytes from 64.233.184.147: icmp_seq=3 ttl=45 time=34.319 ms
64 bytes from 64.233.184.147: icmp_seq=4 ttl=45 time=34.832 ms

--- 64.233.184.147 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 34.319/34.481/34.832/0.185 ms

 

____________________________________________________________


SWTOR Forum Username = OwenBrooks
Australian (Fellow SWTOR Player) volunteer moderator. I do not work for EA.
Photo of my New Speeder 
More information about: Becoming a Champion 
SWTOR FAN Community Website Click Here

Message 52 of 80 (435 Views)

Re: Loading Screen froze with only one character.

★★ Apprentice

@proxos666

no, not Italy.

 

Lithuania.

 

Spoiler
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>ping -t 64.233.184.147

Pinging 64.233.184.147 with 32 bytes of data:
Reply from 64.233.184.147: bytes=32 time=64ms TTL=45
Reply from 64.233.184.147: bytes=32 time=69ms TTL=45
Reply from 64.233.184.147: bytes=32 time=63ms TTL=45
Reply from 64.233.184.147: bytes=32 time=66ms TTL=45
Reply from 64.233.184.147: bytes=32 time=69ms TTL=45
Reply from 64.233.184.147: bytes=32 time=75ms TTL=45
Reply from 64.233.184.147: bytes=32 time=68ms TTL=45
Reply from 64.233.184.147: bytes=32 time=65ms TTL=45
Reply from 64.233.184.147: bytes=32 time=64ms TTL=45
Reply from 64.233.184.147: bytes=32 time=71ms TTL=45
Reply from 64.233.184.147: bytes=32 time=64ms TTL=45
Reply from 64.233.184.147: bytes=32 time=114ms TTL=45
Reply from 64.233.184.147: bytes=32 time=71ms TTL=45
Reply from 64.233.184.147: bytes=32 time=68ms TTL=45
Reply from 64.233.184.147: bytes=32 time=65ms TTL=45
Reply from 64.233.184.147: bytes=32 time=68ms TTL=45
Reply from 64.233.184.147: bytes=32 time=69ms TTL=45
Reply from 64.233.184.147: bytes=32 time=67ms TTL=45
Reply from 64.233.184.147: bytes=32 time=65ms TTL=45
Reply from 64.233.184.147: bytes=32 time=70ms TTL=45
Reply from 64.233.184.147: bytes=32 time=67ms TTL=45
Reply from 64.233.184.147: bytes=32 time=68ms TTL=45
Reply from 64.233.184.147: bytes=32 time=73ms TTL=45
Reply from 64.233.184.147: bytes=32 time=76ms TTL=45
Reply from 64.233.184.147: bytes=32 time=68ms TTL=45
Reply from 64.233.184.147: bytes=32 time=64ms TTL=45
Reply from 64.233.184.147: bytes=32 time=66ms TTL=45
Reply from 64.233.184.147: bytes=32 time=67ms TTL=45
Reply from 64.233.184.147: bytes=32 time=78ms TTL=45
Reply from 64.233.184.147: bytes=32 time=754ms TTL=45
Reply from 64.233.184.147: bytes=32 time=351ms TTL=45
Reply from 64.233.184.147: bytes=32 time=555ms TTL=45
Reply from 64.233.184.147: bytes=32 time=72ms TTL=45
Reply from 64.233.184.147: bytes=32 time=71ms TTL=45
Reply from 64.233.184.147: bytes=32 time=67ms TTL=45
Reply from 64.233.184.147: bytes=32 time=67ms TTL=45
Reply from 64.233.184.147: bytes=32 time=73ms TTL=45
Reply from 64.233.184.147: bytes=32 time=89ms TTL=45
Reply from 64.233.184.147: bytes=32 time=71ms TTL=45
Reply from 64.233.184.147: bytes=32 time=71ms TTL=45
Reply from 64.233.184.147: bytes=32 time=66ms TTL=45
Reply from 64.233.184.147: bytes=32 time=67ms TTL=45
Reply from 64.233.184.147: bytes=32 time=66ms TTL=45
Reply from 64.233.184.147: bytes=32 time=67ms TTL=45
Reply from 64.233.184.147: bytes=32 time=70ms TTL=45
Reply from 64.233.184.147: bytes=32 time=68ms TTL=45
Reply from 64.233.184.147: bytes=32 time=64ms TTL=45
Reply from 64.233.184.147: bytes=32 time=70ms TTL=45

Ping statistics for 64.233.184.147:
Packets: Sent = 48, Received = 48, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 754ms, Average = 100ms
Control-C
^C
C:\WINDOWS\system32>

 

Message 53 of 80 (403 Views)

Re: Loading Screen froze with only one character.

★★ Apprentice

@proxos666

no, not italy.

Lithuania.

 

Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>ping -t 64.233.184.147

Pinging 64.233.184.147 with 32 bytes of data:
Reply from 64.233.184.147: bytes=32 time=64ms TTL=45
Reply from 64.233.184.147: bytes=32 time=69ms TTL=45
Reply from 64.233.184.147: bytes=32 time=63ms TTL=45
Reply from 64.233.184.147: bytes=32 time=66ms TTL=45
Reply from 64.233.184.147: bytes=32 time=69ms TTL=45
Reply from 64.233.184.147: bytes=32 time=75ms TTL=45
Reply from 64.233.184.147: bytes=32 time=68ms TTL=45
Reply from 64.233.184.147: bytes=32 time=65ms TTL=45
Reply from 64.233.184.147: bytes=32 time=64ms TTL=45
Reply from 64.233.184.147: bytes=32 time=71ms TTL=45
Reply from 64.233.184.147: bytes=32 time=64ms TTL=45
Reply from 64.233.184.147: bytes=32 time=114ms TTL=45
Reply from 64.233.184.147: bytes=32 time=71ms TTL=45
Reply from 64.233.184.147: bytes=32 time=68ms TTL=45
Reply from 64.233.184.147: bytes=32 time=65ms TTL=45
Reply from 64.233.184.147: bytes=32 time=68ms TTL=45
Reply from 64.233.184.147: bytes=32 time=69ms TTL=45
Reply from 64.233.184.147: bytes=32 time=67ms TTL=45
Reply from 64.233.184.147: bytes=32 time=65ms TTL=45
Reply from 64.233.184.147: bytes=32 time=70ms TTL=45
Reply from 64.233.184.147: bytes=32 time=67ms TTL=45
Reply from 64.233.184.147: bytes=32 time=68ms TTL=45
Reply from 64.233.184.147: bytes=32 time=73ms TTL=45
Reply from 64.233.184.147: bytes=32 time=76ms TTL=45
Reply from 64.233.184.147: bytes=32 time=68ms TTL=45
Reply from 64.233.184.147: bytes=32 time=64ms TTL=45
Reply from 64.233.184.147: bytes=32 time=66ms TTL=45
Reply from 64.233.184.147: bytes=32 time=67ms TTL=45
Reply from 64.233.184.147: bytes=32 time=78ms TTL=45
Reply from 64.233.184.147: bytes=32 time=754ms TTL=45
Reply from 64.233.184.147: bytes=32 time=351ms TTL=45
Reply from 64.233.184.147: bytes=32 time=555ms TTL=45
Reply from 64.233.184.147: bytes=32 time=72ms TTL=45
Reply from 64.233.184.147: bytes=32 time=71ms TTL=45
Reply from 64.233.184.147: bytes=32 time=67ms TTL=45
Reply from 64.233.184.147: bytes=32 time=67ms TTL=45
Reply from 64.233.184.147: bytes=32 time=73ms TTL=45
Reply from 64.233.184.147: bytes=32 time=89ms TTL=45
Reply from 64.233.184.147: bytes=32 time=71ms TTL=45
Reply from 64.233.184.147: bytes=32 time=71ms TTL=45
Reply from 64.233.184.147: bytes=32 time=66ms TTL=45
Reply from 64.233.184.147: bytes=32 time=67ms TTL=45
Reply from 64.233.184.147: bytes=32 time=66ms TTL=45
Reply from 64.233.184.147: bytes=32 time=67ms TTL=45
Reply from 64.233.184.147: bytes=32 time=70ms TTL=45
Reply from 64.233.184.147: bytes=32 time=68ms TTL=45
Reply from 64.233.184.147: bytes=32 time=64ms TTL=45
Reply from 64.233.184.147: bytes=32 time=70ms TTL=45

Ping statistics for 64.233.184.147:
Packets: Sent = 48, Received = 48, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 754ms, Average = 100ms
Control-C
^C
C:\WINDOWS\system32>

Message 54 of 80 (404 Views)

Re: Loading Screen froze with only one character.

★★ Apprentice

@proxos666

im in Lithuania.

 

3 times this bloody forum deleted this post.

Message 55 of 80 (426 Views)

Re: Loading Screen froze with only one character.

★★ Apprentice

@proxos666

 

Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>ping -t 64.233.184.147

Pinging 64.233.184.147 with 32 bytes of data:
Reply from 64.233.184.147: bytes=32 time=64ms TTL=45
Reply from 64.233.184.147: bytes=32 time=69ms TTL=45
Reply from 64.233.184.147: bytes=32 time=63ms TTL=45
Reply from 64.233.184.147: bytes=32 time=66ms TTL=45
Reply from 64.233.184.147: bytes=32 time=69ms TTL=45
Reply from 64.233.184.147: bytes=32 time=75ms TTL=45
Reply from 64.233.184.147: bytes=32 time=68ms TTL=45
Reply from 64.233.184.147: bytes=32 time=65ms TTL=45
Reply from 64.233.184.147: bytes=32 time=64ms TTL=45
Reply from 64.233.184.147: bytes=32 time=71ms TTL=45
Reply from 64.233.184.147: bytes=32 time=64ms TTL=45
Reply from 64.233.184.147: bytes=32 time=114ms TTL=45
Reply from 64.233.184.147: bytes=32 time=71ms TTL=45
Reply from 64.233.184.147: bytes=32 time=68ms TTL=45
Reply from 64.233.184.147: bytes=32 time=65ms TTL=45
Reply from 64.233.184.147: bytes=32 time=68ms TTL=45
Reply from 64.233.184.147: bytes=32 time=69ms TTL=45
Reply from 64.233.184.147: bytes=32 time=67ms TTL=45
Reply from 64.233.184.147: bytes=32 time=65ms TTL=45
Reply from 64.233.184.147: bytes=32 time=70ms TTL=45
Reply from 64.233.184.147: bytes=32 time=67ms TTL=45
Reply from 64.233.184.147: bytes=32 time=68ms TTL=45
Reply from 64.233.184.147: bytes=32 time=73ms TTL=45
Reply from 64.233.184.147: bytes=32 time=76ms TTL=45
Reply from 64.233.184.147: bytes=32 time=68ms TTL=45
Reply from 64.233.184.147: bytes=32 time=64ms TTL=45
Reply from 64.233.184.147: bytes=32 time=66ms TTL=45
Reply from 64.233.184.147: bytes=32 time=67ms TTL=45
Reply from 64.233.184.147: bytes=32 time=78ms TTL=45
Reply from 64.233.184.147: bytes=32 time=754ms TTL=45
Reply from 64.233.184.147: bytes=32 time=351ms TTL=45
Reply from 64.233.184.147: bytes=32 time=555ms TTL=45
Reply from 64.233.184.147: bytes=32 time=72ms TTL=45
Reply from 64.233.184.147: bytes=32 time=71ms TTL=45
Reply from 64.233.184.147: bytes=32 time=67ms TTL=45
Reply from 64.233.184.147: bytes=32 time=67ms TTL=45
Reply from 64.233.184.147: bytes=32 time=73ms TTL=45
Reply from 64.233.184.147: bytes=32 time=89ms TTL=45
Reply from 64.233.184.147: bytes=32 time=71ms TTL=45
Reply from 64.233.184.147: bytes=32 time=71ms TTL=45
Reply from 64.233.184.147: bytes=32 time=66ms TTL=45
Reply from 64.233.184.147: bytes=32 time=67ms TTL=45
Reply from 64.233.184.147: bytes=32 time=66ms TTL=45
Reply from 64.233.184.147: bytes=32 time=67ms TTL=45
Reply from 64.233.184.147: bytes=32 time=70ms TTL=45
Reply from 64.233.184.147: bytes=32 time=68ms TTL=45
Reply from 64.233.184.147: bytes=32 time=64ms TTL=45
Reply from 64.233.184.147: bytes=32 time=70ms TTL=45

Ping statistics for 64.233.184.147:
    Packets: Sent = 48, Received = 48, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 63ms, Maximum = 754ms, Average = 100ms
Control-C
^C
C:\WINDOWS\system32>
Message 56 of 80 (450 Views)

Re: Loading Screen froze with only one character.

[ Edited ]

@TheSkiv

 

11:30pm here now so gone for the night

 

I tested from Tinklomatas lt to the same IP

 

I am trying to establish if there is a connection or firewall issue going on here, the site shouldn't be deleting you posts , it may be a symptom of something else going on ?

 

Tracing the route to wa-in-f147.1e100.net (64.233.184.147)
     
    1 84.15.6.214 0 msec
      84.15.6.170 0 msec
      84.15.6.214 0 msec
    2 72.14.210.165 [AS 15169] 28 msec 28 msec 28 msec
      3 216.239.56.26 [AS 15169] 28 msec 28 msec 28 msec
      4 216.239.51.177 [AS 15169] [MPLS: Label 457635 Exp 4] 32 msec
        216.239.56.103 [AS 15169] [MPLS: Label 629285 Exp 4] 28 msec
        216.239.51.177 [AS 15169] [MPLS: Label 457635 Exp 4] 32 msec
      5 216.239.40.178 [AS 15169] [MPLS: Label 25727 Exp 4] 36 msec
        216.239.40.214 [AS 15169] [MPLS: Label 24589 Exp 4] 36 msec
        209.85.243.108 [AS 15169] [MPLS: Label 302825 Exp 4] 32 msec
      6 74.125.37.103 [AS 15169] [MPLS: Label 27101 Exp 4] 36 msec
        74.125.37.150 [AS 15169] [MPLS: Label 28104 Exp 4] 36 msec
        74.125.37.103 [AS 15169] [MPLS: Label 25012 Exp 4] 36 msec
      7 216.239.51.147 [AS 15169] 40 msec
        72.14.238.215 [AS 15169] 44 msec
        66.249.95.252 [AS 15169] 40 msec
      8 * * *
      9 wa-in-f147.1e100.net (64.233.184.147) [AS 15169] 32 msec 36 msec 36 msec
    vl000-r-010>
 

 

 

 

 

 

 

 

 

____________________________________________________________


SWTOR Forum Username = OwenBrooks
Australian (Fellow SWTOR Player) volunteer moderator. I do not work for EA.
Photo of my New Speeder 
More information about: Becoming a Champion 
SWTOR FAN Community Website Click Here

Message 57 of 80 (476 Views)

Re: Loading Screen froze with only one character.

★★ Apprentice

@proxos666

well, i cant think of anything. Frown The posts appear for several seconds, but when i refresh they are gone.

 

Have a good night then. Hope you'll have some ideas about my problem tomorrow.

Message 58 of 80 (469 Views)

Re: Loading Screen froze with only one character.

[ Edited ]
★★ Apprentice

@proxos666

@DBWoodynz

so i went through all of the steps on the "how to install on windows 10" guide. Nothing helps! Frown Here is the last log of me running the game. 

 

Spoiler
2015-10-08T09:17:23.799992 00768978 INFO Login user: TheSkiv shardaddress: @:: [Client.Startup](playerclient.cpp:PlayerClient::Login:1920)
2015-10-08T09:17:29.115365 00768978 INFO Renderer using 24-Bit Depth Buffer. [Client.Renderer](dx8cs_services.cpp:`anonymous-namespace'::RendererLogMessageHandler:571)
2015-10-08T09:17:43.154705 00768978 DEBUG Constructed with desired state [CS_SHARD_CONNECTED] [Connect.firestorm.client.ConnectionObject](connectionobject.cpp:ConnectionObject::ConnectionObject:42)
2015-10-08T09:17:43.155720 00768978 DEBUG [OMEGACONNECT] Starting login: TheSkiv : @he6124n01.swtor.com:8995:castlehilltest [Connect.firestorm.client.ConnectionObject](connectionobject.cpp:ConnectionObject::beginConnection:148)
2015-10-08T09:17:43.346279 00768978 DEBUG setState changing state to [CS_LOGGING_IN] [Connect.firestorm.client.ConnectionObject](connectionobject.cpp:ConnectionObject:ConfusedetState:63)
2015-10-08T09:17:44.433988 00768978 INFO [Client] Active area load complete [Client.AreaManager](bwaareamanager.cpp:bwa::AreaManager::_onActiveAreaLoadComplete:895)
2015-10-08T09:17:45.178487 00768978 DEBUG Game launch reply address = ie1poolf1n0002.swtor.com:20063 [Connect.omega.appframework.ServerProxy](serverproxy.cpp:omega::ServerProxy::ReplyGameLaunch:183)
2015-10-08T09:17:45.681168 00768978 DEBUG HandleInitialize completed. [Firestorm.firestorm.client.OmegaClientApp](omegaclientapp.cpp:OmegaClientApp::HandleInitialized:413)
2015-10-08T09:17:45.681168 00768978 DEBUG setState changing state to [CS_APP_INITIALIZED] [Connect.firestorm.client.ConnectionObject](connectionobject.cpp:ConnectionObject:ConfusedetState:63)
2015-10-08T09:17:45.681168 00768978 DEBUG setState changing state to [CS_CONNECTING_REPOSITORY] [Connect.firestorm.client.ConnectionObject](connectionobject.cpp:ConnectionObject:ConfusedetState:63)
2015-10-08T09:17:45.681168 00768978 DEBUG setState changing state to [CS_REPOSITORY_CONNECTED] [Connect.firestorm.client.ConnectionObject](connectionobject.cpp:ConnectionObject:ConfusedetState:63)
2015-10-08T09:17:45.681168 00768978 DEBUG setState changing state to [CS_CONNECTING_COMPILERS] [Connect.firestorm.client.ConnectionObject](connectionobject.cpp:ConnectionObject:ConfusedetState:63)
2015-10-08T09:17:45.681168 00768978 DEBUG setState changing state to [CS_COMPILERS_CONNECTED] [Connect.firestorm.client.ConnectionObject](connectionobject.cpp:ConnectionObject:ConfusedetState:63)
2015-10-08T09:17:45.681168 00768978 DEBUG setState changing state to [CS_CONNECTING_SHARD] [Connect.firestorm.client.ConnectionObject](connectionobject.cpp:ConnectionObject:ConfusedetState:63)
2015-10-08T09:17:45.681168 00768978 DEBUG [SHARDCONNECT] Starting shard server connections [Connect.firestorm.client.ConnectionObject](connectionobject.cpp:ConnectionObject::ScriptCompilersConnected:301)
2015-10-08T09:17:46.104638 00768978 DEBUG [SHARDCONNECT] All connections for shard connect have fully connected. [Connect.firestorm.client.ConnectionObject](connectionobject.cpp:ConnectionObject::connectionsOpen:109)
2015-10-08T09:17:46.104638 00768978 DEBUG Connection Object connected to Omega shard [Connect.firestorm.client.ConnectionObject](connectionobject.cpp:ConnectionObject::ConnectedTOopsmega:326)
2015-10-08T09:17:46.104638 00768978 DEBUG setState changing state to [CS_SHARD_CONNECTED] [Connect.firestorm.client.ConnectionObject](connectionobject.cpp:ConnectionObject:ConfusedetState:63)
2015-10-08T09:17:46.619995 00768978 INFO [Client] Active area load complete [Client.AreaManager](bwaareamanager.cpp:bwa::AreaManager::_onActiveAreaLoadComplete:895)
2015-10-08T09:17:47.128383 00768978 DEBUG TellCharacterSummaries [Firestorm.firestorm.OmegaWorldObject](omegaworldobject.cpp:OmegaWorldObject::TellCharacterSummaries:413)
2015-10-08T09:17:58.911029 00768978 DEBUG TravelPending: tython_blockout : 4611686019869492753 : 4611686019869492753 : 1 : \world\areas\4611686019869492753\area.dat [Firestorm.firestorm.OmegaWorldObject](omegaworldobject.cpp:OmegaWorldObject::TravelPending:274)
2015-10-08T09:18:06.669944 00768978 INFO [Client] Active area load complete [Client.AreaManager](bwaareamanager.cpp:bwa::AreaManager::_onActiveAreaLoadComplete:895)
2015-10-08T09:19:44.131187 00768978 INFO RemoteRenderer process shutdown complete. [Client.Shutdown](dx8_basic.cpp:OSShutDown:2595)
Message 59 of 80 (460 Views)

Re: Loading Screen froze with only one character.

[ Edited ]

@TheSkiv

 

Whist I am not 100% certain your link is the best it can be at present.

 

Going over things and the fact your tracert is showing classic firewall restrictions.

Normally when like this the router/modem needs to allow ICMP Time to Live Exceeded packets

The reason the last hop responds is it does with an echo-reply message and not a TTL exceeded.

 

Can you confirm these ports are open on your router/modem firewall ?

____________________________________________________________


SWTOR Forum Username = OwenBrooks
Australian (Fellow SWTOR Player) volunteer moderator. I do not work for EA.
Photo of my New Speeder 
More information about: Becoming a Champion 
SWTOR FAN Community Website Click Here

Message 60 of 80 (436 Views)