Jaffee Gaffer wrote:
It's just frustrating that I've been dealing with this for more than three years and LL has never admitted that there is a problem.
Inventory not loading reliably has been a known issue for a while, although it's not clear how well acknowledged the issue was in public. It's also very often confused with different problems, such as lost inventory transfers and dragging inventory into objects (among others that I'm working on next). Part of why Viewer 2 is important (or another viewer based on V2, yes I understand there are preferences for other viewers ) is that the codebase is significantly cleaned up and we're able to approach each smaller problem and fix it independently.
[snip]
But again, I do appreciate your work. It seems to have solved the problem, whatever it is. Now I just hope someone puts it in a viewer that makes sense.
Thanks! The technical details fairly straightforward: load inventory over HTTP, rather than UDP. Movement and voice, for example, make sense over UDP because a lost network packet will, at worst, be a momentary jerky movement or a staticy voice, and you continue on without any trouble. Inventory, however, requires that 100% of the data arrives. For this, HTTP is a better protocol because it allows the viewer to identify a complete transmission, and to retry the request if it failed. There's a little more to the story, but that's it in a nutshell.
I've presented about the inventory system at the open source viewers user group (I'd capitalize but I forgot the current official name of this group), and the devs were excited to incorporate the necessary changes, and glad that I provided full docs on the SL wiki. I think it's just a matter of time before your favorite viewers take this up.
Please nudge your favorite viewers' teams to update their code - even if they're staying on 1.23 codebase - because the cost of dodgy inventory loading in some viewers is a lot of unnecessary frustration!