Triple Peccable

If I may step in here for Ann.. I think what she means is the capability will be available across the grid, but only "Professional Content Creators" will have access to the tools, including the expanded permission system and the additional script commands. So, like her, my future in SL will greatly depend on their definition of a Professional Content Creator. Until that is answered it almost makes me want to halt development, because of the risk of losing a lot of work if it does indeed turn out to be a very closed group.

I am pretty sure the date is the date the previous owner purchased it. In other words, the date doesn't change when the person abandoned it, nor when LL auctioned it, nor when it was awarded to the highest bidder.

Wow, snapshots that close-up and detailed might violate my privacy. Someone might actually see where my pot plants are growing!

Yes, you are thinking wayyyy back. There was a deal between Hippo and XStreet that, if I recall correctly, was close to being completed and ready to deploy when the whole thing fell apart. That is scary from a scripter's point of view by itself. Then LL bought XStreet and turned it into SLX. In an effort to fix all the problems introduced by that, LL made mention of coming out with their own vendor. I have had the heebie jeebies about vendors ever since.

Zanara Zenovka wrote: Or maybe once a week a creator could do a show and tell as an educational things for commerce/LL staffers. "This is what I do. These are the tools I use to do it. These are the issues I struggle with. These are the things that could make my life easier." Could actually be quite interesting and eye-opening and help build bridges towards understanding on both sides. Don't think that would work, Zanara. The thing to remember is that the #1 item on LL's priority list is "How can we make money?". So, if we creators show LL how we are making money they will then eventually turn that knowledge and expertise into a new revenue stream for them. On one hand, LL does not hate us. On the other hand, we are disposable. Here's a good example of that: I would love to add a full-featured, networked vending system to my line of products. However, I could wake up any morning, with no warning whatsoever, to find that LL has released their own vendor which is *required* in order to sell anything in world. That completely removes my motivation as a creator of such products. It is too risky to invest that much time in developing a product that could be wiped out overnight. Do you really think that LL would care if they wiped out the entire vendor industry if they believed that taking over that industry themselves could provide a viable revenue stream? Not a chance! I know that LL *wants* to work with us and cater to our needs, but anytime it comes to a decision between what is best for creators and residents vs. what is best for LL's profits, money is going to win every time, even if the decision is short-sighted and causes long term harm to their profits.

I still like my solution: If you are really that worried about people knowing if you are online or not, just stay online 24/7. No script could ever let anyone know if you are actually afk or not! Then we could just leave things as they are...

That JIRA isn't closed, it is quite active. There is even a post today from Oz Linden you should read: https://jira.secondlife.com/browse/SVC-4823

Kwakkelde Kwak wrote: Wolfee Yaffle wrote: I do find it funny that a LSL command that has been in SL since the beginning, is just now starting to make people uneasy. People don't seem to notice something unless it's shown to them in a GUI though, so it's isn't that surprising. Are you talking about the online thingie? There's a big difference between the ll Function and the viewer showing it. the script function needs a avatar key and getting that key requires an action by the person. There's no such thing as llName2Key. There are databases and possibly other ways around it, but it was never intended to work witout the person being involved, unlike the viewer function. The problem is the LSL function will be broken also. I listened part of audio, and the way it sounded to me is that it is not being contemplated, it is definite that the data server function that returns the online status of an avatar will be changed so that it *always* returns OFFLINE unless the script is owned by or created by that avatar. The only thing that wasn't definite is when it will be implemented. But all online status indicators in-world will basically be broken.

Whenever that happens to me a sim restart always fixes it.

Won't be funny if it turns out ot be true...

With the new-ish addition of the script command llRegionSayTo(), any channel can be secure.

Don't rule out a heat issue. There is a bug in the latest viewer that causes it to use 100% of the CPU 100% of the time. That bug wasn't there in the previous versions. If your CPU fan is choked with dust I can see where the problem might not show up until this latest viewer runs for 5 minutes or so. You should be able to download a stress test program that will quickly let you know if that is the problem or not.

This can be used to help with the ban line/vehicle problem: https://marketplace.secondlife.com/p/Explorers-HUD-Essential-for-all-Vehicles-Explorers-and-Landlords/1269113

