Jump to content

Oz Linden

Lindens
  • Content Count

    241
  • Joined

  • Days Won

    1

Everything posted by Oz Linden

  1. Adding substantial data structure support to LSL at this point isn't a very high priority; I think we've got ample existence proof that people can do pretty amazing things without out them. That having been said, there are other things we'd like to do to make LSL more powerful, but other than a few new functions we don't have anything big on the road map for this year. Access to Avatar Complexity would be relatively easy - please file a Feature Request. Some support for redelivery is among the things we'd like to do for Marketplace - we're trying to hire a developer for that - tell your friends.
  2. I'd be interested in hearing what specific changes would make a "real" first person mode. Submit them as Feature Requests in Jira, please. We're working on a number of improvements that we are optimistic will improve framerate for most users. I'm not familiar with "vector copy" - another good candidate for a Feature Request. The chat window does support "compact" mode, and can also be set to be largely transparent. Moving it (and other floaters) outside the main viewer frame is something we've discussed many times. It's a big job; while we have some ideas on how to do it, at the moment it would mean not doing a great many other things. We'll try to get to it eventually though.
  3. I'm not sure I buy the 95% number, given how many people run it... but in any event, we have an active effort working with open source developers to bring the Linux viewer up to date. Grid scope experiences are on the road map for this year. Unless we are very very close, we prefer not to set expectations for release dates of anything - SL is so large and complex, and the number of unexpected events that can occupy developers for a time so large, that we have not found that we can accurately predict very far in advance.
  4. At present, there's no way to read any HTTP headers from an http_response event. The header value is useful if your request is from an outside web request, though. The throttle allows many requests per second (no, I won't tell you exactly how many because it may change and we don't want people trying to see if they can get in just under the limit) to the scripts owned by the same owner in the same region. A good general strategy is to wait a few seconds (possibly with a little randomness added in) before retrying, and if that fails increase how long you wait by multiplying by a small number before retrying again. If all your requestors follow some method like this, eventually they'll get through.
  5. I don't recognize the exact text, but it probably means that the rate of inbound HTTP requests to objects in the region has been exceeded. We don't document the exact value because we don't want people to try to "get the most we can without hitting it". The 503 response has a Retry-After header that tells you how many seconds to wait before your next request. However... right now, the throttle is applied to all scripts in the region. We are looking into two changes (which are currently scheduled to roll to a small RC this week): The limit will apply to all scripts in the region owned by the same user. This should prevent your scripts from being throttled because of requests to someone elses scripts. The limit will be raised slightly for Skilled Gaming regions (because of the first change, the increase may in practice be quite large). We have baseline stats on how frequently this error is occurring now, and will measure how that changes as it goes through the release channel process.
  6. It should already have increased. It's possible you'll need to relog to see it in your viewer...
  7. That happens if some part of your current avatar was not valid or failed to load. It's possible (but should be very rare) that could happen because something took a very long time to load. It's possible that something had changed while you were away. If it happens again, save your SecondLife.log file and post it in a bug report.
  8. I've been doing that for most of 8 years... feel free to come by Open Development User Group and we've got other User Groups
  9. I'm delighted to hear that it's working again, for whatever reason. I really wish I (or even Linden Lab) could take the credit. I certainly hadn't made any changes yet (though I had contemplated some). Maybe someone else did something, or maybe not... Here's hoping that it continues to work. Thank you for your patience, and for your 13 years in Second Life!
  10. Contrary to popular opinion, we do read these. I flagged this for attention yesterday (a Linden Lab holiday), but am just getting to it. I'll make an effort to help sort this out, but let's please eliminate the counterproductive finger pointing and hostility in all directions. We've made a number of changes to how and when we send email, including changes to some of the software used for postcards. These changes are motivated primarily by the fact that email from SL has in the past often been filtered and discarded or rejected because it was sent incorrectly or to bad addresses. We are trying to make it as reliable as email ever is by upgrading nearly everything about how we do it (and by the way, our internal data shows that that is having a very positive effect). The changes will continue for some time. If something we changed broke Typepad posting (and I have no reason to doubt it), then we'll have to find out from them (presumably through you, Prokofy) why they are not using it. It is said above that Support claimed that our mail sending is now more standards compliant; this is true, but it's still possible that we could do something to help Typepad understand it if we knew what was giving them trouble. We make strenuous efforts to test our changes for backward compatibility, but the universe of things that Residents do with our product is far far too large for that testing to be comprehensive.
  11. The "Darn, you have been logged out..." message usually means that some part of the communication between your viewer and the simulator has been blocked. If you're not having problems with other programs, then the most likely culprit is that some firewall feature on your system is blocking the viewer.
  12. Thanks for the detail, Prokofy. It isn't our intention that SLURLs would trigger the update check; we'll fix that. Some of the other cases you mention are harder to explain, especially When crossing sims When teleporting between sims (after you arrive) from a landmark or someone's sent TP When you are just flying around inworld on one sim. but I'll alert our QA people to be watching for those. If you can narrow down a specific circumstance, by all means let us know.
  13. Our viewer doesn't have that message anywhere. It would help if you described the problem very precisely. One of the changes we made with the new updater is that it is only supposed to check for new viewers when you first launch, and for any optional upgrade it silently does the download in the background so that you're not bothered by the option until the new viewer is ready to be installed. If what you're seeing is the new updater, then it's running when it shouldn't.
  14. From the System Requirements page: if for some reason you really can't upgrade your OS, for some time there is a viewer available from the Alternate Viewers Obsolete Platforms page on the wiki that may work for you, but it will get no updates for new features or even for bug fixes.
  15. Please create a Jira bug report for this Create a bug How to report a bug In particular, please include the SL_Launcher.log file from your log directory with your report.
  16. Please file a Jira for this: https://jira.secondlife.com/ Look in your logs directory and see if there is an SL_Launcher.log file and/or and SL_Launcher.old file; if they are there, please attach them to the Jira.
  17. A jira would be welcome. Be sure to specify the site that you're having a problem with. It may be that we need to update the Certificate Authority roots in the simulator.
  18. Done: '''If you have created shortcuts to run the viewer, you should update them to run the new SL_Launcher executable (if you don't, the viewer will complain when you run it, and updates won't work). Note that on a 64 bit Windows, this viewer will be installed in a different folder (Program Files, per Windows convention).'''
  19. That would be nice, but we'd have to search your entire filesystem to find them all... not really good practice.
  20. Delete your shortcut for the viewer and create a new one that points to the new install. There are a few ways this can happen, but what is almost certainly happening to you is that you have the old viewer installed in different location than the new one is going into, and your shortcut points to the old one. When you run the shortcut, it sees that there is an upgrade and installs it, but does not delete the old install. Next time you use the shortcut, you do the same thing again.
  21. You used ["<html><body>", ", ", "</body></html>"] but it should be ["<html><body>", ",", "</body></html>"] note that there is no space following the comma that's inside quotes. That list specifies the parts of the string to be removed and treated as separators when constructing the list; since there are no spaces following the commas in the string returned by the shoutcast service, you get a list containing a single string that includes everything but the tags.
×
×
  • Create New...