Jump to content

Oz Linden

Lindens
  • Content Count

    237
  • Joined

  • Days Won

    1

Everything posted by Oz Linden

  1. This is not a thing. We don't delete accounts when you miss a payment - we don't even limit access until after a considerable grace period.
  2. The documented limits are correct, but as others have pointed out even getting close to them can cause throttling events, and once throttled it will take quite a while for the condition to completely clear (twice the period that triggered the throttle initially, typically). Yesterday I posted an example script to show how to employ a fuzzy exponential backoff to deal with remote server failures; it would work equally well for throttling. http://wiki.secondlife.com/wiki/HTTP_Server_URL_Registration
  3. This is true only after a fairly long grace period (during which Billing will be reaching out to you to get it corrected). It does not happen automatically when a payment fails.
  4. In general, we won't be discussing dates or milestones for our migration to the cloud, only any user visible changes that result from that migration. Initially, we hope that there won't be many of those - it should be more or less invisible to you (digging into the hostnames or IP addresses may provide clues, but not always). We've moved a few things, and are finding and fixing a few problems that crop up with the changes. As noted above, we're also upgrading the OS version for simulators and other things; again, that should be mostly a no-op for users. It's also true that none of the above has anything to do with streaming viewers. We've been monitoring the cost/benefit of streaming viewers for years, and will continue to do so. If/when we think that the cost we can offer a streaming viewer is reasonable, we'll do it. There is https://brightcanopy.com/ now (not a LL product).
  5. That was broken by Facebook, I'm afraid, and it's not clear how we can fix it.
  6. It's sort of a problem with the installer. We went through a few changes in updater strategy over the last few months, partly to be able to protect users who still need 32bit viewers and partly for some other reasons. I think we've ended up at a good solution, but there were some problems with some of the intermediate steps. I think that if you'll delete any shortcuts that you've been using to launch the viewer, and then reinstall one more time, you'll be ok from now on. (The problem is that the shortcut you're using is still pointing to a leftover component from an earlier version) If that doesn't solve it, please zip up all the log files in your log directory and file a bug report on jira. My apologies for the inconvenience.
  7. In order to allow for meaningful testing, yes we do. Everything is very very close to ready, so we're in the home stretch.
  8. Any testing you do with a non-EEP viewer is only testing the temporary attempts to convert the new EEP settings to some approximation of them for non-EEP viewers. These are not perfect and are not really meant to be. Once EEP is promoted to the default viewer we expect that it will be quickly adopted by all actively maintained Third Party Viewers, and we'll all once again be in sync. The only way to see what things will look like with EEP is to use an EEP viewer on an EEP region; the project has made major changes on both the server and viewer side, and we can't make the non-EEP viewers show the same results that an EEP viewer would. Making assertions about how it looks or behaves based on testing with anything other combination is meaningless. If you don't want to test, that's fine (Project viewers are always opt-in), but please don't confuse others by doing invalid tests and making assertions based on them.
  9. Mainland parcel owners have the ability to set the environment for their parcels, so yes, adjacent parcels may have very different environments.
  10. That message usually means that the server is not getting messages from your viewer reliably (too many lost). Check any firewall on your system, and reboot your router and cable or dsl modem (usually it's best to turn both off, turn on the modem and wait for it to come up to normal lights, then turn on your router).
  11. Without commenting now on whether or not we have the specific cost correct (the people that chose that value know much more about it than I do), it is not correct that Land Impact exists only to protect or account for server side resources. Viewers lag too, and objects that produce unnecessary viewer lag have a large negative impact on the experience of Second Life. Land Impact exists not only to limit what you can put out, but to encourage efficient content. Animesh objects are more work for a viewer to process; the increment to LI exists to reflect that cost.
  12. Check what your system sees as the IP address for www.bhr.vivox.com (that's the voice service for the main grid). In a terminal window, type: nslookup www.bhr.vivox.com The correct answer is 74.201.103.238 If you do not get that answer, it means that your system is trying to contact the wrong service. Rebooting your system may fix it; if not, it should correct itself eventually (the actual problem has already been fixed, but some DNS servers are incorrectly still giving out old addresses or otherwise failing to provide the correct one above).
  13. Oz Linden

    auction

    Auctions have started again. See the status update
  14. llHTTPRequest will return a null key whenever there is any error that does not send a request, so you could do something like key request_id = llHTTPRequest(strURL, [HTTP_METHOD,"POST"],llList2String(lRequestsToBeProcessed, 0)) ; if (request_id == NULL_KEY) { llOwnerSay("invalid url " + strURL); }
  15. No request is sent for that error, and no response is generated. It is true that some url parameters that were actually invalid used to be accepted and are now rejected by stricter tests. Feel free to post examples.
  16. Don't believe everything you hear. We are not phasing out classic avatars.
  17. We have that now under Preferences > Advanced. The slider is labeled "UI Size". Use with some caution - it's hard to test everything in the UI for all languages at all sizes, so this slider has been referred to as the "UI Bug Slider", but it does make things much bigger. For example, I'm going to have to edit my preferences by hand to undo it after this demo because I made it so big that the "Ok" button on the Preferences no longer fits on my (not very large) monitor:
  18. That won't change from the way it is now: if you select a personal environment (for example, by selecting "Midday", but it can be anything you pick), then that applies until you choose "Use Shared Environment" or until the end of your session.
  19. The ability of an Experience to set an environment has not yet been released (soon!), so whatever is happening there is not Experience-based.
  20. any time you go from one environment to another, whether by moving to where a new one is in effect or because a day cycle is changing, the setting interpolate. For movement the change takes a few seconds.
  21. Our monitoring doesn't show that. If you are having repeated problems that you can describe more specifically, we could try to help diagnose them, but Jira is a better way to communicate about them than the forum. If you have local recording capability on your system, recording the audio for one of your sessions (with the informed permission of the participants) would be one way to start diagnosing voice issues (many problems produce recognizable audio artifacts). We could also help you learn to do packet captures of the relevant network traffic for analysis.
  22. The speed of light in optical fiber is about 1/3 slower than in a vacuum (the number you used), and there are lots of electronics in the way (a repeater about every 15km on undersea cable, for example).
  23. Sorry ... that's not possible. You were not doing what you thought you were doing. The speed of light isn't that fast. animats is correct; the 'ping' time in the viewer measures the viewer->simulator->viewer time with the message being handled at the application level at both ends, so it is affected by the load at either end as well as the network you're sending over.
  24. No idea, but your request for the logs is the correct next step.
  25. That was a bug in the Release Notes - sorry; simulator animesh support is live everywhere on agni, and the Animesh viewer has reached Release Candidate status. This means that it's believed to be at least very close to its final form. We're monitoring how the Release Candidate viewer behaves in production use... so by all means use it. As for Firestorm... you'll have to ask them.
×
×
  • Create New...