Server Status (outdated)

[seekeronos]

Next month we'll probably switch the play server over to a standalone optimised build and you'll really see some improvement then, but for now the improvements I talked about should be noticable.

Slightly off topic... but would this move to an optimised build coincide with the official move of the emulator to "alpha" status, i.e the end of ST4 with anticipated player wipe?

[Reon]

Supposedly Player Database is completely separate from game. A rollback should only affect the game.

boy, I hope so.. me and elurai just got our hull upgrades yesterday...the server was working fine till it dropped. When it came back up and we logged in, El was having all kinds of issues with lag, invisible mobs, targeting issues, and skills not going through. We just decided to sit it out until server was fixed.

Edited November 1, 2010 by Reon

[Tienbau]

Slightly off topic... but would this move to an optimised build coincide with the official move of the emulator to "alpha" status, i.e the end of ST4 with anticipated player wipe?

where did you get that info from and what do you mean about moving _to_ alpha status?

From Wikipedia:

Pre-Alpha

Pre-alpha refers to all activities performed during the software project prior to testing. These activities can include requirements analysis, software design, software development and unit testing.

In typical open source development, there are several types of pre-alpha versions. Milestone versions include specific sets of functions and are released as soon as the functionality is complete.

Alpha

The alpha phase of the release life cycle is the first phase to begin Software testing. In this phase, developers generally test the software using white box techniques. Additional validation is then performed using black box or gray box techniques, by another testing team. Moving to black box testing inside the organization is known as alpha release.

Alpha software can be unstable and could cause crashes or data loss.

The alpha phase usually ends with a feature freeze, indicating that no more features will be added to the software. At this time, the software is said to be feature complete.

So, pre-alpha is pre-testing, and would apply to the time before ST1, when the server was running but publicly closed.

There's no player-wipe coming any time soon, we've still got a lot to develop.

Switching to an optimised build just marks a divide from worrying about stability and basic operation and instead focusing more on load-balancing and gameplay issues.

[Phamine]

ok..im at a loss,.i can log onto other server,.i can log onto main server with a guild vault toon,.but not my own.

[seekeronos]

where did you get that info from and what do you mean about moving _to_ alpha status?

I'd chalk that up to a mish-mash of many people - including some current and former devs and forum mods - repeatedly stating this particular idea that the stress tests were a pre-alpha or early alpha stage for the emulator (I've been playing/following the project since mid-ST3).

Although I would have thought public testing such as the ST's would have put the emulator into an early beta-test stage at the very least ... (again, my assumption).

Of course, I'm quite willing to be corrected, as y'all would know best what stage of development y'all are in.

Either way, I'm happy to know that I'll have some time to play with my L150 JE and possibly even get my TT up to snuff as well.

[seekeronos]

Editx2: Looks like that was just a fluke (with N7 launcher).

A system reboot fixed it and the updates seem to be finding the correct folder.

[CheezeBaal]

i'm now having issues docking/undocking causing n7 to crash and lots of null items.

[Tienbau]

yes I have seen the huge number of people who are getting login issues looking at the server status update feed.

I'm taking a snapshot of the database and hopefully I'll be able to reproduce the issue and fix it. I understand a lot of people are getting problems with the manu terminals as well ... I'll will try to clear up the issue at the same time.

I already have a list of players who are failing at login, could I get anyone who has seen the 'bad opcode' error when they click on a manu terminal to post here please - I'm not interested in any other error BTW right now. ONLY MANU TERMINAL CRASHES PLEASE, and just the player name.

[Mimir[IS]]

yes I have seen the huge number of people who are getting login issues looking at the server status update feed.

I'm taking a snapshot of the database and hopefully I'll be able to reproduce the issue and fix it. I understand a lot of people are getting problems with the manu terminals as well ... I'll will try to clear up the issue at the same time.

I already have a list of players who are failing at login, could I get anyone who has seen the 'bad opcode' error when they click on a manu terminal to post here please - I'm not interested in any other error BTW right now. ONLY MANU TERMINAL CRASHES PLEASE, and just the player name.

I have been getting these at Job terminals as well as the manu terminals (sorry I know you said manu only...but same error ).

Edited November 1, 2010 by Mimir

[Tienbau]

I have been getting these at Job terminals as well as the manu terminals (sorry I know you said manu only...but same error ).

great, just what I was after - what's the avatar name? Mimir?

[Mimir[IS]]

great, just what I was after - what's the avatar name? Mimir?

MimirTS

[comsciguy82]

Not a manufacturing terminal issue, but I get bad opcodes, lag, and null items from most vendors, sometimes causing windows to kill the proxy and asking me if I want to debug. It has happened on my TT Rastalin, my TS Illiana, and my baby JD Thorndarien.

Edit: Added SS of proxy crash from weapon vendor on Thorndarien.

Edited November 1, 2010 by Thorndarien

[fuulishone]

Some more opcodes for you Tienbau.

Character login opcodes

01/11/10 09:37:51 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:51 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:51 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:53 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:53 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:53 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:38:42 Bad opcode through to Proxy: 0x6b53 Length: 0x2079

Opcodes by same character, at manu term

01/11/10 09:37:51 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:51 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:51 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:53 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:53 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:53 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:38:42 Bad opcode through to Proxy: 0x6b53 Length: 0x2079

A few seconds later these opcodes show up while manu term interface is open, but I've not touched anything on the interface yet, no sub categories, etc.

01/11/10 09:37:51 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:51 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:51 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:53 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:53 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:53 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:38:42 Bad opcode through to Proxy: 0x6b53 Length: 0x2079

These occur once you try to click on a subcategory from the manu interface. (Beams were selected and the display showed no recipes.)

