#Phoenix viewer update code

Long before the viewer code was even open-sourced, LL had a much anticipated project, 'Physical Avatar' which was to give us on-the-fly ragdoll animations (aka 'Expressive Puppeteering') among other wonders. Of course it depends on the settings, but it seems to be impossible to come up with values that look as natural and bouncy as the original Emerald breast physics. I like the additional buttocks and belly physics, but the way that the breast and belly mesh is distorted in v2 looks quite unrealistic and ridiculous imho. If the Phoenix devs, or rather the Emerald devs, had not implemented breast physics in the past, LL would have never realized how popular this feature is and decided to implement their own version. The correct way of implementing this feature would be letting a physics compatible viewer signal that capability to the server and the server has to take care that viewers get data in a protocol format they can handle! LL was either unaware of this when implementing the model changes or too lazy to implement the changes in a way they don't break existing old protocols. As this happened long time after V1 has been released, it doesn't render V1's method a bug. The problem only arised as LL changed the avatar model, thus new parameters have been created. Both are valid methods of handling unknown parameter data. For V2 they changed the way how parameter data is handled in a way that unknown parameters are just ignored. In V1 was agreed upon a different way to handle incoming avatar parameter data, namely aborting if unknown parameter have been received, assuming the data was broken. You can blame LL all you want, but don't forget to blame the TPVs either, 'cause the fix for this issue has been out or over a year. It had been so long that they'd forgotten about it. A bug that that LL fixed in v2 way back in 2009. LL did notify TPVs as soon as they found out, but this is not a problem with v2, it's a bug in v1.

Phoenix viewer update