Das ist momentan alles noch in der "Brainstorming" Phase, d.h. momentan gibt es weder konkrete Pläne noch irgendwelche konkreten Termine für diese Geschichte mit dem Limit.
Und alle Infos, die man bekommen kann, die sind im Wesentlich bei Babbage Linden zu finden (
User:Babbage Linden - Second Life Wiki ) oder hier und da auf der SLDev Liste.
Imaze Rhiano hat das, was bisher in der Diskussion darüber so alles im Raum schwebt mal so zusammengefasst:
Imaze Rhiano on SLDevList schrieb:
Current status:
- Functionality that allows monitor memory usage is ready in server.
- Currently what is missing is UI for client side.Should be done early
2010 - thought most skeptics in audience
agrees that this is really going to happen 2011 - just before world
ends in year 2012.
- Parcel and avatar memory are going to be completely separated. If your
avatar don't have enough memory
for attachment that you are trying to rezz, then you will get error
message and rezzing will fail - even if parcel
have zillion bytes memory available. There is an exception here - in
sandbox sims you can still rezz any object. (OH
audience suggested that sandboxes would be renamed to "crashboxes" -
Babbie didn't make any promises)
- You can show your OWN attachment memory usage, how much different
attachments are using memory and
probably other statistics. This means that you can't look your
girlfriend attachments and see is she really using
that XCite thingie that you bought for her - or is she cheating you
and actually using that other manufacturer's thingie
what was bought by her secret lover that you are not supposed to know.
- You can show your OWN PARCEL memory usage, how much different objects
are using memory, other statistics
and there is also going to be tools that help you to locate those
scripts. You can't show avatar attachments memory
usage in your parcel.
- You can show your OWN REGION - even if you don't own parcel in there
(estate managers), memory usage,
how much different objects are using memory, other statistics and
there is also going to be tools that help you to locate
those scripts. You can't show avatar attachments memory usage in your
region.
- Parcel memory limitations are calculated from parcel's area. Initially
things like double primitives doesn't effect to memory
limitations. Babbie was hoping that someday region owners could
effect to this - like create heavily scripted regions and
lightly scripted regions.
- There is going to be at least half year warning period where residents
can see their memory usages, but limits are not
yet enforced.
- It is not technically feasible to do system that would separated "old"
content from "new" content created after memory
limit introduction - and would allow "old" content stil run without
limits.
- Mono scripts are going to use memory that they are using - might be
much less than 16Kb - LSL classics scripts are
always using 16Kb.
According Babbie, there is at least one avatar that have 7612 scripts
(using about 96Mb memory). And average user have
100 scripts. Highest script count what I have seen what was about 800
scripts - and it is pretty normal that non-techie
person have 200-400 scripts. This kind awful statistics has been
constant motivation about secondary discussion:
"Why people need so many scripts and what we can do for it so that there
is no need for so many scripts?". This discussion
has lead several improvements that ARE COMING to scripts early 2010 -
... err... someday...
(...)
Babbie would really want to hear more reasons why people are using
hundreds scripts. So if you have more reasons - please send them for
Babbie. So that his team can form strategy to overcome reasons behind it.
Wie es aussieht wird es also keine Beschränkung der Anzahl der Scripte pro Agent/Ava geben (udn auch nicht pro Prim), sondern eine Beschränkung der Speichernutzung pro Ava/Agent.
Und die Speicherbegrenzung auf Parzellen wird wohl nichts mit dem Ava zu tun haben (und direkt mit den Prims), sondern von der Größe der Parzellen abhängen, d.h. Anteilig zur gesamten Sim.
Esatate Manager können dann wohl sehen welche Parzelle wie viel Speicher belegt.
Bevor das ganze kommt mit der Beschränkung wird es aber erst mal ein Tool geben, mit dem man den Speicherverbrauch seines eigenen Avas und den Speicherverbrauch auf seiner eigenen Parzelle ansehen kann.
Und erst nachdem man dieses Tool eine ganze Weile zur Verfügung gestellt hat wird irgendwann das Limit eingeführt, wobei nicht zwischen alten und neuen Scripten unterschieden wird und LSO-Skripte immer 16kB Speicher brauchen und Mono-Skripte den Speicher belegen, den sie brauchen (bis 64kB).
100% konkret ist das Ganze aber noch immer nicht, da kann sich noch einiges ändern.
Was mir persönlich fehlt ist aber z.B. eine umfassende Radar-Funktion im offiziellen Viewer, die einfach diese Supertools mit Radar, Freundeerkennung usw. überflüssig macht, die sehr viele mit sich rumschleppen.
Was irgendwie über den Viewer gemacht werden kann (weil die Daten eh schon vorhanden sind) sollte auch über den realisiert werden, egal ob z.B. besagter Radar, (einfacher) Taschenrechner, Plattformrezzer oder Flugfeder oder sowas... das würde die Server schon ziemlich entlasten.