Jump to content

Oz Linden

Lindens
  • Content Count

    264
  • Joined

  • Days Won

    1

Everything posted by Oz Linden

  1. https://community.secondlife.com/knowledgebase/english/how-to-report-a-bug-r224/Section_.3#Section__3_1
  2. Most likely your problem is actually something wrong with the connectivity between you and the servers (if you have a Windows or third party firewall active on your system that may be contributing). I suggest that the next time you experience a problem, save your viewer log file and contact Support to help diagnose the problem.
  3. The latter ... that last component is an identifier produced by our build system
  4. I'm not in Support, so whatever I say must be taken with a grain of salt. My understanding is that the request must come from the region owner. I don't know how they handle mainland and other Linden-owned regions. We will continue to post release notes, and link to them from the About Second Life floater; you'll be able to tell what version you're on. If some behavior changes that's causing you a problem then Support will be able to move you off of it, but please file a bug report first so that we can fix it. Really, all we're doing so far is to hide the name of the RC; whether or not you're in an RC is not really hidden if you just click through to the release notes. It's just one part of a much larger effort to make our simulator evolution more stable. Right now, the RC channels are not very good models of the grid as a whole. Some recent problems got to main channel because they didn't happen (or didn't happen much) in the RCs, or weren't detected when they did. Other parts of this project include much better reporting on what's happening, including things we have not monitored closely before. We're also developing ways of making the RCs more representative of the grid as a whole, but doing that will require being able to change their populations. Our objective is to find problems more quickly and reliably.
  5. We fully appreciate that predictable roll days are important, and that will continue to be a design constraint. Nothing is changing about when rolls happen for some time, and we'll provide ample notice and time for feedback when/if we make any change to that. For a region owner, all that is required to move on to or off of an RC (or any RC) is a support ticket. That will continue to be true. Sometimes being on an RC is more stable than on the main channel; when we're fixing bugs, that's certainly our objective. We're going to try to provide more useful information on what is changing in each new server release, but sometimes we just can't - for example, it wouldn't be a good idea for us to describe that we've disabled a particular griefing vector if it's only disabled on one RC.
  6. Customized stars was considered, and didn't make the cut this time around. It's still on my personal watch list, so maybe next time.
  7. That's true only for direct person to person voice calls. Any group/local/conference voice is anonymous because you are connected through a mixer.
  8. Nope, just dumb luck. When we have a viewer in a nearly-releasable state (in this case, that turned out to be a little optimistic), the last phase of the release process is to offer it as an upgrade to a cohort of randomly selected users. Second Life is so large and complex that it's just not possible for us to test as much as giving to real users will. Normally, once you're on a Release Candidate like this, you'll keep getting those updates, but by manually downloading the default release you removed yourself from the test. For details, see http://wiki.secondlife.com/wiki/Viewer_Integration_and_Release_Processes#Release_Candidate
  9. This is an optical illusion. The further away an object is, the less often the viewer runs its animations (to save trying to make what will be very small changes in distant objects). When animations loop, the updates can end up looking backwards for the same reason that a fan viewed with a strobe light will look like it's running in reverse at some strobe frequencies.
  10. The "flat inventory" problem is very simple... if you have too many items in a single folder, especially the (invisible) top level folder of your inventory, it will slow down login. An 'item' for this purpose is either a folder or something else (an object, a notecard, anything). If you have enough of those very large folders, it can slow down login so much that it times out and you can't log in (if it doesn't happen every time, you're probably right on the edge of too many). It's only one level deep that counts; if folder A has 50 items, one of which is folder B, and B has 12,000 items, those 12,000 are not added to the count for A. We've cautioned people about this many times. Our support team does have a tool that "unflattens" your inventory by creating new subfolders and sorting the items into the too-large folders into those subfolders. They can apply that tool to your next login if you report a problem and it looks as though it might help.
  11. Testing the appearance with any viewer other than the EEP RC viewer is not very meaningful, since only that viewer has the shader changes that accompany the new settings and capabilities. We appreciate that the rendering in this overlap period before the TPVs all have the same rendering pipeline as our viewer is frustrating, and regret having gotten into this situation; we (specifically I) thought that this overlap period would be very short, but it hasn't worked out that way. My apologies. We're working as hard as possible to get the EEP viewer into shape to promote to default, after which we expect that it will be quickly available in most TPVs.
  12. It allows downloads for optional upgrades to happen in the background so that you don't get prompted about the upgrade until the file is ready to be installed. More importantly, it is a 32bit application so that it can check whether or not your system is compatible with the 64bit viewer (a test that's not as simple as whether or not it can run 64bit apps, since some video systems are not supported in the 64bit Windows). By doing that test, it can ensure that no matter which build of the viewer you start with you end up installing one that should work on your system.
  13. When reporting a DNS problem, it is helpful if you describe what you were doing (opening a browser to the marketplace, logging in the viewer, ...), specifically where you are, if possible including what ISP you are connecting through. DNS is a global distributed system, with potentially many layers of caching between you and the systems that provide the information about our current names and addresses; some of those layers don't follow all the rules or are buggy enough that they are sometimes not in sync with us. Flushing your local cache may sometimes help, but won't help with the cache you probably have in your home router, the ones in your ISP, or any of the others that may be in the path. Debugging this can be very frustrating. There's a pretty good page on debugging DNS at https://www.a2hosting.com/kb/getting-started-guide/internet-and-networking/troubleshooting-dns-with-dig-and-nslookup As far as I can tell we didn't change anything last night involved with this, and right now I don't see major providers that have bad data.
  14. The inventory sync run begins at 06:00 SLT. Syncing your inventory is controlled by whether or not you have logged in to aditi in the previous day. So if you log in to aditi on Monday, then Tuesday morning any new agni inventory items should be copied to aditi.
  15. ... but note that Linden Lab does consider it a hack and not supported. We've already been through one round of data loss by users doing this when we improved the parameter validation; that could well happen again. The first law of software reliability: Use it the way the author intended.
  16. Bad effects on scripts may be relevant (or may be bugs in the scripts... hard to say), so it's fine to include it. Subsequent login attempts, regardless of where they are, are not part of the base problem we're most interested in right now.
  17. We are very interested in hearing about TP problems, but it will be far far more useful if you report all of the following: When it happened; this doesn't have to be exact - within a few minutes is plenty accurate. Tell us what time zone you're using (SLT is easiest for us) Where were you when you tried to TP? Where were you trying to go? (region names is all we normally need for start and end locations) If you ended up somewhere else, where was it? Were you disconnected or did you crash? If the viewer window disappears with no message, you crashed; if not, you were disconnected. What viewer were you using? (copy the information from Help > About Second Life) It's easiest for us if you report those in jira, but contrary to what some people think we do watch the forums. This issue is a very very high priority for us right now, so we really will use reports we get, but none of the above is enough for us to learn anything from. If what you want to do is just vent your frustration by all means go ahead, but if you'd like to contribute to solving the problem we need the information above.
  18. That is incorrect. The term 'process credit' means withdrawing your US Dollars (transferring them to PayPal, Skrill, or any other outside institution). Please see this thread for official clarifications.
  19. I have not tried to measure it, but it's not free.
  20. This is quite a bit more involved and expensive than it needs to be. You're essentially using the SHA1 value as an expensive index into a list; if both scripts have the same list of textures in the same order, just passing the index into the list is just as secure and much cheaper.
  21. What that message actually means is that the simulator has determined that messages from your viewer are frequently arriving out of order. Some out of order messages are expected and ok, but if it's happening too much it probably indicates a faulty network path between your viewer and the simulator. Because this can cause problems, certain messages are disabled when this is detected, which is why we suggest relogging somewhere else for a while. I have no idea why that would be related to landmarks or any other part of inventory, but it's possible ...
  22. Last I heard, we fixed that some time ago.
  23. There was a minor glitch in rolling out that change ... should be fixed now, but you may need to relog to see the correct number.
  24. What you're doing is essentially manually crashing the viewer; that can result in problems such as corrupted caches and failure to save settings changes. There's no need to wait for a fix; the link Whirly posted is the fix, and that viewer has no other changes compared to the current default viewer - it's as specific as can be.
  25. This would be far better to handle as a Support ticket or a Jira. In either of those, you could more comfortably have included the details we would need to investigate the problem (such as the names of the users that are not blocked but should be, and where you are seeing the incorrect status).
×
×
  • Create New...