Jump to content

Rayne Keynes

  • Posts

  • Joined

  • Last visited

Everything posted by Rayne Keynes

  1. Thats mostly a setting of the user. I have my viewer set to NEVER automatically accept or open ANYTHING from ANYONE. I dont want the distraction. IF there's a way to force this behavior, despite user settings, I don't think it would a be good, conducive to business idea.
  2. Rya Nitely wrote: I really try to avoid having long titles for my items. Stepping Stones - Light Mossy - Complete Pack. I guess I could do that thank you for responding Rather than extending titles, maybe make a section at the top of the description for more detailed info. So the name would be something like "Stepping Stones - Complete Pack" and then in the description, "These stones are covered in light moss, and have a jagged, realistically carved shape." ADVISORY: THESE STONES ARE NOT PART OF A SET AND MAY NOT MATCH ANY OTHER MOSS ITEMS SOLD BY US. Not necessarily in caps of course,.. but you get the idea. When I did sell on XStreet before LL bought them out, I made heavy use of the description and notes areas,... giving my items a very specific title/name, and then filling in any other important info in the description. Just a thought.
  3. I have never been a fan of Macro boobs, since before the sculptie days. I know several friends that have and swear by them, I find them personally rediculous,... As for clothing, being one of them weirdo furries, I have a hard time as human pants don't work well with digi legs. However, for shorts, skirts, medium dresses and tops,.. I like coldLogic, Duck Nipple, Mon Tissu, and FATEWear. I swear by coldLogic stuff,... they've got several thousand of my L$ already and they're reasonably priced,...
  4. In my opinion, the buyer may have been HOPING for matching "Mossyness" since both items came from the same maker,... however, one would not necessarily EXPECT matching moss from the pictures. Last I checked, there were multiple kinds, textures, consistancies etc, etc of moss. Though it's been years since I had to know one moss from another,.. lol Sounds as though the buyer was reading something into the title of the item entries that wasn't intended. Maybe take some more time to name a little more clearly if at all possible? Maybe put something in the description stating that the pieces do not belong to a set of any kind. Just a suggestion. As to the questionat hand, I dont know about "fair" but, it's his opinion and therefore just as valid as any other,... he isn't syaing it's bad, just that the mossy types don't match and didn't meet his, possibly, unrealistic expectations.
  5. Simply making llRequestAgentData respect the online/offline preference would solve the problem. Without breaking content. To put this in perspective, if we break this function, lets remove groups, and IM ability as well, since neither of these respects the check, and will show someones "true" online status. Simply make llRequestAgentData respect if someone has already checked "appear offline" in there settings, no new function needed, no new permission box needed. If the load on the back end is too much, implement a throtle to slow down incoming requests much as many LSL functions already have. Much better than wholesale breaking a function that is very important to many, upon which many business are based, breaking thousands of pieces of content, and being openly hostile to content creators. To say nothing of the hundreds or thousands of people that will suddenly become outraged and flood creators with IM's when this function stops working.
  6. Yes, thats it, lets add more script load and communication lag than existed with the old system, thats the solution. All so some insecure people can have their "feel good" fix that will do absolutely nothing to enhance or enforce their imagined "privacy".
  7. Yup, and in the meantime we break thousands of pieces of content, even decimating a few whole industires, most of which cannot be realistically or easily fixed. Despite the ignorant protestaions of some,..
  8. And this is why stuff like this still happens with as little opposition as it does,... Double the scripts running for a product there by increasing lag or,... you know wut nvrmnd,.. some people refuse to get the point.
  9. No the content CANNOT be fixed. Unless I start giving out the scripts that my business is based on full perm so they can copy it into their own so it will work,... Try convincing ANY content maker that that's a good idea or an acceptable solution,... "oh, just give out copies of your product full perm so they can be copied and then they'll work,.." THAT is what you and other people are not understanding. People build things like online indicators to be used in clubs, land rental etc so that the OWNER of that business can indicate whether certain employees, dancers, customer service etc, are online or not,... and as such available to answer questions, help with issues etc,... by forcing the people who design these things to give/sell the script full perm so it can be copied into a script owned by/ created by the recipient, your effectively killing that business. Having employess rez there own prim is not acceptable either, because now you have multiple prims from multiple people some of whom you may or may not have edit rights for, so you cant move them if you need to, edit if you change visual design of your business and most importantly, since you dont own the script, you can no longer update it or make changes as your business needs change. The bottom line is, this is BASIC functionality that many businesses are built on, it IS NOT a privacy violation in any sense of the word, and LL by removing it is flat out detroying businesses. So much for being more content creator friendly,..
  10. I agree, this is going to do absolutely nothing to enhance any sort of real privacy while at the same time breaking thousands of products across the grid. I also agree that in this instance, the broken items cannot be fixed and the removed functionality cannot be "worked around". I am having as much trouble getting my staff and some clients to understand this as you are. LL is effectively rmeoving basic functionality from the scripting system that has existed for as long as SL scripting has existed, and upon which literally thousands of content items are based and even to some degree whole SL industries. Not that they care,...
  11. Logging into and out of another grid is an unacceptable solution to testing large numbers or regular testing of medium numbers of textures, when the existing solution works and doesnt harm or impinge on anyone, other than LL's revenue stream,...
  12. Im annoyed to no end about the breaking of the scripts relying on getting a users online status, i fail to see how this is in anyway, a privacy issue, when the same thing can been seen multiple ways using LL or any other viewer. This feature alone will break multiple pieces of content across the grid. Including my entire empoyee status system which relies on the function, some of the rest of which was created by people no longer in SL, forcing owners of said products to buy new versions from different vendors, when nothing was wrong with the old one. Also including some new functions recently added to the LSL library by LL that absolutely rely on being able to get a users online status. I guess some people must still think that they have a right to privacy online and that the internet is anonymous,... I am also absolutely livid about no more temp textures, this is a blatant attempt to increase revenue or act as a money sink for LL. I recently modded a new avatar head, I used temp uploads to test 25 textures on the head before finally settling on one, no way i would upload L$250 worth of textures to discard most of em. Some people will say that the loacal bitmap browser in some viewers will be an adequate replacment, i say it is not, part of the attraction of temp textures, was that those there with you, when you uploaded them, could also see them and 2, or more, sets of eyes is always better to spot problems. Taking temp textures and leaving us only the loacl browser, break the collaborative aspect of what temp textures was designed for. Once again LL has shot themselves in the foot,... anyone who decries this move will be labeled as panicing, and hysterics,... kind of reminds me of the whole "adult content" issue, yup, that one really cleaned up the grid didnt it,.. oh wait,.. um, nvrmnd!
  13. ARC is an almost totally arbitrary, and mostly useless measurement. I simply ignore it with nk ill effects.
  14. If the first frame of your anim isn't marked as a key frame or in some way becomes corruptecd, SL will choke hard on it. The rest of the frames in it aren't as important.
  15. The problem may be the GMA onboard video. If you can, slap another 1GB stick of RAM in that Mini, should help a bit. Between what the GPU is taking and the system, you may be a little light on memory. Despite what Apple says the oldest mac mini's can still take 2GB of total memory. Might require you to open the case though. The issue with 1.23 isn't limited to Macs either, I've seen several people complain about it. If they dont fix it before the next update and obsoleteing 1.22 I wont be able to play SL anymore. If I try to use 1.23 and have Glow enabled, "Basic Shaders", I cant move below 1k meters.
  16. I'm using 1.22.x on a G5 17" iMac,.. I don't know it's insisting you upgrade to 1.23,... It may say theres an upgrade available, that doesn't mean you have to use it.
  17. Your computer is fine for specs, mine is much older and works well. The achilles heel of your system is going to be the GMA video. If you are using SL Viewer 1.23.x, try downloading one of the older versions. I had to go back to 1.22 when I had a similar freezing issue after upgrading to 1.23 Older versions of Second Life can be found here; http://wiki.secondlife.com/wiki/Old_versions
  • Create New...