This bug is seriously nasty. What happens is:

After turning too fast, which is very hard to avoid doing with this glitch, the glitch occurs.

It takes wherever you are, and blanks out any roids, or other ships.

It makes it so moving the mouse by one pixel takes your Mouselook's angle and turns it about 50 degrees in the direction of the movement. (Not the ship, it is unmoveable.)

It also makes it so you are unable to control your ship's speed, and can't turn it. Nor can you make a jump.

Wormholes and jump points suddenly jump to somewhere in the billions, and because ship's movement is uncontrollable, you can't get to that faraway point.

Logging off gets screwed up too. It starts out normally, but if any message is typed in VO, it starts jumping, and just keeps jumping. That is, it would basically be:

10, 9, 487, 486, 485, 10983, 10982, 173845,......etc.

Trying to log off again does the exact same thing.

The way I've escaped from VO is by closing my MacBook, coming back in 10 minutes, opening it, and finding myself on the login screen.

I'll post a picture when I can.

Sounds like lag. Did you try pinging the server?

That's some serious lag there.

Dude you're lagging bad.

Hmm, when this happens do you get a series of messages along the lines of

"octree warning point 12345 "

just before it happens?

I too have sen this bug at random intervals , the only cure is to force quit and relog .

First of all: Every time, my ping was at about 30. I doubt it was lag.

Secondly: you say: Force Quit. Do you mean like force quit Vendetta?

I usually play full-screen.

Looks like someone else is having the same bug I started getting when I upgraded to Leopard. Shape also started having it last night as well.

The first few times I had the bug, I got the octree messages, but the last several times I haven't seen them, even in the errors.log file.

I don't think this bug is lag-induced, because I've been perfectly able to chat with people after the bug has occurred... but there's no way to recover from it short of logging off and on or restarting the VO client entirely.

I've seen a few other things the bug causes that Death Jr. didn't list. For example, when the bug occurs, your powercell loses its recharging ability. Also, I don't think your ship actually warps out that far -- the client just thinks it did -- because it once happened to me while I was near other (NPC) ships, and I was able to hear them moving around.

No wonder, I was using leopard last night... ended up losing the damn bp mission because of it.

-Nautargos

Might it have something to do with the difference in math calculations between Leopard and Tiger, or whatever?

Wow, that's interesting.

It looks like the timer starts skewing further and further away from the correct time.

I wonder what Leopard changed that would cause this. Perhaps some kind of thing that throttles the cpu speed to conserve power but the OS's timer doesn't properly handle it.

Anyone having this problem with a desktop mac or do people only use macbooks these days?

I had this happen once in the last week or so.
Happened just before I got to a jump point and was about/may have started to jump. Distance meter started jumping up, battery no longer recharged, turning could cause the background to vanish.

Strangest thing to me about it was the log off counter and distance meter started jumping up no matter what I did, but the /explode counted down just fine.

I'm on OSX 10.4.11 though, g5 imac.

See this thread. (scroll down a bit)

I'd described the issues I was having to someone familiar with the way OSX handles things, and they suggested it might be the x87 vs. SSE floating-point math that could be causing the problem. (Posts #8 and down in the thread slime linked.)

I seem to be seeing the octree warning bug less since upgrading to 10.5 , but still get the occaisional distance going wild and lock up.

New machine 24" 2.8 gig intel 10.5.1

old machine 20" g5 10.4.10

This might be a wild guess. There is some calculation relating to distance that goes wrong , deep down somewhere. Since the graphics must be distance related silly numbers are used in the graphics calculations and the graphics card returns octree warning errors , or just gives up.
Perhaps it isn't a graphics bug , but a maths bug somewhere ?

Just read the link slime 73 provided , after posting the above. Worth digging along those lines methinks.