I've heard that LL sims will pass baked textures around from one sim to the next as the avatar teleports around, (or at least they used this method once, not sure if they still do). That way asset servers aren't overburdoned with temporary textures and excessive uploads are avoided. I believe the temporary texture feature in some third party viewers exploits this mechanism to provide temporary, free texture uploads.<br>
<br><div class="gmail_quote">On Sun, Sep 25, 2011 at 11:38 AM, Mic Bowman <span dir="ltr"><<a href="mailto:cmickeyb@gmail.com">cmickeyb@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I will carefully disagree with Justin on this one. The viewer doesn't upload textures by default. It only uploads the textures if it believes something has changed. OpenSim doesn't currently respond correctly to the v2/v3 packets for cached appearance and earlier versions of the viewer can be told that that appearance parameters haven't changed so that textures are never uploaded (this saves a lot of bw... remember that if you upload textures they have to be sent out to everyone in the scene so it isn't the upload bw... its like putting new textures on objects every time the sim starts). In practice, people change appearance so infrequently that the baked textures do not fill up the asset database. And even when the do, so long as you don't get stuck in the "assets can never be deleted" way of thinking... (baked textures are marked as temporary anyway)... its pretty easy to clean up the asset db based on a reasonable set of policies.<div>
<div></div><div class="h5"><div>
<br></div><div><br><br><div class="gmail_quote">On Sun, Sep 25, 2011 at 1:25 AM, Neil Canham <span dir="ltr"><<a href="mailto:neil@knowsense.co.uk" target="_blank">neil@knowsense.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Ah - I hadn't appreciated that NPCs need to be cloned from a logged in AV. That makes sense.<div><br></div><div>As for the persistence, like Mic I think there is potentially an argument for it, as an option, for closed private sims for example, or sims where you expect a lot of people to log in at roughly the same time. However, I appreciate that would be a big change so thanks for clarifying how it operates now.</div>
<div><div></div><div>
<div><br></div><div><br></div><div><div class="gmail_quote">On Sat, Sep 24, 2011 at 11:18 PM, Justin Clark-Casey <span dir="ltr"><<a href="mailto:jjustincc@googlemail.com" target="_blank">jjustincc@googlemail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">For ordinary avatars, baked textures don't need permanent persistence since the avatar uploads them on every login or when any body part/wearable is changed. This will have no effect on slow rezzing or cloudiness - if a viewer is in the region it should always have uploaded the textures that it bakes.<br>
<br>
Indeed, there's little value in persisting these since the client will upload them on every login/region entrance. Persisting baked textures would bloat the asset service more than is already the case.<br>
<br>
An NPC, on the other hand, has no viewer from which these baked textures are uploaded. So they have to be disk persisted at the point from which it is cloned from a 'live' avatar.<div><div></div><div>
<br>
<br>
On 24/09/11 19:28, Neil Canham wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div><div>
I confess that I am puzzled. I found this fantastic description from Mic of how 0.7 appearance works<br>
<a href="http://opensim-dev.2196679.n2.nabble.com/What-I-ve-Learned-About-AvatarAppearance-td5655933.html" target="_blank">http://opensim-dev.2196679.n2.<u></u>nabble.com/What-I-ve-Learned-<u></u>About-AvatarAppearance-<u></u>td5655933.html</a> and it fits with what I<br>
see analysing the packets against 0.7.1. So that seems quite clearly to say that baked textures are never persisted,<br>
and that would explain the slow rezzing and 'cloudiness' of avatars that I see regularly. However, the new npc code<br>
seems to require that a baked texture is available to copy from. So are baked textures now persisted in the latest code?<br>
<br>
<br>
<br></div></div>
______________________________<u></u>_________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de" target="_blank">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/<u></u>mailman/listinfo/opensim-dev</a><br>
</blockquote><font color="#888888">
<br>
<br>
-- <br>
Justin Clark-Casey (justincc)<br>
<a href="http://justincc.org/blog" target="_blank">http://justincc.org/blog</a><br>
<a href="http://twitter.com/justincc" target="_blank">http://twitter.com/justincc</a><br>
______________________________<u></u>_________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de" target="_blank">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/<u></u>mailman/listinfo/opensim-dev</a><br>
</font></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de" target="_blank">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
<br></blockquote></div><br>