Varregion - Revision history

Tampa: SizeZ is ignored

2023-02-05T19:43:55Z

SizeZ is ignored

Manni: /* Restrictions */

2023-01-30T10:18:35Z

‎Restrictions

Manni: /* Restrictions */

2023-01-30T10:15:13Z

‎Restrictions

Manni: /* Restrictions */

2023-01-30T10:14:43Z

‎Restrictions

Albertlr Landar: /* Varregions and OAR Files */

2023-01-27T21:31:16Z

‎Varregions and OAR Files

Ubit: /* Things Known to be Broken */

2022-03-16T14:09:56Z

‎Things Known to be Broken

Acryline: /* Configuration */

2022-02-27T12:14:21Z

‎Configuration

Tampa: /* Restrictions */

2022-02-26T23:05:55Z

‎Restrictions

Ubit: /* Restrictions */

2021-10-27T00:16:26Z

‎Restrictions

Ubit: /* Restrictions */

2021-10-26T23:45:30Z

‎Restrictions

@@ Line 17: / Line 17: @@
 * The dimensions must be a multiple of 256 and less than or equal to 4096.
 * The dimensions must be equal so regions are square
-* One region can only have one adjacent region per side, excluding corners or viewers may crash. (so at most 4 regions touching at corners plus other 4, one touching each side) (If you specify the SizeZ isosceles volume for all regions, you don't have this problem. opensim 0.8.0+)
+* One region can only have one adjacent region per side, excluding corners or viewers may crash. (so at most 4 regions touching at corners plus other 4, one touching each side)
 * Adjacent regions must be the same size unless they are all version 0.9 or above. Even then expect glitches from time to time, especially with physics and crossings.
 * With versions prior to 0.9 you must use BulletSim (0.9 ODE engines support varregions).

@@ Line 17: / Line 17: @@
 * The dimensions must be a multiple of 256 and less than or equal to 4096.
 * The dimensions must be equal so regions are square
-* One region can only have one adjacent region per side, excluding corners or viewers may crash. (so at most 4 regions touching at corners plus other 4, one touching each side) (If you specify SizeZ you don't have this problem. opensim 0.8.0+)
+* One region can only have one adjacent region per side, excluding corners or viewers may crash. (so at most 4 regions touching at corners plus other 4, one touching each side) (If you specify the SizeZ isosceles volume for all regions, you don't have this problem. opensim 0.8.0+)
 * Adjacent regions must be the same size unless they are all version 0.9 or above. Even then expect glitches from time to time, especially with physics and crossings.
 * With versions prior to 0.9 you must use BulletSim (0.9 ODE engines support varregions).

@@ Line 17: / Line 17: @@
 * The dimensions must be a multiple of 256 and less than or equal to 4096.
 * The dimensions must be equal so regions are square
-* One region can only have one adjacent region per side, excluding corners or viewers may crash. (so at most 4 regions touching at corners plus other 4, one touching each side)(If you specify SizeZ you don't have this problem. opensim 0.8.0+)
+* One region can only have one adjacent region per side, excluding corners or viewers may crash. (so at most 4 regions touching at corners plus other 4, one touching each side) (If you specify SizeZ you don't have this problem. opensim 0.8.0+)
 * Adjacent regions must be the same size unless they are all version 0.9 or above. Even then expect glitches from time to time, especially with physics and crossings.
 * With versions prior to 0.9 you must use BulletSim (0.9 ODE engines support varregions).

@@ Line 17: / Line 17: @@
 * The dimensions must be a multiple of 256 and less than or equal to 4096.
 * The dimensions must be equal so regions are square
-* One region can only have one adjacent region per side, excluding corners or viewers may crash. (so at most 4 regions touching at corners plus other 4, one touching each side)
+* One region can only have one adjacent region per side, excluding corners or viewers may crash. (so at most 4 regions touching at corners plus other 4, one touching each side)(If you specify SizeZ you don't have this problem. opensim 0.8.0+)
 * Adjacent regions must be the same size unless they are all version 0.9 or above. Even then expect glitches from time to time, especially with physics and crossings.
 * With versions prior to 0.9 you must use BulletSim (0.9 ODE engines support varregions).

@@ Line 72: / Line 72: @@
 change region bigregion
 load oar oar00.oar
-load oar oar01.oar --displacement "<0,256,0>" --merge --force-terrain --force-parcels
+load oar --displacement "<0,256,0>" --merge --force-terrain --force-parcels oar01.oar
-load oar oar10.oar --displacement "<256,0,0>" --merge --force-terrain --force-parcels
+load oar --displacement "<256,0,0>" --merge --force-terrain --force-parcels oar10.oar
-load oar oar11.oar --displacement "<256,256,0>" --merge --force-terrain --force-parcels
+load oar --displacement "<256,256,0>" --merge --force-terrain --force-parcels oar11.oar
 </pre>

← Older revision		Revision as of 14:09, 16 March 2022
Line 78:		Line 78:

	Note the new "--force-terrain" and "--force-parcels" parameters. "--merge", used by itself, is for merging together the objects from multiple OARs. Merging also suppresses the loading of terrain and parcel data which is just what you want when merging objects. But, if loading multiple OARs to create a new, larger region, the terrain and parcel information must be loaded. Thus the new parameters.		Note the new "--force-terrain" and "--force-parcels" parameters. "--merge", used by itself, is for merging together the objects from multiple OARs. Merging also suppresses the loading of terrain and parcel data which is just what you want when merging objects. But, if loading multiple OARs to create a new, larger region, the terrain and parcel information must be loaded. Thus the new parameters.
−
−	~~==Things Known to be Broken==~~
−	* There is some problem with teleporting in and out of larger region. It works for some configurations and not others.
−	* While adjacent regions are usually viewable, sometimes they are not. They appear when you cross over into the region.

	==Implementation Discussion (Obsolete)==		==Implementation Discussion (Obsolete)==

@@ Line 36: / Line 36: @@
 ==Configuration==
 The size is be specified in the <tt>Region.ini</tt> file:
-<pre>
+<source lang="ini">
      [MyRegionName]
      RegionUUID = 95ec77ec-58c5-4ce2-9ff3-b6d1900d78a2
@@ Line 46: / Line 46: @@
      AllowAlternatePorts = False
      ExternalHostName = SYSTEMIP
-</pre>
+</source>
-If size is not specified it will default to the legacy size of 256.
+*If size is not specified it will default to the legacy size of 256.
+*If the given dimensions do not fit the restrictions, acceptable values are computed and warning and error messages are output into the log.
-If the given dimensions do not fit the restrictions, acceptable values are computed and warning and error messages are output into the log.
+*If you leave ExternalHostName at the default 'SYSTEMIP' then this will become the LAN network address of the machine (e.g. 192.168.1.2). This is fine if you are connecting only from within your LAN. If you want to connect to it from a client on the internet, this should be the External IP Address of your router. Fully Qualified Domain Names (FQDNs) can also be used though they will be converted to a numeric IP address before being sent to the viewer.
+*If converting from a mega-region, remember to set:
-If you leave ExternalHostName at the default 'SYSTEMIP' then this will become the LAN network address of the machine (e.g. 192.168.1.2). This is fine if you are connecting only from within your LAN. If you want to connect to it from a client on the internet, this should be the External IP Address of your router. Fully Qualified Domain Names (FQDNs) can also be used though they will be converted to a numeric IP address before being sent to the viewer.
+<source lang="ini">
+ CombineContiguousRegions = false
-If converting from a mega-region, remember to set "<tt>CombineContiguousRegions = false</tt>".
+</source>
+*For llRezObject to work beyond 256m set  in the [Xengine] section of OpenSim.ini (for 512mx512m) :
-For llRezObject to work beyond 256m set "ScriptDistanceLimitFactor = 512.0" (for 512mx512m) in the [Xengine] section of OpenSim.ini.
+<source lang="ini">
+ ScriptDistanceLimitFactor = 512.0
-If you have a very large region you might need to set the database maximum size to a larger value. For instance, a 2816x2816 region (11x11 legacy regions) turns into a 56 megabyte heightmap and, for MySQL, you would need to set <tt>max_allowed_packet</tt> to something like 64M. Version 0.9 stores terrain in compressed format so this depends on terrain complexity.
+</source>
 ==Loading Terrain==