Glitch Infinite Loading Screens (of death)...

  • Thread starter Thread starter Crashalot
  • Start date Start date
C

Crashalot

I'm just wondering, after having experienced well over 100 loading screen failures in recent weeks, what is being done about the issue, or is it simply beyond current capabilities?
Do we even know what the problem is or are we close to a workaround or potential solution?
Or do we have to accept that this just may be the new norm for sailing?
Perhaps a clue might be the dual screens that load once porting? Do we really need 2 screens to load when porting?
Is the fancy loading screen a must-have in the game?
And if we can suddenly see our loot, or the loot we lost, once another game client logs on, can it possibly be therein lies the solution?
Maybe someone who understands such things might offer some dialog regarding the issue, just to keep us all in the loop, in hopes that someday this problem will be resolved.
Savor Beta!
 
This is a very well known issue. It will get fixed. I understand wanting details about it, but it’s just another bug. I’d rather have the developer team working on fixes than spending their time talking about fixes.
 
Crashalot said:
And I'd rather have someone let us know how things are going from time to time or if there's any input from us that might be useful, like logs, etc.
You know, community communicating.
Different strokes for different folks I guess....
Click to expand...
I am here telling you how things are. If information was needed, we would definitely ask for it. But as it is, several players have already made threads about this issue as well as emailed their concerns.

And again, I understand wanting information, but there wouldn’t be much to report. It’s either that the bug is on the docket to get fixed, or the cause is being investigated, or the fix isn’t working as expected, or a fix is coming in the next update.

I know this bug is one of those that is more aggravating, but all we can do is be patient. (I have encountered the loading screen myself, so I get it.) The developer team is working hard, as always, I promise you. This isn’t the only bug out there that needs attention.
 
Cheysa Finn said:
I am here telling you how things are. If information was needed, we would definitely ask for it. But as it is, several players have already made threads about this issue as well as emailed their concerns.

And again, I understand wanting information, but there wouldn’t be much to report. It’s either that the bug is on the docket to get fixed, or the cause is being investigated, or the fix isn’t working as expected, or a fix is coming in the next update.

I know this bug is one of those that is more aggravating, but all we can do is be patient. (I have encountered the loading screen myself, so I get it.) The developer team is working hard, as always, I promise you. This isn’t the only bug out there that needs attention.
Click to expand...

What I read from your comments, "telling me like it is", is that you have no idea what, when or why it happens. I got that. However, my request was an appeal to the devs, who perhaps may or may not know what they are dealing with.
Thanks for your input though.
 
My job is to be a voice for the developer team as much as possible so that they can concentrate on doing what they do best with as little distraction as possible. You’re welcome for the input.
 
I think the infinite load screen is with a possible desync between client and server with the connection server nodes to the ocean servers.

To make this sound more understandable. I'll explain it.

You send a packet to the ocean server through the node network. Somewhere between the node network the packet loses some bytes. Which in turn makes the ocean ask for those lost bytes but the node server can't find the client due to lag or ping issues. Then the desynchronisation starts and the ocean server drops the connection, since it cannot get a full information package.

It could also be this and the trouble of loading the client in an island. Which could cause the server to hiccup and jumble up clients, causing the loading to fail.
 
Hernandez said:
I think the infinite load screen is with a possible desync between client and server with the connection server nodes to the ocean servers.

To make this sound more understandable. I'll explain it.

You send a packet to the ocean server through the node network. Somewhere between the node network the packet loses some bytes. Which in turn makes the ocean ask for those lost bytes but the node server can't find the client due to lag or ping issues. Then the desynchronisation starts and the ocean server drops the connection, since it cannot get a full information package.

It could also be this and the trouble of loading the client in an island. Which could cause the server to hiccup and jumble up clients, causing the loading to fail.
Click to expand...

I like the idea, but because the data can be retrieved by logging in again with a new client, it seems unlikely, albeit without the option of retrieving the loot portion of the sea cargo.
Now I do agree that the transfer or handshake is the issue and some infinite loop leaves it hanging.
 
Crashalot said:
I like the idea, but because the data can be retrieved by logging in again with a new client, it seems unlikely, albeit without the option of retrieving the loot portion of the sea cargo.
Now I do agree that the transfer or handshake is the issue and some infinite loop leaves it hanging.
Click to expand...

Yesterday I experienced that another factor that might contribute to the infinite loading screen is having your sea chest open.

When I docked with it closed. Everything went fine.
 
There could be an improvement in the network In/Out as the other day my loading screen hung for 10 minutes + but when I returned I was on the Pirate Launch Page not crashed!

It's hard to imagine not really being much of a programmer how the boys are finding all these little bugs but the hung screen seems to be basically the TLOPO servers at some point for what ever millionth reason saying... "Hey I don't recognise you... are you sure you've been here before? You look different..."

The following figure illustrates the process of a network I/O operation under Windows.

IC486497.png


When an application calls a file I/O function to access a file on a remote computer, the following events occur:

  • The I/O request is intercepted by a network redirector, also referred to simply as a redirector, on the local computer. This is depicted in the preceding figure by the solid arrow between the application and the client redirector.
  • The redirector constructs a data packet containing all of the information about the request, and sends it to the server where the file is located. This is depicted in the preceding figure by the solid arrow between the client redirector and the server redirector.
  • The redirector on the server receives the packet from the client, authenticates the access to the file required by the I/O request, and, if authenticated, executes the request on behalf of the client. If not, it returns an error code to the redirector on the client. This is depicted in the preceding figure by the curved solid arrow between the server redirector and the file.
  • When the request has been executed, the redirector on the server sends any data resulting from the I/O request to the redirector on the client along with a success notification. This is depicted in the preceding figure by the dotted arrow between the server and the client redirector.
  • The redirector on the client receives the packet from the server and passes the data in the packet to the application along with a success notification. This is depicted in the preceding figure by the dotted arrow between the client redirector and the application.
  • If this doesn't work then...
  • :hypno:
  • :pirate ship:
 
I'm checking in to see if this was fixed and one of the release notes said they "potentially" fixed it (Infinite load screen) so was this fixed? I quit playing due to this and the memory leak, was the memory leak addressed at all? Figured I would ask here instead of making a new topic about issues that have been around for a very long time now. Thanks in advance.
 
Radigan said:
I'm checking in to see if this was fixed and one of the release notes said they "potentially" fixed it (Infinite load screen) so was this fixed? I quit playing due to this and the memory leak, was the memory leak addressed at all? Figured I would ask here instead of making a new topic about issues that have been around for a very long time now. Thanks in advance.
Click to expand...
I have not had the infinite loading screen in quite a while so I'm pretty sure it was fixed. No clue about the memory leak.
 
Radigan said:
I'm checking in to see if this was fixed and one of the release notes said they "potentially" fixed it (Infinite load screen) so was this fixed? I quit playing due to this and the memory leak, was the memory leak addressed at all? Figured I would ask here instead of making a new topic about issues that have been around for a very long time now. Thanks in advance.
Click to expand...
Since the last fix a few days ago... I haven't had the screen:eek: So things are moving forward it seems, there's still a list of new additions and bugs as long as you can imagine (depending on your imagination) but that bit seems to be something that's in the past, pretty much or close ;)... nothing like trying to fiddle with a few million lines of code:D
:pirate ship:
 
My main issues were the loading screens and memory leak, if there is progress on those 2 then that is VERY good news and I will be coming back, thanks for the info!
 
You must log in or register to reply here.
Back
Top