Notes |
|
(0000021)
|
Coruja
|
21-07-08 15:27
|
|
Maybe OSI changed walk packets on these new clients? :( |
|
|
|
have you tested with EF_networkmulti ON and OFF? |
|
|
|
I always had that flag OFF.
So far the "lag" is gone with it turned ON but I would like to test this more before saying for sure. Sometimes it stopped randomly but so far so good. |
|
|
|
I also have this issue, but I found out that if I play with radar map and status closed I can run much more smoothly. Still, I don't think it's totally a client issue, since with other emus the client doesn't behave like that. |
|
|
|
I know it is not a client issue. Simply going back a couple builds to June 6 will remove this issue.
It only happens on the February build and I believe the EF_networkmulti was added at that time so its a logical cause. It seems to be connected in some way at least. |
|
|
|
Okay its been over a week. With EF_networkmulti ON this problem goes away.
I dont know if it will be integrated into sphere permanently but if there are no plans to do that, this should be fixed or sphere should come with it enabled by default :). Thanks for the feedback, else I would be stuck in lagville and recommending 2.0.3 again :S |
|
|
(0000054)
|
Coruja
|
10-08-08 00:48
|
|
But we have problems...
With NetworktMulti ON:
-Server crash (fixed on next release, as it tracker shows)
-Lag on old clients (< 4.0.0)
With NetworkMulti OFF:
-Lag on newest clients (> 5.0.0, or > 6.0.0 I think) |
|
|
(0001884)
|
Ben
|
05-01-14 23:38
|
|
Closing due to old settings that affected this are no longer in use... |
|