![]() ![]() The Marketplace has few ways to find mesh, outside of just searching for MESH. If you wear mesh clothing to a venue where the majority of people see you naked except for a donut, people who run the venue have a right to ask you to change or leave if it is offensive to a lot of their other customers. They are unstable and crash frequently - I have a brand new computer that greatly exceeds the minimum specs for running a mesh viewer and find this to be true in all of the viewersi've tried. Not everyone has had a thrilling experience with the new mesh viewers. When this changes more people will be willing to wear it. Personally, I haven't found any that I am willing to spend money for. Also, there just isn't enough of it out their to suit everyone's tastes. Not everyone is enthralled with mesh clothing right now because most have to alter their shape to someone else's idea of what it should be for the clothes to fit properly and the individuality of their look is important to them. Yes it may their 'problem' but it is a financial one, not because they are incapable of coping with change. Not everyone has a computer capable of running a mesh viewer nor do they have the funds to upgrade. I am not against mesh, but consider these points which have been brought up before in discussions about mesh: Figuring out which value to adjust to get which effect takes more practice than I've been motivated to invest myself, but starting with the Phoenix team distributing their own settings on Marketplace, I'm guessing that enterprising sorts will make a good business from this wearable, eventually.I see a bit of unreasonable behavior and attitudes on both sides. I agree that the range of settings available for LL's avatar physics is pretty overwhelming. They may not even have been aware of the intended extent of the then-tabled Physical Avatar project. When the Emerald developers chose to implement breast physics, I don't know if they decided it was the easiest feature to do without server-side changes (such as it was), or if they just had a bewb fetish and rightly judged that there were many such enthusiasts. 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |