Skybox Security?

Yeah..well you just calculate at their current direction and speed (assuming you can scan them at least twice). If they are at the target altitude, you can warn them, if they are heading in vector towards the target and at the same direction you can warn them. Depends on how you want to handle it.

I understand it perfectly. Like everything else in this thread, it's a satire of landowner rights.

If you really gave a crap about SL aviation, you'd be voting for SVC-22 instead of trying to make fun of landowners.

That has nothing to do with sybox security and scanners. You're talking about region crossing. Besides, voting on an issue isn't going to change things. I'm talking about a resident solution to a problem that's not likely to change from the LL side.

And thanks for labeling me as not "really giving a crap about SL aviation"

Region crossings are a far bigger problem than security orbs.

Making a script heavy orb that scans huge amounts of space that no one ever flies through and the landowner isn't using is not going to benefit anyone.

Yeah, more scripts, that'll help!

Why don't you vote on VWR-11544 and help reduce the number of scripts necessary to do certain things in SL? Maybe that would help with lag and help, in turn, with border crossings?

Hank: You're not scanning any further.

The scanners are physical objects that are moving, thus they can cover the entire area as far as they are allowed to move by the land permissions system. There aren't that many, and they are tiny/invisible/temp-on-rez and moving pretty fast to sample the area they are moving...which is random. It's not perfect, but allows to you scan the entire area. It's not like a static orb in one position that can only scan a sphere of radius 96m. This is multiple objects flying out in all directions scanning their 96m every 0.5 seconds as they move.

When they scan an avatar, they llRegionSay back the key of the avatar, name, position, and other information...which could be trajectory and speed. The current test system doesn't do that, but I plan to implement that.

The server interprets the data, and decides on whether or not they are in a protected area. If so, they are sent a warning mesage and the amount of time they have to get out of the area specified (yes, I specify the area), with a default of 120 seconds. People can choose to be added to a list of people not to be notified if they are a neighbor that encroaches on the land frequently, but doesn't want to be notified. If the neighbor isn't actually over the land, they wouldn't get notified anyways.

If you have a typical parcel, say a 4096, that's only 64m across. You're only at best adding 32m to the 96m of the scan. That's derisory.

You're not solving any problem that needs to be solved with this wacky scheme of yours.

If your plot is only that big, the scanners would only go straight up instead of out. If it scans something that's not over your land, nothing is done with the information since they aren't over your land. I guess I could program it to vary the scan radius, though the extra calculations probably would negate the gains. I'll check into that.

The problem I'm trying to solve is two things...

1. Allowing skybox/land owners to know who is on their land.
2. Allowing flyers to get advanced notice of their encroaching upon "forbidden" land before it actually happens. Otherwise you arrive, get stuck, get sent home, lose vehicle, lose friends, etc.

Aviators don't care about objects thousands of meters away in a direction they aren't travelling and landowners don't care about aviators thousands of meters away from their buildings.

How is this idea of yours an improvement over the 96M radius of current security orbs?

Exactly; they don't care unless they are traveling towards an area where they'll get teleported home. That's the point. To get early warning that you are about to head into a "forbidden" area.

Because the distance of detection isn't enough until it's too late. What, you think you can get out of the area in 10 seconds when you have just run into an invisible skybox that hasn't rezzed yet, and you are now stuck? You are thinking....

Dang; if I had only known I would have avoided the area.

..or...

Dang; I hate these security orbs! Not enough time to get out!

I guess things could just stay the same.

Oh yes, that will not cause hideous lag.

So the only question is what category to put the AR in? Unfair usage of region resources or excessive spripted objects?

Then people wonder why the lindens are thinking of script limits.

Better than developing a griefer tool to harass pilots thousands of meters away from even being able to see the skybox your system is protecting.

The vast majority of aviators over the mainland are travelling along a horizontal plane, not a vertical one.

All your system does is make the radius covered larger so the jackasses who think a 0 second delay is a good idea can screw over more aviators.

Where do you get "griefer tool" and "harassing pilots thousands of meters away" from?

The device would only tell someone who was on a flightpath near the area. It wouldn't harass people thousands of meters away for no reason.

If they aren't traveling towards the protected area, then they would never know that the thing existed. If they were traveling towards the protected area, they would be notified so they could avoid the area. The only alternative is complete ignorance of the area until it's too late.

And thanks for not thinking I would enforce minimums so it wouldn't be a scanner that would be used for griefing. Geeze...you think I'm a newbie scripter?

Let's see, 5 scripts running at a time, doing a simple scan. Compare that to land bots teleporting in and out of sims to fill land barron's pocket books, land scanners flying all over the world doing the same, attachments with hundreds of scripts running to resize clothing. Do you even know what you are talking about?

I know how to script so it doesn't lag, thanks. Do you? Do you plow through all the scripts you make, taking the best knowledge from other people, trying to optimize every function and everything you do? Do you rez dozens of your objects and test sim performance before you release something? I do regular code reviews on my products to make sure they are working as efficiently as they could be.

No, I think you're a troll who has spent most of this thread ranting against landowners over nonexistant problems.

Oh, you are making it TOO easy!

Misunderstanding and saying what my system is without any knowledge of it is unfair and trollish IMHO. Misunderstanding what causes lag, what is appropriate use of scripting resoures, and knowing nothing of the code behind it is just ignorant. Thanks.

/me solves teh problem bi buyin' Hanks Griefer banner thingy, editin' teh script to ONLY look for Hank and sets it out on his lawn, happy in teh knowledge taht he dusn't hafta ban Hank, his own piece of crap will keep him far-far away!

Um, all who know physical objects lag the physics engine raise your hands ...

5 physical objects that aren't physically interacting with other objects are not going to lag the sim. Lag is when the simulator can't keep up with processing tasks within a reasonable time. You want to prevent lag? Try banning the land bot accounts that are going in and out of simulators instead of ranting against someone who is putting a very small and tiny script.

Gotta love ignorant mobs.

So it's actually got less range than scanning 96m in all directions for almost all potential users.

No, the range is increased vertically form 0m to 4096m, and 96m outward in the vector that the scanner is traveling (i.e. in the current form it is "shot" up at a random angle). It doesn't, however, do anything or say anything to people outside of the land owner's land or isn't going to intersect the protected area. Scanning is different from action.

All it is is an increase in scanning range (i.e. the entire plot both horizontally and vertically), with early warning, and enforced minimums on scanning rate and courtesy-time to leave the parcel. A win-win for both land owners and flyers.

Vertical range, as already explained, is irrelevant.

And misquoting me makes it irrelevant (notice how you cut off half my sentence to make your point)? You left out the bit of a 96m scan moving outwards, extending the horizontal range past 96m.

Move a 96m radius scanner 100m, you've now got a 196m scan. Move it 500m and now it's 596 meters.