01/11/10 09:37:51 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:51 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:51 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:53 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:53 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:53 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:38:42 Bad opcode through to Proxy: 0x6b53 Length: 0x2079

Choosing projectiles next spewed this bunch of codes and caused the display to refresh, but showed the beams from the previous click.

01/11/10 09:37:51 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:51 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:51 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:52 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:53 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:53 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:37:53 Bad opcode through to Proxy: 0x6966 Length: 0x6e49
01/11/10 09:38:42 Bad opcode through to Proxy: 0x6b53 Length: 0x2079

Any further clicks didn't seem to work. Choosing yet another new category eventually caused the net7proxy to crash with 3 final opcodes that I didn't catch before it crashed.

[Noxmire]

ONLY MANU TERMINAL CRASHES PLEASE, and just the player name.

Might want to edit this info into your post there, Fuulish. It doesn't mention which character you got those opcodes on.

[fuulishone]

Might want to edit this info into your post there, Fuulish. It doesn't mention which character you got those opcodes on.

The avatar id is in the first code block. These were the codes that led up to the final manu term crash. As it wasn't an insta-crash like some folks, I posted the various codes to make it more clear and perhaps easier to identify what is exactly going on.

[ryprx]

Here are the manu term opcodes leading to crash of net7proxy for avatar Wormholio:

Net7Proxy version 1.97

Using IP: 127.0.0.1 (127.0.0.1)

01/11/10 12:40:45 Attempting to connect to IP address: 87.106.15.67

01/11/10 12:40:45 Sending login.

01/11/10 12:40:46 login OK

01/11/10 12:40:46 UDP packet optimisation selected (reduces server load).

01/11/10 12:41:26 MVAS thread running

01/11/10 12:41:26 Received Master login confirm, new UDP port is 3642 Avatar_id

= 1073758697

01/11/10 12:41:26 <server> Master Login received - UDP sector port: 3642

01/11/10 12:41:26 >> Commence Login check.

01/11/10 12:41:26 Sending Login packet - connection active

01/11/10 12:41:29 Sending data file 'GalaxyMap.dat'

01/11/10 12:41:30 Sending StartAck to Server 16873

01/11/10 12:41:31 >> Login check: Login OK

01/11/10 12:41:32 Bad opcode through to Proxy: 0x0000 Length: 0x0

01/11/10 12:41:55 Bad opcode through to Proxy: 0x6d70 Length: 0x6975

01/11/10 12:42:10 Bad opcode through to Proxy: 0x0000 Length: 0x0

01/11/10 12:42:29 Bad opcode through to Proxy: 0xffffbc00 Length: 0x0

01/11/10 12:42:32 Bad opcode through to Proxy: 0x6568 Length: 0x7720

01/11/10 12:42:35 Bad opcode through to Proxy: 0x0000 Length: 0x0

[Lot]

Server down.

Dunno if crashed or brought down either way hope server stays down until issues with proxy packet sequences get a chance to become fixed. However long it takes ... good luck.

[CptGemini]

Server down.

Dunno if crashed or brought down either way hope server stays down until issues with proxy packet sequences get a chance to become fixed. However long it takes ... good luck.

yea its down, the enb notifier is displaying a red mark, and says its last seen about 8 minutes ago.

Edited November 1, 2010 by CptGemini

[Bolt]

Server down.

Dunno if crashed or brought down either way hope server stays down until issues with proxy packet sequences get a chance to become fixed. However long it takes ... good luck.

personaly id rather play with it bugged than not play at all. with my TE stuck in earth station at least it forces me to lvl up my alts that have been neglected sence they have droped behind in lvling. but hey thats just me.

[Nexeo]

One day, soon we will laugh at all this.

[Bolt]

yes but not soon™ enough for m;)

[VonBon]

i knew it was a matter of time before it would go bo0m...

basicly theres not much you can do in game now... cant hunt , depending on the toon you cant see mobs or they appear right on top of you while your looking around then go away as fast as they appeared..

you cant buy anything at a Vendor or crash to desktop, you cant build anything, lists are gone... most of my toons have NULL itmes, either equipment loaded or in hold or vault.

gating or docking crashes.

if you do crash it takes 3 , 4 , 5 relogs to get back in..

other then that the game is running fine lol

[Toreava]

I actually think this is the fun part of beta testing. Yea - I know, I've heard it before. Not supposed to be fun. Although I do not have autism, I do have pattern/jigsaw puzzle thinking. It's great until you take English classes, although it works well with those, too, for termpapers. I tend to "see" things others miss, but would give it all up for a verbal thought process. That's why I fish around looking for input about patterns. I'm sure Tien will find the path and set us all straight.

And when I went back to college, I became (go figure) an English Major. Nice way to trail away from microtechnology. Beat myself over the head, but I learned much.

[wogboard3]

servers down hopefully it will be up and fixed soon1!! thank ya devs

[alurra [Fmr. ADV]]

I didn't receive any 'bad op' codes, at least none that I got the chance to look at. My builder toon is Aspasia, and she was completely unable to get into her 'devices' recipe list. All other items were available for builds, but within 5 seconds of clicking on devices I would get the "lost connection to server" message and before I could get back to the desktop to look for any relevant information, the N7 screen was already closed and gone.

On a another note, which this has nothing to do with manufacturing terminals. I made the mistake of docking one of my characters, Lachesis, at N7 last night which seemed to just 'blackhole' the entire account. I could not get her off that station, speak with any of the NPC nor could I get any of the other characters on that account logged in from different stations. The game client just hung and generated the bad switching message thing. Sorry, can't be more specific, I didn't write it down and I am at work right now and unable to try to get it again.