|
Chris Wilde
Custom User Title
Join date: 21 Jul 2004
Posts: 768
|
01-10-2006 11:49
I will explain the tool/feature first because its use should be appearent after reading my idea. (Not sure if anyone else has proposed this before) Concept of how it works: The user brings up the Land Tool. Selects an area of land in a sim. Clicks the new Filter Area button. This tells the client which area in that sim to not render. Any objects/sounds/particles/etc. contained within that area are filtered out by the SL client and not rendered. The area(s) filtered are stored locally on the clients machine. Benefits: - Requires no server side changes - No changes at all in the data LL sends the client; no owner ID, object ID, etc. needed. - Flexibility to filter what you want (ie filter a builders sandbox but not his lovely estate) - Non-land owners can use this as well - Eliminates alot of LL policing or judgement calls on intent or validity of user content - Does not trample on anyones freedom - Simple concept using some of the tools we already have Support Prop 905! ***FILTER AREA***No loss of freedom! No server/data side changes! No policing!
|
|
Justin Cline
yes I do feel lucky
Join date: 1 Jun 2005
Posts: 44
|
01-15-2006 01:51
Very good idea Chris, your purposal would take care of alot of issues that have been a pain in alot of peoples sides and help free LL up from all the AR they get from people complainig about what some one has on their land, very simple if you dont like it fitler it out!!!  great purposal I sure hope it will be implemented ASAP!!! BTW I pulled all my votes from other purposals and put them in this one
|
|
Duke Scarborough
Degenerate Gambler
Join date: 30 Apr 2006
Posts: 158
|
Potential Issues
05-12-2006 10:59
I. If you filter out someone's land and do not render it, you may end up flying through their structures, and interfering with them without realizing it.
II. You could forget that you're ignoring land and nice people could move in later on...
I would suggest that this can be corrected in your proposal as such:
1. Users may select plots of land to NOT be rendered within their client software. 2. Such land will become NO-ENTRY to that user, constrained by the client software. 3. Such ignore settings will be reviewed by the client software every 30 days by asking the user to review their ignored plots of land, just to remind them.
Otherwise, a very interesting proposal. It would allow a user to completely IGNORE the idiots that have surrounded their land in an effort to force them to sell out. Of course, it would also allow you to completely ignore the Klingon Death Cruiser sitting just outside your doorstep.
|
|
Haravikk Mistral
Registered User
Join date: 8 Oct 2005
Posts: 2,482
|
05-13-2006 16:34
What if the filtered areas were tied to the owner? So if the owner of a plot of land changes then your filter no longer applies, so new people moving in isn't affected? I guess you could argue that someone constantly switching land ownership could grief you, but I think then you'd definitely have a case.
The filter could be more like "Ignore area", the client displays you as flying through that plot of land, while the server treats you as having stopped at the edge (basically the client stops sending your position info to the server when you hit the edge of an ignored area), when you reach the other side you update again server-side. So you have a seamless client-side experience, but the server treats you as having stopped then TPed to the other side of the ignored area. Things like chat from the area would also be ignored. The idea is to allow you to explore the area as though it had been made phantom, without actually letting you into the area at all. The client should have enough info to let you walk on the ground or such.
A hot-key to toggle ignored areas on/off would be neat, or even a secondary tool which shows the ignored areas and allows you to click to toggle them on/off (perhaps to see if it's changed).
_____________________
Computer (Mac Pro): 2 x Quad Core 3.2ghz Xeon 10gb DDR2 800mhz FB-DIMMS 4 x 750gb, 32mb cache hard-drives (RAID-0/striped) NVidia GeForce 8800GT (512mb)
|