Jump to content

Oz Linden

  • Content Count

  • Joined

  • Days Won


Everything posted by Oz Linden

  1. In order to allow for meaningful testing, yes we do. Everything is very very close to ready, so we're in the home stretch.
  2. 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.
  3. Mainland parcel owners have the ability to set the environment for their parcels, so yes, adjacent parcels may have very different environments.
  4. 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).
  5. 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.
  6. 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 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).
  7. Oz Linden


    Auctions have started again. See the status update
  8. 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); }
  9. 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.
  10. Don't believe everything you hear. We are not phasing out classic avatars.
  11. 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:
  12. 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.
  13. The ability of an Experience to set an environment has not yet been released (soon!), so whatever is happening there is not Experience-based.
  14. 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.
  15. 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.
  16. 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).
  17. 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.
  18. No idea, but your request for the logs is the correct next step.
  19. 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.
  20. Our team is working on it. The Linden-created auctions we've been running have uncovered a few minor issues and elicited a few requests from our Land team for improved (even over the old system) administration features. When those changes are done, we plan to enable Resident auction sales. Sorry, I try hard not to produce time estimates (it tempts fate), but rest assured that they're coming.
  21. I don't expect that we'll provide owner control for the conversion. Instead, we'll have some extended period (tbd) during which owners will be able to see both the old and new values are but all enforcement will remain only on the old values. We'll be monitoring closely how much content would be disrupted if/when we were to throw the switch to using the new values. At some point, with ample notice, we'll switch to enforcing on the newer more accurate values. This is not something you need to be concerned will sneak up on you; we'll be very public about it. We're making progress on developing better formulas and testing them; when we think we're close enough to where we'll end up, we'll document how the new formulas work, and hopefully provide tools in the viewer that will help you analyze costs.
  22. This one we're sort of working on; we are not going to abolish the "prim number" system, but we are evaluating ways to update the way that both Avatar Rendering Complexity and the "streaming" component of Land Impact are calculated ("streaming" isn't a very good name for it - it should be "rendering", and we'll probably change that name). Since any change to how we calculate these, especially LI, could be disruptive we are taking it very slowly and carefully. We'll have more on this as we get closer to rolling out the change, including better advice for content creators on how to optimize content. (the rest of your list is interesting too)
  23. Delete your viewer shortcut on the Start menu (or whatever shortcut you're using to start the viewer), and then either reinstall or recreate the shortcut from the new install.
  24. The most important things are: Clarity - think of your jira a persuasive essay you're turning in for an English class final exam. Assume that the reader knows nothing at all about Second Life (you'd be amazed how often I find out about some SL feature I'd never heard of because someone asks for a change related to it). Simplicity - part of Clarity, but worth calling out separately. Don't ask for more than one thing in one Jira unless they are absolutely inseparable. Create multiple Jiras when you've got a list of things you think would be good additions. Not only does it make it much easier to understand, it means that if we decide to Accept some part of it we've got the internal Jira ready to use. Value - explain why this makes Second Life better, especially how it make it possible to create more engaging content, attracts new users, keeps existing users, etc. It's also worth noting ... we often Accept jiras that have some good idea or that do a good job of explaining a problem, even if we don't think that the specific proposal for how to address the problem is exactly what we think we should do about it. And of course, everything in our large backlog of good ideas must compete for developer time and other resources; just because we Accept it doesn't mean it will get worked on soon (it might or might not depending on many factors).
  • Create New...