![]() 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 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. 1,746,000 recognized programs - 5,228,000 known versions - Software News. The viewer contains features meant to improve performance and enhance your game experience. 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. Free phonex secondlife download software at UpdateStar - Phoenix Viewer is a viewing tool developed for Second Life. It had been so long that they'd forgotten about it. A bug that that LL fixed in v2 way back in 2009. In fact, most get angry if you suggest it.LL did notify TPVs as soon as they found out, but this is not a problem with v2, it's a bug in v1. How can the problem be caused by my inventory not loading when them changing out of Phoenix fixes it?īut yea most people in game right now won't accept anything is wrong with Phoenix. what viewer are you using? They always say, Phoenix. ![]() Somebody says to me, "Hey you are Ruthed" I ask. These viewers change all the time with updates and I'm curious if the differences between the viewers is the real problem and not asset server. I've been told I was Ruthed about 10 times now and every time I ask and they say they are on Phoenix. ![]() So far in my experince only Phoenix people have seen me as Ruthed. Ok well if people are seeing Ruthed people on Viewer 2 my theory goes out the window. like hours go by and I see myself fine, but then somebody will send me a screen shot of myself as half female/half male.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |