Jump to content

Willow Wilder

Resident
  • Content Count

    167
  • Joined

  • Last visited

Community Reputation

283 Excellent

4 Followers

About Willow Wilder

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I noticed a problem with projectors, but not in relation to the SL servers. It is viewer related, so I submitted a bug report on Thursday. See if this looks relevant https://jira.secondlife.com/browse/BUG-228038
  2. Yes, that's true; not viewer-specific. We've managed to get some viewer logs from Firestorm users, but it would be more helpful for LL to investigate the issue with users on the SL viewer and with SL viewer logs. Firestorm users are not always agreeable to such a test, particularly in a situation where it is not known the exact steps to reproduce something (which is the case with the link above). As far as I know, no one on our team is able to reproduce the L&F issue as it is often random, so that ties our hands somewhat in terms of offering support.
  3. There are more than a few people who would like to see the back end of this bug. It could use some attention. I can point you to this bug report which is a variation, but that won't really help you much https://jira.secondlife.com/browse/BUG-225557 Your own bug report submitted with logs from a session when this occurs would be my suggestion.
  4. According to this meeting, profile feed is not going to die https://modemworld.me/2019/11/16/2019-tpvd-meeting-week-46-summary/ As I mentioned, I was able to successfully share to feed using the Legacy Profiles Viewer. Oh, and thank you Oz.
  5. Support ticket is the way to go if you haven't logged into the beta grid recently. Submitting multiple tickets won't help. http://wiki.secondlife.com/wiki/Preview_Grid
  6. Thanks for checking that. Seems a fix has yet to be deployed. I've linked your post with the bug report noted above. This may have something to do with the Project Legacy Profiles viewer. I was able to successfully upload to profile feed using that viewer. https://releasenotes.secondlife.com/viewer/6.3.2.530836.html SL Share has already seen the end of Facebook. Flickr and Twitter are next. As far as I know, share to profile feed will continue.
  7. Consider that it is the profile feed. I've noticed a few other mentions of problems with the profile feed in the past couple of weeks, some of which have been reported on the bug tracker, including this one https://jira.secondlife.com/browse/BUG-227940 An easy test would be to download and install the official Second Life Viewer and try a quick share to feed. If it fails to post, then you know you can eliminate your new PC and the viewer as being the problem. https://secondlife.com/support/downloads/
  8. Reported this to Catznip. Try this page again https://get.catznip.com/downloads Downloads and Jira appear to be online atm. Other pages give a 502 bad gateway.
  9. That won't help because all fonts are not supported as noted on the bug report, and it appears those sites just throw them all together. Unless you can distinguish one font type from another, it will be hit and miss. You absolutely want to avoid Unicode font, but I couldn't say specifically what other font types.
  10. Not a good idea. Not quite. It will be gone within an hour. That's how long the server takes to decide to spit it back at you. The web profile takes longer to update. Firestorm has no control over display names or web profiles. See this bug report for an explanation https://jira.secondlife.com/browse/BUG-11555 along with related links.
  11. Some users have been known to get upset when you take their toys away (or otherwise change the behavior of features/options). It's true. You heard it here first. Also, way to go mom.
  12. Facebook was gone when Umeshu Maintenance was promoted to release back in early September. I haven't noticed any crying since then.
  13. To access the RC sandboxes, you just need to be a member of the Second Life Beta inworld group
  14. Yes, the post immediately before yours said file a BUG Jira:
×
×
  • Create New...