These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Issues, Workarounds & Localization

 
  • Topic is locked indefinitely.
Previous page12
 

Has anyone else been experience warping away issues or screen loading issues when losing a ship

First post
Author
Previous Topic Next Topic
Goremageddon Box
Guerrilla Flotilla
#21 - 2012-06-23 14:37:45 UTC
I also notice lag while undocking, warping, anything I click takes awhile before the action seems to be processed. It seems much slower then I remember before.
Bruce Wie
Useless Industries
Memento Moriendo
#22 - 2012-06-23 20:12:14 UTC
Ravenclaw2kk wrote:
I've not had the lag issue while my ship is exploding (and that happens a lot) but i have noticed a lot more socket disconnects than i am used to, but with myself and fellow fleet members.

Something in the patch borked things up, i hope they find it and fix it.



Yeah ive had them randomly happening as well. Yeah this patch has done something, but they wont acknowledge it.

Your tinfoil hat is in the post.
Indahmawar Fazmarai
#23 - 2012-06-23 20:23:16 UTC
Had this trouble docking, my ship was still in space after Aura said "docking request accepted", than after some 20 seconds i was disconnected, then logged in back and my ship was in station... luckiily.
Bruce Wie
Useless Industries
Memento Moriendo
#24 - 2012-06-24 19:47:30 UTC
Indahmawar Fazmarai wrote:
Had this trouble docking, my ship was still in space after Aura said "docking request accepted", than after some 20 seconds i was disconnected, then logged in back and my ship was in station... luckiily.



Yeah socket closures also seem to be creeping up to an unacceptable level.

Your tinfoil hat is in the post.
Bruce Wie
Useless Industries
Memento Moriendo
#25 - 2012-06-24 19:56:41 UTC
EVE is Serious Business: You shall not feel entitled to being allowed to play EVE just because you are paying it.



Love that quote

Your tinfoil hat is in the post.
Bruce Wie
Useless Industries
Memento Moriendo
#26 - 2012-06-24 21:25:47 UTC
Goremageddon Box wrote:
I also notice lag while undocking, warping, anything I click takes awhile before the action seems to be processed. It seems much slower then I remember before.



MM yeah

Your tinfoil hat is in the post.
Bruce Wie
Useless Industries
Memento Moriendo
#27 - 2012-06-25 19:48:52 UTC
Goremageddon Box wrote:
I also notice lag while undocking, warping, anything I click takes awhile before the action seems to be processed. It seems much slower then I remember before.



It is much slower especially using the jump function.

Your tinfoil hat is in the post.
ISD Stensson
The Scope
Gallente Federation
#28 - 2012-06-25 19:55:09 UTC
Thread moved from EVE General Discussion to Issues, Workarounds & Localization forum.

[b]ISD Stensson Captain Community Communication Liaisons (CCLs) Interstellar Services Department[/b]
HeyImStuck
Republic University
Minmatar Republic
#29 - 2012-06-25 20:48:59 UTC
CCP Sputnik wrote:
Sione Tolutau wrote:
Hi guys sorry I've posted this in another thread but I am having the exact same issue
Location: New Zealand
ISP: slingshot

I don't have any packet loss when it happens for me. ping -t was this at all times from log in to "Socket was closed":
Reply from 87.237.38.200: bytes=32 time=301ms TTL=108

and tracert was this:

2 11 ms 11 ms 11 ms cpiak1-l9-G-internet.tranzpeer.net [202.180.81.32]
3 12 ms 10 ms 11 ms vlan93-cpcak3-e1.tranzpeer.net [202.180.76.68]
4 11 ms 11 ms 10 ms vlan7-cpcak3-s1.tranzpeer.net [202.180.81.49]
5 44 ms 11 ms 12 ms x7-1-0-101.akbr5.global-gateway.net.nz [202.50.234.61]
6 12 ms 11 ms 12 ms ae1-2.akbr4.global-gateway.net.nz [202.50.232.77]
7 12 ms 12 ms 11 ms ae1-10.tkbr9.global-gateway.net.nz [202.50.232.37]
8 135 ms 142 ms 136 ms xe7-0-0.labr5.global-gateway.net.nz [202.50.232.18]
9 168 ms 167 ms 173 ms ae1-3.sjbr2.global-gateway.net.nz [203.96.120.94]
10 167 ms 169 ms 149 ms ae0.pabr4.global-gateway.net.nz [203.96.120.74]
11 169 ms 168 ms 138 ms vlan60.csw1.SanJose1.Level3.net [4.69.152.62]
12 146 ms 147 ms 149 ms vlan60.csw1.SanJose1.Level3.net [4.69.152.62]
13 141 ms 141 ms 211 ms ae-2-2.ebr2.NewYork1.Level3.net [4.69.135.186]
14 208 ms 211 ms 205 ms ae-92-92.csw4.NewYork1.Level3.net [4.69.148.46]
15 220 ms 209 ms 212 ms ae-92-92.csw4.NewYork1.Level3.net [4.69.148.46]
16 274 ms 208 ms 208 ms ae-91-91.ebr1.NewYork1.Level3.net [4.69.134.77]
17 285 ms 278 ms 284 ms ae-56-221.csw2.London1.Level3.net [4.69.153.130]
18 274 ms 273 ms 278 ms ae-56-221.csw2.London1.Level3.net [4.69.153.130]
19 * 273 ms 277 ms ae-2-52.edge4.London1.Level3.net [4.69.139.106]
20 278 ms 283 ms 302 ms srv248-e.ccp.cc [87.237.36.248]
21 305 ms 311 ms 307 ms srv248-e.ccp.cc [87.237.36.248]
22 307 ms 302 ms 312 ms srv200-g.ccp.cc [87.237.38.200]

