Jump to content

Pauline Darkfury

Resident
  • Posts

    241
  • Joined

  • Last visited

Everything posted by Pauline Darkfury

  1. Bill Woodland wrote: I hope this is in the right place but how do I add prim count to a parceled off peice of land...........................parceling off sections for vendors is what i am trying to do. Very short answer: you can't, the prim quota for a parcel is based on its size. Alternatively, if you are talking about how to make your rental system count prims correctly, contact the creator of the system for support. Having said that, all parcels in the same region that are owned by the same person or group share a common, region-wide pool of prims. So, if all the land is under the same ownership, per-parcel limits do not apply, only the combined limit based on the total area of land under that ownership in the region. There is one exception to that, the region's object bonus can adjust how many prims are allocated based on the size of parcels, but it's a region-wide setting which impacts all parcels, and the region's 15,000 limit still applies. The region object bonus is an estate setting which LL will not change on mainland, and most estates will not change unless the entire region is under the ownership of just 1 person (or group).
  2. Actually, for a fairly large number of regions, I am the judge for those things. They are banned across a very large number of regions that I'm involved with, and will be estate-returned if found. These spam-rezzing temp prim systems cause significant strain on the servers. Rezzing/derezzing prims and loading/unloading scripts are 4 of the most costly operations for the sim. These systems constantly stress those operations, and are extremely harmful when used on a large scale. They claim to offer "free" prims, but the reality is that those prims are extremely costly for the server and every AV within draw distance of them.
  3. One of the resource-stealing, server-abusing, lag-creating spam-temp-rezzing systems seems to have partly broken (sadly not in a good way). It now spam shouts base 64 encoded data on each rez (which since it's an abusive spam-rezzer, that's a lot of spam shouted).
  4. You just need to look at the land sales search and/or for sale parcels on the world map. You should be able to find a random 512 sq.m. parcel for L$512 or less (i.e. L$1/sq.m.). TP to the parcel buy it, that's all there is to it. Linden Homes are the only free parcels for Premium, in terms of obtaining the parcel itself. All normal mainland has to be purchased from someone (Gov Linden, in the case of abandonments).
  5. The airport needs a rez zone for people who actually want to use it as an airport. Griefing isn't harmless fun, you're dead wrong about that. You and everyone else there need to make a point of ARing the griefers for each and every incident.
  6. It's really a case of people expecting a bit too much from LL here, tbh. LL do provide a reasonably complete set of documentation between the KB & wiki. Their service does not include hand holding in terms of how to properly make best use of the virtual land they provide, and has never been sold as including that. If you need that sort of service, you shouldn't be going direct to LL for your land, but to one of the many established private estates or mainland rental companies. The level of service does vary with these 3rd party suppliers, but the best of them will be very glad to work with you and help you solve critical issues such as griefing type things.
  7. A technical solution preventing 16 sq.m. parcels being cut is not viable, as they are very necessary as a temporary measure when cutting odd-shaped parcels. People also need micro-parcels for some legitimate uses, such as creating rez-zones / unpacking areas, allowing members of a different group to set home, etc. What's needed is for LL to actually reliably enforce their existing policies, plus be a lot more ready to use the section of discretionary power to simply reclaim an obstructive micro-parcel that is causing significant harm to a holder of a much larger parcel. They also need to get tough with people who commit deliberate acts of vandalism by microcutting land as awkwardly as possible when abandoning, or those that buy perfectly good land, cut some micros out of it for ad space, then abandon the now vastly less useful parcel they cut.
  8. It's 100% manual once enabled. You get to pick which objects get returned because you return by right-clicking the troublesome object. If you're one of the nice landowners who tolerate the sort of situations described by Hugsy, as long as they are not actually bothering you, you need take no action, they will all still work as they do today. The change is that you'll be able to more or less instantly deal with the stuff which is a problem. If you're on a new enough viewer, the return option will un-grey for encroachment-returnable objects (if the feature is enabled in the region's config). It does seem like it's hopefully going to get enabled soon, as long as Patch and the other Concierge Lindens don't see any serious issues. Still no timescale for it, but Andrew seems to be supportive of it, and I'm going to keep nudging him gently about it.
  9. Yeah, that's a fair point about it being difficult to get support if you can't get to the website. Have you tried https://support.secondlife.com/ ? As for Verizon, it's def worth trying to see if that's a common factor with the people having problems.
  10. Ahh, ok, if you're having problems getting to the main secondlife.com website, you may well have some sort of network issue. It could be routing, could be a forced HTTP proxy at your ISP, could be DNS, could be something at LL — there's not enough information to accurately guess at that. You should def contact LL support, to see if they can find any problems for you, but probably also talk to your ISP's support, as the issue could well be in a stealth HTTP proxy on their network (a system which is supposed to transparently proxy and cache your HTTP requests, if they have such a thing).
  11. There's a few things to note / clear up here. Firstly, as long as you're able to resolve DNS names on the Internet, changing your DNS server should never influence the route of your packets to a particular IP address. That's not how IP routing works. DNS is used to resolve a hostname to an IP address. After that, you have no control over how the packets are routed once you pass them to your ISP, it's controlled by their internal routing tables, then the BGP peering between ISPs. Generally, the best results are likely to be achieved by using your ISP's DNS servers. You should only change your DNS servers if you actually understand how it works, or to attempt to fix a problem where you are unable to correctly resolve names to/from numeric IP addresses. The only way you can change the routing of your packets is to use a different ISP, or tunnel/proxy your connection via a server elsewhere on the Internet. As for the traceroute timing out, there's 2 forms of traceroute, UDP & ICMP. The timeouts you're seeing are most likely down to using UDP traceroute, and it's standard practice to block those at the edge of a non-public network (i.e. at the point where LL's private network connects to the public Internet). That's what you are seeing. If you were to use an ICMP traceroute, you would see the internal route through LL's network to the sim server (which should be neither a big deal nor a security risk, where the target is a public-facing server, such as the sim servers) The traceroute given in the first post od this thread tells me that your packets are getting to LL's network ok, so the problem is more likely to be with your viewer or an individual region server. The timeouts seen on hops 11 and 14 are not of great interest, it's not unusual for intermediate hops on a route to not respond to traceroute sometimes, plus there are bugs in some network stacks and routers which cause the packet TTLs to be handled incorrectly (causing a fake missing hop).
  12. Hmm, I'm sorry to say, but I think there's a horrible showstopper with region crossings & TPs between main channel & LeTigre after today's roll. I'm having a terrible failure rate with disconnects being caused, going between Virrat (main), Orivesi (LeTigre), and Smithers Bluff (main). All mainland Class 7s. Edit: Actually, a few hours later, I'm slightly less convinced it's LeTigre causing the issues, and maybe some sort of network occasional network issue inside LL. Not sure now, as it's not following any consistent rate or pattern. It really was dreadful flying or TPing between the sims above earlier, but seems to have calmed down now (/me hopes she's not speaking too soon…).
  13. Jo, it all depends on just what periods those numbers in your original post are averaged over. If the average used to calculate the overall % performance is over an hour, 45% is terrible. Those FPS & dilation numbers are terrible as well, but I'd guess that they are the instantanous readings, not an average. The point where you need to be worried is if you are seeing long and sustained periods of dilation below 0.90, and sim FPS below 40. Some people will tell you anything less than 1.00 & 45 is a problem, but frankly they are wrong. Spikes are expected behaviour when someone enters or leaves, and can easily drop both numbers right down for 5-10s, but that's not the primary thing to worry about. It's the sustained numbers when nobody is entering or leaving that are the big concern, so the long term averages on those. Your monitoring tool may or may not be giving you a good long term average, it just depends how it's been coded. It also depends on the sampling rate of the monitoring tool. If it doesn't sample the data often enough, the average will not be terribly accurate, as those numbers change fairly rapidly.
  14. No, Casper didn't buy Apez. He just offered a lifeline to merchants who were on the system, in terms of easy migration to his own vending system, with data import and so on.
  15. Marianne McCann wrote: that's highly surprising, and a bit disturbing. I agree entirely. I sincerely hope that it's not a sign that certain bits of LDPW content are going to be chopped, if they somehow don't meet particular criteria. That would be a really sad thing, as regarless of the traffic that any individually see, they all collectively are something that gives mainland some character and history. Some comment on the issue from either Michael or Guy would be much appreciated.
  16. You need to set the region to allow public access, and then turn public access off on a per-parcel basis (for the parcel(s) that are not intended to be public). It's expected behaviour that if you disable public access at the region level, that hits the entire region, regardless of parcel settings.
  17. Apez still owes me a small amount of money, and I'd frankly be rather surprised if it ddin't owe other people a rather large amount of money. The website for it is down now, has been for a while; store & sim got sold and the Apez stuff cleared from it last year; and the reputation is completely and utterly trashed. On top of that, the scripting is years overdue an update, with the highest script count and sctipt times of any vending system or rent box that I've seen. If it's not dead, it's been circling the drain for a rather long time now.
  18. This is almost certainly SVC-6905 / "immortal prims" (can't take/delete/return/die/temp-delete them). The underlying bug is fixed, but the fix has not yet been deployed to the full grid (hence the Jira status being "Fix Pending"). The fix is currently under test on BlueSteel, and should hopefully go grid wide sometime in the next week or 2. Please do not add more to the Jira unless you find a case where it's still happening on a BlueSteel region. The problem is caused by communications between the asset server and sim getting lost, so if there's significant issues with either you're more likely to encounter it. In the meantime, a region restart will reset the status of the objects, allowing you to attempt to return them again (but if the region or asset servers are still having issues, they can become stuck again). Wearing them does appear to mostly work, but I have seen cases where that has left an in-world copy of the object at 0,0,0, using prims on the SW corner parcel, so a restart is strongly recommended as the safest way to get rid of them.
  19. Luc Starsider wrote: … The radio is similar in a way. Someone on a parcel nearby have a radio stream playing, but have not set the parcel to keep sounds withing the parcel boundries. That is why you hear the radio even if you are not playing it yourself. Also in this case, your best bet is to find the parcel the radio is playing on, and see if the owner can change it so the sound stays within their parces. Don't know if a ticket can be filed for this. There's no such setting. Streaming audio is always solely for the current parcel and you don't hear it outside the parcel. The only sounds which cross parcel boundaries are object/gesture sounds, and that's what the "Restrict gesture and object sounds to parcel" setting does. It has no bearing on streaming audio whatsoever. The OP may, however, be hearing object sounds from an adjacent parcel, rather than streaming audio, and they can block those by turning on that restriction setting (it works both ways, stopping object & gesture sounds going both in and out of the parcel). LL won't ever adjust someone else's parcel options for you (if the parcel is owned by an account or group in good standing), so don't put a ticket in for that.
  20. 1.x viewers are not adding any delay to mesh whatsoever. 1.x viewers are not preventing the adoption of mesh by creators. Mesh is not yet here because it's not ready to be used on the main grid at present. Creators are not adopting it yet because the main grid does not support mesh. Saying that 1.x is delaying adoption of mesh or slowing LL's work on mesh is frankly just absurd and bordering on being pure FUD. Mesh will arrive when it's ready, and nobody should be wanting mesh to be deployed on the main grid before that point (does anyone reading this really want one of the largest changes to SL in years on the main grid before LL are extremely confident that the server code is ready?). The truth is that mesh will eventually provide a major incentive for people to finally upgrade from 1.x to 2.x (and hopefully at that point there will be stable 2.x viewers that actually have all of the important features that keep many of us using 1.x). 2.x is still missing some critical functionality that estate managers and landowners need and depend on. As it stands today, you could pay me to use a 2.x viewer, but I sincerely doubt that you could afford to do so!
  21. Alexi Raynier wrote: … It would be even more welcome if we were given more time between restart… … I really could not agree less with that. The weekly restarts have vastly improved performance grid-wide, as the memory leaks in the server can no longer build up to the point where they cause chronic lag in busy regions (and for all other regions sharing the same server as busy regions). Additionally, the weekly upgrades are allowing much smaller changes than was previously possible, allowing much easier identification of where new issues are coming from and allowing old bugs to be tackled on an incremental basis. In the past when we had a month or more between major upgrades, the 1.x.0 release frequently caused far larger problems which were much harder for LL to narrow down to the specific change which caused the issue. We absolutely must keep moving forwards and tackling old bugs and much wished for changes at the current rate. Any form of slowdown on that would cause far more longer term damage to SL than the disruption of a weekly upgrade restart (which is now vastly quicker than it used to be, with regions often only offline for around 10 minutes, compared to 30-60 minutes a year ago). Keep up the good work, Oskar, and whatever you do, please stick to the weekly version rolls, it's a clear order of magnitude better than the previous mega-update system.
  22. I think that "fixing" SVC-6573 (Block execution of ungrouped scripts on ungrouped land that blocks scripts.) is an incredibly bad idea and an absurd waste of precious development time on something that's frankly a non-issue. It introduces risk and disruption for what appears to be zero benefit or justification. If someone wants to set no-scripts on an ungrouped parcel, they can already do that just fine by turning off both options. Changing this is going to break existing content in subtle and non-obvious ways, and there's precisely zero resident support recorded in Jira for the change in behaviour.
  23. Hi Maestro, thanks :-) In that case, I'll gladly repeat my tests once the dust has settled on this week's LeTigre roll and post the findings in the Mono 2 forum/thread.
  24. Thanks, Oskar :-) Does this week's LeTigre have any changes which would make it worthwhile repeating the tests in http://community.secondlife.com/t5/mono2-performance/mono-2-performance/td-p/831617 to see if it's now better than 2-4x worse than previous performance for rez/derez lag?
  25. ArgontheDevil Ormega wrote: We don't pay tier to be good neighbors. We pay tier to enjoy our land. It would seem from one look at the sphere described by the OP that it could not be moved as it would overlap everyone around it. So talking to the person would not make much sense, would it? And someone who is going to put a house over a sandbox is not interesting in being any kind of neighbor. On the other hand, my sandbox owner neighbor is a very good person and he immediately acted to remove an offending object as soon as I wrote him which makes me very happy for two reasons. First it means I have a good neighbor. Second, I have a sandbox next door to build on. There's every reason to talk to the person. Although the OP didn't have any rights to have the sphere there, the neighbour's action was the sort of thing to severely damage any future cooperation. On this occasion, the neighbour had rights on their side, but later on the boot could easily be on the other foot. If your neighbour communicated with you solely by dumping visual blight when something was bugging them, would you be more inclined to help them if they later needed your assistance, or more inclined not to bother? You sound like you're both normally a good neighbour and have a good neighbour, if there's an issue you talk to each other and work it out. Even although the OP really only had once choice, to remove the scenic sphere, if that was what the neighbour wanted, a little diplomacy goes a long way with these things, paving the way for future cooperation. When I manage to catch up with my neighbours, I always try to emphasise the willingness to communicate and cooperate about boundary issues or even random things to help them out. Want some help rezzing your house/trees/etc? Sure, happy to help you get it right. Need some space to temporarily rez something? Sure, use a spare corner of my land if I've got the prims free. Tree encroaching a little onto my land? Yeah well, no big deal as long as it's phantom and not blocking something, might need to talk about it again in the future, but go ahead and let it encroach a couple of m for now as long as the prims are counted on your land. Want me to make some small changes to my land that won't hurt me but will benefit you? Sure, let's figure out what will work for both of us.
×
×
  • Create New...