Jump to content

Jack Abraham

Resident
  • Posts

    262
  • Joined

  • Last visited

Everything posted by Jack Abraham

  1. Thanks for the update Oskar. I can certainly understand urgency around a permissions exploit. We'll hang on. Especially since llCastRay is coming at last!
  2. Aeysha, it appears those changes were on Magnum since 8/23, so they were at least being tested somewhere. The release notes seem to be a combination of the Magnum and Le Tigre prior releases. Still, double plus ungood. We are out of business until this is fixed.
  3. Oskar, when time permits and root cause is known, I'd be curious to know how SVC-7283 slipped into the main server without apparently being present on Le Tigre.
  4. Falcon gets his own channel? I'm holding my breath...
  5. Yay for physics improvements and 64m prims! . . . Now when do we get llCastRay?
  6. This is me, rejoicing much. Now, about llCastRay...
  7. Nyx; This is brain damaged. If implemented, Linden Lab will once again snatch defeat from the jaws of victory. You've managed to make mesh objects completely unattractive to me both as a creator and consumer, by making them cost more in prims than equivalent non-mesh objects, despite the non-mesh objects being more resource intensive. Brilliant.
  8. Alexi, we have asked for them. "We want less lag." "We want sim crossings to work." That's what Oskar's pushing out here. I tend to agree with you about search (and the effects that's had on the economy), display names, the children's invasion, etc., but that's not Oskar's turf. You're complaining about restarts, but I'm really not seeing the connection between the weekly restarts and the problems you're describing. The weekly restarts are a result of the fact that an statistically useless portion of SL activity occurs on the beta grid. They simply can't test very effectively without rolling things out to the main grid. Yes, that creates problems, but my perception of things has been that teleports are getting more reliable, sim crossings better, sim crashes less frequent, and scripting tools better at a steady pace. Oskar, Maestro, and their cohorts are very responsive to problems that they can fix.
  9. Mostly snarking at how sparse information has been in the past; seemed like the only thing appearing on the Jive flog was the weekly releases and gushing about Facebook. I do see it and have the forum bookmarked now.
  10. They not letting you blog releases any more Oskar? Must've been making the rest of the Lindens look bad by keeping us informed.
  11. Definitely needs an off option. While I assume it's great for photography and machima (I don't do either), it breaks immersion and is a nightmare for building. In RL my eyes adjust focus when I look at something different, so I'm unaware of any areas being out of focus unless I seek them. With default settings, I'm constantly aware that my avatar is out of focus.
  12. FJ, thanks for keeping us informed. Your willingness to be frank with us about problems, and give us a timeline, is welcome and refreshing.
  13. Once sidebar panels are undocked, they behave like any other floating window in the Viewer. Except close them and then reopen them as floaters still. So the sidebar still forces itself constantly into my view, asserting that it is more important than the world. The planar texturing is a great new feature and the Snowstorm team has steadily improved the viewer despite losing two more of its members. By this time next year it might be usable.
  14. Q, thanks for stepping into the arena and defending why you do what you do. I may not always agree, but I do respect that the positions are considered.
  15. Just to add one more voice to the cacaphony... One reason you're getting requests for options, Q, is that Lindens have made clear that changing the current default behavior is not something you're willing to entertain. We need an option to eliminate the sidebar because, it seems to us, when we say "eliminate the sidebar" you stick your fingers in your ears and go "la la la." When we say "the colors are too dark and give me eyestrain," or "this strobing gives me a headache," we're told that we must be wrong. Since the One True Interface has been found and anything we propose is received as inferior, we are forced to ask for the option to have things work for us, rather than having it work for us by default. If this is not how you want to be perceived, you're going to have to demonstrate, over time, that you are listening and willing to make fundamental changes in response to resident requirements. This is not something the Lindens have managed to do in my few years in Second Life. Indeed, the perception in my SL social circle is that Second Life succeeds despite Linden Lab, not because of it. We are used to seeing you as part of the problem, not as part of the solution. Snowstorm is changing that perception, at least for me. It's only a start, but a promising one. But until the major issues – chat focus, interface sprawl, and the infernal sidebar – your credibility is going to be slightly less than that of the Iraqi Information Minister. We've been burned too many times. There will be different use cases, and they will necessitate different options. When I'm scripting, I want every llDialog call to go through and I don't want to receive any IMs or group chat requests. When I'm in the public sandboxes, I want llDialog spam protection, and I want to receive IMs only from friends and certain groups. When I'm being sociable, I want IMs and group chat working at full speed – and I don't even want to see script errors. For the web, I'd use four or five different pieces of software for that, not one viewer. I personally use three different TPV viewers on a regular basis in part so that I can keep my options tweaked to the three different use cases I have. On the UI side of the problem, perhaps what's needed is a use case manager interface, with the actual choices less accessible (as a preference list or the current debug options), but the summary ("scripting", "clubbing", "patroling", plus "supported" for dealing with support) higher up. This does not address code complexity, of course.
  16. To each their own talents, Kwant. I can handle Mono vs. LSL, but I only wear one color.
×
×
  • Create New...