Jump to content

arabellajones

Resident
  • Content Count

    154
  • Joined

  • Last visited

Community Reputation

31 Excellent

About arabellajones

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. The instructions for the Search (the box at the top of the page) look broken. I used two words, entered as "word1 word2" and the results clearly use the OR function, returning every entry containing either or both words. The suggestion to improve the search was "word1 AND word2", but that treated "AND" as just another word, not as a logic function. Google did return a few relevant results to the same basic search string, but may have stopped indexing the forums last year. I did try digging for a JIRA on this, but I only read and write English
  2. For me, all the viewers have a problem with not picking up on the OS defaults I set, such as font and mouse pointer size. I also struggle with some colour schemes, which Firestorm handles well, the SL viewer doesn't. Yes, there is an add-on for the SL viewer, but I've had it broken by a viewer upgrade. The basic colour scheme is pretty poor. I struggle with the JIRA systems that Linden Lab and the Firestorm team use. I am not convinced it is a viable bug-reporting tool, however good it might be as a tool for planning the work being done. I end up feeling that I need an exorcist more than I need a programmer.
  3. This is something I have been watching with my system for the past few days. I have a program that displays the readings for various temperature sensors. I'm running Linux, so the specifics won't be much help. What I do see is the video card temperature rising, so dropping back the video settings could help. It depends on the video hardware, but the Advanced Lighting Model setting can be more efficient. Firestorm can also limit the frame rate, which will help a little. (There are some jobs I would not try running in the current weather.)
  4. It is still lousy documentation. It needs improving.
  5. A Project Viewer for Estate Access Management came out in August 2018. There were a few mentions of it then, but I've not found any definite source for when it merged into the main SL viewer. I assume it must have, because now it's part of the latest Firestorm Viewer. The only thing I can find which might pass as documentation is a pair of article in Inara Pey's blog, which assume everyone knows what an Estate Manager is. I eventually found this old web page on the SL Wiki: https://wiki.secondlife.com/wiki/Estate_Manager I am not an estate manager. I can ban people from the parcel I control. I can see how being able to get at least some of the info, such as a banned resident's last-logged-in date can be useful to me. But I am not an estate manager. I reckon, with the Firestorm-led hype, that it's time to update that web-page to cover the EAM features, making it clear who can, and cannot, use them. In the past, extensions to section-A through feature-B have suffered from only having B->A links provided, so that a search which finds section-A doesn't have a chance of revealing feature-B. I think one web-page, covering Estate Managers and the current tools, is enough
  6. What has started me off is the lousy optimization to the Mole-attributed items of the SL16B freebie outfits, up to five 1024-size textures for a pair of shoes, with two of those textures for the inside of the shoes, not visible while they are worn. It might be the poor mole was only responsible for loading the versions distributed, but somebody at the lab signed off on this crap, and they couldn't even be arsed to upload a smaller version of the usually invisible textures. This solution depends on finding somebody competent. I doubt I would be up to the job, but on the evidence I don't think a Linden would recognise competence if it sat on their face!
  7. It might not be the ideal solution, maybe a last-resort one to do with support guidance, but the relevant setting is likely to be in one of the preferences files which can be edited while the viewer isn't running. Looks like it's in user_settings/settings.xml and search the file for "TextureMemory". Either I am in totally the wrong place, or setting the value to 512 would fix it. Is it really that simple to fix?
  8. I can just remember a few things that RLV made possible which were replaced by other viewer functions. One was a system of photographic filters which now seem to be handled by Windlight. And, as long as everybody involved is having fun, RLV does have a place in sexual roleplay. I can think of things I would agree to do. There are a few things I can think of where RLV can usefully automate something, but somebody could do the same thing manually. What I would run away from, very very fast, would be the sort of guy who can't ask, who can't communicate, and thinks RLV is all that's needed. It's like the AFK places I see. What's the point? The big feature of SL is being able to communicate with other players. If you don't want to do that, why not download a porn video?
  9. I know the place where this happened, but as long as there is nothing more than that automated acknowledgement of an AR, I am not sure that anyone can be sure whether the Lindens do anything. I can think of a couple of places where these creeps could have been standing, outside of Nor's area of control, where they would be able to harass new residents directed to info and teaching facilities. There needs to be some attention paid to 24/7 support cover, because Second Life is global. There are some long gaps, and the daily variations are, very roughly, 28k users to 45k. I'm not sure how you could pick out events such as this from the AR stream to direct to an overnight team, but just waiting for normal office hours starts to seem reckless. I hope the Lindens can do better than that on the computer security side, because they're holding my personal data (and just shoving the responsibility over to Tilia doesn't change the timing problem). I'm in Europe. Does Linden Lab (and it's subsidiaries) want to be in the same legal mess over European data as Google and Facebook?
  10. There are many websites that have been reporting basic stats, such as concurrency, for all the time I have been using SL. But all of them seem to have stopped getting updates at various times over the last couple of months, most recently https://eregion.kicks-ass.net/munin/servers/akari.eregion.home/SL_Online_Now.html which stopped updating on Tuesday. It's less clear when https://e*****up.com/slstats/concurrency/ stopped getting data, but it seems to have been a couple of weeks ago. Point is, it's not all at the same time, so it's unlikely to be some change to the API. And Firestorm is still reporting a changing concurrency figure. These charts did give some sign of connection problems, you could see if there was a sudden drop in numbers, when it had happened, and whether it was continuing. And, unlike a web page from Linden Lab, it didn't vanish when somebody plugged in a vacuum cleaner. A wild guess, but I know some sites watch out for repeated requests from the same IP address, and block automated requests when they exceed a limit. The requests made by the Firestorm viewer don't all come from the same IP address, so that sort of filtering would fit what I see. Add a bit of security by obscurity to the thinking. It doesn't help that I am using Linux: there's not much chance of getting a straight answer from Linden Lab. Also, I'm in Europe, and I am usually tucked up in bed when those in-world meetings with the Lindens happen. So somebody else is going to have to ask.
  11. The viewer colour scheme, and there is no supported alternative, is pretty horrible. Yes, there is Starlight, but the default colour settings make me struggle to read anything, and no viewer seems able to pick up the OS setting for the mouse cursor. This is not good UI design, and my eyes are old enough to notice this sort of thing. So the viewer is efficient, but is that enough to make it good?
  12. This is one of the tricky settings. What I am seeing my viewer built-in Help telling me is that this only affects UDP traffic, which has been shrinking for years. Stuff such as textures have been shifted to http. Just that is a huge difference. There are recommendations for the setting, based on the type of connection, and they haven't changed since the days when everything was UDP. That does make me wonder if I can trust the advice. If the UDP traffic has been halved, it wouldn't surprise me if the minimum recommendation hadn't dropped that much, but no change at all just doesn't make sense. This is one of those things where any definite answer is likely to be wrong for you. All you can do is try. That 1500 setting is the absolute maximum setting recommended, labelled as "cable", and all I know is that I can't get "cable". That tech used to be high-speed co-axial, and my current DSL is faster than some "cable" tech that was being used a decade ago. And using the Wi-Fi label, the standards for that have changed too, it can be much faster, but the number of wi-fi systems I see as I walk along the street with my smartphone, all from router/modems using the same out-of-the-box default channel, I have a feeling that anyone using wi-fi, for anything, needs to do some serious thinking about how it is set up. I think I would stick with the Wi-Fi label because of the bandwidth sharing with your neighbours, a totally different class of problem, but "DSL" and "cable" are looking antiquated as labels I would say you have to try different Connection settings. You might even get better results down at 250 or 300, but I would try 1500, 1000, and 500. There's no point in going higher, there just isn't going to be that much UDP traffic now. And Second Life is rather unusual in how it shares UDP and HTTP. Keep an eye on packet-loss rates.
  13. As you understand it, but why can't they make it clear? The inactive account thing looks to include just logging on as activity. I'm not 100% clear whether that includes logging in to Second Life, Sansar, or whatever else Tilia might provide these services for. I remember some of the past problems there were, with even just buying a few L$, for people outside the USA. The US financial industry seems so primitive, compared to the rest of the world.
  14. The computer I am currently using is about ten years old, with a much more recent graphics card. The old nVidia 750 I used was pretty slow, but OK for standing around at an event. The replacement I got makes other things more comfortable. Computers which are that old can fail for all sorts of reasons. I don't think I am using anything super-powerful. And I am trying, when I make stuff, not to waste the computer power my audience might have. I have seen a fancy dress with an ARC of over 1 million. I did look, once. It did did nasty things to the frame rate that old 750 was giving me.
  15. When I look at some of the behaviour of non-rigged mesh in SL, I do wonder how many creators know what they're doing.. You can make vehicle wheels which don't collapse into lumps of triangles as you move to the side of the road: I've done it. ARC is used by the Max Complexity limit in graphics settings. You know, the Jelly Dolls. It's a poorly implemented pieced of UI and to see anything over about 350k complexity you have to switch off the limit. That's risky, because of griefers with graphics bombs. As far as I can tell, the LOD switching is badly calculated for rigged mesh, making the Medium->Low and Low->Lowest switching mostly irrelevant, because of Draw Distance settings. but it still seems to happen, and the ARC calculation gives plausible answers. We have confusing documentation (and I have ranted about that) but I don't see any signs of things not working as documented. Could things be done better? Yes, but I am not confident that some of the big name, high sales, creators could optimise their way out of a soggy wet paper bag. Rather than learn just how to do their job, they start screaming "It's a bug!", and go on to do nothing. And you know what started me off on this: people using 1024-size textures with pointless alpha channels. Let me check, rez the original version of this pair of shoes, so it does't invoke the rigged-mesh bug excuse: 6264 display weight. Used reduced size textures, without the alpha channels, and I get a display weight of 2998. The LOD switching distances shown by the Firestorm editor look right for a mesh object of that size. Let's try the Inspect right-click... 1024-size textures with alpha channels: 12,288 KB VRAM Reduced-size textures with no alpha channels: 1,536 KB VRAM Yep, it's an insanely high triangle count as well, but textures are so easy to re-scale, and it looks like these people don't even bother to try. The Download/Streaming weight reported doesn't change, which is a bit odd.
×
×
  • Create New...