Jump to content

Gwyneth Llewelyn

  • Content Count

  • Joined

  • Last visited

Community Reputation

15 Good

About Gwyneth Llewelyn

  • Rank
    Advanced Member

Recent Profile Visitors

420 profile views
  1. The issue about 'we're not being paid to do LL's own marketing' (something that has been always discussed over and over again) reminded me of a current ad being ran by the German supermarket chain LIDL. Around here, they have recently launched a campaign under the slogan Nobody sells us like our customers — clearly pointing out that the best form of advertising a product or service is word-of-mouth (even though LIDL, naturally enough, uses all sorts of advertising, on both traditional and digital media). I find it amusing that a supermarket chain has no problem in engaging their customers
  2. Actually, that used to be the case... we'd have personal tutors (volunteers), and, over time, we'd become tutors for newbies. That system was stopped when it became clear that some unscrupulous tutors were just interested in having newbies in order to sell them their content (newbies used to come in to SL very rich and not really knowing how much things costed...) The idea has its merits; the problem is always the same: how to 'police' volunteers to make sure they behave according to a strict Code of Conduct?...
  3. In other words: you want something like Sansar Plus I don't disagree with you, Coffee. I believe you're right. The real issue with Sansar was that — for obvious reasons — it was impossible to upload one's SL avatar and inventory to Sansar and have it there. This will always be a thorn on LL's side: how to dramatically improve SL while keeping the same content around? (And, of course, within a reasonable budget — you shouldn't need to mortgage Amazon to get enough money to do such a project) Their first serious attempt at 'dramatic improvement' was, well, Sansar. But for that to work,
  4. I love to bump old threads just for the fun of it, so here I am again Sooo this thread started in 2019. Fun days. We had no idea what was happening under the hood. Sansar seemed to be a failure, but, alas, it was still around, and thus it was a potential 'escape' for people fans of virtual worlds and Linden Lab. If not, there were other alternatives, such as, say, Philip Rosedale's own High Fidelity. And Facebook's Horizon was... well, on the horizon. Oh, and of course, there was always OpenSim as a 'last chance'. It's two years later (or so), six months after the last post before mi
  5. Heh. They did this, ages ago: https://wiki.secondlife.com/wiki/Open_Grid_Public_Beta/Teleport_How_To It was done as a test project in 2008 and only worked from the SL Beta Grid. As you can see, you could not bring your own inventory to an OpenSimulator grid, and vice-versa. Torley (a Linden back then) did an amusing video trying out this feature: But you don't really need to worry. This was only a proof-of-concept project. Linden Lab never intended it to become a 'feature', just show that it was possible. They had had serious discussions back then if it would make any
  6. Small correction: OpenSimulator is 98% compatible with Second Life, and it uses the same viewer. You just cannot transfer any content from SL to any OpenSim grid (and aye, that includes L$). The main difference between both platforms is that most OpenSimulator-based grids may use slightly worse hardware and connectivity than Linden Lab, but there are some exceptions...
  7. I'm afraid that this is indeed the case... the lag is still there. There is, however, a difference. Super-performant computers successfully 'mask' the issue. Recently I've been somewhat 'forced' to give up my ancient hardware — it was impossible to do some of my academic work related to Second Life and the Open-Source-Platform-Not-To-Be-Mentioned-Here because of this issue on the Cocoa code. The new computer has such a huge performance that the chat lag is almost imperceptible. It's still there, for those — like me — who know what to look for, but I can imagine that the majority of people wil
  8. Monty, Thanks for the clarification. Not being a professional programmer, and unfamiliar with the viewer code (the last time I looked at it and managed to compile it was for 1.7.X.... eons ago ), I was relying on some rumour I heard that most of the CHUI code is rendered using the built-in web browser, fully integrated in the UI. I tried to track down the place where I had read that, but couldn't find it. This was what led me to believe that Internet Plugins might play a role in it: if CHUI launches somehow some of the browser code, then it might launch the associated plugins as well, and so
  9. Ha, I was too optimistic! 3.7.4 still has the issue. It's just that without any Internet Plugins, it takes much, much longer to appear. When it does, however, it's as bad as before — making chat, IM, group chat unusable. Relogging will somehow "reset" things, and even when logging back in to a busy text-chat area, it will give you more minutes of "normal" responsiveness... It's not fun relogging every 20 minutes or so, though.
  10. Update: under 3.7.4, eventually the issue appears again. It seems to be just a question of time. It takes much longer to appear, though. When it does, however, it's just as before — even without any Internet Plugins.
  11. @Freya thanks so much for your help! I followed all those links and apparently the issues are related to same class of problems, namely, some strange incompabilities between CHUI and some combinations of hardware/software. In fact, for almost a year, I was pretty much sure that the way CHUI renders text, using a different pipeline order, was causing the problem on older Apple hardware, which, as you so well mentioned, probably has older OpenGL implementations. So, my assumptions for all those months were that the problem would be "unfixable" — probably Apple's OpenGL on old Macs was reverting
  12. In my case, I had to track down where my browsers stored Internet Plugins (on the Mac, they're under ~/Library/Internet Plug-Ins and /System/Library/Internet Plug-Ins) and delete them. The hint I had was that I still had the Kitely plugin installed, but Kitely has abandoned it, claiming that it had serious problems with the "new way SL viewers do log in". It just happens that this "new way" was introduced at the same time that CHUI became incorporated into the viewer code. I'm not putting the blame on Kitely, it could be any other Internet Plugin interfering, but after suffering for almost a y
  13. If switching to compact view doesn't make a difference, try this: track down where your browsers store Internet Plugins (on the Mac, they're under ~/Library/Internet Plug-Ins and /System/Library/Internet Plug-Ins) and delete them. In my case that worked wonders!
  14. @Nalates — I had this on JIRA for many months now. Because most of that year the JIRA was closed, I couldn't get more people to test it out and report. Fortunately, the Firestorm JIRA was open, and I could post and comment there — as well as two dozens of others with the same issue. Whirly, who is active on both LL's and Firestorm's JIRA, kept the information flowing. Alexa Linden closed BUG-4423 as a duplicate of BUG-4121, but I have no access to that. I understand that only "new" bug reports are available to all users. I wished to add the following comment (which I posted on Firestorm's JIR
  • Create New...