I just got the hyperspace bug today in sector 12, whereby my out of control ship was sent thousands of kilometers away from the center of the sector, yet I'd still receive damage from bots at my initial location as if I'm standing completely still. This bug has been around since the 3.0.x days of Vendetta. And because it appears so randomly it would be nearly impossible to get a verbose log of it to find out wtf is going on.

The good news is that it rarely happens. The bad news is that when it happens... you're almost always dead from a dumb bot killing your ship. This would no doubt be extremely annoying if it were to make it into the final version of Vendetta, where money and death actually means something. When you log off it tosses you back to where you were last time, but by the time it lets you log off chances are you would've been killed by a bot. Will this ever be fixed? Or have the devs already fixed this but haven't released the fix in the test version?

The elusive hyerspace bug lives on...

You are a bug magnet :P

The solution to this is obvious. We must all fly with all sorts of verbosity turned on.

I wouldn't mind verbose logging being on all the time, except it tends to spam your chat area with weird messages. Maybe if those messages were only viewable under the console it would be bearable. But even if it was left on all the time, do you think all those lines of text in your errors.log would start to take up lots of hard drive space etc. (esp. with 3+ hrs gameplay). That might be preventable if the errors.log file would overwrite really really old messages and have a specific length.

Verbose probably wouldn't help here anyway. What ship and what engine were you using? What were you doing?

I wouldn't be surprised if this was Mac-specific.. has anyone ever had this happen on a PC? Sounds like a numerical precision problem going horribly awry.

It happens on pretty much every ship configuration. I was in a Warthog this time with a medium/fast charge combo. But it has also happened back in 3.0.x and 3.1.x with the Hornet and Ragnarok, in a heavy/heavy combo. It doesn't happen at any specific time. In this case I was botting in sector 12. But in the previous versions I was simply cruising around in a sector when all of a sudden BAM I get tossed hundreds and thousands of meters away from the nearest wormhole with absolutely no control over my ship. Yet the bots and players in my initial location could damage me.

I can tell you this though. Back in 3.1.x when it happened, I asked players whether they could see my ship or not. It turns out they could... but only as a ghost thing. They could shoot it but not receive any damage confirmation, yet I would take delayed damage from my hyperspace location. And my ghost ship would appear to be drifting infinitely without being able to be disturbed by outside forces. In other words it appears like the ship has timed out, when in reality I wasn't.

To put it simply, the sector splits up a player's locations into two areas. It doesn't know which ship model to allow the player to control, so both of them drift off endlessly at two completely different locations. One continues to travel away from the center of the sector at a phenomenal rate, while the other is slowly drifting at the initial location which the anamoly occured. It's obviously some type of synchonization problem. I don't know if PC users have experienced it to, but if they have I highly recommend that they report it.

If there's anymore more I can do to help, let me know. AFAIK this bug occurs randomly and to my knowledge has no way of being duplicated. Arrgh!!

I had it also, a1. It was also in 12 and it was also yesterday. I was in a Valk Med/FC. We had just expelled an Itani pilot from 12. There were still gems and other ordinance in the air after the Itani pilot's ship exploded. I started an uncontrolled nose-up loop. I only let it go for a few seconds and then escape/quit. There was no countdown. I logged back on and was not very far from where I was when I quit. I use a 1Ghz iMac.

<a1k0n> "Sounds like a numerical precision problem going horribly awry."

Isn't that a windows/intel problem? I've never heard of any numerical anomolies on the Mac or it's processors.

It wouldn't be a processor bug. It'd be a library bug. And there's been no problems like that since F00F anyhow.