I saw some really crazy stuff earlier this week becuase of the bug Natales mentioned. There was so much extra traffic being created by LL's servers that I had to clear my internet traffic log because of the HUGE increase in size. In fact, it was so bad that it would not surprise me if some equipment on LL's end thought there might have been some sort of attack going on. That, in turn, might have triggered something on their end that resulted in port scans, it is tough to say. The moral of this story is I would wait before I did anything if I were you. The bug has been fixed and rolled out, so it is quite possible the port scans will not reoccur. Don't make any decisions based on anything the grid did last week.

For over 6 months I have been trying to tell the Lindens about exactly the issue you described, Wolf. But the term I use is "sleep", because the homestead open water sims you mentioned are acting exactly like they go to sleep after a period of non-use. Theoretically, one would study the problem, collect data, present it on the JIRA, and the Lindens would take it from there. However, I tried that and it didn't work. It appears that they don't want any new JIRA's about this issue, they want all comments to be placed at the end of a 4.5 year old "catch all" JIRA, which allows them to ignore the comments if they choose to so do. When it comes to this particular problem, they have definitely chosen to do so. They either: A) Do not know how bad it is because they think all the region crossing problems are related to SL just being SL, or B) They do realize the sims are "going to sleep" but have no idea how to fix it. I tried to open a specific JIRA on this "going to sleep" issue, which started about 9 months ago, but it was closed as a duplicate JIRA of the 4.5 year old "catch-all" JIRA. Since I sell a product related to sim crossings I have put in a lot of time studying this particular issue, I have a wealth of information about it. But I have *no way* to get that information to someone who matters. ETA: There is a silver lining here, I believe. The Lindens tweaked region crossing performance not too long ago, and now I see they are doing it again. Tweaking is fine, so once we finally convince them that unused homestead regions are going to sleep (and they fix it) region crossings will be so tweaked they'll be absolutely awesome!

MB, is it possible all the objects giving you problems are deeded?

The problem is with a bot, not a script. The region where the bot normally lives is Dobinson. I created a JIRA: https://jira.secondlife.com/browse/SVC-7613

I have a data collection bot that most of the time just sits and does nothing. Since yesterday's roll the amount of data being xferred to and from SL from him has almost quadrupled. Again, that is with him just sitting alone, high in the sky, doing nothing. Anything on your end that could explain that, Oskar?

LeTigre code went to all the RC channels yesterday, because of a bug in the Bluesteel code that was causing sim crashes. So we won't have that function available until next week at the earliest..

I like Nalates' blog: http://blog.nalates.net/the-stuff/sl-script-related/

It takes a live support chat, a phone call, or a support ticket in order to get a mainland region restarted. Normally that would be done by someone who owns land in the region, but anyone could contact support to get a mainland region restarted as long as they have a good enough reason.

SL sends a packet of data to your viewer for every frame. At dozens of frames per second, it can add up to a lot of data. Here's a little tip that I bet many are not aware of: When the SL viewer is minimized (or even if it is visible but it is not the active window), the frame rate is reduced. That means it is using less internet bandwidth. So just making sure the SL viewer isn't the "active" (or focused) window when you walk away from your computer for a while can help. But for those of you who do not mind changing Debug settings, you can reduce the frame rate even more when the viewer isn't the focus. Just go into the debug settings and find BackgroundYieldTime. I set mine to 400. This slows the frame rate to 2.5 frames per second, but only when the viewer is not the active window. Works great, and saves a little bandwidth.

Megaregions are fine, but it isn't the right solution to the problem. Regions crossings *can* be fixed, and I know people will laugh at me for saying this, but I think they actually *will* be fixed at some point. Introducing something like megaregions is fine, but region crossings need to be fixed anyway.

The title is a property of the prim, not the scripts. So once it is set it will stay even if you delete the script. What you need to do is place another script in the hair which sets the tile to nothing (""). Then you can delete that script.

Sounds like it could be heat related to me. Most programs don't tax the CPU like the viewer does. Make sure the computer is free of dust build-up, especially on the CPU and power supply fans. You may be able to download a utility program that will report the CPU's temperature, which could help. You can also download and run various stress testing and benchmark programs. If the problem is one of cooling those types of programs will probably fail also.