|
Garth FairChang
~ Mr FairChang ~
Join date: 24 Jun 2003
Posts: 275
|
06-21-2004 22:35
As of now we have to relog to get rid of ghosts. They are often a big problem at events and when building. This has yet to be addressed.
How about a menu item that refreshes the client from the server. Like clears current client and updates it totally from the server to clear ghosts?
Is this possible?
_____________________
Garth FairChang ~Cheeky Brit~ ' Have a nice day  ' http://www.fairchang.com
|
|
Oz Spade
ReadsNoPostLongerThanHand
Join date: 23 Sep 2003
Posts: 2,708
|
06-22-2004 02:27
I've heard this idea tossed around before, but not sure if anyone has suggested it on here yet. From my knowledge it would be possible.
And I agree, it would be nice to have something ANYTHING to clear ghosting other than reloging.
_____________________
"Don't anticipate outcome," the man said. "Await the unfolding of events. Remain in the moment." - Konrad
|
|
Hawk Statosky
Camouflage tourist
Join date: 11 Nov 2003
Posts: 175
|
06-22-2004 03:42
I third this one - be very useful to have, even only on the debug menu as suggested.
Should be able to tie into the startup sequence or something - I imagine most of the codework's already there.
_____________________
This .sig has been cancelled due to lack of interest.
|
|
Tiger Crossing
The Prim Maker
Join date: 18 Aug 2003
Posts: 1,560
|
06-22-2004 08:17
Though to prevent griefers from killing a server by repeatedly calling this over and over, you'd have to give it a time delay like once every 15 minutes max.
I'd prefer some sort of detection in the client for ghosted objects. When I try to edit a ghost, the edit window attempts to fetch information about it. At THAT moment, the server should be telling the client "What you talkin' 'bout, Willis?" and the client should go "Oopsie!" and POOF, the ghost is gone.
_____________________
~ Tiger Crossing
~ (Nonsanity)
|
|
Hawk Statosky
Camouflage tourist
Join date: 11 Nov 2003
Posts: 175
|
06-22-2004 08:51
Hrm. Okay, how about a modification?
Resync with 15 minute delay, and resync selected object (not prim) only, with a 10 second delay.
Given that it's either something random we just deleted, or the whole [non-pg] world that appears to ghost I reckon that could cover the eventualities...
Thoughts?
_____________________
This .sig has been cancelled due to lack of interest.
|
|
Garth FairChang
~ Mr FairChang ~
Join date: 24 Jun 2003
Posts: 275
|
06-22-2004 09:45
Anything would be nice, just as ghosting in 1.3 was getting better, along comes 1.4 and makes it much worst. For me at any rate.
Ghosting needs to be addressed, even if only in a method to manually clear it is possible
_____________________
Garth FairChang ~Cheeky Brit~ ' Have a nice day ' http://www.fairchang.com
|
|
Jon Morgan
Senior Member
Join date: 28 May 2004
Posts: 174
|
06-22-2004 19:41
IMO manual refreshing is almost as bad as relogging. Instead, I think, the bandwidth meter should be monitored internally so that whenever traffic dies down pretty low, and at least 120 seconds have passed, whichever happens LAST, then an auto-refresh occurs to verify the existence of each object. This can be relatively low-bandwidth, as all you would need per object is: 1) the object key, and 2) the coordinates. The query should consist of a single response of a full list, and anything not listed should be purged by the client.
|