VGOEmulator.net

Today's update on this, seems to be a real big mess going on. I was online, to grab the screenshot of Abilities and was merely standing there in IoD not moving. I was fine for 20 mins, when a 2nd player logged in -- immediately, my client closed. I tried to get back in, and soon as I clicked Play, my client closed. There are no errors or warnings in the console log. After my next attempt, I am back in the world but was unusual behavior.

This is on the latest SVN rev as of this morning.

Check out this oddity, it might be a hint into what's going on. My character "Cleveland" was camped in Khal, which is a fairly populated area. I signed into the game and right away I typed .rift Halgarad, because I wanted to go see my people. I began to .rift, when I landed in Halgarad for a second, then immediately got the splash screen again and was back to character select.

Theory? If all the spawns being sent to the client haven't made it there yet, and you leave, crash (client, not world).

Log:
Edit: So far, any place I .rift to is causing a disconnect. It could be that I loaded all characters up with all their abilities (~200 or so ea). So
Theory2: It could be simply related to the amount of data we're shoving at the client, and not being patient enough for it to process it all (?) as Blackstorm also getting kicked to Char Select - and predominantly after I've set everyone up for 150-200 abilities to shove to their book. Not blaming Abilities, but this added data could help expose the real problem.

To test, try your existing chars with 15+ pages of abilities. Rift around. if you crash, make a new toon which will have only 1 page of abilities. Rift again. Note any crashes or client boots.

Logged in a bit ago with Character: Zarlore and here is what occurred:

I CTD's twice on my initial attempt to log into the game (khal) to see the new abilities.
After waiting about 15 minutes, I was able to stay connected and use the /reloadui and check out the abilities just fine.

after a few moments of moving around khal, I tried to .rift to another chuck. I entered IsleofDawn fine but Crashed to Character Select after 20 secs or so after entering chunk

I waited about 5 minutes and attempted to log in again and immediately was sent back to Character select
Clicked "Play" again at character select and successfully entered IsleOfDawn
The Abilities dialog only showed 9
I performed a /reloadui and all 14 pages re-populated
Ran around IsleofDawn - no issues

I .rifted to Khal and crashed to Character Select immediately
Clicked Play, entered khal for a few secs, and then crashed to Character Select.

Hope this helps a bit

Continued....

I waited about 5 mintes at character select and entered khal but was dropped back to Character Select in 5 secs
I immediately hit play and entered khal just fine.
No Abilities listed in the Dialog
performed a /reloadui and all 14 pages appeared. no issues
.speed seems to be disabled or not working
Crashed to Character Selected after 2 minutes

* Unstable *

Thanks for the confirmation. I just restarted New Telon this minute, removing all abilities except Starter ones that Faux implemented. We'll look into the problem now that it's easily reproducible. Let us know if the world is still unstable with very few abilities loaded (though I still do not feel Abilities themselves are causing it, but exacerbating whatever problems we already had).

Well reverting back certainly cleared up the instability. No issues to report with just the handful of abilities

Here's another thing that just happened, that has happened before in exactly the same manner.

I was once again standing in the world for an undetermined length of time (afk painting a bedroom ) so it was >>a while<<.
[quote]15:34:44.452 D Command Player 'John' .rift to chunk 'Khal' (85)[/quote]
I came back to the desk and noticed I was still there, in Khal, facing the city. There was 1 NPC in my view point. I turned 180 degrees around, the buildings drew in as did the NPCs directly behind me. Not 5 mins later, I CTD, client closed.
[quote]17:07:07.240 I UDP New client connected from 71.55.77.225:50932
17:07:07.240 I UDP Received session request from 71.55.77.225:50932 with connection ID 1336182441
17:07:07.286 I Chunk Chunk shutdown cancelled for Jalen's Crossing.
17:07:07.474 I Chunk New Session: Account ID: 312 Session ID: 'e4jrs003b6bao192kattlst1e4'
17:07:07.739 D Chunk control_text='HELLO REVISION=0 MINVER=3151 VER=3186'
17:07:07.973 D Chunk control_text='LOGIN'
17:07:17.988 I UDP Client from 98.223.250.51:64289 set to disconnect : Timeout
17:07:21.717 I Chunk Shutdown timer expired. Shutting down Ca'ial Brael.
17:07:23.059 I UDP Client from 98.223.250.51:64289 has been removed.
17:07:23.059 D Account Client Destroyed: 4
17:08:46.207 D Char Character Amnath Set to Offline
17:08:46.207 I UDP Client from 71.55.77.225:50931 set to disconnect : Timeout
17:08:51.277 I UDP Client from 71.55.77.225:50931 has been removed.
17:08:51.277 D Account Client Destroyed: 3
17:08:55.692 I UDP Client from 71.55.77.225:50932 set to disconnect : Timeout
17:08:56.347 D Char Character John Set to Offline
17:08:56.347 I UDP Client from 68.98.218.5:62235 set to disconnect : Timeout
17:09:00.762 I UDP Client from 71.55.77.225:50932 has been removed.
17:09:00.762 D Account Client Destroyed: 2
17:09:01.417 I UDP Client from 68.98.218.5:62235 has been removed.
17:09:01.417 D Account Client Destroyed: 1
17:09:05.895 I Chunk Starting chunk shutdown timer for Jalen's Crossing.
17:09:22.494 D Char Character Amnath Set to Offline
17:09:22.494 D Char Saved character 'Amnath Garanov' (517) data.
17:09:22.697 D Account Character Destroyed: 1
17:09:37.174 D Char Character John Set to Offline
17:09:37.174 I UDP Client from 68.98.218.5:58495 set to disconnect : Timeout
17:09:42.244 I UDP Client from 68.98.218.5:58495 has been removed.
17:09:42.244 D Account Client Destroyed: 0
17:09:42.307 I Chunk Starting chunk shutdown timer for Khal.[/quote]
Was this a mass-disconnect again? Or coincidentally the moment I turn 180 degrees around, everyone gets disconnected?

