Second Life Wiki - User contributions [en]

User:Andy Tir

2012-09-02T09:48:30Z

Andy Tir: rewrite to update for relevant data

I am nomadic resident, extremely rare inworld nowadays. You can still [[mailto:silpol@yahoo.com mail me]] at mailbox I check '''sometimes'''.

[[http://about.me/silpol In meatspace]], my last job had been for Nokia, I had done [[http://en.wikipedia.org/wiki/Maemo Maemo software]] for [[http://en.wikipedia.org/wiki/Nokia_770_Internet_Tablet Nokia 770]], [[http://en.wikipedia.org/wiki/Nokia_N800 N800]], [[http://en.wikipedia.org/wiki/Nokia_N810 N810]], [[http://en.wikipedia.org/wiki/Nokia_N900 N900]], [[http://en.wikipedia.org/wiki/Nokia_N9 N9]] and [[http://en.wikipedia.org/wiki/Nokia_N950 N950]]... The future is open.

{{ISO_639-3/cat-speaking|eng}}
{{ISO_639-3/cat-speaking|rus}}
{{ISO_639-3/cat-speaking|ukr}}
{{ISO_639-3/cat-speaking|fin}}
{{SL-hCard|name=Andy Tir
|uuid=00000000-0000-0000-0000-000000000000
|mode=size
|photo_x=200
|photo_y=200
|image=[[Image:Andy_Tir_with_ChaCha_Martini.jpg|300px]]
|rezday=09/01/2006
|rezdayISO=2006-09-01
|account=Resident
|partner= 
|about= 
|achieve= 
|links= 
}}

User:Andy Tir

2007-12-16T11:29:03Z

Andy Tir:

I am nomadic resident, appear time to time in SL. You can [[mailto:silpol@yahoo.com mail me]].

In RL, I do my job at Nokia, last few years were about [[http://www.nokia.com/770 Nokia 770]] & [[http://www.nokia.com/n800 Nokia 800]] & [[http://www.nokia.com/n810 Nokia 810]]

{{ISO_639-3/cat-speaking|eng}}
{{ISO_639-3/cat-speaking|rus}}
{{ISO_639-3/cat-speaking|ukr}}
{{ISO_639-3/cat-speaking|fin}}
{{SL-hCard|name=Andy Tir
|uuid=00000000-0000-0000-0000-000000000000
|mode=size
|photo_x=200
|photo_y=200
|image=[[Image:Andy_Tir_with_ChaCha_Martini.jpg|300px]]
|rezday=09/01/2006
|rezdayISO=2006-09-01
|account=Resident
|partner= 
|about= 
|achieve= 
|links= 
}}

File:Andy Tir with ChaCha Martini.jpg

2007-12-16T10:52:39Z

Andy Tir: Andy Tir and ChaCha Martini at Pharaoh Tomb

Andy Tir and ChaCha Martini at Pharaoh Tomb

User:Andy Tir

2007-12-16T10:38:58Z

Andy Tir:

I am probably permanent resident . You can [[mailto:silpol@yahoo.com mail me]].

In RL, I do my job at Nokia, last few years were about [[http://www.nokia.com/770 Nokia 770]] & [[http://www.nokia.com/n800 Nokia 800]] & [[http://www.nokia.com/n810 Nokia 810]]

{{ISO_639-3/cat-speaking|eng}}
{{ISO_639-3/cat-speaking|rus}}
{{ISO_639-3/cat-speaking|ukr}}
{{ISO_639-3/cat-speaking|fin}}
{{SL-hCard|name=Andy Tir
|uuid=
|mode=size
|photo_x=200
|photo_y=200
|image=
|rezday=09/01/2006
|rezdayISO=2006-09-01
|account=Resident
|partner=
|about=
|achieve=
|links=
}}

User:Andy Tir

2007-12-16T10:32:31Z

Andy Tir:

User:Sudane Erato

2007-12-16T10:14:48Z

Andy Tir: New page: Dean (owner) of C.D.S.

Dean (owner) of C.D.S.

User talk:SignpostMarv Martin/Archive/Implementing new features

2007-02-12T07:31:05Z

Andy Tir: /* Alternate Rendering Engines */

== Alternate Rendering Engines ==
* Heh, isn't SL already running on an open source 3D engine? :-) [[User:Eddy Stryker|Eddy Stryker]] 19:55, 9 January 2007
** Nope. Just saying we-do-this-and-that does not make things happen :) [[User:Andy Tir|Andy Tir]] 23:31, 11 February 2007 (PST)

== Better Sound Support ==
* '''Seconded'''. [[Community Bounties#VLC instead of QuickTime]] might help. [[User:SignpostMarv Martin|SignpostMarv Martin]] 07:51, 9 January 2007 (PST)

== Removing Texture Loading ==
* '''Comment''' How complete do you want this to be? I made a very quick and easy patch that prevents the client from requesting any image downloads, but in my experience it still rendered a few textures like the grass terrain and avatar hair. It sped up the framerate a lot, but didn't change the GPU requirements to run SL. If the latter is your goal you'd probably have better luck by removing shaders and disabling OpenGL extensions. --[[User:Eddy Stryker|Eddy Stryker]] 12:01, 9 January 2007 (PST)

* '''Seconded''' -- Disabling texture download/display would be a great asset to people interested in communication more than shopping/etc. [[User:Kamilion Schnook|Kamilion Schnook]]
** As long as you like the color grey :-) --[[User:Eddy Stryker|Eddy Stryker]] 12:01, 9 January 2007 (PST)
* '''Comment:''' As far as I was aware, libSL clients don't load textures, due to the lack of JPEG 2000 support :-P [[User:SignpostMarv Martin|SignpostMarv Martin]] 07:51, 9 January 2007 (PST)
** This is somewhat incorrect. libsecondlife has had JPEG2000 support for quite some time through our jasper shim called libjaspernet, and some projects use it. Most don't however, as there are few interactive GUI clients using libsecondlife. --[[User:Eddy Stryker|Eddy Stryker]] 12:01, 9 January 2007 (PST)

== Patching it so that llLoadURL opens the F1 Help Browser ==
* '''Seconded''' [[User:SignpostMarv Martin|SignpostMarv Martin]] 07:51, 9 January 2007 (PST)
* Streaming media urls can be implemented in this manner by making use of string concatenation, e.g. <nowiki>llParcelMediaCommandList([PARCEL_MEDIA_COMMAND_URL,'http://' + (string)llGetOwner() + ':' + stringVar__password + '@icecast.example.com:8000',PARCEL_MEDIA_COMMAND_AGENT,llGetOwner()]);</nowiki> [[User:SignpostMarv Martin|SignpostMarv Martin]] 07:51, 9 January 2007 (PST)
* The problem with this, is that doing this via serverside script is that there's only one media URL, and you'd be connecting to it with the owner's key -- What is wanted is each individual client responds with it's own key. For instance, integrating a "Who is listening in SL" to an icecast server. Each connected client supplies it's own key/name via rewriting, and a name2key/key2name DB displays each individually connected user's SL information. [[User:Kamilion Schnook|Kamilion Schnook]] 20:35 Jan 8, 2007 PST
**Using the PARCEL_MEDIA_COMMAND_AGENT, I'm told you can give each agent their own stream to listen to. So you could do the user method, or more likely, append a query string, e.g:<div style="font-size:140%;"><code class="lsl"><nowiki>llParcelMediaCommandList([PARCEL_MEDIA_COMMAND_URL,'http://' + (string)llGetOwner() + ':' + stringVar__password + '@icecast.example.com:8000',PARCEL_MEDIA_COMMAND_AGENT,llGetOwner()]);</nowiki></code></div>
**[[User:SignpostMarv Martin|SignpostMarv Martin]] 03:31, 10 January 2007 (PST)

== Adding a Avatar Local Stream Channel ==

== Peer to Peer Voice over IP using above idea, improved ==

== More efficient local cache ==
* '''Comment:''' Seronis has some good ideas on how this should be implemented. [[User:SignpostMarv Martin|SignpostMarv Martin]] 07:51, 9 January 2007 (PST)
* '''Comment:''' Definitely. One cache per region, to a configurable cap total, would be an immense load off the asset servers, and off of our poor bandwidth. [[User:Buckaroo Mu|Buckaroo Mu]] 11:30, 9 January 2007 (PST)

== [http://en.wikipedia.org/wiki/Client-To-Client_Protocol CTCP] protocol layered on IM system ==
* Bleh ? [[User:SignpostMarv Martin|SignpostMarv Martin]] 07:51, 9 January 2007 (PST)

== Command Line Interface Improvements ==

== More sophisticated IM features ==
* '''Seconded''' with a big hell yes. In a large group, it's difficult to keep track of a conversation when there is a mass exodus from the session. It's annoying having the system spam the window. [[User:SignpostMarv Martin|SignpostMarv Martin]] 07:51, 9 January 2007 (PST)

== Shortcut/Link/Alias function in Inventory ==
A pure viewer based solution can "only" be a hack at best. A possible implementation could be:

#) Change the viewer, so that when a drag and drop operation is performed on a 'no-copy' item, the error is trapped
#) for each error, register the UUID of the object in a special notecard
#) When presenting the contents of a folder in the viewer, preset a mixture of the real contents and the contents of the note card
#) Hide the special notecard
#) Handle folder drops onto the avatar
#) Handle moving of the special links
#) Handle deletion of the special links
#) Handle deletion of the original 'no-copy' item

This will only a partial solution, as an scrips running on the servers will still see the real contents of the folder.

:Yea, I realized that this would really have to include a new Inventory Type ID - but do the servers do checking for type IDs? This may be something that can be done client-side with either no server-side change or only one very minor one - the assignment of a Type ID. For instance: Assume the new Inventory Type of Link, which simply stores the UUID of the original object. The simplest thing to do with them regarding copying would be to make them either no-transfer, or "delete on transfer" - they simply go away if you try to transfer them. In every other way, it behaves as a normal inventory item. [[User:Buckaroo Mu|Buckaroo Mu]] 09:15, 11 January 2007 (PST)

::This definitely could be fudged by using a series of specially named notecards (for configuration data), allowing the feature to be implemented without requiring modifications to the server
::[[User:SignpostMarv Martin|SignpostMarv Martin]] 10:03, 11 January 2007 (PST)

:::It ''could be'' fudged with notecards - but how many hacks do you want in SL? The assignment of an additional inventory type at the server end, as far I as can tell from the viewer source, would require probably two lines of code. We need to work with LL to see if they would support this inclusion, rather than make kludges that work but are far less elegant, and may break scripts. [[User:Buckaroo Mu|Buckaroo Mu]] 16:16, 12 January 2007 (PST)

::::You're forgetting something: the servers aren't built for dynamic assets. 'Fudging' it would allow the community to decide on features and interfaces while Linden Lab make the significant changes to the server required for this to work.
::::[[User:SignpostMarv Martin|SignpostMarv Martin]] 21:12, 12 January 2007 (PST)

:::::If you ''fudge'' this via notecards, serverside scrips working on inventories will see the inventory as it really is. In effect making life complicated for LSL scripts, because now they have to parse a notecard as well.
:::::[[User:Duffy Langdon|Duffy Langdon]]

== DirectX3D Hardware Acceleration ==

The OpenGL code is scattered all over the entire codebase. You'd have to abstract out all the 3D code first, it wouldn't be an improvement it would be a complete rewrite.

== GPGPU Support ==

== Multiple Monitor Support ==
* '''Seconded''' I've been wanting this since I only had one monitor :-D [[User:SignpostMarv Martin|SignpostMarv Martin]] 11:13, 10 January 2007 (PST)

== Embedded scripting language for client-side plugins ==
One way of doing this would be to exploit the xpcom architecture of Mozilla. Exposing the viewer core as xpcom interfaces. That way the flexibility and extensibility of the Mozilla engine could be used.

The viewer already includes the mozilla engine, using xpcom it will be possible to use Javascript, Java, C++ (Mono/.Net is under way).

This would require that a definition of an interface layer between the core viewer and the xpcom system inside Mozilla, once that was defined and implemented, the viewer functionality could be extened using almost any language.

[[User:Duffy Langdon|Duffy Langdon]] 12:34, 10 January 2007

== Nude patch ==
It's inevitable. Any bets on how long it will be?
# Ages ago. Around about the time alpha textures for clothes were allowed. [[User:SignpostMarv Martin|SignpostMarv Martin]] 00:53, 11 January 2007 (PST)
# Do bear in mind that my mention of a possible implementation for the 'nude patch' would be akin to hallucinating, due to the also mentioned ability to run extra-stringent checks on the server side for submitted content in PG regions. [[User:SignpostMarv Martin|SignpostMarv Martin]] 01:08, 11 January 2007 (PST)

I don't think a nude patch could work anyway - the skin and clothing textures are combined on the wearer's client, then the combined texture is uploaded to the server as the single texture that appears on the avatar. That's why "rebaking" your textures on your client affects how other people see you. You could possibly just apply the same skin to everyone but you might just as well leave everyone unrezzed then ;) - Yumi Murakami

: and chase all your payig customers away ? In order for us to build our business out in SL and represent our RL business inside SL such things should never be possible therefor as this is a technical wiki and forum how to further create a better client i suggest to build as much security in the client as possible ro prevent such 'attacks' on our avatars. [[User:River Senyurt|River Senyurt]] 11:34, 12 January 2007

:: As I described in the Barriers to implementation section for this "feature", security such as this would have to be built into the server. Since the Viewer is now GPL, all it would take is for someone to remove this 'security' layer, and you're right back where you started, thus Linden Lab are highly unlikely to spend time implementing such a mechanism in the client. The method I described has benefits for both the main and teen grids anyway.

:: Aside from the odd oversight over the years (e.g. texture uploads, megaprims), all security and validation operations are executed on the server side. It fits into LL's behaviour to implement such checks on the server, and while they could, and most likely will do something alone these lines, there is unfortunately nothing you can do to stop somebody else making their client get nervous imagine you in your underwear. Or less.
:: [[User:SignpostMarv Martin|SignpostMarv Martin]] 04:18, 12 January 2007 (PST)

== Out of sight., out of mind ==

# The client has an option to prevent certain types of objects from being rendered
# Objects are addressed server-side by UUID

The client would have be made aware of the UUID of an object, categorising it as a new type of object, and a hotkey could be used to toggle the visibility.

Similarly, if a photographer or machinimaker is working in-world, the following options would be useful:

* Do not render anything other than the land owner's objects
* Do not render objects not owned by people on your friends list
* Do not render avatars on your friends list

This would enable people to deal with certain types of griefer attacks more easily, much in the same way that toggling particles on and off can be useful when particle poofers have been dropped.

[[User:SignpostMarv Martin|SignpostMarv Martin]] 15:32, 12 January 2007 (PST)

=== Visual mute ===
Maybe add Visual Mute, that makes agent's avatar and objects not rendered?
[[User:Tharkang Varayez|Tharkang Varayez]] 04:59, 13 January 2007 (PST)

== Night skies ==

I'm working on customizing the night sky. Since the sky, and especially the starfield, are strictly client-side effects, this would involve storing the data in a local file. Where would be the best place to store this, and what would be the best way to access it?

Are there any plans for things like sim-wide data storage? Such a thing would make it possible to assign per-sim or per-area skies. I figure a decent starfield would require between 8k and 16k of storage; objects like comets, planets, and the like would be much smaller. --[[User:Carnildo Greenacre|Carnildo Greenacre]] 00:48, 13 January 2007 (PST)

=== Marv's crazy thoughts ===
Rename feature to "Celestial Effects"
:''Since the effects you refer to- comets, planets, starfiled, and one assumes Aurora Borealis, as well as celestial bodies such as nebulae, pulsars, supernovas, asteroid fields etc etc, are '''effects seen in the sky''' or space''' (which is the basic definition of 'celestial'), it would make sense to make allowance for the code to be extended to provide this wider scope.''

I would suggest implementing bitTorrent (or other P2P protocol) client, putting an option in the Network tab, and adding the necessary UI elements that say "Customised Celestial Effects Server XYZ has '''n''' celestial packs available for this parcel/simulator, please select download", as well as options for saving/deleting/editing said celestial effects.

Separate bandwidth control options would be advised, although the gzipped/7zipped celestial effects packages are likely to be rather small.

Since it would be cool to have the ability to edit the celestial effects, it might make sense to implement a version control system, so once people have played around with the effects package, they could submit their take on the pack/their improvements back to the server.
* It would be useful to alert people who are using another version of the effects pack that another version has been made available

I'm going to hazard a guess that doing a mashup of CVS/SVN + bitTorrent might be a pain in the ass, but with 20k+ concurrent Resis, and filesizes of less than 16kb (adding support for procedural generation of content to help lower things further would be advised), this would make things rather efficient if it was pulled off.

Individual items of content should be made available for distribution individually- one person's comet effect might be better than another's for example.

Since these creations will involve intellectual property, I would advise enforcing a Creative Commons licensing policy from the get-go.

==== Summary ====
* Rename feature to "Celestial Effects"
* use bitTorrent or other P2P technology to distribute content
* use Version Control systems for server-side storage
* enforce Creative Commons licensing ( CC BY-NC-ND for example would mean refusing submissions back to the central storage server.
** Since multiple servers are likely to be made available, it would make sense for the following two features to be added to the servers
**# Checking to make sure someone hasn't resubmitted someone else's content as a fresh asset.
**# Allowing communication between servers to check results.
* Allow individual assets of the effects package to be modified or replaced
** An option for:
*** Always use asset X for asset type Y
*** Never use asset type Y
*** Never use assets under a specific CC license
** This would mean a single data format could be designed for things such as constellations, which could be combined with any number of celestial effects for the numerous '''Star''' asset types, rendering effects for specific subsets of the '''Star''' asset type.

=== Celestial Asset Types ===
* Stars
* Nebulae
* Comets
* Asteroids
* See [http://en.wikipedia.org/wiki/Celestial_body the Wikipedia article on celestial bodies for full list]

I'm going to stop myself short on this, as I feel this feature alone would eat up a rather large amount of the talk page and is complex enough that it should be given it's own sub-section of the wiki, [[Project:Celestial Effects]], since I have all kinds of crazy ideas in mind for this :-D

[[User:SignpostMarv Martin|SignpostMarv Martin]] 08:52, 13 January 2007 (PST)

== Implement other languages options - Dutch ==

At this moment I'm already changing my english GUI from SL client into a Dutch (nederlands) language version. So my question is if somebody is interested in this and maybe in the future, to add this in the official beta release.
Although there is still a lot of work to do.

--[[User:Crash Crabe|Crash Crabe]] 01:09, 25 January 2007 (PST)

User:Andy Tir

2007-02-12T07:30:19Z

Andy Tir:

I am relatively fresh newbie. You can ping me on silpol@yahoo.com

In RL, I do my job at Nokia, last two years were about [[http://www.nokia.com/770 Nokia 770]] & [[http://www.nokia.com/n800 Nokia 800]]

User:SignpostMarv Martin/Archive/Implementing new features

2007-02-12T07:24:03Z

Andy Tir: /* Removing Texture Loading */

{{OSWikiContribBox}}

Of course, a really valuable way to contribute is to add a new feature. Try to work with the community and with Linden Lab in planning the feature before running off and implementing new things. Though we appreciate your hard work, we can't accept every new feature, since maintaining new features comes with a cost. Try thinking of ways to use APIs to make plugins, or perhaps propose new APIs to make the viewer more extensible, before adding new things to the core viewer.

== Ideas for new Features ==
If you have an idea for a new feature you'd like to see in the client, consider adding it to this list.

Discussion on each topic can be found in this article's [[Talk:{{PAGENAME}}|Talk page]]

=== Alternate Rendering Engines ===
[[User:Fox Diller|Fox Diller]]

* older hardware support, etc...
* [http://www.google.ca/search?q=Open+Source+3D+Engine (''Open Source 3D Engine'')]

==== Barriers to Implementation ====

=== Out of sight, out of mind ===
[[User:Lee Ponzu|Lee Ponzu]] 13:56, 12 January 2007 (PST)

Sometimes a neighbor puts up an annoying sign or other object.

Let the user select the sign, and mark it invisible. This tells the client viewer to stop rendering it, making it effectively invisible.

Of course, this could be applied to any type of object.

=== Permit mapping of textures with a depth offset. ===

[[User:Jherek Cerminara|Jherek Cerminara]]

As an alternative to marking objects invisible from one's parcel, I'd like to see a different feature: the ability to map textures on the face of a cube, but at a depth offset. The effect would be that the face becomes a "window", with the texture seen in the distance through the face of the cube. This would permit us to put windows with real-world scenes or textures anywhere, it would permit 10x10x10 holodecks, and it would also make it easy to cover up unsightly views.

(However, while I think such a feature would be really useful, the real solution to ugly neighborhoods is better urban planning and public policy, in RL as in SL.)

=== Better Sound Support ===
[[User:Falk Bergman|Falk Bergman]] (by way of #opensl on IRC)

* Preload status
* playback control, etc...
** Quote: ''llKelly: eightltr: yes, that idea has been suggested in the past. ('''L$1 per 1sec audio''') I think we would rather improve the methods of linking to externally hosted sounds.''
* MIDI Support - maybe with some nice clientside Wavetables
* MOD, XM, ect. Support

==== Barriers to Implementation ====

=== Removing Texture Loading ===
[[User:Falk Bergman|Falk Bergman]] (by way of #opensl on IRC)

* so SL can run on less powerful Systems (say the N800/N770)
** not to say about other small systems, but N800/N770 has 3D hardware support in it's TI OMAP chip, but legal issues stopped (so far) to write open-sourced driver for that box, and closed-sourced driver has "license clash" problem with rest of (mainly FLOSS'ed) stuff. Don't waste your time in expectations - the company behind 3d accelerator for TI OMAP is rigid bunch of lawyers. -- [[User:Andy Tir|Andy Tir]] 23:24, 11 February 2007 (PST)

==== Barriers to Implementation ====

=== Patching it so that llLoadURL opens the F1 Help Browser ===
[[User:Falk Bergman|Falk Bergman]] (by way of #opensl on IRC)

* Adding keyword replacement in llLoadURL, Streaming media support, and other external links
** For instance, to provide an icecast stream with a agent UUID, <nowiki>http://'''agentkey''':apassword@icecast.somehost.com:8000</nowiki> as a parcel URL
* To provide an external website with a SL User Name, <nowiki> http://www.somesite.com/somephp.php?query=stuff&slname=''agentname''&action=buy&deliveryto=''agentkey''</nowiki>

==== Barriers to Implementation ====
* Unless the LSL2 VM starts supporting optional parameters, you risk breaking thousands of scripts
** '''Workaround:''' Prefix urls with ubrowser:, e.g. '''<nowiki>ubrowser:http://example.com</nowiki>''', which will result in the dialog box indicating that the url will open inside the client.
** '''Alternative Workaround:''' Clientside rewriting only, for connecting to media URLs

=== Adding a Avatar Local Stream Channel ===
[[User:Falk Bergman|Falk Bergman]] (by way of #opensl on IRC)

* that has a Range of X Meters around an Avatar
* This would be used for Local Audio Streaming
** Or Local VoIP chat
** Teamspeak...

==== Barriers to Implementation ====

=== Peer to Peer Voice over IP using above idea, improved ===
[[User:Kamilion Schnook|Kamilion Schnook]]

* Capible clients advertise themselves via below CTCP-style protocol
* Clients use multicast packets to broadcast to a list of addresses the server manages of clients in range.
* In effect, this would give each avatar two unidirectional shoutcast-style stream impliments, or one bidirectional impliment.

==== Barriers to Implementation ====

=== Pseudo-Voice ===
[[User:Lee Ponzu|Lee Ponzu]] 13:49, 12 January 2007 (PST)

Most of our computers have local, client-side voice synthesis. Yes, it sounds like a robot, but it is still voice. Real voice, ala Skype, is fine. But just like we use Avatars to hide our real selves, we need a way to hide our real voice.

A huge advantage is that we could get voice without adding to the bandwidth. The text is coming anyway.

*The simplest idea is that one could mark one or more Avatars, and their Chat would be rendered as voice, as well.

*Slightly fancier---One could set the voice characteristics (male, female, pitch, etc.) for each other Avatar.

*Fanciest---Each user can set ones voice characteristics using Appearance, and those setings would be used on each local client.

==== Barriers to Implementation ====

I can't think of any. Sounds petty easy to me.

[[User:SignpostMarv Martin|SignpostMarv Martin]] (15:46, 12 January 2007 (PST)):

===== Distributed Processing =====
* Processing the audio on the local client and streaming it in-world would require Peer-to-Peer streaming audio.

===== Local Processing =====
* Distributing text-to-speech preferences would require modifications to the server-side code, using 3rd party servers, or Peer-to-Peer protocols.
* Allowing for the ability to add processing the data for up to 400 avatars (100 avatars per sim, within shout distance of region corner) at once would add significant processing overhead.

While distributed processing would probably mean less CPU-intensive code, local processing would have the distinct advantage of allowing users' preferences to be overridden, allowing people to do such things as cap voice pitch, preventing annoying chipmunk-speak from occuring.

==== Addendum ====
[[User:Alderic LeShelle|Alderic LeShelle]] (00:55, 25 January 2007 (PST)):

* It is possible to restrict changes to client side only. One may use existing chat/IM protocols to transmit speech preference data or use a client-to-client protocol to achieve it.

Distributed processing would mean a considerable network bandwidth impact, be it on each client or a dedicated chat server where local processing would simply add the chat preference data traffic to the network, but the speech synthesis CPU load on each client.
It is easier to cap the CPU load, though, for example by simply capping speech synthesis for avatars out of a certain, configurable, hearing range, or simply disabling speech synthesis for the nth nearest avatar and further away.

=== More efficient local cache ===
I'm working on this. We are going to use Berkeley DB with ARC replacement policy. It's going to fly. [[User:Gigs Taggart|Gigs Taggart]] 17:54, 31 January 2007 (PST)

==== Barriers to Implementation ====

=== [http://en.wikipedia.org/wiki/Client-To-Client_Protocol CTCP] protocol layered on IM system ===
[[User:Kex Godel|Kex Godel]]

==== Barriers to Implementation ====
Establishing a circuit between two clients will probably require server side assistance, since circuits are UDP based, and most clients will be behind NAT's and firewalls. CTCP will require a clientside listening socket either implemented via [http://www.faqs.org/rfcs/rfc3489.html RFC 3489] or some sort of UPnP code using a TCP direct connection.

=== Command Line Interface Improvements ===
[[User:Kex Godel|Kex Godel]]

* for changing preferences sending an IM, teleporting, etc
** for example: "/set drawdist 96", "/set sound off", "/tp ahern", or "/im kex godel hello"
** would need an escape system which doesn't conflict with script command gestures (or a reserved words like how /me is)
** Or better yet, the Ctrl-G Gesture management window could be improved to allow this, and even allow rebinding /commands

==== Barriers to Implementation ====
* Implementing an escape system which doesn't conflict with script command gestures (or a reserved words like how /me is)

=== More sophisticated IM features ===
* muting/filtering/autoresponse options
** mute or do not alert on IMs by started by a group, agent, or group-agent
** Autoreply to IMs received while (Away)
** Sidebar Userlist of Active Users who are currently participating in a Group IM Session.
*** When a user says something, they're added. When a user leaves the session, they're removed from the list.
* More control over filtering specific objects/textures/sounds/agents/etc

==== Barriers to Implementation ====
* Anything that requires server-side modification [[User:SignpostMarv Martin|SignpostMarv Martin]] 11:11, 11 January 2007 (PST)

=== Shortcut/Link/Alias function in Inventory ===
*Add a "link" ("alias", "shortcut") facility to the inventory, that would not break Permissions. For instance, I have one nice set of prim dress shoes that are no-copy, and four tuxedos. I cannot make complete separate outfits, because I have only one copy of the shoes. However, using a "link", I could create an outfit folder with the tux and a link to the no-copy shoes. Still means I would only have the one set, but it would make changing clothes much much easier. [[User:Buckaroo Mu|Buckaroo Mu]] 09:23, 9 January 2007 (PST)

==== Potential Barriers to Implementation ====

=== DirectX3D Hardware Acceleration ===
*A DirectX3D-driven version of the viewer, allowing those with ATi or Intel hardware accelerated cards to take advantage of the processing power. The system could allow selection as a preference of OpenGL or DirectX3D, as many Windows-only games currently do. Conditional build statements would keep the option from appearing in the non-DirectX3D capable builds. [[User:Buckaroo Mu|Buckaroo Mu]] 09:28, 9 January 2007 (PST)

==== Barriers to Implementation ====

=== GPGPU Support ===
*A method of offloading some of the [http://www.gpgpu.org/ graphics processing to the GPU] might help increase framerate. [[User:Buckaroo Mu|Buckaroo Mu]] 09:37, 9 January 2007 (PST)

==== Barriers to Implementation ====

=== Multiple Monitor Support ===
*Support for detachable sub-windows, allowing the inventory, chat history, IM, etc. windows to be moved to a second monitor (if available). This is a very highly-desired feature (by those that have dual-monitor systems). [[User:Buckaroo Mu|Buckaroo Mu]] 09:37, 9 January 2007 (PST)
* This could potentially be done using an external program, if SL had some way of exposing this data in a crossplatform way. (Does NT support named pipes?) Some libsecondlife projects such as SLeek are already exposing this. [[User:Kamilion Schnook|Kamilion Schnook]] 20:39 Jan 9 2007

==== Barriers to Implementation ====

=== Implement GUI in Native Widgets ===

I also would like to see multiple monitor support, but I'd prefer this to happen by implementing the inventory system and other parts using native palettes, toolbars, and windows (dockable to the SL window).

=== Embedded scripting language for client-side plugins ===
[[User:Heather Goodliffe|Heather Goodliffe]], [[User:Yumi Murakami|Yumi Murakami]]

* Make the client more powerful and plugable
* Embed a scripting language, such as LUA or Python, within Second Life to enable client plug-ins to be written in a modular fashion. Client plugins would be distributed via Second Life itself; hopefully LL would eventually agree to create a new object type for these, but for testing purposes notecards would probably suffice.
* Let me second that: I'd like to see client-side scripting as well. It should be easy to add that (in particular, using Lua), and it would let users fix so many usability problems. At a minimum, the scripting language should be able to access the functionality available through the menus, it should permit key bindings and grab keys, access preference settings, and it should be able to listen to chat and IM, so that commands can be triggered from there. [[User:Jherek Cerminara|Jherek Cerminara]]

==== Known Barriers to Implementation ====

=== Nude patch ===
[[User:Carnildo Greenacre|Carnildo Greenacre]]

*Modify the client to not render any avatar clothes or attachments.

==== Barriers to Implementation ====

===== Steps to how Linden Lab could 'disable' a 'nude patch' =====

# Run a check on clothing textures including alpha information
#* Check for alpha information around the genitalia, refuse upload if check returns positive
# Composite clothing textures server-side when avatars are:
#* In PG regions
#* Viewable from PG regions

A 'nude patch' would function by:
* somehow submitting full alpha textures on all clothes no matter what was worn (prevented by LL as described above)
* ignoring what the server says regarding skins
** Could use procedurally generated textures based on avatar shape, and primitar type to prevent ''''Attack of the ''(nude)'' Clones''''
:[[User:SignpostMarv Martin|SignpostMarv Martin]] 01:02, 11 January 2007 (PST)
** I don't think a nude patch could work anyway - the skin and clothing textures are combined on the wearer's client, then the combined texture is uploaded to the server as the single texture that appears on the avatar. That's why "rebaking" your textures on your client affects how other people see you. You could possibly just apply the same skin to everyone but you might just as well leave everyone unrezzed then ;) - Yumi Murakami
* [http://somegeekstuff.wordpress.com/2007/01/26/second-life-nude-patch/ here] is a quick and dirty solution ;)

=== Two Tier Search ===
Yumi Murakami

* Server performs a possibly less-effective search which is database efficient, such as the current fulltext search. The client then performs its own search, refining the results. Should allow extra flexibility and take some load off LL's database.

==== Barriers to Implementation ====

=== User Interface Improvements ===
Yumi Murakami

* General improvements to the user interface. Maybe move to a seperate article: [[User Interface Improvements]]

==== Barriers to Implementation ====

=== More Text for Abuse and Bug Reports ===
[[User:Anders Nordberg|Anders Nordberg]]

* Bug Reports as well as Abuse Reports are currently very limited in the amount to text you can enter. Very difficult sometimes to describe a bug in just 2 or 3 sentences...

'''NOTE: A lengthy bug report that would benefit from additional material such as videos or photos could possibly be submitted to [https://jira.secondlife.com Jira] --[[User:SignpostMarv Martin|SignpostMarv Martin]]'''

==== Barriers to Implementation ====

=== Attachments registering as additional limbs for animation ===
[[User:Alderic LeShelle|Alderic LeShelle]]

* Attachments with distinct object names (like wings, tails, extra limbs...) may register themselves in the skeletal structure of the avatar, so that a BVH animation might animate them as well.

==== Barriers to Implementation ====

=== Much Longer Land Draw Distance ===
[[User:Huns Valen]]

* The idea is to have a separate slider for land draw distance. It must be greater than or equal to the "master" draw distance. As drawing land is much less resource-intensive than drawing objects and avatars, it should be possible to have a land draw distance measured in kilometers, not meters.
* Could possibly use colored map textures (from the world map, not from the viewer-generated local map) as terrain patch, rather than the supplied patch, although this might not look great for closer-in terrain.
** Perhaps all terrain within 512 meters could be drawn using the sim-supplied textures, and anything further could be drawn using the world map textures.

==== Barriers to Implementation ====

* Would require child connections to more simulators to render "sorta near" terrain (that is, beyond the draw distance for objects and avatars, but within the usual "far clip.") The simulators would have to JUST send land, not objects/avs/etc. as that would defeat the purpose of having a lower draw distance. (Terrain beyond the usual far clip would all be done as world map textures.)
* Colored map textures may not be available in suitable resolution for it to look really good. However, it should be acceptable to many residents in lieu of the "version 2" graphics engine we were shown previews of in 2005 (and which subsequently was cancelled.)
* If this works well as a proof of concept, LL might be persuaded to make higher-resolution world map textures available, and work on some server-side optimizations.

== See Also ==
Linden Lab is considering offering bounties for especially desirable features in the viewer.

* [[Linden Lab Bounties]]
* [[Community Bounties]]
* [[:Category:Bounties]]