Extrude Ragu
As a content creator in a private region, I'd like to be able to exceed the 64meter object size build limit.
Whilst it is possible to split up meshes, it creates significant extra work in the content creation process, especially if like me you are trying to iterate on a large build, because you then need to join the model up and split it up again every time... plus all the lod models, position them all in-world, etc. Being able to upload and rez a large build directly speeds up the content creation process significantly.
I understand that builds were limited to 64 meters primarily due to griefing concerns on the mainland and sandbox regions. Therefor I propose to put this ability behind an estate setting, so that the 64m limit continues to be enforced on mainland or private regions where large builds are not desired.
I also understand there has been appetite for clientside skyboxes - I just want to say in my case I make large sim-sized floating islands that people stand on and npc's pathfind on, so whilst I think client side skyboxes are neat, it would not meet my needs I think.
## Proposed Implementation
### New estate setting
Allow Large Builds
- Can be set to
Estate Managers
,
Group
or
Everyone
Default: Estate Managers only
### New internal flag for inventory objects
Objects when taken to inventory will have a flag set on them that a simulator can check to determine if the object is a large build.
### Rezzing Behaviour
When a user attempts to rez an object, the simulator will check if the object is a large build from the aforementioned flag, and only rez the object if the rezzer has permission to rez it based on estate settings.
If the user is not allowed to rez the object, an error like
You are not allowed to rez large builds here
could be displayed.
### Mesh Uploader Behavior
The mesh uploader will no longer resize objects larger than >64m to be 64m, but will instead display a prominent warning that the object is a large build and may only be rezzed in certain regions.
### Script Behaviour
To avoid scoping the project to oblivion, scripts can continue to refuse to size objects greater than 64m. Most of the builds don't need to be resized by a script as they've already been scaled correctly in the modelling application. Perhaps something for later work if there is interest.