Originally by: Waagaa Ktlehr

---

Supercaps are desync'd 95% of the time because smaller ships are allowed to bump into them.

I think it's due to a rounding error somewhere. Either that or information latency, but the latter I could only know for sure if I knew how the client and server handle warping.

There's an easy fix to this:
1) Fire whoever wrote the current code that does "bumping"
2) Add this to the bumping code:
A,B = two objects
IF A.Mass < B.Mass / 100 THEN NoBump();

2) will solve a lot of the problems and issues with supercap balance as well. :)

---

Originally by: Dianabolic

---

Originally by: Waagaa Ktlehr

---

Supercaps are desync'd 95% of the time because smaller ships are allowed to bump into them.

I think it's due to a rounding error somewhere. Either that or information latency, but the latter I could only know for sure if I knew how the client and server handle warping.

There's an easy fix to this:
1) Fire whoever wrote the current code that does "bumping"
2) Add this to the bumping code:
A,B = two objects
IF A.Mass < B.Mass / 100 THEN NoBump();

2) will solve a lot of the problems and issues with supercap balance as well. :)

---

Smartbombs actually destroying corpses' would be nice, too.

---

Originally by: Alex Under

---

This is just theory of mine, but has anyone looked at "HEAT" being a culprit? After all, this whole desync stuff only started happening after it was introduced. From my understanding, EVE send information back and forth between all the ships in system, so now with "HEAT", it now also has to relay that information to all the other ships/pilots in system. Similar to how everyone's bookmarks and other information is shared to all other pilots in system, I am guessing so is HEAT.

---

Quote:

---

I find that desync has no bearing on how many people you have in system but may have something to do with information not being relayed properly between the ships/pilots in the same system. Because relogging ususally fixes the desync problem so perhaps on relogging the information is then properly passed along to everyone? Who knows... it's just a theory of mine. But perhaps can be looked at?

---

Originally by: Dianabolic

---

Originally by: Waagaa Ktlehr

---

Supercaps are desync'd 95% of the time because smaller ships are allowed to bump into them.

I think it's due to a rounding error somewhere. Either that or information latency, but the latter I could only know for sure if I knew how the client and server handle warping.

There's an easy fix to this:
1) Fire whoever wrote the current code that does "bumping"
2) Add this to the bumping code:
A,B = two objects
IF A.Mass < B.Mass / 100 THEN NoBump();

2) will solve a lot of the problems and issues with supercap balance as well. :)

---

Smartbombs actually destroying corpses' would be nice, too.

---

Originally by: Drykor

---

Edited by: Drykor on 07/08/2007 17:03:09
I'd like to come and help, but I just duplicated my original Eve folder (the old test server installation wouldn't work) and it still won't connect, saying I have an incompatible release and must update manually. But when I go to the support page it says: We were unable to locate a patchfile for your build no. (35183).

edit: actually, never mind, I found the patch elsewhere, kinda confusing though.

---

Originally by: hydraSlav

---

Dude, its not about attacking a POS. Get people on test server, split them into equal groups, have one side on gate, another waiting in another system. Then on command, everyone jumps in. Then watch those that jump in battle heavy lag (but still continue to be connected), and watch those already in system desynch and die without knowing it.

---

Originally by: Laendra

---

Why don't you come over to the US to do your testing from there, since you'll be a lot further away from the servers, you're likely to get desynched a lot more. Just a theory. :)

---

Originally by: Barthezz

---

So without flying there, how does one get to the test system?

---

Originally by: midge Mo'yb

---

Originally by: Barthezz

---

So without flying there, how does one get to the test system?

---

im sure theres a channel to request transport

---

Originally by: Barthezz

---

Originally by: midge Mo'yb

---

Originally by: Barthezz

---

So without flying there, how does one get to the test system?

---

im sure theres a channel to request transport

---

Well in an indirect way, that was what I was asking The news post doesnt mention anything, neither does this post.

---

Originally by: Dark Shikari

---

Desync is caused in certain cases when a huge amount of bumping goes on; if a mothership gets bumeped by a ton of ships trying to warp the client will often think it got away when it didn't... or vice versa.

---

Originally by: SexxxSlave

---

Edited by: SexxxSlave on 07/08/2007 17:38:25

Originally by: Dark Shikari

---

Desync is caused in certain cases when a huge amount of bumping goes on; if a mothership gets bumeped by a ton of ships trying to warp the client will often think it got away when it didn't... or vice versa.

---

once again, DS becomes the self-proclaimed expert on all of these in game issues. FFS, CCP make this douche a dev already because he KNOWS EVERYTHING!!!!!

---

Originally by: David Hackworth

---

ò If you find yourself in a fair fight, you didn't plan your mission properly.

---

Originally by: TerrorWOLF

---

Anyone thought that it might be cache related?? It started after the cache and log files where moved. And people started using or not using /end /LUA:OFF

---

Originally by: Dark Shikari

---

Desync is caused in certain cases when a huge amount of bumping goes on; if a mothership gets bumeped by a ton of ships trying to warp the client will often think it got away when it didn't... or vice versa.

---

Originally by: CCP Oveur

---

I'm very sorry w0rmy, I beg your forgiveness.

---

Originally by: Dianabolic

---

I was never sworn to secrecy, w0rmy, sorry to dissappoint you.

---

Originally by: TerrorWOLF

---

Anyone thought that it might be cache related?? It started after the cache and log files where moved. And people started using or not using /end /LUA:OFF

---

Originally by: Aragorn Angelus

---

I Relaoded the client etc etc etc nothing... 3 hours wasted trying tro log into Sisi....

---

Originally by: w0rmy

---

Originally by: Dark Shikari

---

Desync is caused in certain cases when a huge amount of bumping goes on; if a mothership gets bumeped by a ton of ships trying to warp the client will often think it got away when it didn't... or vice versa.

---

Or if youre in system alone, and warp into an asteroid while ratting

---

Originally by: Waagaa Ktlehr

---

Edited by: Waagaa Ktlehr on 07/08/2007 16:36:46
Supercaps are desync'd 95% of the time because smaller ships are allowed to bump into them.

I think it's due to a rounding error somewhere. Either that or information latency, but the latter I could only know for sure if I knew how the client and server handle warping.

There's an easy fix to this:
1) Fire whoever wrote the current code that does "bumping"
2) Add this to the bumping code:
A,B = two objects
IF A.Mass < B.Mass / 100 THEN NoBump();

-EDIT- Let me clarify this pseudo code.
It boils down to: If A's mass is less than 1% of B's mass, then B will not be allowed to get bumped by A. This holds true for all objects A and B that are bound to interact with eachother.

2) will solve a lot of the problems and issues with supercap balance as well. :)

---

Originally by: SexxxSlave

---

Edited by: SexxxSlave on 07/08/2007 17:38:25

Originally by: Dark Shikari

---

Desync is caused in certain cases when a huge amount of bumping goes on; if a mothership gets bumeped by a ton of ships trying to warp the client will often think it got away when it didn't... or vice versa.

---

once again, DS becomes the self-proclaimed expert on all of these in game issues. FFS, CCP make this douche a dev already because he KNOWS EVERYTHING!!!!!

---