hope this helps..


Thank you Sione Tolutau.

I wanted to highlight your post to show people which information they should include in their petitions about the socket closed issue. Having all this information makes it a lot easier for us to figure out who, in this long trace, is responsible for dropping the ball/package.

PS. You might not see the package loss via ping -t if only packages within specific port rages get dropped.



While your computer generates some records, these records are generated client side and are not considered conclusive regarding reimbursement. According to our records, your ------- was killed at 20:30:52 and your pod was lost at 20:30:59. Any discrepancies with your own record of events indicates an issue either with your EVE client, your local computer's hardware or software, your local internet connection or third party hardware or software between the game server and your local client. Unfortunately, such issues are not eligible for reimbursement.

Explain that please dev. you provide evidence they tell you" While your computer generates some records, these records are generated client side and are not considered conclusive regarding reimbursement." Petition denied.
Bruce Wie
Useless Industries
Memento Moriendo
#30 - 2012-06-26 15:29:25 UTC
HeyImStuck wrote:
CCP Sputnik wrote:
Sione Tolutau wrote:
Hi guys sorry I've posted this in another thread but I am having the exact same issue
Location: New Zealand
ISP: slingshot

I don't have any packet loss when it happens for me. ping -t was this at all times from log in to "Socket was closed":
Reply from 87.237.38.200: bytes=32 time=301ms TTL=108

and tracert was this:

2 11 ms 11 ms 11 ms cpiak1-l9-G-internet.tranzpeer.net [202.180.81.32]
3 12 ms 10 ms 11 ms vlan93-cpcak3-e1.tranzpeer.net [202.180.76.68]
4 11 ms 11 ms 10 ms vlan7-cpcak3-s1.tranzpeer.net [202.180.81.49]
5 44 ms 11 ms 12 ms x7-1-0-101.akbr5.global-gateway.net.nz [202.50.234.61]
6 12 ms 11 ms 12 ms ae1-2.akbr4.global-gateway.net.nz [202.50.232.77]
7 12 ms 12 ms 11 ms ae1-10.tkbr9.global-gateway.net.nz [202.50.232.37]
8 135 ms 142 ms 136 ms xe7-0-0.labr5.global-gateway.net.nz [202.50.232.18]
9 168 ms 167 ms 173 ms ae1-3.sjbr2.global-gateway.net.nz [203.96.120.94]
10 167 ms 169 ms 149 ms ae0.pabr4.global-gateway.net.nz [203.96.120.74]
11 169 ms 168 ms 138 ms vlan60.csw1.SanJose1.Level3.net [4.69.152.62]
12 146 ms 147 ms 149 ms vlan60.csw1.SanJose1.Level3.net [4.69.152.62]
13 141 ms 141 ms 211 ms ae-2-2.ebr2.NewYork1.Level3.net [4.69.135.186]
14 208 ms 211 ms 205 ms ae-92-92.csw4.NewYork1.Level3.net [4.69.148.46]
15 220 ms 209 ms 212 ms ae-92-92.csw4.NewYork1.Level3.net [4.69.148.46]
16 274 ms 208 ms 208 ms ae-91-91.ebr1.NewYork1.Level3.net [4.69.134.77]
17 285 ms 278 ms 284 ms ae-56-221.csw2.London1.Level3.net [4.69.153.130]
18 274 ms 273 ms 278 ms ae-56-221.csw2.London1.Level3.net [4.69.153.130]
19 * 273 ms 277 ms ae-2-52.edge4.London1.Level3.net [4.69.139.106]
20 278 ms 283 ms 302 ms srv248-e.ccp.cc [87.237.36.248]
21 305 ms 311 ms 307 ms srv248-e.ccp.cc [87.237.36.248]
22 307 ms 302 ms 312 ms srv200-g.ccp.cc [87.237.38.200]

hope this helps..


Thank you Sione Tolutau.

I wanted to highlight your post to show people which information they should include in their petitions about the socket closed issue. Having all this information makes it a lot easier for us to figure out who, in this long trace, is responsible for dropping the ball/package.

PS. You might not see the package loss via ping -t if only packages within specific port rages get dropped.



While your computer generates some records, these records are generated client side and are not considered conclusive regarding reimbursement. According to our records, your ------- was killed at 20:30:52 and your pod was lost at 20:30:59. Any discrepancies with your own record of events indicates an issue either with your EVE client, your local computer's hardware or software, your local internet connection or third party hardware or software between the game server and your local client. Unfortunately, such issues are not eligible for reimbursement.

Explain that please dev. you provide evidence they tell you" While your computer generates some records, these records are generated client side and are not considered conclusive regarding reimbursement." Petition denied.





Funny you get moved and nobody can hear you scream

Your tinfoil hat is in the post.
Bruce Wie
Useless Industries
Memento Moriendo
#31 - 2012-06-27 01:22:29 UTC
Ravenclaw2kk wrote:
I've not had the lag issue while my ship is exploding (and that happens a lot) but i have noticed a lot more socket disconnects than i am used to, but with myself and fellow fleet members.

Something in the patch borked things up, i hope they find it and fix it.




Totally agree with you there .

Your tinfoil hat is in the post.
Bruce Wie
Useless Industries
Memento Moriendo
#32 - 2012-06-28 11:14:15 UTC

Patch notes for EVE Online: Inferno 1.1.3

To be released on Thursday, June 28, 2012.

Miscellaneous

Removed excessive saving of user settings during session change and improved the speed of settings serialization.



Finally they acknowledge the problem

Your tinfoil hat is in the post.
Previous page12