i was destroying atremis collectors for a good 2 hours getting up heavy weapons xp.

at one point i ran into 4 collectors that refused to take damage. this isn't lag as they were firing, dodging fire and so was i. i heard that little ''beep'' that tells if you, if you've hit them however they took no damage.

i was firing at them for a good 7 minutes before my hull was too low and i had to ''jet'' away =P the loadout i was using: dual advanced gatling turrets, and 3 tachyon mk2s. overall this happend about 5 times. i can assure you there was no lag.. the movements and everything were normal, just me taking damage and not them.

as for the spelling error, the mission line reads "Great job! You were able to disable the ship. The ""hostange"" was jettisoned in a stasis pod and the pirate is running away.''

note "Hostange".

here's some screens. sometimes they give off that hit noise, on some others you only see your guns hit them, but no noise (again, they're moving fine, and shooting at you.. not lag)

http://www.elite-knights.com/vendetta/1.jpg < - 5 minutes shooting.

http://www.elite-knights.com/vendetta/2.jpg < - different bot, firing at it for 20 minutes.i actaully managed to damage this one a little, but it returned to invincibility.

I had this happen yesterday as well. It wasn't laggy, and the bots could hit me just fine. But my shots did no damage to them. After a few minutes, it went back to normal. Maybe Metana was having a hiccup.

wow guys this sucked. I was making a trade run that had taken me 30 min. b/c i was going cross universe. I came across this "invincible bots" and well yeah they dont take damage. dual adv. gattling turrets didnt even take a sliver off of em. it sucked b/c i the died trying to run away and i lost my cargo which,by the time i got back to where i was, had already disappered.

Hmm, that's very interesting. It's a clock sync issue and I need to look more closely at the synchronization code. The bot wasn't invincible, the server just didn't believe that you hit him because your timing was off (from its point of view, which itself may have been out of sync).

According to the logs, you entered Azek N2 at 18:42:51, started plugging away at one of the bots 18:43:11, was not able to register a hit for the next ten seconds, and then 11 seconds later, at 18:43:32, KJ-6945s (the bot targeted in your first screenshot) died. CZ-7579w died 5 seconds later. You had similar trouble shooting several bots in succession until you died five minutes later.

I intend to correct this. The clock sync code isn't very smart and can go out of whack if there's too much "jitter" as it measures round-trip-time of packets. There's also a Linux socket option extension for making accurate timestamps of packets that I'm not taking advantage of. I will also make /ping more informative (with jitter measurements) and have the sector raise hell if thinks its own clock is out of sync.

5 minutes? =O that's the last time i'm reporting a bug when i'm half asleep =P

yes, this is one of the times i decided to take screens and report it as the problem was becoming more rampent.

i have found a temporary work around, however this is for dual monitor users. if you press the printscreen key the game freezes for a second (pretty normal on dual monitor systems) and once the screenshot is done the bot is killable again.

this works on both windows, and linux systems. as long as the game freezes for a second, or half second things will return to normal.

Yep, a delay longer than a half second or so forces a clock resync.

Does a resync get forced every time you enter a sector or dock?