I just had an idea, what if the land tools considered the position of large mass of prims?
Say...
You set your land to No-Access, you have a build at the bottom of the property, and a sky box at the top.
The Land automaticly calculates the total mass and grouping of prims, if the mass x ammount == x, then around that grouping a No-Access zone goes around that mass of prims. The zone would span to say... 20 sqm in every direction of the mass, unless that would go over the lines of the property, in which case it ends there, except up and down of course.
This way, you could have a large mass sky box, surrounded by No-Access, but, small prims (say randomly strewn small cubes, or a small build) would not get a No-Access because their total mass is not enough.
This would also allow for planes to fly between a No-Access skybox above and a No-Access home on the ground. While still giving the owner security.
Thoughts on this?
Say...
You set your land to No-Access, you have a build at the bottom of the property, and a sky box at the top.
The Land automaticly calculates the total mass and grouping of prims, if the mass x ammount == x, then around that grouping a No-Access zone goes around that mass of prims. The zone would span to say... 20 sqm in every direction of the mass, unless that would go over the lines of the property, in which case it ends there, except up and down of course.
This way, you could have a large mass sky box, surrounded by No-Access, but, small prims (say randomly strewn small cubes, or a small build) would not get a No-Access because their total mass is not enough.
This would also allow for planes to fly between a No-Access skybox above and a No-Access home on the ground. While still giving the owner security.
Thoughts on this?
A problem could arise if you want just *land* to be private. So... in order to compensate for this, the default current hight-limited parameters would be maintained...
I.e. say you have a forest, with no prims in the air, but you want the forest, to remain private, you would set No-Entry normaly, the No-Entry would then act as it currently does since you have no mass of prims above the default height.
Anyone spot holes in this?