Installation OAR Opensimulator

Exemple Upload depuis console OpenSim.exe : 

load oar  OAR-Military_Metaverse(4X4).tgz

Exemple Upload avec options :

load oar  --merge  --skip-assets  --displacement <768,0,0>  --rotation 0 --no-objects  --force-terrain OAR-Military_Metaverse(4X4).tgz

Options :

--merge  : Specify to merge the contents of the reading OAR with the existing contents in the region. 

--skip assets  : If set, this will not load any of the assets from the OAR, though all other data will be loaded. This saves a lot of time and database operations if loading an OAR multiple times on a grid -- specify --skip-assets after the first time the OAR is loaded on a grid as the assets would have already been loaded the first time the OAR files was loaded. 

--displacement  : Specify a displacement that is added to all objects in the OAR file as they are added to the region. The displacement MUST be specified as "<x,y,z>". 
So, for instance, to load an OAR from a 256x256 region into the middle of a larger 512x512 region, the parameter would be --displacement "<128,128,0>". 
Note that you can specify a "Z" displacement which will move the objects up or down. 
Thus --displacement "<0,0,1000>" will put all the OAR's objects up high for a sky box.
The displacement is also applied to the terrain if it is included. The 'Z' component is added to the terrain's heights. 

--rotation  : The degrees to rotate all the objects loaded from the OAR. 

--rotation-center :The center around which to rotate objects on load. NOTE: As of 0.8.1 this does nothing and will be removed soon. 

--no-objects : Don't load any scene objects. 

--force-terrain : Force terrain loading on --merge. Normally, --merge does not overwrite the existing region's terrain. 

--force-parcels : Force parcel loading on --merge. Normally, --merge does not overwrite the existing region's parcel data. 

--default-user "<first-name> <last-name>" : Instead of setting object ownership to the estate owner, assign it to the named user. This only applies to objects that have UUIDs that do not match any user account in the receiving grid's installation. There is currently no option that will force a change of owner for all loaded objects no matter whether they match a user in the receiving installation. One workaround to achieve this would be to save the OAR with the --publish "save oar" option to strip owner information and then reload it. 

--debug : Force the archiver to display messages about where each object is being placed.