Jump to content

Oz Linden

Lindens
  • Content Count

    258
  • Joined

  • Days Won

    1

Everything posted by Oz Linden

  1. You would also need to add *.lindenlab.com, since many backend services use names in that domain
  2. Thanks for taking the time to pull your questions together, Cummere. I know a number of others have had similar questions, and I wanted to take a minute to address them here. I hope this will help clarify things. 1) What is meant by shared experience? Making a simple statement that covers all possible cases is not easy ... there is an unavoidable element of judgement in interpreting this rule; I'll try to answer below, but that should not be taken as modifying the policy itself. We will certainly help developers with proposals to understand whether or not a feature might fall under it. It's worth noting that the vast majority of all changes made by third party viewers have certainly not been a problem. The fact that there have been some problems in the past motivated our adding this rule so that in the future developers would work closely with us to prevent any more like them. A shared experience change is one that modifies the definition of the elements that make up the virtual world, or how they behave, in such a way that users on other viewers don’t experience the same virtual reality. This rule does not affect changes to rendering, user interface, or the controls a viewer offers for interacting with the world. 2) What counts as the latest released Linden Lab viewer? Do the Snowstorm and Beta viewers count as released? The Release viewer is the benchmark, but the difference in time is normally quite small (a few weeks). If the relative release schedules of our viewer and that of some TPV are causing a problem, then we will discuss making allowances for that if the stability of the feature makes that a reasonable thing to do. The whole point of the Development and Beta viewer builds is to test things - which implies that those tests may reveal the need to modify the feature, potentially including changes that would not be compatible with the earlier version, so the likelihood of this kind of problem would have to be taken into consideration. 3) Does this mean systems like RLV and integrated AO's are no longer allowed? No. 4) Does this mean that third party viewers may no longer experiment with and help test new features? No - if the feature would fall under the 2.k rule, then it is faster and easier for everyone if the primary development and testing of it be done based on the common upstream code we make available to everyone, but parallel work by developers in test versions (not the default downloads) of TPVs will usually be ok as long as everyone (including the users of those test viewers) understands that the feature may change in incompatible ways, or even in an extreme case be withdrawn (such as if it is found to be harmful in some unresolvable way). 5) Does this mean that text only viewers or "voice only" viewers would no longer be allowed? No - failing to provide a common feature is not the same as adding a new feature. Users who choose to use such viewers are making a choice that is up to them.
  3. We run this contest on an ongoing basis, but entries are not limited to those intended for new users. The primary prize is that the idea gets used in the viewer. My feeling is that is enough for most creative people, but if I'm wrong, I'm interested to hear about what else might work. http://wiki.secondlife.com/wiki/User:Oz_Linden
  4. It sounds like a better comparison would be to set the driver to maximum on Windows...
  5. This has been fixed in 3.2.5, for which a Beta version is available.
  6. You're running Beta viewers, which are intentionally updated more frequently and can be less stable. Run the Release viewer
  7. There are many ways to make an object rotate with a script... can you be more specific?
  8. That message was unfortunately not constructed well, and steps have been taken to make sure that misleading phrasing is not used in future messages. Let me be clear: There has been no change in the Policy on Third Party Viewers or the Terms of Service. It is ok to connect to Second Life with any viewer that complies with the Policy on Third Party Viewers, even if that viewer is not in the Third Party Viewer Directory. I will not comment on whether or not any particular enforcement action was justified, and suggest that public forums are not the best place to discuss individual cases. If you believe that your account was improperly affected, the process you should follow is here: http://bit.ly/hBIjz 
  9. The real answer is that while we have some theories about that, we're not yet sure. There are a number of things that might be going on in the equipment between the system that you're running the viewer on and our servers - your home router and/or modem included. Some of what we are doing may be putting more load on them than they can handle, or otherwise tickling bugs in them. We're researching these problems.
  10. I must have misunderstood your question before, but what you are describing is the intended functionality.... The entries in the Sun menus are shortcuts to the Second Life default settings for those four fixed skys - they are not controls to change the time of day in the region. If you want to manually switch between fixed skys that you have in your presets, then you must use the World>Environment Editor>Environment Settings dialog. Sorry for the misunderstanding.
  11. Create a Sky preset for each of your key times (9, 12, 3); save each of those settings with its own name (my-9, my-12, my-3). Create a Day Cycle preset. In that preset, insert a marker at each of those times and set each marker to the appropriate sky preset. Save that Day Cycle preset with its own name (my-day). Open the Environment editor, select 'Use Custom Settings', and select your saved day (my-day).
  12. The 'time' in the SL 4-hour day can be read in LSL with llGetSunDirection. Making this at least approximately agree with the sun position in the SL sky can be done in the new environment settings controls: the sun position in a sky setting is set using a time of day, so if that position matches the time in the day cycle that the setting is used, the time and the sun will be in rough agreement. These new controls can be used now in the Windlight Region Settings Project Viewer and will be in the 2.8.0 Beta
  13. You can now download a Project Viewer that allows you to set the Environment Settings for your regions, and any user entering the region will see the settings you set (for now, only if they are also running the project viewer). We've revamped the interface for editing environment settings as part of this feature, and are looking for your feedback on it here. See http://community.secondlife.com/t5/Land/This-Project-Viewer-Lets-Landowners-Control-Environment-Settings/ba-p/925883
  14. If it is that Mac problem (you didn't say whether or not you were on a Mac), we believe it is fixed in the current Beta viewer; try that...
  15. prim attachments won't move, but a tattoo layer will...
  16. https://jira.secondlife.com/browse/STORM-1100 tracks making a bunch of updates to the GPU recognition in the viewer.  Many thanks to the several people who have been checking and contributing updated entries. A test viewer for this issue can be download from the wiki at https://wiki.secondlife.com/wiki/Downloading_test_builds#Developer_Builds Note: this is a developer test viewer; it may well not be as stable as released viewers.  It will not automatically update the way released viewers do. If you have been having trouble with your GPU being recognized or you believe it has been incorrectly classified, then please download that viewer and report by adding a comment STORM-1100 You can find relevant log entries in your SecondLife.log file by searching for 'GPU'.
  17. Known problem for which we have a fix - it will be in the next update. https://jira.secondlife.com/browse/SH-1319
  18. It's unlikely that anyone can help unless you provide quite a bit more information. For example, you didn't say what viewer you're running or what version it is, where you were or what you were doing when you crash, etc. A better place to report problems like this is the Jira, but read the advice on how to report a bug https://wiki.secondlife.com/wiki/Issue_tracker and make sure that you attach the log files (there's a link there to how to find them).
  19. This is not the right place to report a crash. Go follow the steps at https://wiki.secondlife.com/wiki/Bug_Tracker#Steps_to_create_a_good_report Make sure you attach a log file to your report (there is a link there for how to find it on your system).
  20. The same goes with Viewer 2, but Linden Lab insists on this being the standard Viewer, and probably the mandatory one in a short time. Let me say this as clearly and succinctly as possible: Linden Lab has no plans to make any single viewer (2 or any other) mandatory. We don't have any plans to make any such plans.
  21. What's really scary about this thread not only for Second Life but real life is that two major coder Lindens, Oz and Yoz, have come on to soothingly explain why we can't have democracy, citing the usual code-constrained geek arguments. Suddenly, you come up with this idea that "the votes aren't democractic enough and don't include enough of the user base" to claim that as your reason for making less democracy. We didn't say that we removed them because they were not democratic - we said that we removed them because having them was not useful. I note that in the poll you posted on the subject, you gave 6 possilble answers rather than just "yes" or "abstain". Those are the two choices one has with Jira voting. It isn't surprising to me that you chose to offer more granularity than that - it makes the results more interesting and useful. In any event, who said that product decisions about Second Life should be democratic? Democrocy is fine in its place - I'm a huge fan of New England Town Meeting style government for small civic groups, for example, but that doesn't mean that it's the only way to make decisions, or that it's the best way in every circumstance. Linden Lab has many stakeholders to consider in each of its product decisions, emphatically including our customers; but even our customers don't all have the same interests, and there are other stakeholders and many considerations in any product decision. We have to listen to as many perspectives as we can (which is what this entire initiative is about), gather the wisest heads we can find, and make the best decision we can think of. Being human, we will on occasion not make a perfect decision the first time, so we'll have to keep on listening and sometimes revise our thinking. It helps that process if those giving us feedback can be more nuanced than a yes/abstain bit. It also helps if they discuss the actual issue in a civil and constructive way rather than competing to see who can come up with the most insidious interpretation of our motives, or the most colorful flame. We're making an effort to improve how we listen in hopes that you, our customers and our fellow Second Life residents, will engage in a positive way.
  22. One thing I've been meaning to ask / suggest regarding User Groups: It would be great if we had an easy way to submit agenda suggestions for particular User Groups. I know that this can often be achieved at the meeting itself (i.e. suggesting an agenda at the end for the next meeting). However, why waste time putting together an agenda at the meeting itself if agenda items could be pulled together in advance? Most of the user groups do have a way for you to do that ... if nothing else, you can always contact the Linden responsible for the meeting. For example, my twice-weekly Open Development User Group agenda is on a wiki page you can edit.
  23. Why doesn't Linden Labs pay attention to JIRA voting currently? Why is removing our ability to vote the solution that was chosen? Will we be able to shut off the spammy emails that "watching" a JIRA issue entails? I believe that you really are sincere about trying to improve communication. Thanks for giving us the benefit of the doubt on that... :-) It is perhaps slightly overstating things to say that we don't pay attention; we have certainly looked at the vote numbers on issues and at least some of the time taken them into consideration, but there are many factors that make Jira vote counts a poor quality measure of broad customer sentiment. After all, consider that several hundred votes is a high number as jira votes go, but miniscule compared to almost any subset of the customer base you choose. Combine that with the lack of negative votes, and you're left with a mechanism for making real-world business tradeoffs that's essentially a yes-or-abstain input - we probably would not serve our customers well by making it a dominant factor. We didn't want to develop a new solution... we'd rather focus on making Second Life better than on making Jira better, so we decided to choose from the alternatives it already has. Yes, using Watch gets you emails from all the people who write comments, and some of those comments will probably be pretty low value flames. Some will also be updates on what is happening with the issue. Jira does not have a separate control for turning those off (see previous comment about not spending our time working on Jira). I hope that people will recognize how little value those have and reduce how often they are posted, but we'll see. We will be reading them (whatever you may think, we've been reading them right along). I've got a pretty long watch list, myself. My own feeling is that the fact that watching means signing up for the emails will cause people (as someone noted earlier) to make a concious choice to only watch the ones that they think really matter one way or the other. That means that we Lindens can treat the number of watchers as a better guage of how much people care than we ever could with votes.
×
×
  • Create New...