[quote]12:28:25.553 E UDP Received packet with unknown protocol opcode 0x2C00 (11264) from 71.207.194.112:58732
0000: 2C 00 09 03 83 ,....
12:28:25.553 D Char Character Msbhaven Set to Offline
12:28:25.553 I UDP Client from 71.207.194.112:58732 set to disconnect : Application
12:28:25.834 D Account Client Created: 3
12:28:25.834 I UDP New client connected from 71.207.194.112:58732
12:28:25.834 I UDP Client from 71.207.194.112:58732 set to disconnect : Application
12:28:25.865 D Account Client Created: 4
12:28:25.865 I UDP New client connected from 71.207.194.112:58732
12:28:25.865 I UDP Client from 71.207.194.112:58732 set to disconnect : Application
12:28:31.262 I UDP Client from 71.207.194.112:58732 has been removed.
12:28:31.262 D Account Client Destroyed: 3
12:28:31.262 I UDP Client from 71.207.194.112:58732 has been removed.
12:28:31.262 D Account Client Destroyed: 2
12:28:31.262 I UDP Client from 71.207.194.112:58732 has been removed.
12:28:31.262 D Account Client Destroyed: 1
12:28:31.340 I Chunk Starting chunk shutdown timer for Three Rivers Village.[/quote]

So, this just happened to me for the first time... standing next to a broker with Cyrcle and in the middle of typing in chat, I was forced out of the game.

[quote]10:03:17.550 D Command Player 'Cyrcle' used command '.summon' (17)
10:04:36.986 E Packet Server packet struct (type=2) (client) with opcode 0x0000052C (1324) not found
0000: 00 09 0A 11 02 00 2C 05 - 00 00 00 00 00 00 9B DB ......,.........
10:04:36.986 E Chunk Unhandled opcode 0x0000052C (1324) from 68.98.218.5
10:05:06.095 D Command Player 'John Adams' used command '.spawn' (14)
10:05:29.230 E UDP Received packet with unknown protocol opcode 0xFE00 (65024) from 68.98.218.5:29273
0000: FE 00 09 0B 13 .....
10:05:29.230 D Char Character John Set to Offline
10:05:29.230 I UDP Client from 68.98.218.5:29273 set to disconnect : Application
10:05:30.977 D Account Character Created: 3[/quote]
Naturally, when it happens to me, now it's a major concern j/k ...


I know we have lots of irons in the fire, but (devs) I have listed some Defects that really should take precidence over other features because they effect the player base -- our Testers. If we keep inconveniencing them with CTDs and random functionality failing, they will stop helping. Let's get these items nailed down, either with workarounds or real solutions.

Thinking about this very consistent unknown opcode issue; Can anyone tell me why encountering this specific (and seemingly random) opcode causes the world to boot a client? This could be the root of the issue entirely; if we trap the "unknown protocol opcode" better, and stop booting connections (partially) we could at least work around this issue for now.

Secondly, when I came back in -- even with Lokked's remedy -- I had no MOTD, no chat, no commands, etc. I was only out of the world maybe 10s though. So ONCE AGAIN, I am going to insist we kill all World connections when Login requests a list of an accounts characters. This needs to be done. I don't much care for caveats at this point because this is an annoyance and we can solve it. Agreed?

1324 is the opcode sent back saying the player exited the broker window (I think by ending the dialog with the broker, rather than using the window exit itself). I have not yet put a handler in for it, because I'm not sure what to do with it, and putting a blank handler code in might make it easy to forget that it is being sent and needs to be handled. I've seen it quite a few times in my testing but it certainly doesn't break the client or the server. I can certainly add something in to grab it and ignore it, but something more must be going on for that to cause a crash. If it is just an ignored opcode at this point (and kicks up an error message in the server log) is there really any difference in handling it by accepting it and doing nothing?

EDIT: I just looked in VisualParser at the log with all the broker action and it was only sent twice. It is named OP_ClientMarketDone. In both cases it looks like it only sent the opcode with no other useful data. It's probably just there for the server to send a code back to close the broker window? No similar codes are sent if you close the broker window yourself rather than ending the dialog.

EDIT2: I see code 1325 is OP_ServerExchangeStartEnd. So we just need to send it back whenever we get code 1324 to tidy things up.