Jump to content

Michi Lumin

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Michi Lumin

  • Rank
    Advanced Member
  1. Just got hit by this one today. NO WAY for me to revoke the assailant's permissions, since permissions cannot be revoked on a worn object. It's unbelievable that this is STILL an issue, and is still being ignored. The JIRA has been open and acknowledged for *8 YEARS*. This is a MAJOR issue where someone can PERMANENTLY take control of another's avatar with ZERO recourse. This needs to be fixed. I've had my account for 12 years and now I may have to abandon it due to this issue.
  2. Czari Zenovka wrote: Fourm life is such that I expect refutations/debates; however, let's keep it to topics I have actually addressed. Well, seeing as the original topic was about the "removal" of the "temporary texture" "feature", and that was a direct side effect of SSB/Sunshine, I think it's rather on topic. If your intent was to jog the discussion over to other features that you feel were unnecessary (yet feel took time from fixes), then that's an entire other ball of wax. The other thing is, LL is not monolithic. People will say things like, "Why are you adding shadows witho
  3. Czari Zenovka wrote: I agree with you on LL constantly adding more annoying things features, most of which I could do without and the majority of which always have to then be debugged. Server side baking (aka 'project sunshine') isn't a "feature". It's a paradigm shift in how textures are composited. And it is better, and it is the right way to do it. Yes, *coincidentally* and as a *side effect* some old ways of doing things do not function. But they are ways of doing things that, once again, LL never had on the radar in the first place. The old way: 1.Retrieve all texture layers
  4. LL didn't "take away temp uploads". It was an incidental loss of functionality that only existed in TPVs that was necessary to institute server side texture assemblage. Greater good, and all. Client side baking was a mess. Again for clarity: TPVs gave people temp uploads, as an unofficial feature, taking advantage of client side texture compositing. It was never meant to be supported, and was basically a hack-in involving the way the *client* (viewer) assembled textures. As Phil said above, the feature was never meant to be there in the first place. (Using TPVs' 'unofficial' features, it's s
  5. Knowing the current LL, probably the latter... I'm guessing that they saw that we noticed it, and expediently removed it. Historically, well -- at least in the 'later half' of SL's history so far - transparency (in LL's opinion) hasn't been a "good thing" to the Lab. Not something they want to foster. I'm not sure why this is, because it leaves the resident body to form a lot of opinions through pure conjecture, which can't help the customer-to-service climate. A little transparency would remove a lot of resident populace uneasiness, and bolster confidence. (Really, LL; A little tiny bit wo
  6. Same happening to me for 7 months now... Does not seem that a fix is coming any time soon...
  7. Ok, so I'm not the only one. We were told to file a JIRA by support, which was recently closed as a "duplicate", but the 'original' of the duplicate is marked as 'inactive' and hasn't been updated much since October of 2010. I'm a bit concerned about back-billing on this as well; at this point it would be L$41958, or around USD $170. I'm not sure if the listing enhancements are still active, though, as I've never seen the enhancements actually appear. It's just frustrating to me that LL can't at least give a small status update such as "Yes, we know, and we're still working on it" - ins
  8. Since July, I've had "Charging, cannot edit right now" for 6 of our products with 'listing enhancements'. The forum post about this says to contact support, but when I do contact support, they say there is nothing they can do, and to file a JIRA. When I do file a JIRA, it gets closed as a duplicate of an existing JIRA that hasn't been touched for months. The last update on this was October 8... So these listings have been stuck in this state for 6 months now (half a year) and the last word I've seen was from October 8 (2 months ago.) Is anyone else still having this problem with lis
  9. December 13. Here we are, 6 months in since this problem began in July. The last 'movement' on this issue was 2 months ago, October 8. I understand things taking a while but this is a bit ridiculous. And I understand that our merchant account may be an 'exception' but there is no way whatsoever to bring attention to this issue or have it manually resolved. Messages to Commerce Linden have gone ignored; JIRAs are getting closed and support tickets are closed. But this is still a very real continuing problem that probably would take a DBA a few minutes to fix; whether it's removing or changin
  10. This is getting just a -little- ridiculous at this point... Six listings, stuck in "Charging, cannot edit.." -- *two months* even after acknowledgement of the problem. Can somebody, anybody, on the LL side tell me if this is even still being actively worked on? Or are these listings just simply going to be stuck in this state forever? Do we need to remove, and remake the listings on our end? Would this even fix it? Support keeps telling me its a "dev issue that is known and being worked on." That's been -- a long time. It appears that some of our listings have been 'stuck' this way si
  11. Just to clarify: I work with Eltee Statosky (Luskwood Creatures) who previously mentioned that as of Nov. 5 (and now Nov. 6) - that yes we still have 6 "stuck listings" and this means "Charging, cannot edit.." I did try contacting Support, and they said they couldn't do anything abut the issue. (I'm *not* trying to be cynical, but outright, it seems that Support's task is only to tell residents where the knowledge base is, or to say no. It appears that there's very little if anything they can actually resolve -- mostly by policy.) It's a little tough to swallow.. When a group or online
  12. They were defaulted to be unchecked in some builds... I know it's gone back and forth. I know some folks in the render department prefer masking vs blending because it simplifies lighting. Personally I'm not a fan of it because it does break content; so whether that's going to land on enabled or disabled by default is still up in the air. I do know on some previous builds the default has been to -disable- the auto masks and use blending. It seems to me that now, after some other bug fixes with lighting, even with deferred (Shadows) enabled, lighting falloff matches on alpha objects, so it'
  13. Aha! Auto Alpha masks. You can change this back to the old behavior To get this looking back how it did: Turn on the Advanced menu with Ctrl-Alt-D Turn on the Develop menu with Ctrl-Alt-Q Develop -> Rendering; UNCHECK "Automatic Alpha Masks (deferred)" and "Automatic Alpha Masks (non-deferred)". (Make sure both are unchecked.)
  14. Agreed- the JIRA has essentially become a knowledge base over the years. Getting rid of that functionality is absolutely removing a resource from SL. Additionally, due to the fact that bug regression seems to be somewhat common in SL viewer builds (there is after all a lot of disparate merging going on - i'm not faulting LL for that; regression happens in most dev environments from time to time), referring to previously fixed issues really has in the past, short circuited the need to start from scratch. It's another form of duplicated effort, but a duplicate nonetheless. Innula Zenovka wrot
  15. To me it's not even the publicity and searchability that kills it. It's the inability to have a dialogue with the dev team and work towards an outcome. You know, "mutually beneficial". As in "Here's what I'm seeing" / "Can you clarify?" / "Yeah, here" / "Ok I see it now, try this fix" / "That worked for the most part but there's just this one thing that's still not working" / "Ok, try this one." / "Yup, that did it" (jira closed). Versus "My second-lifes doesnt work it is broek plz fix plox"... (spend next month praying for a release note.) But maybe that's just me. However you're right
  • Create New...