Soo, a little update.

GP3Ds continue to test, and I have to say that we’re very impressed with the quality of the bug reports we’re getting, and the hours of testing the GP3Ds are putting in. It’s almost like they’re addicted to pain or something…

The good news is that we continue to close in on the bugs, in particular at least one laggy GP3D’s lag problems, which they solved themselves by adjusting a router setting. Yes, their router had a setting which was making There lag out. We kid you not. So far, the evidence has been strong on this, but we’re going to to a leetle more analysis before we charge ahead.

The bad news is that it looks like we’ve got some issues with nametag color restoration we have to resolve, as well as making sure we understand the problems our GP3Ds are having .

We know you all are excited and anxious to get in-world, but we’d much rather fix these problems (especially those involving data, like nametag colors) now, with a few GPs, instead of later, with hundreds or thousands of members.

Finally, we have had one very unfortunate event. A Cloud-Based malfunction in the teleport system caused a teleport to, well, uh, not complete as we expected, and, well, words can’t describe the results (the content below may be shocking):

They, of course, will be like that forever. There’s nothing we can do. Pity they weren’t turned the other way so they could get a nice view of the lake.

*** UPDATE ***

The router setting which needed to be turned off in that particular instance is “IP Flood Detection”. We’ve found it on a “Motorola Surf Board”, which is stock for some Cable Providers (Comcast, etc).

Obviously, you shouldn’t do this unless you know exactly what you’re doing. Adjust at your own risk. Your Mileage May Vary. Not a Toy. Do not use near open fire or flame. Do not Eat.

*** UPDATE ***