OpenSimulator - User contributions [en]

Talk:Debian 4 Build Instructions

2009-01-20T12:19:41Z

Max Ping:

According to the README in the Source distribution the valid parameters to "--with-libgdiplus=" are

<copy-paste README>
--with-libgdiplus=installed,sibling,<path>
</end copy-paste>

"--with-libgdiplus=yes" makes no more sense than the instructions previously linked to advising "--with-libgdiplus=no"

== Include a paragraph about placing Mono-2.0.1 in /usr/local/bin ==

I'm thinking it would be a good idea to include instructions for using the command "./configure --prefix=/usr/local" so that this Mono installation gets put in /usr/local/bin so as not to disturb any pre-existing installations of Mono. Most common distros of Linux that have /usr/local/bin in $PATH will have it following /bin and /usr/bin so that software that requires/depends on Mono < 2.0.1 will still find the proper binary when using $PATH. Of course user needs to specify <path> when calling Mono-2.0.1 but seems a small point that is easily remedied. Not to mention the benefit of easily reverting OpenSim to using previous install of Mono by having it still available in /usr/bin

Naturally i didn't actually read the documentation about the libgdiplus parameters - I was basing that on the opposite of what now appears to be the incorrect original instruction - I propose that we change it to "installed" for the sake of accuracy, although it does seem to work anyway

With reg alternate mono - I suggest that we expand the page to cover all debian distros & mono configs ultimately making it a "deeper" debian experience - I think this page should become "Debian Build Instructions" then an general overview of which configs are supported or work best from our experience

Debian 4 Build Instructions

2009-01-19T14:15:07Z

Max Ping:

The following packages and their dependencies are required to run OpenSim on a default Debian 4 netinstall:

* mono
* libmono-corlib2.0-cil
* libmono-sqlite2.0-cil
* libmono-system-web2.0-cil
* libmono-microsoft8.0-cil
* libmono-system-runtime2.0-cil
* libmono-oracle2.0-cil (new dependency since r7587)

Hint #1: It is possible to use Debian Etch, but you will need to add custom repositories for mono to work. However installing or upgrading to Lenny/Sid will enable you to use the standard debian repositories. This is a good thing.

Hint #2: OpenSim will run on Mono 1.9.1, but seems to run a little better on Mono 2.0.1

''' Upgrading Etch to Lenny '''

I culled this from the a a little post on go2linux http://www.go2linux.org/upgrading-debian

To upgrade the Linux Debian Stable Etch to testing Lenny, just need to follow these two steps.

1. Edit sources.list

sudo vi /etc/apt/sources.list

and change all words etch to lenny, or stable to testing

2. Update and upgrade

sudo aptitude update

sudo aptitude install apt dpkg aptitude

sudo aptitude full-upgrade

This will also work when moving from Lenny to Sid.

Note: When I ran aptitude full-upgrade , I got a bunch of package configuration options - I took the safe option and just went with whatever it suggested. If you have no idea what you are doing (like me) then that's probably your best bet.

''' Getting the prerequisites '''

Ok first you need a bunch of stuff to get started - then you need Mono 2.0.1 (trembles) or better...

aptitude install subversion ruby
aptitude install nant ( this gets you a bunch of the mono stuff anyway )
aptitude install build-essential swig autoconf gawk mono-common binfmt-support bison libglib2.0-dev

And a few more things...

aptitude install libmono-microsoft8.0-cil
aptitude install libmono-oracle2.0-cil

''' Install Mono 2.0.1 '''

Yes... you know you wan't to do it... this is one way ( compile from source ) there are several others but this worked for me.

wget http://ftp.novell.com/pub/mono/sources/mono/mono-2.0.1.tar.bz2
tar xf mono-2.0.1.tar.bz2
cd mono-2.0.1
./configure --with-libgdiplus=yes
make (you may see a bunch of warnings, but do what I did - ignore them)
make install

Ok cool, now type "mono -V" and you should see something like this:

Mono JIT compiler version 2.0.1 (tarball)
Copyright (C) 2002-2008 Novell, Inc and Contributors. www.mono-project.com
TLS: __thread
GC: Included Boehm (with typed GC)
SIGSEGV: altstack
Notifications: epoll
Architecture: x86
Disabled: none

''' Now for Opensim itself! '''

Just do this:

svn co http://opensimulator.org/svn/opensim/trunk opensim (this may take a few minutes)
cd opensim
./runprebuild.sh
nant

nearly there...

cd bin
mono OpenSim.exe

Enjoy :)

Debian 4 Build Instructions

2009-01-19T14:09:11Z

Max Ping:

Debian 4 Build Instructions

2009-01-19T13:54:53Z

Max Ping:

Debian 4 Build Instructions

2009-01-19T13:46:40Z

Max Ping:

The following packages and their dependencies are required to run OpenSim on a default Debian 4 netinstall:

* mono
* libmono-corlib2.0-cil
* libmono-sqlite2.0-cil
* libmono-system-web2.0-cil
* libmono-microsoft8.0-cil
* libmono-system-runtime2.0-cil
* libmono-oracle2.0-cil (new dependency since r7587)

Hint #1: It is possible to use Debian Etch, but you will need to add custom repositories for mono to work. However installing or upgrading to Lenny/Sid will enable you to use the standard debian repositories. This is a good thing.

Hint #2: OpenSim will run on Mono 1.9.1, but seems to run a little better on Mono 2.0.1

''' Upgrading Etch to Lenny '''

I culled this from the a a little post on go2linux http://www.go2linux.org/upgrading-debian

To upgrade the Linux Debian Stable Etch to testing Lenny, just need to follow these two steps.

1. Edit sources.list

sudo vi /etc/apt/sources.list

and change all words etch to lenny, or stable to testing

2. Update and upgrade

sudo aptitude update

sudo aptitude install apt dpkg aptitude

sudo aptitude full-upgrade

This will also work when moving from Lenny to Sid.

Note: When I ran aptitude full-upgrade , I got a bunch of package configuration options - I took the safe option and just went with whatever it suggested. If you have no idea what you are doing (like me) then that's probably your best bet.

''' Getting the prerequisites '''

Ok first you need a bunch of stuff to get started - then you need Mono 2.0.1 (trembles) or better...

aptitude install subversion ruby
aptitude install nant ( this gets you a bunch of the mono stuff anyway )
aptitude install build-essential swig autoconf gawk mono-common binfmt-support bison libglib2.0-dev

And a few more things...

aptitude install libmono-microsoft8.0-cil
aptitude install libmono-oracle2.0-cil

''' Install Mono 2.0.1 '''

Yes... you know you wan't to do it... this is one way ( compile from source ) there are several others but this worked for me.

wget http://ftp.novell.com/pub/mono/sources/mono/mono-2.0.1.tar.bz2
tar xf mono-2.0.1.tar.bz2
cd mono-2.0.1
./configure --with-libgdiplus=yes
make (chuckle at the "Function Emit Trampolines bit)
make install

Debian 4 Build Instructions

2009-01-19T13:40:12Z

Max Ping:

The following packages and their dependencies are required to run OpenSim on a default Debian 4 netinstall:

* mono
* libmono-corlib2.0-cil
* libmono-sqlite2.0-cil
* libmono-system-web2.0-cil
* libmono-microsoft8.0-cil
* libmono-system-runtime2.0-cil
* libmono-oracle2.0-cil (new dependency since r7587)

Hint #1: It is possible to use Debian Etch, but you will need to add custom repositories for mono to work. However installing or upgrading to Lenny/Sid will enable you to use the standard debian repositories. This is a good thing.

Hint #2: OpenSim will run on Mono 1.9.1, but seems to run a little better on Mono 2.0.1

''' Upgrading Etch to Lenny '''

I culled this from the a a little post on go2linux http://www.go2linux.org/upgrading-debian

To upgrade the Linux Debian Stable Etch to testing Lenny, just need to follow these two steps.

1. Edit sources.list

sudo vi /etc/apt/sources.list

and change all words etch to lenny, or stable to testing

2. Update and upgrade

sudo aptitude update

sudo aptitude install apt dpkg aptitude

sudo aptitude full-upgrade

This will also work when moving from Lenny to Sid.

Note: When I ran aptitude full-upgrade , I got a bunch of package configuration options - I took the safe option and just went with whatever it suggested. If you have no idea what you are doing (like me) then that's probably your best bet.

''' Getting the prerequisites '''

Ok first you need a bunch of stuff to get started - then you need Mono 2.0.1 (trembles) or better...

aptitude install subversion ruby
aptitude install nant ( this gets you a bunch of the mono stuff anyway )
aptitude install build-essential swig autoconf gawk mono-common binfmt-support bison libglib2.0-dev

''' Install Mono 2.0.1 '''

Yes... you know you wan't to do it... this is one way ( compile from source ) there are several others but this worked for me.

wget http://ftp.novell.com/pub/mono/sources/mono/mono-2.0.1.tar.bz2
tar xf mono-2.0.1.tar.bz2
cd mono-2.0.1
./configure --with-libgdiplus=yes
make (chuckle at the "Function Emit Trampolines bit)
make install

Debian 4 Build Instructions

2009-01-19T13:38:47Z

Max Ping:

The following packages and their dependencies are required to run OpenSim on a default Debian 4 netinstall:

* mono
* libmono-corlib2.0-cil
* libmono-sqlite2.0-cil
* libmono-system-web2.0-cil
* libmono-microsoft8.0-cil
* libmono-system-runtime2.0-cil
* libmono-oracle2.0-cil (new dependency since r7587)

Hint #1: It is possible to use Debian Etch, but you will need to add custom repositories for mono to work. However installing or upgrading to Lenny/Sid will enable you to use the standard debian repositories. This is a good thing.

Hint #2: OpenSim will run on Mono 1.9.1, but seems to run a little better on Mono 2.0.1

''' Upgrading Etch to Lenny '''

I culled this from the a a little post on go2linux http://www.go2linux.org/upgrading-debian

To upgrade the Linux Debian Stable Etch to testing Lenny, just need to follow these two steps.

1. Edit sources.list

sudo vi /etc/apt/sources.list

and change all words etch to lenny, or stable to testing

2. Update and upgrade

sudo aptitude update

sudo aptitude install apt dpkg aptitude

sudo aptitude full-upgrade

This will also work when moving from Lenny to Sid.

Note: When I ran aptitude full-upgrade , I got a bunch of package configuration options - I took the safe option and just went with whatever it suggested. If you have no idea what you are doing (like me) then that's probably your best bet.

''' Getting the prerequisites '''

Ok first you need a bunch of stuff to get started - then you need Mono 2.0.1 (trembles) or better...

aptitude install subversion ruby
aptitude install nant ( this gets you a bunch of the mono stuff anyway )
aptitude install build-essential swig autoconf gawk mono-common binfmt-support bison libglib2.0-dev

''' Install Mono 2.0.1 '''

Yes... you know you wan't to do it... this is one way ( compile from source ) there are several others but this worked for me.

# wget http://ftp.novell.com/pub/mono/sources/mono/mono-2.0.1.tar.bz2
# tar xf mono-2.0.1.tar.bz2
# cd mono-2.0.1
# ./configure --with-libgdiplus=yes
# make (chuckled at the "Function Emit Trampolines bit)
# make install

Debian 4 Build Instructions

2009-01-19T13:18:05Z

Max Ping:

Debian 4 Build Instructions

2009-01-19T13:16:32Z

Max Ping:

Debian 4 Build Instructions

2009-01-19T13:10:37Z

Max Ping:

Debian 4 Build Instructions

2009-01-19T13:00:57Z

Max Ping:

Debian 4 Build Instructions

2009-01-19T12:49:16Z

Max Ping: New page: The following packages and their dependencies are required to run OpenSim on a default Debian 4 netinstall: * mono * libmono-corlib2.0-cil * libmono-sqlite2.0-cil * libmono-system-web2.0-...

Build Instructions

2009-01-19T12:48:53Z

Max Ping: Moved Debian 4 instructions to seperate page

[[Category:Users]]
This page covers building OpenSim from source code on multiple platforms. Please help us keep this page up to date as the project progresses.

==Download from SVN==
Check out the [[Download]] Section

==MS Windows==

OpenSim requires either the .Net framework version 2.0, or the latest Mono. It supports the following compilers:
* [http://msdn2.microsoft.com/en-us/express/aa700756.aspx Microsoft Visual C# Express Edition] (note: not Visual C++)
* [http://www.mono-project.com/ mono]

Note for people who just downloaded the sources from http://dist.opensimulator.org/ (the "Downloads" link on the left) be advised that some important things are missing (like MySQL template scripts). For such features, you must download using svn!

Additional note: any Microsoft C# Express edition should work (2005 or 2008)

Additional note: It is possible to develope on Windows Vista 64 bits with the following tweaks:
# Select OpenSim project properties from solution and choose platform to be x86. Rebuild solution.
# Select OpenSim.exe properties under solution bin folder and choose windows xp sp 2 compatibility mode + run as administrator.

=== Building ===

* In the top-level directory, run the '<tt>runprebuild.bat</tt>' file. This will create a VS2005 solution file, a nant build file and a '<tt>compile.bat</tt>' file.
* If you prefer VS2008, run the '<tt>runprebuild2008.bat</tt>' instead.

* Open the resulting sln file with visual studio and build it there, or
* Run the '<tt>compile.bat</tt>' file. This will build the executable using MSBuild.
* if you prefer to use nant, run nant in the same top-level directory. This will build the executables.

If you don't care about physics (walking on prims, etc), ignore the rest of this section.

=== Running ===

Recent versions of OpenSim come without an <tt>OpenSim.ini</tt> file. Copy the <tt>OpenSim.ini.example</tt> file to <tt>OpenSim.ini</tt> before making any changes.

Double-click on the <tt>OpenSim.exe</tt> executable file in the <tt>bin</tt> directory. This will start up OpenSim in standalone mode.

The debugger in VS2005 C# may be used to step through the code. For those that use a Cygwin shell, you may find that one or more dll's have permissions that cause problems running. Most find that a "<tt>chmod 777 *</tt>" from the <tt>bin</tt> directory solves this.

Physics can be invoked by adding the appropriate line to the [Startup] section of <tt>OpenSim.ini</tt>. For ODE, that would be:

physics = OpenDynamicsEngine

You can also add a command line option to a shortcut, or run from a command prompt with:

-physics=OpenDynamicsEngine

'''''Windows Vista'''''

Some people have reported that to run on Windows Vista, you must first disable Windows Firewall. Under the new "Start" button of Vista, select "Control panel". Then double-click "Windows Firewall". In the window that pops up, on the left column, select "Turn Windows Firewall on or off". You will have to give permission for this to run, then select the option "Off (not recommended)". Click "OK" and exit from the Windows Firewall window.

If you have McAfee SecurityCenter, see the description below.

Once all the security features are disabled, right click on <tt>OpenSim.exe</tt> and select "Run as administrator". This will pop up a window asking permission, select "Allow". Your OpenSim server should run in a DOS-like window and accept connections.

'''''McAfee Security'''''

McAfee Security does not allow applications to listen on ports not explicitly specified. You have two options: 1) disable firewall protection all together, 2) enable <tt>OpenSim.exe</tt> to be able to open ports.

''Disable firewall''

Open McAfee SecurityCenter. Select "Internet & Network". In the lower left corner is a small link to "Configure...". Select this. In the right side of the window, select the bar that says "Firewall protection is enabled". Here you can select "Off".

''Enable <tt>OpenSim.exe</tt> to open ports''

Open McAfee SecurityCenter. Select "Internet & Network". In the lower left corner is a small link to "Configure...". Select this. In the right side of the window, select the bar that says "Firewall protection is enabled". Select the "Advanced..." button. This will pop up a new window.

In the new window, on the left side, select "Program Permissions." In the middle on the right side of the window, select the "Add Allowed Program" button. Use the browser that pops up to find the OpenSim executable and select it.

Finally, select "OK" and exit the McAfee SecurityCenter window.

==Linux/Mac OS X/FreeBSD==

The easiest plaform to get running on the Linux side is Ubuntu 8.10, 32bit. This is what most of the developers running Linux use. If you are looking for the quick path, start there.

=== Ubuntu 8.04 / 8.10 ===

For Ubuntu users on older distributions (7.10, 8.04, etc.) '''you need''' to upgrade your mono to 1.9.1.

You can use the built in packages for mono. However, for better performance, you may want to [http://xyzzyxyzzy.net/2008/05/08/updated-mono-build-script-for-hardy-heron-and-mono-191/ upgrade mono to 1.9.1] ([http://tempvariable.blogspot.com/2008/04/installing-mono-191-on-ubuntu-804-hardy.html Other simple method])

sudo apt-get install subversion nant mono-gmcs libmono-microsoft8.0-cil \
libmono-system-runtime2.0-cil libgdiplus libmono-i18n2.0-cil libmono-oracle2.0-cil ruby
svn co http://opensimulator.org/svn/opensim/trunk opensim
cd opensim
./runprebuild.sh
nant

To upgrade the Mono version to the latest stable build Mono 2.0.1, read this page [[Build Instructions/Ubuntu-Mono-2.0.1 | Ubuntu on Mono 2.0.1]]

=== openSUSE 10.3 and 11 ===

Install an openSUSE 11 or 10.3 with its default options, add the online repositories
when finished installing do an online update with all the latest packages.

In yast install these packages, for running Opensim in standalone mode.
(there is a slight diffrence between 10.3 and 11 but following should be same)
subversion
nant
mono-jscript
- check that mono-core is installed

If you just want to use SQLite then jump to last section
within this post.

* Optional mysql - for Opensim running in Grid mode:
Install these mysql packages via yast
mysql
mysql-client
mysql-administrator
mysql-gui-tools
mysql-query-browser

Before building create the mysql database.
/etc/init.d/mysql start
mysql -u root -p -h localhost
(when asked for password just hit enter)

mysql> create database opensim;
mysql> quit

set the configuration in bin/mysql_connection.ini
Or on later builds set the connection string inside bin/OpenSim.ini

Build after installation of above in bash terminal. i save it in /opt

su -
cd /opt
svn co http://opensimulator.org/svn/opensim/trunk opensim
cd opensim
./runprebuild.sh
nant

After this you should be able to continue on starting the diffrent Servers, look in the mysql-config section,or
just run your OpenSim as a Standalone. By - eagleFX

=== Mac OS X 10.5/10.4 ===
* OpenSim is now working on PowerPC Macs! Thanks to DrScofield and those who helped him. Current nightly builds for PowerPC are not working, not sure about Intel so use the 0.5 Build. OpenSim works on Intel Macs. I'm testing on PowerBook G4. Tested these step on 10.5, but not 10.4 but should work --[[User:Mokele|Mokele]] 22:36, 14 February 2008 (PST) (Works on iMac G5 with OS 10.4.11, including expanding to local grid mode. --[[User:Magnuz|Magnuz]] 2008-12-15 10:50 (CET))
* Install XCode Developers Tools from DVD/CD Installation Disk or download from http://developer.apple.com/. You have to create an Apple account to access the downloads if you don't have an Apple account.
* Install X11 for 10.4 from the Optional Install from the DVD/CD Installation Disk. X11 for 10.5 is installed by default.
* Install Mono 1.2.5 from http://ftp.novell.com/pub/mono/archive/1.2.5/macos-10-universal/5/MonoFramework-1.2.5_5.macos10.novell.universal.dmg (The more recent releases Mono 1.2.6, 1.9.1 and 2.0.1 do not appear to work with these installation instructions. --[[User:Magnuz|Magnuz]] 2008-12-14 15:56 (CET)) and in Terminal or X11 edit the .profile file and add the following line:
export PKG_CONFIG_PATH="/Library/Frameworks/Mono.framework/Versions/Current/lib/pkgconfig/:${PKG_CONFIG_PATH}"
* Compile OpenSim
svn co http://opensimulator.org/svn/opensim/tags/0.5.0-release opensim
cd opensim
./runprebuild.sh
nant

* Download and Compile libopenjpeg-libsl-2.1.2.0.dylib and libsecondlife.dll
* libopenjpeg-libsl-2.1.2.0.dylib:
svn co http://opensimulator.org/svn/opensim-libs/old/libsl1550 opensim-libs
cd opensim-libs/openjpeg-libsl
make -f Makefile.osx
cp libopenjpeg-libsl-2.1.2.0.dylib ../../bin
* Note: The Makefile that creates the libopenjpeg-libsl-2.1.2.0.so does not compile on PowerPC, but works properly on Intel Macs. Looks like a gcc issue with compile options. (It appears to work on iMac G5 with OS X 10.4.11. --[[User:Magnuz|Magnuz]] 2008-12-14 15:55 (CET))

* libsecondlife.dll: (for PowerPC Only, see details on this step [http://xyzzyxyzzy.net/2008/02/12/installing-opensim-on-powerpcor-of-eggs-and-virtual-worlds installing OpenSim on PowerPC…or: of eggs and virtual worlds])
cd .. (back into opensim-libs)
nant
cp bin/libsecondlife.dll ../bin

* Edit the libsecondlife.dll.config (PowerPC Only). Remove the cpu="x86" tag in the last dllmap line.

=== FreeBSD 6.2 ===
su
cd /usr/ports/devel/subversion/ && make install clean (you may also need to rebuild apr-svn if this step fails)
cd /usr/ports/lang/mono/ && make install clean
cd /usr/ports/devel/nant/ && make install clean
cd /usr/ports/databases/sqlite3/ && make install clean
cd /usr/ports/x11-toolkits/libgdiplus/ && make install clean
cd /opensim/installation/directory/
svn co http://opensimulator.org/svn/opensim/trunk opensim
cd opensim
./runprebuild.sh
nant

Note: [http://opensimulator.org/wiki/OpenSim:FAQ#System.DllNotFoundException:_..2Flibopenjpeg-libsl-2.1.2.0.so|Follow the instructions on the FAQ to fix the]
"System.DllNotFoundException: ./libopenjpeg-libsl-2.1.2.0.so" issue, but use "gmake" instead of "make"

For ODE Physics you must do the following:
cd /usr/ports/graphics/libGL/ && make install clean
cd /usr/ports/graphics/libGLU/ && make install clean
cd /opensim/installation/directory/
svn co http://opensimulator.org/svn/opensim-libs/trunk opensim-libs
cd opensim-libs/unmanaged/OpenDynamicsEngine2/
sh autogen.sh
./configure --enable-shared --enable-release --disable-demos
make
mv ./ode/src/.libs/libode.so /opensim/installation/directory/opensim/bin/

=== RedHat Enterprise Linux 4 ===
sudo vi /etc/yum.repos.d/mono.repo

[mono]
name=Mono for rhel-4-i386 (stable)
baseurl=http://ftp.novell.com/pub/mono/download-stable/rhel-4-i386/
enabled=1
gpgcheck=0

sudo yum install mono-complete monodoc-core nant
svn co svn co http://opensimulator.org/svn/opensim/trunk opensim
cd opensim
./runprebuild.sh
nant

=== RedHat Enterprise Linux 5 ===

The instructions below also work on other RedHat Linux flavors such as CentOS or maybe Fedora.

1. Put the [http://download.opensuse.org/repositories/Mono/RHEL_5/Mono.repo Mono.repo] file in the /etc/yum.repo.d/ directory:
$ sudo su -
$ cd /etc/yum.repos.d/
$ wget http://download.opensuse.org/repositories/Mono/RHEL_5/Mono.repo
Naturally use the most [http://download.opensuse.org/repositories/Mono up-to-date link for your distribution].

2. Install Mono and related tools with yum:
$ yum install mono nant mono-jscript mono-nunit
Make sure to use nunit-console2 to run your tests.

=== Fedora 5 ===
* I needed to build latest mono and nant from sources to build OpenSim successfully, the ones available in yum repository didn't work so I had to uninstall and build and configure the packages.

For detailed instructions go [http://ruakuu.blogspot.com/2008/06/installing-and-configuring-opensim-on.html here]

=== Debian 4 ===

For detailed instructions please see [[Debian 4 Build Instructions]]

=== CentOS 5.2 32bit ===

For detailed instructions please see [[CentOS 5.2 Build Instructions]]

=== 64bit ===
Please note that only 32bit binaries are provided in the bin/ directory of subversion. If you want to use 64bit, you'll need to rebuild these shared objects. See [[Installing and running on x86-64]]

=== Physics (Open Dynamics Engine ODE) ===
As installed from svn, ODE will work on most 32 bit platforms. If you get an ODE-related crash, and/or a libode.so not found type of error, you will need to build libode from source.

Remove <tt>libode.so</tt> from the <tt>./bin</tt> folder. (Note that subsequent svn updates may replace it again; best fix is to copy your built <tt>libode.so</tt> to <tt>bin</tt>). Do NOT remove <tt>ode.net.dll</tt>! Download the latest source from:

svn co http://opensimulator.org/svn/opensim-libs/trunk/unmanaged/OpenDynamicsEngine

OpenSim requires a couple of patches on top of ODE which are not yet included upstream. When compiling, make sure to use the following configure options:

--with-trimesh=gimpact
--enable-shared

Make sure the configure script confirms these choices, and always compile with single precision (I believe that's the default). Try <code> make -k </code> if you get errors relating to drawstuff, test*, or openGL. <code> make install </code> should put <tt>libode.so</tt> in the proper place (usually <tt>/usr/local/lib</tt>), and it should be seen by opensim (<tt>ode.net.dll</tt>)

'''''Note:''' if OpenSim fails to launch with <tt>Exception: System.DllNotFoundException: ode</tt>, after compiling ODE, just copy <tt>libode.so</tt> from its usual place (probably <tt>/usr/local/lib/</tt>) to ./bin/, as per [http://metafuturing.net/index.php/OpenSim_Notebook_1 this suggestion]''

Setting up ODE for 64 Bits systems:

========================================================================
HOWTO on setting up and Install OpenSim on SLES10 - SP1 64Bit

1. I installed Mono 2.01, added this installation source in Yast2
This distro supports installing packages via YaST. Add the following installation source to YaST:
* http://ftp.novell.com/pub/mono/download-stable/SLE_10 [^]
For assistance with using repositories and installing packages with YaST, visit the Yast help page.

"nant" was installed also via this operation.

2. I installed subversion from http://software.opensuse.org/search [^]

SLES/SLED10 ->
subversion-1.5.2-34.2.x86_64.rpm

3. I downloaded and installed the lastest SVN version of opensim as usual (like a 32 bit system):
http://opensimulator.org/wiki/Build_Instructions [^]

4. I downloaded and installed the Open Dynamics Engine (ODE) to replace the 32 bit version of ODE with a 64 bit version.

I did that with the following linux commands:
(it is expected that you have all required Linux building tools installed):

# cd
# svn co http://opensimulator.org/svn/opensim-libs/trunk/unmanaged/OpenDynamicsEngine [^]
# cd OpenDynamicEngine
# chmod a+x ou/bootstrap
# sh autogen.sh

I installed/updated SLES10 with these rpm's for autogen.sh to run properly. http://software.opensuse.org/search [^]

SLES/SLED10 ->
- autoconf-2.61-168.1.x86_64.rpm
- automake-1.10.1-5.3.x86_64.rpm

# CFLAGS="-m64" ./configure --enable-shared
# make

I installed gtk2-devel via yast2, and all its dependancies, because make keept failing.

# cp ./ode/src/.libs/libode.so /opt/opensim/bin/

note:
in this directory it had made several versions of the "libode.so" because of running the previous commands several times
so i had to copy libode.so.1.0.0 to /opt/opensim/bin/libode.so

# vi ../opensim/bin/OpenSim.ini (change av_capsule_standup_tensor_linux to 1700000)

The 'chmod' command is required to fix permissions that are wrong.
The change in OpenSim.ini is required to avoid that avatars have bend legs and/or their feet are in the ground.
========================================================================

===Running===
Recent versions of OpenSim come without an <tt>OpenSim.ini</tt> file. Copy the <tt>OpenSim.ini.example</tt> file to <tt>OpenSim.ini</tt> before making any changes.
<code>
cd bin
mono OpenSim.exe
</code>

Note: if you are running a 32bit Server such as Ubuntu 8.0.4 you need the alternative launcher:

<code>
mono OpenSim.32BitLaunch.exe
</code>

* To invoke ODE, add the option:
-physics=OpenDynamicsEngine
to the <tt>mono OpenSim.exe</tt> line

or add <code> physics = OpenDynamicsEngine </code> to the [Startup] section of <tt>OpenSim.ini</tt>. Same deal for other physics engines, when available.

On mono 1.2.6, some distributions may see
Unhandled Exception: System.NotSupportedException: CodePage 1252 not supported
on startup when using mysql. This can be resolved by installing the package libmono-i18n2.0-cil (see http://bugs.mysql.com/bug.php?id=33938).

=== Additional Items ===

* [[GC_NO_EXPLICIT|GC NO EXPLICIT]] - Enable Large Heap in Mono, this has been known to help performance and stability

== Hardware selection guide ==

An often-asked question is "what kind of hardware do I need to successfully run OpenSim?" Unfortunately, the answer is "it depends". The number of regions hosted on a given machine, number of simultaneous avatars on those regions, number of prims, use of scripts, etc., all affect hardware requirements. So, to help you make a more informed selection, some examples of hardware used are listed in the [[Hardware_Selection_Guide|hardware selection guide]].

[[Category:Users]]

CentOS 5.2 Build Instructions

2009-01-07T07:03:04Z

Max Ping:

The following process worked for me, please feel free to improve it as it may not be the best way :)

From a fresh install:

# yum update
# yum install subversion ruby

To get Mono 1.9.1 I added the Mono.repo file in the /etc/yum.repo.d/ directory:

# sudo su -
# cd /etc/yum.repos.d/
# wget http://download.opensuse.org/repositories/Mono/RHEL_5/Mono.repo

I then installed mono

# yum install mono nant libgdiplus mono-jscript mono-nunit

So far so good, mono -V shows 1.9.1 has installed :)

Now just a couple of other things that you may need:

# yum install swig autoconf gawk bison gcc

And then build and install mono 2.0.1 from source

# wget http://ftp.novell.com/pub/mono/sources/mono/mono-2.0.1.tar.bz2
# tar xf mono-2.0.1.tar.bz2
# cd mono-2.0.1
# ./configure --with-libgdiplus=yes
# make (may take a while)
# make install

Yay! mono -V and I have Mono 2.0.1 :)

Now all i have to do is open the right ports and install OpenSim as usual...

Once you have OpenSimulator running you may want to follow these instructions for setting up a crontab entry that checks your server to see it is running and restarts if it ain't.

[[How to set up OSWatchdog to automatically restart a crashed server on Linux(Universal)]]

CentOS 5.2 Build Instructions

2009-01-06T14:22:16Z

Max Ping:

CentOS 5.2 Build Instructions

2009-01-05T14:04:16Z

Max Ping:

The following process worked for me, please feel free to improve it as it may not be the best way :)

NB In progress do not follow these instructions yet!!

From a fresh install:

# yum update
# yum install subversion ruby

To get Mono 1.9.1 I added the Mono.repo file in the /etc/yum.repo.d/ directory:

# sudo su -
# cd /etc/yum.repos.d/
# wget http://download.opensuse.org/repositories/Mono/RHEL_5/Mono.repo

I then installed mono

# yum install mono nant libgdiplus mono-jscript mono-nunit

So far so good, mono -V shows 1.9.1 has installed :)

Now just a couple of other things that you may need:

# yum install swig autoconf gawk bison gcc

And then build and install mono 2.0.1 from source

# wget http://ftp.novell.com/pub/mono/sources/mono/mono-2.0.1.tar.bz2
# tar xf mono-2.0.1.tar.bz2
# cd mono-2.0.1
# ./configure --with-libgdiplus=yes
# make (may take a while)
# make install

Yay! mono -V and I have Mono 2.0.1 :)

Now all i have to do is open the right ports and install OpenSim as usual...

CentOS 5.2 Build Instructions

2009-01-05T13:25:35Z

Max Ping:

The following process worked for me, please feel free to improve it as it may not be the best way :)

NB In progress do not follow these instructions yet!!

From a fresh install:

# yum update
# yum install subversion ruby

To get Mono 1.9.1 I added the Mono.repo file in the /etc/yum.repo.d/ directory:

# sudo su -
# cd /etc/yum.repos.d/
# wget http://download.opensuse.org/repositories/Mono/RHEL_5/Mono.repo

I then installed mono

# yum install mono nant libgdiplus

So far so good, mono -V shows 1.9.1 has installed :)

Now just a couple of other things that you may need:

# yum install swig autoconf gawk bison gcc

And then build and install mono 2.0.1 from source

# wget http://ftp.novell.com/pub/mono/sources/mono/mono-2.0.1.tar.bz2
# tar xf mono-2.0.1.tar.bz2
# cd mono-2.0.1
# ./configure --with-libgdiplus=yes
# make (may take a while)
# make install

Yay! mono -V and I have Mono 2.0.1 :)

Now all i have to do is open the right ports and install OpenSim as usual...

CentOS 5.2 Build Instructions

2009-01-05T13:07:53Z

Max Ping:

The following process worked for me, please feel free to improve it as it may not be the best way :)

NB In progress do not follow these instructions yet!!

From a fresh install:

# yum update
# yum install subversion ruby

To get Mono 1.9.1 I added the Mono.repo file in the /etc/yum.repo.d/ directory:

# sudo su -
# cd /etc/yum.repos.d/
# wget http://download.opensuse.org/repositories/Mono/RHEL_5/Mono.repo

I then installed mono

# yum install mono nant libgdiplus

So far so good, mono -V shows 1.9.1 has installed :)

Ok, now to install mono 2.0.1

# yum install swig autoconf gawk bison gcc

Build and install mono 2.0.1

# wget http://ftp.novell.com/pub/mono/sources/mono/mono-2.0.1.tar.bz2
# tar xf mono-2.0.1.tar.bz2
# cd mono-2.0.1
# ./configure --with-libgdiplus=yes
# make (chuckled at the "Function Emit Trampolines bit)
# make install

CentOS 5.2 Build Instructions

2009-01-05T12:51:19Z

Max Ping:

The following process worked for me, please feel free to improve it :)

NB In progress do not follow these instructions yet!!

From a fresh install:

# yum update
# yum install subversion ruby

To get Mono 1.9.1 I added the Mono.repo file in the /etc/yum.repo.d/ directory:

$ sudo su -
$ cd /etc/yum.repos.d/
$ wget http://download.opensuse.org/repositories/Mono/RHEL_5/Mono.repo

I then installed mono

# yum install mono nant libgdiplus

# aptitude install build-essential swig autoconf gawk mono-common binfmt-support bison pkg-config libglib2.0-dev

Build and install mono 2.0.1

# wget http://ftp.novell.com/pub/mono/sources/mono/mono-2.0.1.tar.bz2
# tar xf mono-2.0.1.tar.bz2
# cd mono-2.0.1
# ./configure --with-libgdiplus=yes
# make (chuckled at the "Function Emit Trampolines bit)
# make install

CentOS 5.2 Build Instructions

2009-01-05T12:27:23Z

Max Ping:

The following process worked for me, please feel free to improve it :)

NB In progress do not follow these instructions yet!!

From a fresh install:

# yum update
# sudo apt-get install subversion nant libgdiplus ruby
# aptitude install build-essential swig autoconf gawk mono-common binfmt-support bison pkg-config libglib2.0-dev

Build and install mono 2.0.1

# wget http://ftp.novell.com/pub/mono/sources/mono/mono-2.0.1.tar.bz2
# tar xf mono-2.0.1.tar.bz2
# cd mono-2.0.1
# ./configure --with-libgdiplus=yes
# make (chuckled at the "Function Emit Trampolines bit)
# make install

CentOS 5.2 Build Instructions

2009-01-05T12:01:18Z

Max Ping: New page: The following process worked for me, please feel free to improve it :) as follows...

The following process worked for me, please feel free to improve it :)

as follows...

Build Instructions

2009-01-05T12:00:24Z

Max Ping: /* Linux/Mac OS X/FreeBSD */

[[Category:Users]]
This page covers building OpenSim from source code on multiple platforms. Please help us keep this page up to date as the project progresses.

==Download from SVN==
Check out the [[Download]] Section

==MS Windows==

OpenSim requires either the .Net framework version 2.0, or the latest Mono. It supports the following compilers:
* [http://msdn2.microsoft.com/en-us/express/aa700756.aspx Microsoft Visual C# Express Edition] (note: not Visual C++)
* [http://www.mono-project.com/ mono]

Note for people who just downloaded the sources from http://dist.opensimulator.org/ (the "Downloads" link on the left) be advised that some important things are missing (like MySQL template scripts). For such features, you must download using svn!

Additional note: any Microsoft C# Express edition should work (2005 or 2008)

Additional note: It is possible to develope on Windows Vista 64 bits with the following tweaks:
# Select OpenSim project properties from solution and choose platform to be x86. Rebuild solution.
# Select OpenSim.exe properties under solution bin folder and choose windows xp sp 2 compatibility mode + run as administrator.

=== Building ===

* In the top-level directory, run the '<tt>runprebuild.bat</tt>' file. This will create a VS2005 solution file, a nant build file and a '<tt>compile.bat</tt>' file.
* If you prefer VS2008, run the '<tt>runprebuild2008.bat</tt>' instead.

* Open the resulting sln file with visual studio and build it there, or
* Run the '<tt>compile.bat</tt>' file. This will build the executable using MSBuild.
* if you prefer to use nant, run nant in the same top-level directory. This will build the executables.

If you don't care about physics (walking on prims, etc), ignore the rest of this section.

=== Running ===

Recent versions of OpenSim come without an <tt>OpenSim.ini</tt> file. Copy the <tt>OpenSim.ini.example</tt> file to <tt>OpenSim.ini</tt> before making any changes.

Double-click on the <tt>OpenSim.exe</tt> executable file in the <tt>bin</tt> directory. This will start up OpenSim in standalone mode.

The debugger in VS2005 C# may be used to step through the code. For those that use a Cygwin shell, you may find that one or more dll's have permissions that cause problems running. Most find that a "<tt>chmod 777 *</tt>" from the <tt>bin</tt> directory solves this.

Physics can be invoked by adding the appropriate line to the [Startup] section of <tt>OpenSim.ini</tt>. For ODE, that would be:

physics = OpenDynamicsEngine

You can also add a command line option to a shortcut, or run from a command prompt with:

-physics=OpenDynamicsEngine

'''''Windows Vista'''''

To run on Windows Vista, you must first disable Windows Firewall. Under the new "Start" button of Vista, select "Control panel". Then double-click "Windows Firewall". In the window that pops up, on the left column, select "Turn Windows Firewall on or off". You will have to give permission for this to run, then select the option "Off (not recommended)". Click "OK" and exit from the Windows Firewall window.

If you have McAfee SecurityCenter, see the description below.

Once all the security features are disabled, right click on <tt>OpenSim.exe</tt> and select "Run as administrator". This will pop up a window asking permission, select "Allow". Your OpenSim server should run in a DOS-like window and accept connections.

'''''McAfee Security'''''

McAfee Security does not allow applications to listen on ports not explicitly specified. You have two options: 1) disable firewall protection all together, 2) enable <tt>OpenSim.exe</tt> to be able to open ports.

''Disable firewall''

Open McAfee SecurityCenter. Select "Internet & Network". In the lower left corner is a small link to "Configure...". Select this. In the right side of the window, select the bar that says "Firewall protection is enabled". Here you can select "Off".

''Enable <tt>OpenSim.exe</tt> to open ports''

Open McAfee SecurityCenter. Select "Internet & Network". In the lower left corner is a small link to "Configure...". Select this. In the right side of the window, select the bar that says "Firewall protection is enabled". Select the "Advanced..." button. This will pop up a new window.

In the new window, on the left side, select "Program Permissions." In the middle on the right side of the window, select the "Add Allowed Program" button. Use the browser that pops up to find the OpenSim executable and select it.

Finally, select "OK" and exit the McAfee SecurityCenter window.

==Linux/Mac OS X/FreeBSD==

The easiest plaform to get running on the Linux side is Ubuntu 8.10, 32bit. This is what most of the developers running Linux use. If you are looking for the quick path, start there.

=== Ubuntu 8.04 / 8.10 ===

For Ubuntu users on older distributions (7.10, 8.04, etc.) '''you need''' to upgrade your mono to 1.9.1.

You can use the built in packages for mono. However, for better performance, you may want to [http://xyzzyxyzzy.net/2008/05/08/updated-mono-build-script-for-hardy-heron-and-mono-191/ upgrade mono to 1.9.1] ([http://tempvariable.blogspot.com/2008/04/installing-mono-191-on-ubuntu-804-hardy.html Other simple method])

sudo apt-get install subversion nant mono-gmcs libmono-microsoft8.0-cil \
libmono-system-runtime2.0-cil libgdiplus libmono-i18n2.0-cil libmono-oracle2.0-cil ruby
svn co http://opensimulator.org/svn/opensim/trunk opensim
cd opensim
./runprebuild.sh
nant

To upgrade the Mono version to the latest stable build Mono 2.0.1, read this page [[Build Instructions/Ubuntu-Mono-2.0.1 | Ubuntu on Mono 2.0.1]]

=== openSUSE 10.3 and 11 ===

Install an openSUSE 11 or 10.3 with its default options, add the online repositories
when finished installing do an online update with all the latest packages.

In yast install these packages, for running Opensim in standalone mode.
(there is a slight diffrence between 10.3 and 11 but following should be same)
subversion
nant
mono-jscript
- check that mono-core is installed

If you just want to use SQLite then jump to last section
within this post.

* Optional mysql - for Opensim running in Grid mode:
Install these mysql packages via yast
mysql
mysql-client
mysql-administrator
mysql-gui-tools
mysql-query-browser

Before building create the mysql database.
/etc/init.d/mysql start
mysql -u root -p -h localhost
(when asked for password just hit enter)

mysql> create database opensim;
mysql> quit

set the configuration in bin/mysql_connection.ini
Or on later builds set the connection string inside bin/OpenSim.ini

Build after installation of above in bash terminal. i save it in /opt

su -
cd /opt
svn co http://opensimulator.org/svn/opensim/trunk opensim
cd opensim
./runprebuild.sh
nant

After this you should be able to continue on starting the diffrent Servers, look in the mysql-config section,or
just run your OpenSim as a Standalone. By - eagleFX

=== Mac OS X 10.5/10.4 ===
* OpenSim is now working on PowerPC Macs! Thanks to DrScofield and those who helped him. Current nightly builds for PowerPC are not working, not sure about Intel so use the 0.5 Build. OpenSim works on Intel Macs. I'm testing on PowerBook G4. Tested these step on 10.5, but not 10.4 but should work --[[User:Mokele|Mokele]] 22:36, 14 February 2008 (PST) (Works on iMac G5 with OS 10.4.11, including expanding to local grid mode. --[[User:Magnuz|Magnuz]] 2008-12-15 10:50 (CET))
* Install XCode Developers Tools from DVD/CD Installation Disk or download from http://developer.apple.com/. You have to create an Apple account to access the downloads if you don't have an Apple account.
* Install X11 for 10.4 from the Optional Install from the DVD/CD Installation Disk. X11 for 10.5 is installed by default.
* Install Mono 1.2.5 from http://ftp.novell.com/pub/mono/archive/1.2.5/macos-10-universal/5/MonoFramework-1.2.5_5.macos10.novell.universal.dmg (The more recent releases Mono 1.2.6, 1.9.1 and 2.0.1 do not appear to work with these installation instructions. --[[User:Magnuz|Magnuz]] 2008-12-14 15:56 (CET)) and in Terminal or X11 edit the .profile file and add the following line:
export PKG_CONFIG_PATH="/Library/Frameworks/Mono.framework/Versions/Current/lib/pkgconfig/:${PKG_CONFIG_PATH}"
* Compile OpenSim
svn co http://opensimulator.org/svn/opensim/tags/0.5.0-release opensim
cd opensim
./runprebuild.sh
nant

* Download and Compile libopenjpeg-libsl-2.1.2.0.dylib and libsecondlife.dll
* libopenjpeg-libsl-2.1.2.0.dylib:
svn co http://opensimulator.org/svn/opensim-libs/old/libsl1550 opensim-libs
cd opensim-libs/openjpeg-libsl
make -f Makefile.osx
cp libopenjpeg-libsl-2.1.2.0.dylib ../../bin
* Note: The Makefile that creates the libopenjpeg-libsl-2.1.2.0.so does not compile on PowerPC, but works properly on Intel Macs. Looks like a gcc issue with compile options. (It appears to work on iMac G5 with OS X 10.4.11. --[[User:Magnuz|Magnuz]] 2008-12-14 15:55 (CET))

* libsecondlife.dll: (for PowerPC Only, see details on this step [http://xyzzyxyzzy.net/2008/02/12/installing-opensim-on-powerpcor-of-eggs-and-virtual-worlds installing OpenSim on PowerPC…or: of eggs and virtual worlds])
cd .. (back into opensim-libs)
nant
cp bin/libsecondlife.dll ../bin

* Edit the libsecondlife.dll.config (PowerPC Only). Remove the cpu="x86" tag in the last dllmap line.

=== FreeBSD 6.2 ===
su
cd /usr/ports/devel/subversion/ && make install clean (you may also need to rebuild apr-svn if this step fails)
cd /usr/ports/lang/mono/ && make install clean
cd /usr/ports/devel/nant/ && make install clean
cd /usr/ports/databases/sqlite3/ && make install clean
cd /usr/ports/x11-toolkits/libgdiplus/ && make install clean
cd /opensim/installation/directory/
svn co http://opensimulator.org/svn/opensim/trunk opensim
cd opensim
./runprebuild.sh
nant

Note: [http://opensimulator.org/wiki/OpenSim:FAQ#System.DllNotFoundException:_..2Flibopenjpeg-libsl-2.1.2.0.so|Follow the instructions on the FAQ to fix the]
"System.DllNotFoundException: ./libopenjpeg-libsl-2.1.2.0.so" issue, but use "gmake" instead of "make"

For ODE Physics you must do the following:
cd /usr/ports/graphics/libGL/ && make install clean
cd /usr/ports/graphics/libGLU/ && make install clean
cd /opensim/installation/directory/
svn co http://opensimulator.org/svn/opensim-libs/trunk opensim-libs
cd opensim-libs/unmanaged/OpenDynamicsEngine2/
sh autogen.sh
./configure --enable-shared --enable-release --disable-demos
make
mv ./ode/src/.libs/libode.so /opensim/installation/directory/opensim/bin/

=== RedHat Enterprise Linux 4 ===
sudo vi /etc/yum.repos.d/mono.repo

[mono]
name=Mono for rhel-4-i386 (stable)
baseurl=http://ftp.novell.com/pub/mono/download-stable/rhel-4-i386/
enabled=1
gpgcheck=0

sudo yum install mono-complete monodoc-core nant
svn co svn co http://opensimulator.org/svn/opensim/trunk opensim
cd opensim
./runprebuild.sh
nant

=== RedHat Enterprise Linux 5 ===

The instructions below also work on other RedHat Linux flavors such as CentOS or maybe Fedora.

1. Put the [http://download.opensuse.org/repositories/Mono/RHEL_5/Mono.repo Mono.repo] file in the /etc/yum.repo.d/ directory:
$ sudo su -
$ cd /etc/yum.repos.d/
$ wget http://download.opensuse.org/repositories/Mono/RHEL_5/Mono.repo
Naturally use the most [http://download.opensuse.org/repositories/Mono up-to-date link for your distribution].

2. Install Mono and related tools with yum:
$ yum install mono nant mono-jscript mono-nunit
Make sure to use nunit-console2 to run your tests.

=== Fedora 5 ===
* I needed to build latest mono and nant from sources to build OpenSim successfully, the ones available in yum repository didn't work so I had to uninstall and build and configure the packages.

For detailed instructions go [http://ruakuu.blogspot.com/2008/06/installing-and-configuring-opensim-on.html here]

=== Debian 4 ===

The following packages and their dependencies are required to run OpenSim on a default Debian 4 netinstall:
* mono
* libmono-corlib2.0-cil
* libmono-sqlite2.0-cil
* libmono-system-web2.0-cil
* libmono-microsoft8.0-cil
* libmono-system-runtime2.0-cil
* libmono-oracle2.0-cil (new dependency since r7587)

Hint: Currently (Nov/28/2008) it is possible to use Debian etch, but you will need to add custom repositories for mono to work. However installing or upgrading to Lenny/Sid will enable you to use the standard debian repositories.

=== CentOS 5.2 32bit ===

For detailed instructions please see [[CentOS 5.2 Build Instructions]]

=== 64bit ===
Please note that only 32bit binaries are provided in the bin/ directory of subversion. If you want to use 64bit, you'll need to rebuild these shared objects. See [[Installing and running on x86-64]]

=== Physics (Open Dynamics Engine ODE) ===
As installed from svn, ODE will work on most 32 bit platforms. If you get an ODE-related crash, and/or a libode.so not found type of error, you will need to build libode from source.

Remove <tt>libode.so</tt> from the <tt>./bin</tt> folder. (Note that subsequent svn updates may replace it again; best fix is to copy your built <tt>libode.so</tt> to <tt>bin</tt>). Do NOT remove <tt>ode.net.dll</tt>! Download the latest source from:

svn co http://opensimulator.org/svn/opensim-libs/trunk/unmanaged/OpenDynamicsEngine

OpenSim requires a couple of patches on top of ODE which are not yet included upstream. When compiling, make sure to use the following configure options:

--with-trimesh=gimpact
--enable-shared

Make sure the configure script confirms these choices, and always compile with single precision (I believe that's the default). Try <code> make -k </code> if you get errors relating to drawstuff, test*, or openGL. <code> make install </code> should put <tt>libode.so</tt> in the proper place (usually <tt>/usr/local/lib</tt>), and it should be seen by opensim (<tt>ode.net.dll</tt>)

'''''Note:''' if OpenSim fails to launch with <tt>Exception: System.DllNotFoundException: ode</tt>, after compiling ODE, just copy <tt>libode.so</tt> from its usual place (probably <tt>/usr/local/lib/</tt>) to ./bin/, as per [http://metafuturing.net/index.php/OpenSim_Notebook_1 this suggestion]''

Setting up ODE for 64 Bits systems:

========================================================================
HOWTO on setting up and Install OpenSim on SLES10 - SP1 64Bit

1. I installed Mono 2.01, added this installation source in Yast2
This distro supports installing packages via YaST. Add the following installation source to YaST:
* http://ftp.novell.com/pub/mono/download-stable/SLE_10 [^]
For assistance with using repositories and installing packages with YaST, visit the Yast help page.

"nant" was installed also via this operation.

2. I installed subversion from http://software.opensuse.org/search [^]

SLES/SLED10 ->
subversion-1.5.2-34.2.x86_64.rpm

3. I downloaded and installed the lastest SVN version of opensim as usual (like a 32 bit system):
http://opensimulator.org/wiki/Build_Instructions [^]

4. I downloaded and installed the Open Dynamics Engine (ODE) to replace the 32 bit version of ODE with a 64 bit version.

I did that with the following linux commands:
(it is expected that you have all required Linux building tools installed):

# cd
# svn co http://opensimulator.org/svn/opensim-libs/trunk/unmanaged/OpenDynamicsEngine [^]
# cd OpenDynamicEngine
# chmod a+x ou/bootstrap
# sh autogen.sh

I installed/updated SLES10 with these rpm's for autogen.sh to run properly. http://software.opensuse.org/search [^]

SLES/SLED10 ->
- autoconf-2.61-168.1.x86_64.rpm
- automake-1.10.1-5.3.x86_64.rpm

# CFLAGS="-m64" ./configure --enable-shared
# make

I installed gtk2-devel via yast2, and all its dependancies, because make keept failing.

# cp ./ode/src/.libs/libode.so /opt/opensim/bin/

note:
in this directory it had made several versions of the "libode.so" because of running the previous commands several times
so i had to copy libode.so.1.0.0 to /opt/opensim/bin/libode.so

# vi ../opensim/bin/OpenSim.ini (change av_capsule_standup_tensor_linux to 1700000)

The 'chmod' command is required to fix permissions that are wrong.
The change in OpenSim.ini is required to avoid that avatars have bend legs and/or their feet are in the ground.
========================================================================

===Running===
Recent versions of OpenSim come without an <tt>OpenSim.ini</tt> file. Copy the <tt>OpenSim.ini.example</tt> file to <tt>OpenSim.ini</tt> before making any changes.
<code>
cd bin
mono OpenSim.exe
</code>

Note: if you are running a 32bit Server such as Ubuntu 8.0.4 you need the alternative launcher:

<code>
mono OpenSim.32BitLaunch.exe
</code>

* To invoke ODE, add the option:
-physics=OpenDynamicsEngine
to the <tt>mono OpenSim.exe</tt> line

or add <code> physics = OpenDynamicsEngine </code> to the [Startup] section of <tt>OpenSim.ini</tt>. Same deal for other physics engines, when available.

On mono 1.2.6, some distributions may see
Unhandled Exception: System.NotSupportedException: CodePage 1252 not supported
on startup when using mysql. This can be resolved by installing the package libmono-i18n2.0-cil (see http://bugs.mysql.com/bug.php?id=33938).

=== Additional Items ===

* [[GC_NO_EXPLICIT|GC NO EXPLICIT]] - Enable Large Heap in Mono, this has been known to help performance and stability

== Hardware selection guide ==

An often-asked question is "what kind of hardware do I need to successfully run OpenSim?" Unfortunately, the answer is "it depends". The number of regions hosted on a given machine, number of simultaneous avatars on those regions, number of prims, use of scripts, etc., all affect hardware requirements. So, to help you make a more informed selection, some examples of hardware used are listed in the [[Hardware_Selection_Guide|hardware selection guide]].

[[Category:Users]]

Cross-region terrain making with L3DT

2009-01-05T11:39:19Z

Max Ping: /* Generating the Heightfield */

This tutorial has been put together from several sources on the web it is aimed at region operators who want to make detailed cross region terrains quickly and easily.

It describes the generation of the terrain files needed to seamlessly fill a 2x3 region. Obviously you can adapt it to fit your specific requirements. Designing a terrain map for a single region is relatively straightforward, however if you want your region to span across a number of regions we are faced with a few challenges. The main one is seam-matching, in other words getting the edge of one sim to match the edge of the next. The inbuilt terraforming tools are quite good in OpenSimulator, however they struggle on region boundaries - thus you end up with jagged edges where the regions meet.

To resolve this you need to create a larger terrain map and then split it into tiles.

There are two ways to do this, either draw it by hand using a graphics package, or use a terrain generating tool as a starting point. You can just use the terrain generator to get started quickly although in reality you will probably end up mixing both techniques. The manual technique has been well described by Fu Barr here: http://opensimulator.org/wiki/Terrain_making so i will focus on the easy way.

The principle reason why I wanted to start with a generated terrain is time - it takes a long time to draw your heightmap by hand so using the generator gives you a little kick start. It can also generate very realistic terrains which factor in things like age and erosion, in minutes rather than hours :)

Enjoy the tutorial and feel free to contribute/improve it -

[[Max Ping]]

== The Objective ==

My objective is to create a 6 region heightmap based on the idea of an ancient volcanic archipelago. Thus I wanted a few islands with nice curved stretches of beach, some cliffs and drop offs and a higher regions. I already had in mind roughly what i wanted so that was a good start. I personally like islands because you get lots of terrain variation and the sunsets in OpenSim can be... well stunning :) It's very useful to have an idea in your mind of what you want before you start...

== The Process ==

I used the L3DT Editor from Bundysoft, the standard edition is free and it does a great job of creating heightmaps, it generates nice and realisitc terrain- you can also drop in and fly around the terrain in a 3d view which will be familiar to OpenSimmers and great for previewing before you upload the regions. You can get the product here:

http://www.bundysoft.com/L3DT/downloads/standard.php

[[Image:Design map1.png|100px|thumb|left|First iteration of design map]][[Image:Design map2.png|100px|thumb|left|Second iteration of design map]]

== Generating your terrain files - The Design Map ==

The first thing you will generate is a design map - this is a "blocky" representation of the landmass which means you can rapidly paint your terrain before you actually apply the terrain calculation.

1. Click "New Map" and choose the "Design/inflate (blank)" Algorithm

2. My desired region size is 2x3, which is 512m x 768m. Note that I set the horizontal scale to 1m

3. I then used the default HF/DM ratio of 64 - this allows you to roughly plot your land mass

4. Now the fun begins :) Click the edit icon to bring up the Design map brush - there's lots you can do here - you just have to experiment with the brushes... Personally I found the easiest method was to simply ignore all the other brushes and focus on the altitude brush. The design map starts at sea level, so I set the altitude to "-20" then hit "apply to all". From this starting point I built my islands up from there, keeping the altitude in the range of -20 to 44m. Remember it can be pretty rough to begin with as you can gradually build up the terrain to suit your needs.

7. After a bit of experimenting I found that the altitude tools on the designmap at 512x768 was a bit limited, so i decided to double the size of the map to give me more accuracy. I chose Operations > Design Map > Resize Design map, and increased the size to 1024x1536 which generated a new larger scale design map derived from the orginal - you can immediately see the improvement in accuracy. You could have started with the large scale initially, but by starting small you lets L3DT do much of the hard work for you. As you can see i then further tweaked the map to get the features i wanted.

Note: I kept a border of -20m all around my terrain file, this was for ease of adding new regions later on

== Generating the Heightfield ==
[[Image:First_heightfield.jpg|100px|thumb|left|Exported image file]]

5. When you are happy with your design map, hit the calc button, choose Heightfield and watch l3DT do it's magic.

6. If it's not quite right, go back to your design map and tweak it, then hit calc again

7. When you think you nearly have it thats a good time to head over into the 3d view. The system uses roughly the same movement controls as OS so it's pretty easy to get to grips with. Here you can "fine tune" your terrain features to get it closer to what you are looking for. Mouse Tools > Edit Active Map.

[[Image:Editing in Sapphire.jpg|200px|thumb|left|Editing in Sapphire]]

8. Close Sapphire and then use File > Export > Active map, use .PNG format - at this point I resized back to 512x768

Using the grids and snapping in your editor comes in very handy. I then use guides to show where the final cuts will be. Tio speed things up you can use "slice along guides" when you export to get the files you need.

== Making OpenSimulator use the new terrain files ==

You need to now tell OpenSimulator to use the new terrain textures on your grid. For example: if you have 4 regions called Region1, Region2, Region3 and Region4... you need to add a section to your startup_commands.txt that looks like this:

change-region Region1
terrain load path_to_textures/terrain_for_region1.png

change-region Region2
terrain load path_to_textures/terrain_for_region2.png

etc...

Note: you can also add Terrain commands here, but if you follow the instructions above you won't have to

Step 9. '''Restart your OpenSimulator instance and fine-tune your terrain height.'''

== Notes ==

When you have your new terrain files loaded - make sure you disable the startup_commands, as every time you restart your server your terrain files will be re-uploaded, removing any in-game terraforming you have done
[[Image:terrain_in_opensim.jpg|200px|thumb|left|Here is the region in OpenSimulator :)]]

File:Terrain in opensim.jpg

2009-01-05T11:30:21Z

Max Ping:

Cross-region terrain making with L3DT

2009-01-05T11:29:37Z

Max Ping: /* Notes */

This tutorial has been put together from several sources on the web it is aimed at region operators who want to make detailed cross region terrains quickly and easily.

It describes the generation of the terrain files needed to seamlessly fill a 2x3 region. Obviously you can adapt it to fit your specific requirements. Designing a terrain map for a single region is relatively straightforward, however if you want your region to span across a number of regions we are faced with a few challenges. The main one is seam-matching, in other words getting the edge of one sim to match the edge of the next. The inbuilt terraforming tools are quite good in OpenSimulator, however they struggle on region boundaries - thus you end up with jagged edges where the regions meet.

To resolve this you need to create a larger terrain map and then split it into tiles.

There are two ways to do this, either draw it by hand using a graphics package, or use a terrain generating tool as a starting point. You can just use the terrain generator to get started quickly although in reality you will probably end up mixing both techniques. The manual technique has been well described by Fu Barr here: http://opensimulator.org/wiki/Terrain_making so i will focus on the easy way.

The principle reason why I wanted to start with a generated terrain is time - it takes a long time to draw your heightmap by hand so using the generator gives you a little kick start. It can also generate very realistic terrains which factor in things like age and erosion, in minutes rather than hours :)

Enjoy the tutorial and feel free to contribute/improve it -

[[Max Ping]]

== The Objective ==

My objective is to create a 6 region heightmap based on the idea of an ancient volcanic archipelago. Thus I wanted a few islands with nice curved stretches of beach, some cliffs and drop offs and a higher regions. I already had in mind roughly what i wanted so that was a good start. I personally like islands because you get lots of terrain variation and the sunsets in OpenSim can be... well stunning :) It's very useful to have an idea in your mind of what you want before you start...

== The Process ==

I used the L3DT Editor from Bundysoft, the standard edition is free and it does a great job of creating heightmaps, it generates nice and realisitc terrain- you can also drop in and fly around the terrain in a 3d view which will be familiar to OpenSimmers and great for previewing before you upload the regions. You can get the product here:

http://www.bundysoft.com/L3DT/downloads/standard.php

[[Image:Design map1.png|100px|thumb|left|First iteration of design map]][[Image:Design map2.png|100px|thumb|left|Second iteration of design map]]

== Generating your terrain files - The Design Map ==

The first thing you will generate is a design map - this is a "blocky" representation of the landmass which means you can rapidly paint your terrain before you actually apply the terrain calculation.

1. Click "New Map" and choose the "Design/inflate (blank)" Algorithm

2. My desired region size is 2x3, which is 512m x 768m. Note that I set the horizontal scale to 1m

3. I then used the default HF/DM ratio of 64 - this allows you to roughly plot your land mass

4. Now the fun begins :) Click the edit icon to bring up the Design map brush - there's lots you can do here - you just have to experiment with the brushes... Personally I found the easiest method was to simply ignore all the other brushes and focus on the altitude brush. The design map starts at sea level, so I set the altitude to "-20" then hit "apply to all". From this starting point I built my islands up from there, keeping the altitude in the range of -20 to 44m. Remember it can be pretty rough to begin with as you can gradually build up the terrain to suit your needs.

7. After a bit of experimenting I found that the altitude tools on the designmap at 512x768 was a bit limited, so i decided to double the size of the map to give me more accuracy. I chose Operations > Design Map > Resize Design map, and increased the size to 1024x1536 which generated a new larger scale design map derived from the orginal - you can immediately see the improvement in accuracy. You could have started with the large scale initially, but by starting small you lets L3DT do much of the hard work for you. As you can see i then further tweaked the map to get the features i wanted.

Note: I kept a border of -20m all around my terrain file, this was for ease of adding new regions later on

== Generating the Heightfield ==
[[Image:First_heightfield.jpg|100px|thumb|left|Exported image file]]

5. When you are happy with your design map, hit the calc button, choose Heightfield and watch l3DT do it's magic.

6. If it's not quite right, go back to your design map and tweak it, then hit calc again

7. When you think you nearly have it thats a good time to head over into the 3d view. The system uses roughly the same movement controls as OS so it's pretty easy to get to grips with. Here you can "fine tune" your terrain features to get it closer to what you are looking for. Mouse Tools > Edit Active Map.

[[Image:Editing in Sapphire.jpg|200px|thumb|left|Editing in Sapphire]]

8. Close Sapphire and then use File > Export > Active map, use .PNG format - at this point I resized back to 512x768

Using the grids and snapping in your editor comes in very handy. I then use guides to show where the final cuts will be. Tio speed things up you can use "slice along guides" when you export to get the files you need.

Step 8. '''Making OpenSimulator use the new textures.'''

You need to now tell OpenSimulator to use the new terrain textures on your grid. For example: if you have 4 regions called Region1, Region2, Region3 and Region4... you need to add a section to your startup_commands.txt that looks like this:

change-region Region1
terrain load path_to_textures/terrain_for_region1.png

change-region Region2
terrain load path_to_textures/terrain_for_region2.png

change-region Region3
terrain load path_to_textures/terrain_for_region3.png

change-region Region4
terrain load path_to_textures/terrain_for_region4.png

Note: you can also add Terrain commands here, but if you follow the instructions above you won't have to

Step 9. '''Restart your OpenSimulator instance and fine-tune your terrain height.'''

== Notes ==

When you have your new terrain files loaded - make sure you disable the startup_commands, as every time you restart your server your terrain files will be re-uploaded, removing any in-game terraforming you have done
[[Image:terrain_in_opensim.jpg|200px|thumb|left|Here is the region in OpenSimulator :)]]

File:Editing in Sapphire.jpg

2009-01-05T11:27:11Z

Max Ping:

Cross-region terrain making with L3DT

2009-01-05T11:26:51Z

Max Ping:

This tutorial has been put together from several sources on the web it is aimed at region operators who want to make detailed cross region terrains quickly and easily.

It describes the generation of the terrain files needed to seamlessly fill a 2x3 region. Obviously you can adapt it to fit your specific requirements. Designing a terrain map for a single region is relatively straightforward, however if you want your region to span across a number of regions we are faced with a few challenges. The main one is seam-matching, in other words getting the edge of one sim to match the edge of the next. The inbuilt terraforming tools are quite good in OpenSimulator, however they struggle on region boundaries - thus you end up with jagged edges where the regions meet.

To resolve this you need to create a larger terrain map and then split it into tiles.

There are two ways to do this, either draw it by hand using a graphics package, or use a terrain generating tool as a starting point. You can just use the terrain generator to get started quickly although in reality you will probably end up mixing both techniques. The manual technique has been well described by Fu Barr here: http://opensimulator.org/wiki/Terrain_making so i will focus on the easy way.

The principle reason why I wanted to start with a generated terrain is time - it takes a long time to draw your heightmap by hand so using the generator gives you a little kick start. It can also generate very realistic terrains which factor in things like age and erosion, in minutes rather than hours :)

Enjoy the tutorial and feel free to contribute/improve it -

[[Max Ping]]

== The Objective ==

My objective is to create a 6 region heightmap based on the idea of an ancient volcanic archipelago. Thus I wanted a few islands with nice curved stretches of beach, some cliffs and drop offs and a higher regions. I already had in mind roughly what i wanted so that was a good start. I personally like islands because you get lots of terrain variation and the sunsets in OpenSim can be... well stunning :) It's very useful to have an idea in your mind of what you want before you start...

== The Process ==

I used the L3DT Editor from Bundysoft, the standard edition is free and it does a great job of creating heightmaps, it generates nice and realisitc terrain- you can also drop in and fly around the terrain in a 3d view which will be familiar to OpenSimmers and great for previewing before you upload the regions. You can get the product here:

http://www.bundysoft.com/L3DT/downloads/standard.php

[[Image:Design map1.png|100px|thumb|left|First iteration of design map]][[Image:Design map2.png|100px|thumb|left|Second iteration of design map]]

== Generating your terrain files - The Design Map ==

The first thing you will generate is a design map - this is a "blocky" representation of the landmass which means you can rapidly paint your terrain before you actually apply the terrain calculation.

1. Click "New Map" and choose the "Design/inflate (blank)" Algorithm

2. My desired region size is 2x3, which is 512m x 768m. Note that I set the horizontal scale to 1m

3. I then used the default HF/DM ratio of 64 - this allows you to roughly plot your land mass

4. Now the fun begins :) Click the edit icon to bring up the Design map brush - there's lots you can do here - you just have to experiment with the brushes... Personally I found the easiest method was to simply ignore all the other brushes and focus on the altitude brush. The design map starts at sea level, so I set the altitude to "-20" then hit "apply to all". From this starting point I built my islands up from there, keeping the altitude in the range of -20 to 44m. Remember it can be pretty rough to begin with as you can gradually build up the terrain to suit your needs.

7. After a bit of experimenting I found that the altitude tools on the designmap at 512x768 was a bit limited, so i decided to double the size of the map to give me more accuracy. I chose Operations > Design Map > Resize Design map, and increased the size to 1024x1536 which generated a new larger scale design map derived from the orginal - you can immediately see the improvement in accuracy. You could have started with the large scale initially, but by starting small you lets L3DT do much of the hard work for you. As you can see i then further tweaked the map to get the features i wanted.

Note: I kept a border of -20m all around my terrain file, this was for ease of adding new regions later on

== Generating the Heightfield ==
[[Image:First_heightfield.jpg|100px|thumb|left|Exported image file]]

5. When you are happy with your design map, hit the calc button, choose Heightfield and watch l3DT do it's magic.

6. If it's not quite right, go back to your design map and tweak it, then hit calc again

7. When you think you nearly have it thats a good time to head over into the 3d view. The system uses roughly the same movement controls as OS so it's pretty easy to get to grips with. Here you can "fine tune" your terrain features to get it closer to what you are looking for. Mouse Tools > Edit Active Map.

[[Image:Editing in Sapphire.jpg|200px|thumb|left|Editing in Sapphire]]

8. Close Sapphire and then use File > Export > Active map, use .PNG format - at this point I resized back to 512x768

Using the grids and snapping in your editor comes in very handy. I then use guides to show where the final cuts will be. Tio speed things up you can use "slice along guides" when you export to get the files you need.

Step 8. '''Making OpenSimulator use the new textures.'''

You need to now tell OpenSimulator to use the new terrain textures on your grid. For example: if you have 4 regions called Region1, Region2, Region3 and Region4... you need to add a section to your startup_commands.txt that looks like this:

change-region Region1
terrain load path_to_textures/terrain_for_region1.png

change-region Region2
terrain load path_to_textures/terrain_for_region2.png

change-region Region3
terrain load path_to_textures/terrain_for_region3.png

change-region Region4
terrain load path_to_textures/terrain_for_region4.png

Note: you can also add Terrain commands here, but if you follow the instructions above you won't have to

Step 9. '''Restart your OpenSimulator instance and fine-tune your terrain height.'''

== Notes ==

When you have your new terrain files loaded - make sure you disable the startup_commands, as every time you restart your server your terrain files will be re-uploaded, removing any in-game terraforming you have done

Cross-region terrain making with L3DT

2009-01-05T11:23:02Z

Max Ping: /* Generating your terrain files - The Design Map */

This tutorial has been put together from several sources on the web it is aimed at region operators who want to make detailed cross region terrains quickly and easily.

It describes the generation of the terrain files needed to seamlessly fill a 2x3 region. Obviously you can adapt it to fit your specific requirements. Designing a terrain map for a single region is relatively straightforward, however if you want your region to span across a number of regions we are faced with a few challenges. The main one is seam-matching, in other words getting the edge of one sim to match the edge of the next. The inbuilt terraforming tools are quite good in OpenSimulator, however they struggle on region boundaries - thus you end up with jagged edges where the regions meet.

To resolve this you need to create a larger terrain map and then split it into tiles.

There are two ways to do this, either draw it by hand using a graphics package, or use a terrain generating tool as a starting point. You can just use the terrain generator to get started quickly although in reality you will probably end up mixing both techniques. The manual technique has been well described by Fu Barr here: http://opensimulator.org/wiki/Terrain_making so i will focus on the easy way.

The principle reason why I wanted to start with a generated terrain is time - it takes a long time to draw your heightmap by hand so using the generator gives you a little kick start. It can also generate very realistic terrains which factor in things like age and erosion, in minutes rather than hours :)

Enjoy the tutorial and feel free to contribute/improve it -

[[Max Ping]]

== The Objective ==

My objective is to create a 6 region heightmap based on the idea of an ancient volcanic archipelago. Thus I wanted a few islands with nice curved stretches of beach, some cliffs and drop offs and a higher regions. I already had in mind roughly what i wanted so that was a good start. I personally like islands because you get lots of terrain variation and the sunsets in OpenSim can be... well stunning :) It's very useful to have an idea in your mind of what you want before you start...

== The Process ==

I used the L3DT Editor from Bundysoft, the standard edition is free and it does a great job of creating heightmaps, it generates nice and realisitc terrain- you can also drop in and fly around the terrain in a 3d view which will be familiar to OpenSimmers and great for previewing before you upload the regions. You can get the product here:

http://www.bundysoft.com/L3DT/downloads/standard.php

[[Image:Design map1.png|150px|thumb|left|First iteration of design map]][[Image:Design map2.png|150px|thumb|left|Second iteration of design map]]

== Generating your terrain files - The Design Map ==

The first thing you will generate is a design map - this is a "blocky" representation of the landmass which means you can rapidly paint your terrain before you actually apply the terrain calculation.

1. Click "New Map" and choose the "Design/inflate (blank)" Algorithm

2. My desired region size is 2x3, which is 512m x 768m. Note that I set the horizontal scale to 1m

3. I then used the default HF/DM ratio of 64 - this allows you to roughly plot your land mass

4. Now the fun begins :) Click the edit icon to bring up the Design map brush - there's lots you can do here - you just have to experiment with the brushes... Personally I found the easiest method was to simply ignore all the other brushes and focus on the altitude brush. The design map starts at sea level, so I set the altitude to "-20" then hit "apply to all". From this starting point I built my islands up from there, keeping the altitude in the range of -20 to 44m. Remember it can be pretty rough to begin with as you can gradually build up the terrain to suit your needs.

7. After a bit of experimenting I found that the altitude tools on the designmap at 512x768 was a bit limited, so i decided to double the size of the map to give me more accuracy. I chose Operations > Design Map > Resize Design map, and increased the size to 1024x1536 which generated a new larger scale design map derived from the orginal - you can immediately see the improvement in accuracy. You could have started with the large scale initially, but by starting small you lets L3DT do much of the hard work for you. As you can see i then further tweaked the map to get the features i wanted.

Note: I kept a border of -20m all around my terrain file, this was for ease of adding new regions later on

== Generating the Heightfield ==
[[Image:First_heightfield.jpg|150px|thumb|left|Exported image file]]

5. When you are happy with your design map, hit the calc button, choose Heightfield and watch l3DT do it's magic.

6. If it's not quite right, go back to your design map and tweak it, then hit calc again

7. When you think you nearly have it thats a good time to head over into the 3d view. The system uses roughly the same movement controls as OS so it's pretty easy to get to grips with. Here you can "fine tune" your terrain features to get it closer to what you are looking for. Mouse Tools > Edit Active Map.

8. Close Sapphire and then use File > Export > Active map, use .PNG format - at this point I resized back to 512x768

Using the grids and snapping in your editor comes in very handy. I then use guides to show where the final cuts will be. Tio speed things up you can use "slice along guides" when you export to get the files you need.

Step 8. '''Making OpenSimulator use the new textures.'''

You need to now tell OpenSimulator to use the new terrain textures on your grid. For example: if you have 4 regions called Region1, Region2, Region3 and Region4... you need to add a section to your startup_commands.txt that looks like this:

change-region Region1
terrain load path_to_textures/terrain_for_region1.png

change-region Region2
terrain load path_to_textures/terrain_for_region2.png

change-region Region3
terrain load path_to_textures/terrain_for_region3.png

change-region Region4
terrain load path_to_textures/terrain_for_region4.png

Note: you can also add Terrain commands here, but if you follow the instructions above you won't have to

Step 9. '''Restart your OpenSimulator instance and fine-tune your terrain height.'''

== Notes ==

When you have your new terrain files loaded - make sure you disable the startup_commands, as every time you restart your server your terrain files will be re-uploaded, removing any in-game terraforming you have done

Cross-region terrain making with L3DT

2009-01-05T11:21:04Z

Max Ping: /* Generating the Heightfield */

This tutorial has been put together from several sources on the web it is aimed at region operators who want to make detailed cross region terrains quickly and easily.

It describes the generation of the terrain files needed to seamlessly fill a 2x3 region. Obviously you can adapt it to fit your specific requirements. Designing a terrain map for a single region is relatively straightforward, however if you want your region to span across a number of regions we are faced with a few challenges. The main one is seam-matching, in other words getting the edge of one sim to match the edge of the next. The inbuilt terraforming tools are quite good in OpenSimulator, however they struggle on region boundaries - thus you end up with jagged edges where the regions meet.

To resolve this you need to create a larger terrain map and then split it into tiles.

There are two ways to do this, either draw it by hand using a graphics package, or use a terrain generating tool as a starting point. You can just use the terrain generator to get started quickly although in reality you will probably end up mixing both techniques. The manual technique has been well described by Fu Barr here: http://opensimulator.org/wiki/Terrain_making so i will focus on the easy way.

The principle reason why I wanted to start with a generated terrain is time - it takes a long time to draw your heightmap by hand so using the generator gives you a little kick start. It can also generate very realistic terrains which factor in things like age and erosion, in minutes rather than hours :)

Enjoy the tutorial and feel free to contribute/improve it -

[[Max Ping]]

== The Objective ==

My objective is to create a 6 region heightmap based on the idea of an ancient volcanic archipelago. Thus I wanted a few islands with nice curved stretches of beach, some cliffs and drop offs and a higher regions. I already had in mind roughly what i wanted so that was a good start. I personally like islands because you get lots of terrain variation and the sunsets in OpenSim can be... well stunning :) It's very useful to have an idea in your mind of what you want before you start...

== The Process ==

I used the L3DT Editor from Bundysoft, the standard edition is free and it does a great job of creating heightmaps, it generates nice and realisitc terrain- you can also drop in and fly around the terrain in a 3d view which will be familiar to OpenSimmers and great for previewing before you upload the regions. You can get the product here:

http://www.bundysoft.com/L3DT/downloads/standard.php

== Generating your terrain files - The Design Map ==

[[Image:Design map1.png|150px|thumb|left|First iteration of design map]][[Image:Design map2.png|150px|thumb|left|Second iteration of design map]]

The first thing you will generate is a design map - this is a "blocky" representation of the landmass which means you can rapidly paint your terrain before you actually apply the terrain calculation.

1. Click "New Map" and choose the "Design/inflate (blank)" Algorithm

2. My desired region size is 2x3, which is 512m x 768m. Note that I set the horizontal scale to 1m

3. I then used the default HF/DM ratio of 64 - this allows you to roughly plot your land mass

4. Now the fun begins :) Click the edit icon to bring up the Design map brush - there's lots you can do here - you just have to experiment with the brushes... Personally I found the easiest method was to simply ignore all the other brushes and focus on the altitude brush. The design map starts at sea level, so I set the altitude to "-20" then hit "apply to all". From this starting point I built my islands up from there, keeping the altitude in the range of -20 to 44m. Remember it can be pretty rough to begin with as you can gradually build up the terrain to suit your needs.

7. After a bit of experimenting I found that the altitude tools on the designmap at 512x768 was a bit limited, so i decided to double the size of the map to give me more accuracy. I chose Operations > Design Map > Resize Design map, and increased the size to 1024x1536 which generated a new larger scale design map derived from the orginal - you can immediately see the improvement in accuracy. You could have started with the large scale initially, but by starting small you lets L3DT do much of the hard work for you. As you can see i then further tweaked the map to get the features i wanted.

Note: I kept a border of -20m all around my terrain file, this was for ease of adding new regions later on

== Generating the Heightfield ==
[[Image:First_heightfield.jpg|150px|thumb|left|Exported image file]]

5. When you are happy with your design map, hit the calc button, choose Heightfield and watch l3DT do it's magic.

6. If it's not quite right, go back to your design map and tweak it, then hit calc again

7. When you think you nearly have it thats a good time to head over into the 3d view. The system uses roughly the same movement controls as OS so it's pretty easy to get to grips with. Here you can "fine tune" your terrain features to get it closer to what you are looking for. Mouse Tools > Edit Active Map.

8. Close Sapphire and then use File > Export > Active map, use .PNG format - at this point I resized back to 512x768

Using the grids and snapping in your editor comes in very handy. I then use guides to show where the final cuts will be. Tio speed things up you can use "slice along guides" when you export to get the files you need.

Step 8. '''Making OpenSimulator use the new textures.'''

You need to now tell OpenSimulator to use the new terrain textures on your grid. For example: if you have 4 regions called Region1, Region2, Region3 and Region4... you need to add a section to your startup_commands.txt that looks like this:

change-region Region1
terrain load path_to_textures/terrain_for_region1.png

change-region Region2
terrain load path_to_textures/terrain_for_region2.png

change-region Region3
terrain load path_to_textures/terrain_for_region3.png

change-region Region4
terrain load path_to_textures/terrain_for_region4.png

Note: you can also add Terrain commands here, but if you follow the instructions above you won't have to

Step 9. '''Restart your OpenSimulator instance and fine-tune your terrain height.'''

== Notes ==

When you have your new terrain files loaded - make sure you disable the startup_commands, as every time you restart your server your terrain files will be re-uploaded, removing any in-game terraforming you have done

File:First heightfield.jpg

2009-01-05T11:19:59Z

Max Ping:

Cross-region terrain making with L3DT

2009-01-05T11:18:41Z

Max Ping: /* Generating your terrain files */

This tutorial has been put together from several sources on the web it is aimed at region operators who want to make detailed cross region terrains quickly and easily.

It describes the generation of the terrain files needed to seamlessly fill a 2x3 region. Obviously you can adapt it to fit your specific requirements. Designing a terrain map for a single region is relatively straightforward, however if you want your region to span across a number of regions we are faced with a few challenges. The main one is seam-matching, in other words getting the edge of one sim to match the edge of the next. The inbuilt terraforming tools are quite good in OpenSimulator, however they struggle on region boundaries - thus you end up with jagged edges where the regions meet.

To resolve this you need to create a larger terrain map and then split it into tiles.

There are two ways to do this, either draw it by hand using a graphics package, or use a terrain generating tool as a starting point. You can just use the terrain generator to get started quickly although in reality you will probably end up mixing both techniques. The manual technique has been well described by Fu Barr here: http://opensimulator.org/wiki/Terrain_making so i will focus on the easy way.

The principle reason why I wanted to start with a generated terrain is time - it takes a long time to draw your heightmap by hand so using the generator gives you a little kick start. It can also generate very realistic terrains which factor in things like age and erosion, in minutes rather than hours :)

Enjoy the tutorial and feel free to contribute/improve it -

[[Max Ping]]

== The Objective ==

My objective is to create a 6 region heightmap based on the idea of an ancient volcanic archipelago. Thus I wanted a few islands with nice curved stretches of beach, some cliffs and drop offs and a higher regions. I already had in mind roughly what i wanted so that was a good start. I personally like islands because you get lots of terrain variation and the sunsets in OpenSim can be... well stunning :) It's very useful to have an idea in your mind of what you want before you start...

== The Process ==

I used the L3DT Editor from Bundysoft, the standard edition is free and it does a great job of creating heightmaps, it generates nice and realisitc terrain- you can also drop in and fly around the terrain in a 3d view which will be familiar to OpenSimmers and great for previewing before you upload the regions. You can get the product here:

http://www.bundysoft.com/L3DT/downloads/standard.php

== Generating your terrain files - The Design Map ==

[[Image:Design map1.png|150px|thumb|left|First iteration of design map]][[Image:Design map2.png|150px|thumb|left|Second iteration of design map]]

The first thing you will generate is a design map - this is a "blocky" representation of the landmass which means you can rapidly paint your terrain before you actually apply the terrain calculation.

1. Click "New Map" and choose the "Design/inflate (blank)" Algorithm

2. My desired region size is 2x3, which is 512m x 768m. Note that I set the horizontal scale to 1m

3. I then used the default HF/DM ratio of 64 - this allows you to roughly plot your land mass

4. Now the fun begins :) Click the edit icon to bring up the Design map brush - there's lots you can do here - you just have to experiment with the brushes... Personally I found the easiest method was to simply ignore all the other brushes and focus on the altitude brush. The design map starts at sea level, so I set the altitude to "-20" then hit "apply to all". From this starting point I built my islands up from there, keeping the altitude in the range of -20 to 44m. Remember it can be pretty rough to begin with as you can gradually build up the terrain to suit your needs.

7. After a bit of experimenting I found that the altitude tools on the designmap at 512x768 was a bit limited, so i decided to double the size of the map to give me more accuracy. I chose Operations > Design Map > Resize Design map, and increased the size to 1024x1536 which generated a new larger scale design map derived from the orginal - you can immediately see the improvement in accuracy. You could have started with the large scale initially, but by starting small you lets L3DT do much of the hard work for you. As you can see i then further tweaked the map to get the features i wanted.

Note: I kept a border of -20m all around my terrain file, this was for ease of adding new regions later on

== Generating the Heightfield ==
[[Image:heightfield.png|150px|thumb|left|Exported image file]]

5. When you are happy with your design map, hit the calc button, choose Heightfield and watch l3DT do it's magic.

6. If it's not quite right, go back to your design map and tweak it, then hit calc again

7. When you think you nearly have it thats a good time to head over into the 3d view. The system uses roughly the same movement controls as OS so it's pretty easy to get to grips with. Here you can "fine tune" your terrain features to get it closer to what you are looking for. Mouse Tools > Edit Active Map.

8. Close Sapphire and then use File > Export > Active map, use .PNG format - at this point I resized back to 512x768

Using the grids and snapping in your editor comes in very handy. I then use guides to show where the final cuts will be. Tio speed things up you can use "slice along guides" when you export to get the files you need.

Step 8. '''Making OpenSimulator use the new textures.'''

You need to now tell OpenSimulator to use the new terrain textures on your grid. For example: if you have 4 regions called Region1, Region2, Region3 and Region4... you need to add a section to your startup_commands.txt that looks like this:

change-region Region1
terrain load path_to_textures/terrain_for_region1.png

change-region Region2
terrain load path_to_textures/terrain_for_region2.png

change-region Region3
terrain load path_to_textures/terrain_for_region3.png

change-region Region4
terrain load path_to_textures/terrain_for_region4.png

Note: you can also add Terrain commands here, but if you follow the instructions above you won't have to

Step 9. '''Restart your OpenSimulator instance and fine-tune your terrain height.'''

== Notes ==

When you have your new terrain files loaded - make sure you disable the startup_commands, as every time you restart your server your terrain files will be re-uploaded, removing any in-game terraforming you have done

Cross-region terrain making with L3DT

2009-01-05T11:10:08Z

Max Ping:

This tutorial has been put together from several sources on the web it is aimed at region operators who want to make detailed cross region terrains quickly and easily.

It describes the generation of the terrain files needed to seamlessly fill a 2x3 region. Obviously you can adapt it to fit your specific requirements. Designing a terrain map for a single region is relatively straightforward, however if you want your region to span across a number of regions we are faced with a few challenges. The main one is seam-matching, in other words getting the edge of one sim to match the edge of the next. The inbuilt terraforming tools are quite good in OpenSimulator, however they struggle on region boundaries - thus you end up with jagged edges where the regions meet.

To resolve this you need to create a larger terrain map and then split it into tiles.

There are two ways to do this, either draw it by hand using a graphics package, or use a terrain generating tool as a starting point. You can just use the terrain generator to get started quickly although in reality you will probably end up mixing both techniques. The manual technique has been well described by Fu Barr here: http://opensimulator.org/wiki/Terrain_making so i will focus on the easy way.

The principle reason why I wanted to start with a generated terrain is time - it takes a long time to draw your heightmap by hand so using the generator gives you a little kick start. It can also generate very realistic terrains which factor in things like age and erosion, in minutes rather than hours :)

Enjoy the tutorial and feel free to contribute/improve it -

[[Max Ping]]

== The Objective ==

My objective is to create a 6 region heightmap based on the idea of an ancient volcanic archipelago. Thus I wanted a few islands with nice curved stretches of beach, some cliffs and drop offs and a higher regions. I already had in mind roughly what i wanted so that was a good start. I personally like islands because you get lots of terrain variation and the sunsets in OpenSim can be... well stunning :) It's very useful to have an idea in your mind of what you want before you start...

== The Process ==

I used the L3DT Editor from Bundysoft, the standard edition is free and it does a great job of creating heightmaps, it generates nice and realisitc terrain- you can also drop in and fly around the terrain in a 3d view which will be familiar to OpenSimmers and great for previewing before you upload the regions. You can get the product here:

http://www.bundysoft.com/L3DT/downloads/standard.php

== Generating your terrain files ==

The first thing you will generate is a design map - this is a "blocky" representation of the landmass which means you can rapidly paint your terrain before you actually apply the terrain calculation.

[[Image:Design map1.png|150px|thumb|right|First iteration of design map]][[Image:Design map2.png|150px|thumb|right|Second iteration of design map]]

1. Click "New Map" and choose the "Design/inflate (blank)" Algorithm

2. My desired region size is 2x3, which is 512m x 768m. Note that I set the horizontal scale to 1m

3. I then used the default HF/DM ratio of 64 - this allows you to roughly plot your land mass

4. Now the fun begins :) Click the edit icon to bring up the Design map brush - there's lots you can do here - you just have to experiment with the brushes... Personally I found the easiest method was to simply ignore all the other brushes and focus on the altitude brush. The design map starts at sea level, so I set the altitude to "-20" then hit "apply to all". From this starting point I built my islands up from there, keeping the altitude in the range of -20 to 44m. Remember it can be pretty rough to begin with as you can gradually build up the terrain to suit your needs.

5. When you are happy with your design map, hit the calc button, choose Heightfield and watch l3DT do it's magic.

6. If it's not quite right, go back to your design map and tweak it, then hit calc again

7. After a bit of experimenting I found that the altitude tools on the designmap at 512x768 was a bit limited, so i decided to double the size of the map to give me more accuracy. I chose Operations > Design Map > Resize Design map, and increased the size to 1024x1536 which generated a new larger scale design map derived from the orginal - you can immediately see the improvement in accuracy. You could have started with the large scale initially, but by starting small you lets L3DT do much of the hard work for you. As you can see i then further tweaked the map to get the features i wanted.

Note I kept a border of -20m all around my terrain file, this was for ease of adding new regions later on

7. When you think you nearly have it thats a good time to head over into the 3d view. The system uses roughly the same movement controls as OS so it's pretty easy to get to grips with. Here you can "fine tune" your terrain features to get it closer to what you are looking for. Mouse Tools > Edit Active Map.

8. Close Sapphire and then use File > Export > Active map, use .PNG format - at this point I resized back to 512x768

5. Leave design map checked and hit OK

The first thing L3DT will generate is a design map - this is a blocky representation of what will be calcualted but it gives you a good idea of what the results will be before you actually apply the terrain calculation.

You may need to generate your initial terrain several times until you get something that looks close to what you desire, you can also generate several terrains and then mash them together later in a graphics package

Once you are happy, choose "CALC" and "Heightfield" - this then generates an accurate terrain file.

Then choose File > Export > Export Map > Heightfield and choose .PNG format ( way easier than messing around with RAW files)
Now you can choose to simply cut this png, or in my case I offset the png so that I could position it better in the 9x9 grid (remeber why I chose edge wrapping?). Basically you double the canvas size, then copy the heightfile. Using the grids and snapping in your editor comes in very handy. I then use guides to show where the final cuts will be. Tio speed things up you can use "slice along guides" when you export to get the files you need.

Step 8. '''Making OpenSimulator use the new textures.'''

You need to now tell OpenSimulator to use the new terrain textures on your grid. For example: if you have 4 regions called Region1, Region2, Region3 and Region4... you need to add a section to your startup_commands.txt that looks like this:

change-region Region1
terrain load path_to_textures/terrain_for_region1.png

change-region Region2
terrain load path_to_textures/terrain_for_region2.png

change-region Region3
terrain load path_to_textures/terrain_for_region3.png

change-region Region4
terrain load path_to_textures/terrain_for_region4.png

Step 9. '''Restart your OpenSimulator instance and fine-tune your terrain height.'''

== Notes ==

When you have your new terrain files loaded - make sure you disable the startup_commands, as every time you restart your server your terrain files will be re-uploaded, removing any in-game terraforming you have done

Cross-region terrain making with L3DT

2009-01-05T11:04:49Z

Max Ping:

This tutorial has been put together from several sources on the web it is aimed at region operators who want to make detailed cross region terrains quickly and easily.

It describes the generation of the terrain files needed to seamlessly fill a 2x3 region. Obviously you can adapt it to fit your specific requirements. Designing a terrain map for a single region is relatively straightforward, however if you want your region to span across a number of regions we are faced with a few challenges. The main one is seam-matching, in other words getting the edge of one sim to match the edge of the next. The inbuilt terraforming tools are quite good in OpenSimulator, however they struggle on region boundaries - thus you end up with jagged edges where the regions meet.

To resolve this you need to create a larger terrain map and then split it into tiles.

There are two ways to do this, either draw it by hand using a graphics package, or use a terrain generating tool as a starting point. You can just use the terrain generator to get started quickly although in reality you will probably end up mixing both techniques. The manual technique has been well described by Fu Barr here: http://opensimulator.org/wiki/Terrain_making so i will focus on the easy way.

The principle reason why I wanted to start with a generated terrain is time - it takes a long time to draw your heightmap by hand so using the generator gives you a little kick start. It can also generate very realistic terrains which factor in things like age and erosion, in minutes rather than hours :)

Enjoy the tutorial and feel free to contribute/improve it -

[[Max Ping]]

== The Objective ==

My objective is to create a 6 region heightmap based on the idea of an ancient volcanic archipelago. Thus I wanted a few islands with nice curved stretches of beach, some cliffs and drop offs and a higher regions. I already had in mind roughly what i wanted so that was a good start. I personally like islands because you get lots of terrain variation and the sunsets in OpenSim can be... well stunning :) It's very useful to have an idea in your mind of what you want before you start...

== The Process ==

I used the L3DT Editor from Bundysoft, the standard edition is free and it does a great job of creating heightmaps, it generates nice and realisitc terrain- you can also drop in and fly around the terrain in a 3d view which will be familiar to OpenSimmers and great for previewing before you upload the regions. You can get the product here:

http://www.bundysoft.com/L3DT/downloads/standard.php

== Generating your terrain files ==

The first thing you will generate is a design map - this is a "blocky" representation of the landmass which means you can rapidly paint your terrain before you actually apply the terrain calculation.

1. Click "New Map" and choose the "Design/inflate (blank)" Algorithm
2. My desired region size is 2x3, which is 512m x 768m. Note that I set the horizontal scale to 1m
3. I then used the default HF/DM ratio of 64 - this allows you to roughly plot your land mass

4. Now the fun begins :) Click the edit icon to bring up the Design map brush - there's lots you can do here - you just have to experiment with the brushes... Personally I found the easiest method was to simply ignore all the other brushes and focus on the altitude brush. The design map starts at sea level, so I set the altitude to "-20" then hit "apply to all". From this starting point I built my islands up from there, keeping the altitude in the range of -20 to 44m. Remember it can be pretty rough to begin with as you can gradually build up the terrain to suit your needs.
[[Image:Design map1.png|100px|thumb|right|First iteration of design map]]
[[Image:Design map2.png|100px|thumb|right|Second iteration of design map]]

5. When you are happy with your design map, hit the calc button, choose Heightfield and watch l3DT do it's magic.

6. If it's not quite right, go back to your design map and tweak it, then hit calc again

7. After a bit of experimenting I found that the altitude tools on the designmap at 512x768 was a bit limited, so i decided to double the size of the map to give me more accuracy. I chose Operations > Design Map > Resize Design map, and increased the size to 1024x1536 which generated a new larger scale design map derived from the orginal - you can immediately see the improvement in accuracy. You could have started with the large scale initially, but by starting small you lets L3DT do much of the hard work for you. As you can see i then further tweaked the map to get the features i wanted.

Note I kept a border of -20m all around my terrain file, this was for ease of adding new regions later on

7. When you think you nearly have it thats a good time to head over into the 3d view. The system uses roughly the same movement controls as OS so it's pretty easy to get to grips with. Here you can "fine tune" your terrain features to get it closer to what you are looking for. Mouse Tools > Edit Active Map.

8. Close Sapphire and then use File > Export > Active map, use .PNG format - at this point I resized back to 512x768

5. Leave design map checked and hit OK

The first thing L3DT will generate is a design map - this is a blocky representation of what will be calcualted but it gives you a good idea of what the results will be before you actually apply the terrain calculation.

You may need to generate your initial terrain several times until you get something that looks close to what you desire, you can also generate several terrains and then mash them together later in a graphics package

Once you are happy, choose "CALC" and "Heightfield" - this then generates an accurate terrain file.

Then choose File > Export > Export Map > Heightfield and choose .PNG format ( way easier than messing around with RAW files)
Now you can choose to simply cut this png, or in my case I offset the png so that I could position it better in the 9x9 grid (remeber why I chose edge wrapping?). Basically you double the canvas size, then copy the heightfile. Using the grids and snapping in your editor comes in very handy. I then use guides to show where the final cuts will be. Tio speed things up you can use "slice along guides" when you export to get the files you need.

Step 8. '''Making OpenSimulator use the new textures.'''

You need to now tell OpenSimulator to use the new terrain textures on your grid. For example: if you have 4 regions called Region1, Region2, Region3 and Region4... you need to add a section to your startup_commands.txt that looks like this:

change-region Region1
terrain load path_to_textures/terrain_for_region1.png

change-region Region2
terrain load path_to_textures/terrain_for_region2.png

change-region Region3
terrain load path_to_textures/terrain_for_region3.png

change-region Region4
terrain load path_to_textures/terrain_for_region4.png

Step 9. '''Restart your OpenSimulator instance and fine-tune your terrain height.'''

== Notes ==

When you have your new terrain files loaded - make sure you disable the startup_commands, as every time you restart your server your terrain files will be re-uploaded, removing any in-game terraforming you have done

File:Design map2.png

2009-01-05T11:03:21Z

Max Ping:

Cross-region terrain making with L3DT

2009-01-05T11:02:52Z

Max Ping:

This tutorial has been put together from several sources on the web it is aimed at region operators who want to make detailed cross region terrains quickly and easily.

It describes the generation of the terrain files needed to seamlessly fill a 2x3 region. Obviously you can adapt it to fit your specific requirements. Designing a terrain map for a single region is relatively straightforward, however if you want your region to span across a number of regions we are faced with a few challenges. The main one is seam-matching, in other words getting the edge of one sim to match the edge of the next. The inbuilt terraforming tools are quite good in OpenSimulator, however they struggle on region boundaries - thus you end up with jagged edges where the regions meet.

To resolve this you need to create a larger terrain map and then split it into tiles.

There are two ways to do this, either draw it by hand using a graphics package, or use a terrain generating tool as a starting point. You can just use the terrain generator to get started quickly although in reality you will probably end up mixing both techniques. The manual technique has been well described by Fu Barr here: http://opensimulator.org/wiki/Terrain_making so i will focus on the easy way.

The principle reason why I wanted to start with a generated terrain is time - it takes a long time to draw your heightmap by hand so using the generator gives you a little kick start. It can also generate very realistic terrains which factor in things like age and erosion, in minutes rather than hours :)

Enjoy the tutorial and feel free to contribute/improve it -

[[Max Ping]]

== The Objective ==

My objective is to create a 6 region heightmap based on the idea of an ancient volcanic archipelago. Thus I wanted a few islands with nice curved stretches of beach, some cliffs and drop offs and a higher regions. I already had in mind roughly what i wanted so that was a good start. I personally like islands because you get lots of terrain variation and the sunsets in OpenSim can be... well stunning :) It's very useful to have an idea in your mind of what you want before you start...

== The Process ==

I used the L3DT Editor from Bundysoft, the standard edition is free and it does a great job of creating heightmaps, it generates nice and realisitc terrain- you can also drop in and fly around the terrain in a 3d view which will be familiar to OpenSimmers and great for previewing before you upload the regions. You can get the product here:

http://www.bundysoft.com/L3DT/downloads/standard.php

== Generating your terrain files ==

The first thing you will generate is a design map - this is a "blocky" representation of the landmass which means you can rapidly paint your terrain before you actually apply the terrain calculation.

1. Click "New Map" and choose the "Design/inflate (blank)" Algorithm
2. My desired region size is 2x3, which is 512m x 768m. Note that I set the horizontal scale to 1m
3. I then used the default HF/DM ratio of 64 - this allows you to roughly plot your land mass

4. Now the fun begins :) Click the edit icon to bring up the Design map brush - there's lots you can do here - you just have to experiment with the brushes... Personally I found the easiest method was to simply ignore all the other brushes and focus on the altitude brush. The design map starts at sea level, so I set the altitude to "-20" then hit "apply to all". From this starting point I built my islands up from there, keeping the altitude in the range of -20 to 44m. Remember it can be pretty rough to begin with as you can gradually build up the terrain to suit your needs. [[Image:Design map1.png|200px|thumb|left|First iteration of design map]]

5. When you are happy with your design map, hit the calc button, choose Heightfield and watch l3DT do it's magic.

6. If it's not quite right, go back to your design map and tweak it, then hit calc again

7. After a bit of experimenting I found that the altitude tools on the designmap at 512x768 was a bit limited, so i decided to double the size of the map to give me more accuracy. I chose Operations > Design Map > Resize Design map, and increased the size to 1024x1536 which generated a new larger scale design map derived from the orginal - you can immediately see the improvement in accuracy. You could have started with the large scale initially, but by starting small you lets L3DT do much of the hard work for you. As you can see i then further tweaked the map to get the features i wanted.[[Image:Design map2.png|200px|thumb|left|Second iteration of design map]]

Note I kept a border of -20m all around my terrain file, this was for ease of adding new regions later on

7. When you think you nearly have it thats a good time to head over into the 3d view. The system uses roughly the same movement controls as OS so it's pretty easy to get to grips with. Here you can "fine tune" your terrain features to get it closer to what you are looking for. Mouse Tools > Edit Active Map.

8. Close Sapphire and then use File > Export > Active map, use .PNG format - at this point I resized back to 512x768

5. Leave design map checked and hit OK

The first thing L3DT will generate is a design map - this is a blocky representation of what will be calcualted but it gives you a good idea of what the results will be before you actually apply the terrain calculation.

You may need to generate your initial terrain several times until you get something that looks close to what you desire, you can also generate several terrains and then mash them together later in a graphics package

Once you are happy, choose "CALC" and "Heightfield" - this then generates an accurate terrain file.

Then choose File > Export > Export Map > Heightfield and choose .PNG format ( way easier than messing around with RAW files)
Now you can choose to simply cut this png, or in my case I offset the png so that I could position it better in the 9x9 grid (remeber why I chose edge wrapping?). Basically you double the canvas size, then copy the heightfile. Using the grids and snapping in your editor comes in very handy. I then use guides to show where the final cuts will be. Tio speed things up you can use "slice along guides" when you export to get the files you need.

Step 8. '''Making OpenSimulator use the new textures.'''

You need to now tell OpenSimulator to use the new terrain textures on your grid. For example: if you have 4 regions called Region1, Region2, Region3 and Region4... you need to add a section to your startup_commands.txt that looks like this:

change-region Region1
terrain load path_to_textures/terrain_for_region1.png

change-region Region2
terrain load path_to_textures/terrain_for_region2.png

change-region Region3
terrain load path_to_textures/terrain_for_region3.png

change-region Region4
terrain load path_to_textures/terrain_for_region4.png

Step 9. '''Restart your OpenSimulator instance and fine-tune your terrain height.'''

== Notes ==

When you have your new terrain files loaded - make sure you disable the startup_commands, as every time you restart your server your terrain files will be re-uploaded, removing any in-game terraforming you have done

File:Design map1.png

2009-01-05T11:01:31Z

Max Ping:

Cross-region terrain making with L3DT

2009-01-05T11:00:49Z

Max Ping:

This tutorial has been put together from several sources on the web it is aimed at region operators who want to make detailed cross region terrains quickly and easily.

It describes the generation of the terrain files needed to seamlessly fill a 2x3 region. Obviously you can adapt it to fit your specific requirements. Designing a terrain map for a single region is relatively straightforward, however if you want your region to span across a number of regions we are faced with a few challenges. The main one is seam-matching, in other words getting the edge of one sim to match the edge of the next. The inbuilt terraforming tools are quite good in OpenSimulator, however they struggle on region boundaries - thus you end up with jagged edges where the regions meet.

To resolve this you need to create a larger terrain map and then split it into tiles.

There are two ways to do this, either draw it by hand using a graphics package, or use a terrain generating tool as a starting point. You can just use the terrain generator to get started quickly although in reality you will probably end up mixing both techniques. The manual technique has been well described by Fu Barr here: http://opensimulator.org/wiki/Terrain_making so i will focus on the easy way.

The principle reason why I wanted to start with a generated terrain is time - it takes a long time to draw your heightmap by hand so using the generator gives you a little kick start. It can also generate very realistic terrains which factor in things like age and erosion, in minutes rather than hours :)

Enjoy the tutorial and feel free to contribute/improve it -

[[Max Ping]]

== The Objective ==

My objective is to create a 6 region heightmap based on the idea of an ancient volcanic archipelago. Thus I wanted a few islands with nice curved stretches of beach, some cliffs and drop offs and a higher regions. I already had in mind roughly what i wanted so that was a good start. I personally like islands because you get lots of terrain variation and the sunsets in OpenSim can be... well stunning :) It's very useful to have an idea in your mind of what you want before you start...

== The Process ==

I used the L3DT Editor from Bundysoft, the standard edition is free and it does a great job of creating heightmaps, it generates nice and realisitc terrain- you can also drop in and fly around the terrain in a 3d view which will be familiar to OpenSimmers and great for previewing before you upload the regions. You can get the product here:

http://www.bundysoft.com/L3DT/downloads/standard.php

== Generating your terrain files ==

The first thing you will generate is a design map - this is a "blocky" representation of the landmass which means you can rapidly paint your terrain before you actually apply the terrain calculation.

1. Click "New Map" and choose the "Design/inflate (blank)" Algorithm
2. My desired region size is 2x3, which is 512m x 768m. Note that I set the horizontal scale to 1m
3. I then used the default HF/DM ratio of 64 - this allows you to roughly plot your land mass

4. Now the fun begins :) Click the edit icon to bring up the Design map brush - there's lots you can do here - you just have to experiment with the brushes... Personally I found the easiest method was to simply ignore all the other brushes and focus on the altitude brush. The design map starts at sea level, so I set the altitude to "-20" then hit "apply to all". From this starting point I built my islands up from there, keeping the altitude in the range of -20 to 44m. Remember it can be pretty rough to begin with as you can gradually build up the terrain to suit your needs. [[Image:design_map.png]]

5. When you are happy with your design map, hit the calc button, choose Heightfield and watch l3DT do it's magic.

6. If it's not quite right, go back to your design map and tweak it, then hit calc again

7. After a bit of experimenting I found that the altitude tools on the designmap at 512x768 was a bit limited, so i decided to double the size of the map to give me more accuracy. I chose Operations > Design Map > Resize Design map, and increased the size to 1024x1536 which generated a new larger scale design map derived from the orginal - you can immediately see the improvement in accuracy. You could have started with the large scale initially, but by starting small you lets L3DT do much of the hard work for you. As you can see i then further tweaked the map to get the features i wanted.

Note I kept a border of -20m all around my terrain file, this was for ease of adding new regions later on

7. When you think you nearly have it thats a good time to head over into the 3d view. The system uses roughly the same movement controls as OS so it's pretty easy to get to grips with. Here you can "fine tune" your terrain features to get it closer to what you are looking for. Mouse Tools > Edit Active Map.

8. Close Sapphire and then use File > Export > Active map, use .PNG format - at this point I resized back to 512x768

5. Leave design map checked and hit OK

The first thing L3DT will generate is a design map - this is a blocky representation of what will be calcualted but it gives you a good idea of what the results will be before you actually apply the terrain calculation.

You may need to generate your initial terrain several times until you get something that looks close to what you desire, you can also generate several terrains and then mash them together later in a graphics package

Once you are happy, choose "CALC" and "Heightfield" - this then generates an accurate terrain file.

Then choose File > Export > Export Map > Heightfield and choose .PNG format ( way easier than messing around with RAW files)
Now you can choose to simply cut this png, or in my case I offset the png so that I could position it better in the 9x9 grid (remeber why I chose edge wrapping?). Basically you double the canvas size, then copy the heightfile. Using the grids and snapping in your editor comes in very handy. I then use guides to show where the final cuts will be. Tio speed things up you can use "slice along guides" when you export to get the files you need.

Step 8. '''Making OpenSimulator use the new textures.'''

You need to now tell OpenSimulator to use the new terrain textures on your grid. For example: if you have 4 regions called Region1, Region2, Region3 and Region4... you need to add a section to your startup_commands.txt that looks like this:

change-region Region1
terrain load path_to_textures/terrain_for_region1.png

change-region Region2
terrain load path_to_textures/terrain_for_region2.png

change-region Region3
terrain load path_to_textures/terrain_for_region3.png

change-region Region4
terrain load path_to_textures/terrain_for_region4.png

Step 9. '''Restart your OpenSimulator instance and fine-tune your terrain height.'''

== Notes ==

When you have your new terrain files loaded - make sure you disable the startup_commands, as every time you restart your server your terrain files will be re-uploaded, removing any in-game terraforming you have done

File:Step2.png

2009-01-05T10:56:47Z

Max Ping:

Cross-region terrain making with L3DT

2009-01-05T10:55:42Z

Max Ping:

This tutorial has been put together from several sources on the web it is aimed at region operators who want to make detailed cross region terrains quickly and easily.

It describes the generation of the terrain files needed to seamlessly fill a 2x3 region. Obviously you can adapt it to fit your specific requirements. Designing a terrain map for a single region is relatively straightforward, however if you want your region to span across a number of regions we are faced with a few challenges. The main one is seam-matching, in other words getting the edge of one sim to match the edge of the next. The inbuilt terraforming tools are quite good in OpenSimulator, however they struggle on region boundaries - thus you end up with jagged edges where the regions meet.

To resolve this you need to create a larger terrain map and then split it into tiles.

There are two ways to do this, either draw it by hand using a graphics package, or use a terrain generating tool as a starting point. You can just use the terrain generator to get started quickly although in reality you will probably end up mixing both techniques. The manual technique has been well described by Fu Barr here: http://opensimulator.org/wiki/Terrain_making so i will focus on the easy way.

The principle reason why I wanted to start with a generated terrain is time - it takes a long time to draw your heightmap by hand so using the generator gives you a little kick start. It can also generate very realistic terrains which factor in things like age and erosion, in minutes rather than hours :)

Enjoy the tutorial and feel free to contribute/improve it -

[[Max Ping]]

== The Objective ==

My objective is to create a 6 region heightmap based on the idea of an ancient volcanic archipelago. Thus I wanted a few islands with nice curved stretches of beach, some cliffs and drop offs and a higher regions. I already had in mind roughly what i wanted so that was a good start. I personally like islands because you get lots of terrain variation and the sunsets in OpenSim can be... well stunning :) It's very useful to have an idea in your mind of what you want before you start...

== The Process ==

I used the L3DT Editor from Bundysoft, the standard edition is free and it does a great job of creating heightmaps, it generates nice and realisitc terrain- you can also drop in and fly around the terrain in a 3d view which will be familiar to OpenSimmers and great for previewing before you upload the regions. You can get the product here:

http://www.bundysoft.com/L3DT/downloads/standard.php

== Generating your terrain files ==

The first thing you will generate is a design map - this is a "blocky" representation of the landmass which means you can rapidly paint your terrain before you actually apply the terrain calculation.

1. Click "New Map" and choose the "Design/inflate (blank)" Algorithm [[Image:step1.png]]

2. My desired region size is 2x3, which is 512m x 768m. Note that I set the horizontal scale to 1m [[Image:step2.png]]

3. I then used the default HF/DM ratio of 64 - thi s allows you to roughly plot your land mass [[Image:step3.png]]

4. Now the fun begins :) Click the edit icon to bring up the Design map brush - there's lots you can do here - you just have to experiment with the brushes... Personally I found the easiest method was to simply ignore all the other brushes and focus on the altitude brush. The design map starts at sea level, so I set the altitude to "-20" then hit "apply to all". From this starting point I built my islands up from there, keeping the altitude in the range of -20 to 44m. Remember it can be pretty rough to begin with as you can gradually build up the terrain to suit your needs.

5. When you are happy with your design map, hit the calc button, choose Heightfield and watch l3DT do it's magic.

6. If it's not quite right, go back to your design map and tweak it, then hit calc again

7. After a bit of experimenting I found that the altitude tools on the designmap at 512x768 was a bit limited, so i decided to double the size of the map to give me more accuracy. I chose Operations > Design Map > Resize Design map, and increased the size to 1024x1536 which generated a new larger scale design map derived from the orginal - you can immediately see the improvement in accuracy. You could have started with the large scale initially, but by starting small you lets L3DT do much of the hard work for you. As you can see i then further tweaked the map to get the features i wanted.

Note I kept a border of -20m all around my terrain file, this was for ease of adding new regions later on

7. When you think you nearly have it thats a good time to head over into the 3d view. The system uses roughly the same movement controls as OS so it's pretty easy to get to grips with. Here you can "fine tune" your terrain features to get it closer to what you are looking for. Mouse Tools > Edit Active Map.

8. Close Sapphire and then use File > Export > Active map, use .PNG format - at this point I resized back to 512x768

5. Leave design map checked and hit OK

The first thing L3DT will generate is a design map - this is a blocky representation of what will be calcualted but it gives you a good idea of what the results will be before you actually apply the terrain calculation.

You may need to generate your initial terrain several times until you get something that looks close to what you desire, you can also generate several terrains and then mash them together later in a graphics package

Once you are happy, choose "CALC" and "Heightfield" - this then generates an accurate terrain file.

Then choose File > Export > Export Map > Heightfield and choose .PNG format ( way easier than messing around with RAW files)
Now you can choose to simply cut this png, or in my case I offset the png so that I could position it better in the 9x9 grid (remeber why I chose edge wrapping?). Basically you double the canvas size, then copy the heightfile. Using the grids and snapping in your editor comes in very handy. I then use guides to show where the final cuts will be. Tio speed things up you can use "slice along guides" when you export to get the files you need.

Step 8. '''Making OpenSimulator use the new textures.'''

You need to now tell OpenSimulator to use the new terrain textures on your grid. For example: if you have 4 regions called Region1, Region2, Region3 and Region4... you need to add a section to your startup_commands.txt that looks like this:

change-region Region1
terrain load path_to_textures/terrain_for_region1.png

change-region Region2
terrain load path_to_textures/terrain_for_region2.png

change-region Region3
terrain load path_to_textures/terrain_for_region3.png

change-region Region4
terrain load path_to_textures/terrain_for_region4.png

Step 9. '''Restart your OpenSimulator instance and fine-tune your terrain height.'''

== Notes ==

When you have your new terrain files loaded - make sure you disable the startup_commands, as every time you restart your server your terrain files will be re-uploaded, removing any in-game terraforming you have done

File:Step1.png

2009-01-05T10:53:29Z

Max Ping:

Cross-region terrain making with L3DT

2009-01-05T10:51:53Z

Max Ping:

This tutorial has been put together from several sources on the web it is aimed at region operators who want to make detailed cross region terrains quickly and easily.

It describes the generation of the terrain files needed to seamlessly fill a 2x3 region. Obviously you can adapt it to fit your specific requirements. Designing a terrain map for a single region is relatively straightforward, however if you want your region to span across a number of regions we are faced with a few challenges. The main one is seam-matching, in other words getting the edge of one sim to match the edge of the next. The inbuilt terraforming tools are quite good in OpenSimulator, however they struggle on region boundaries - thus you end up with jagged edges where the regions meet.

To resolve this you need to create a larger terrain map and then split it into tiles.

There are two ways to do this, either draw it by hand using a graphics package, or use a terrain generating tool as a starting point. You can just use the terrain generator to get started quickly although in reality you will probably end up mixing both techniques. The manual technique has been well described by Fu Barr here: http://opensimulator.org/wiki/Terrain_making so i will focus on the easy way.

The principle reason why I wanted to start with a generated terrain is time - it takes a long time to draw your heightmap by hand so using the generator gives you a little kick start. It can also generate very realistic terrains which factor in things like age and erosion, in minutes rather than hours :)

Enjoy the tutorial and feel free to contribute/improve it -

[[Max Ping]]

== The Objective ==

My objective is to create a 6 region heightmap based on the idea of an ancient volcanic archipelago. Thus I wanted a few islands with nice curved stretches of beach, some cliffs and drop offs and a higher regions. I already had in mind roughly what i wanted so that was a good start. I personally like islands because you get lots of terrain variation and the sunsets in OpenSim can be... well stunning :) It's very useful to have an idea in your mind of what you want before you start...

== The Process ==

I used the L3DT Editor from Bundysoft, the standard edition is free and it does a great job of creating heightmaps, it generates nice and realisitc terrain- you can also drop in and fly around the terrain in a 3d view which will be familiar to OpenSimmers and great for previewing before you upload the regions. You can get the product here:

http://www.bundysoft.com/L3DT/downloads/standard.php

== Generating your terrain files ==

The first thing you will generate is a design map - this is a "blocky" representation of the landmass which means you can rapidly paint your terrain before you actually apply the terrain calculation.

1. Click "New Map" and choose the "Design/inflate (blank)" Algorithm [Next] [[img]]

2. My desired region size is 2x3, which is 512m x 768m. Note that I set the horizontal scale to 1m

3. I then used the default HF/DM ratio of 64 - thi s allows you to roughly plot your land mass [Next]

4. Now the fun begins :) Click the edit icon to bring up the Design map brush - there's lots you can do here - you just have to experiment with the brushes... Personally I found the easiest method was to simply ignore all the other brushes and focus on the altitude brush. The design map starts at sea level, so I set the altitude to "-20" then hit "apply to all". From this starting point I built my islands up from there, keeping the altitude in the range of -20 to 44m. Remember it can be pretty rough to begin with as you can gradually build up the terrain to suit your needs.

5. When you are happy with your design map, hit the calc button, choose Heightfield and watch l3DT do it's magic.

6. If it's not quite right, go back to your design map and tweak it, then hit calc again

7. After a bit of experimenting I found that the altitude tools on the designmap at 512x768 was a bit limited, so i decided to double the size of the map to give me more accuracy. I chose Operations > Design Map > Resize Design map, and increased the size to 1024x1536 which generated a new larger scale design map derived from the orginal - you can immediately see the improvement in accuracy. You could have started with the large scale initially, but by starting small you lets L3DT do much of the hard work for you. As you can see i then further tweaked the map to get the features i wanted.

Note I kept a border of -20m all around my terrain file, this was for ease of adding new regions later on

7. When you think you nearly have it thats a good time to head over into the 3d view. The system uses roughly the same movement controls as OS so it's pretty easy to get to grips with. Here you can "fine tune" your terrain features to get it closer to what you are looking for. Mouse Tools > Edit Active Map.

8. Close Sapphire and then use File > Export > Active map, use .PNG format - at this point I resized back to 512x768

5. Leave design map checked and hit OK

The first thing L3DT will generate is a design map - this is a blocky representation of what will be calcualted but it gives you a good idea of what the results will be before you actually apply the terrain calculation.

You may need to generate your initial terrain several times until you get something that looks close to what you desire, you can also generate several terrains and then mash them together later in a graphics package

Once you are happy, choose "CALC" and "Heightfield" - this then generates an accurate terrain file.

Then choose File > Export > Export Map > Heightfield and choose .PNG format ( way easier than messing around with RAW files)
Now you can choose to simply cut this png, or in my case I offset the png so that I could position it better in the 9x9 grid (remeber why I chose edge wrapping?). Basically you double the canvas size, then copy the heightfile. Using the grids and snapping in your editor comes in very handy. I then use guides to show where the final cuts will be. Tio speed things up you can use "slice along guides" when you export to get the files you need.

Step 8. '''Making OpenSimulator use the new textures.'''

You need to now tell OpenSimulator to use the new terrain textures on your grid. For example: if you have 4 regions called Region1, Region2, Region3 and Region4... you need to add a section to your startup_commands.txt that looks like this:

change-region Region1
terrain load path_to_textures/terrain_for_region1.png

change-region Region2
terrain load path_to_textures/terrain_for_region2.png

change-region Region3
terrain load path_to_textures/terrain_for_region3.png

change-region Region4
terrain load path_to_textures/terrain_for_region4.png

Step 9. '''Restart your OpenSimulator instance and fine-tune your terrain height.'''

== Notes ==

When you have your new terrain files loaded - make sure you disable the startup_commands, as every time you restart your server your terrain files will be re-uploaded, removing any in-game terraforming you have done

Cross-region terrain making with L3DT

2009-01-05T10:35:51Z

Max Ping: New page: This tutorial has been put together from several sources on the web it is aimed at region operators who want to make detailed cross region terrains quickly and easily. It describes the ge...

This tutorial has been put together from several sources on the web it is aimed at region operators who want to make detailed cross region terrains quickly and easily.

It describes the generation of the terrain files needed to seamlessly fill a 2x3 region. Obviously you can adapt it to fit your specific requirements. Designing a terrain map for a single region is relatively straightforward, however if you want your region to span across a number of regions we are faced with a few challenges. The main one is seam-matching, in other words getting the edge of one sim to match the edge of the next. The inbuilt terraforming tools are quite good in OpenSimulator, however they struggle on region boundaries - thus you end up with jagged edges where the regions meet.

To resolve this you need to create a larger terrain map and then split it into tiles.

There are two ways to do this, either draw it by hand using a graphics package, or use a terrain generating tool as a starting point. You can just use the terrain generator to get started quickly although in reality you will probably end up mixing both techniques. The manual technique has been well described by Fu Barr here: http://opensimulator.org/wiki/Terrain_making so i will focus on the easy way.

The principle reason why I wanted to start with a generated terrain is time - it takes a long time to draw your heightmap by hand so using the generator gives you a little kick start. It can also generate very realistic terrains which factor in things like age and erosion, in minutes rather than hours :)

Enjoy the tutorial and feel free to contribute/improve it -

[[Max Ping]]

== The Objective ==

My objective is to create a 6 region heightmap based on the idea of an ancient volcanic archipelago. Thus I wanted a few islands with nice curved stretches of beach, some cliffs and drop offs and a higher regions. I already had in mind roughly what i wanted so that was a good start. I personally like islands because you get lots of terrain variation and the sunsets in OpenSim can be... well stunning :) It's very useful to have an idea in your mind of what you want before you start...

The Process:

I used the L3DT Editor from Bundysoft, the standard edition is free and it does a great job of creating heightmaps, it generates nice and realisitc terrain- you can also drop in and fly around the terrain in a 3d view which will be familiar to OpenSimmers and great for previewing before you upload the regions. You can get the product here:

http://www.bundysoft.com/L3DT/downloads/standard.php

Generating your terrain files:

The first thing YOU will generate is a design map - this is a "blocky" representation of the landmass which means you can rapidly paint your terrain before you actually apply the terrain calculation.

1. Click "New Map" and choose the "Design/inflate (blank)" Algorithm [Next]

2. My desired region size is 2x3, which is 512m x 768m. Note that I set the horizontal scale to 1m

3. I then used the default HF/DM ratio of 64 - thi s allows you to roughly plot your land mass [Next]

4. Now the fun begins :) Click the edit icon to bring up the Design map brush - there's lots you can do here - you just have to experiment with the brushes... Personally I found the easiest method was to simply ignore all the other brushes and focus on the altitude brush. The design map starts at sea level, so I set the altitude to "-20" then hit "apply to all". From this starting point I built my islands up from there, keeping the altitude in the range of -20 to 44m. Remember it can be pretty rough to begin with as you can gradually build up the terrain to suit your needs.

5. When you are happy with your design map, hit the calc button, choose Heightfield and watch l3DT do it's magic.

6. If it's not quite right, go back to your design map and tweak it, then hit calc again

7. After a bit of experimenting I found that the altitude tools on the designmap at 512x768 was a bit limited, so i decided to double the size of the map to give me more accuracy. I chose Operations > Design Map > Resize Design map, and increased the size to 1024x1536 which generated a new larger scale design map derived from the orginal - you can immediately see the improvement in accuracy. You could have started with the large scale initially, but by starting small you lets L3DT do much of the hard work for you. As you can see i then further tweaked the map to get the features i wanted.

Note I kept a border of -20m all around my terrain file, this was for ease of adding new regions later on

7. When you think you nearly have it thats a good time to head over into the 3d view. The system uses roughly the same movement controls as OS so it's pretty easy to get to grips with. Here you can "fine tune" your terrain features to get it closer to what you are looking for. Mouse Tools > Edit Active Map.

8. Close Sapphire and then use File > Export > Active map, use .PNG format - at this point I resized back to 512x768

5. Leave design map checked and hit OK

The first thing L3DT will generate is a design map - this is a blocky representation of what will be calcualted but it gives you a good idea of what the results will be before you actually apply the terrain calculation.

You may need to generate your initial terrain several times until you get something that looks close to what you desire, you can also generate several terrains and then mash them together later in a graphics package

Once you are happy, choose "CALC" and "Heightfield" - this then generates an accurate terrain file.

Then choose File > Export > Export Map > Heightfield and choose .PNG format ( way easier than messing around with RAW files)
Now you can choose to simply cut this png, or in my case I offset the png so that I could position it better in the 9x9 grid (remeber why I chose edge wrapping?). Basically you double the canvas size, then copy the heightfile. Using the grids and snapping in your editor comes in very handy. I then use guides to show where the final cuts will be. Tio speed things up you can use "slice along guides" when you export to get the files you need.

Step 8. '''Making OpenSimulator use the new textures.'''

You need to now tell OpenSimulator to use the new terrain textures on your grid. For example: if you have 4 regions called Region1, Region2, Region3 and Region4... you need to add a section to your startup_commands.txt that looks like this:

change-region Region1
terrain load path_to_textures/terrain_for_region1.png

change-region Region2
terrain load path_to_textures/terrain_for_region2.png

change-region Region3
terrain load path_to_textures/terrain_for_region3.png

change-region Region4
terrain load path_to_textures/terrain_for_region4.png

Step 9. '''Restart your OpenSimulator instance and fine-tune your terrain height.'''

== Notes ==

When you have your new terrain files loaded - make sure you disable the startup_commands, as every time you restart your server your terrain files will be re-uploaded, removing any in-game terraforming you have done

Terrain making

2009-01-05T10:27:28Z

Max Ping:

This page describes a workflow for creating large, detailed, cross-region terrains. This workflow works for me, but you may find the whole process to be a little baroque. Feel free to provide the community with a sleeker option.

enjoy!

Fu Barr.

NB: For a slightly less baroque technique check out Max Ping's [[Cross-region terrain making with L3DT]]

== Overview ==

There are many ways to create heightmaps for terrains. You can use a specialised application with 3D terrain previews, or you can hand-craft each heightmap by drawing the gray-scales with a bitmap editor like the GIMP, Adobe Photoshop or DeLuxe-Paint II.

The workflow described here is based on using a combination of both: a specialised terrain application is used to create each individual heightmap, and a bitmap editor is then used to combine, cleanup and export the maps to OpenSimulator.

The reason for this seemingly convoluted way of doing things is that I like detailed region terrains and the 3D-preview of a terrain editor provides me with more 'control' over what I'm doing compared to using only a bitmap editor.

== Creating a detailed terrain map. ==

Step 1. '''Sketch the contours of your map.'''

This sketch should be a birds-eye view only, 3D-ness should remain in your minds-eye.

I cannot stress enough that the secret to good terrain is imagination, and in my experience the fastest path from imagination to workable idea is pen and paper. So, raid the laserprinter and dont be afraid to sketch several versions to see which one does the most justice to your vision.

Step 2. '''Divide the sketch into squares.'''

Once you have a map you like, draw straight lines across the map as per the number of regions you want this map to span. For example: a 2x2 grid would have two lines cutting the map into 4 equal squares: one going top to bottom and one going left to right.

Sometimes the lines cut your map into odd shapes like very thin slices of slope at the edge of regions, or little bits of river and lake in the corners of regions. If you redesign around these oddities now you'll have an easier time of it when you come to assembling the terrains.

Step 3. '''Use the 3D terrain editor to add detail.'''

Run your terrain editor and draw each square of your map adding in the 3D detail. Save each square as a simple gray-scale bitmap like a PNG or a TIFF.

Take care not to overdo the height thing. A good rule of thumb is not to exceed 60 metres height differential between the lowest and the highest points on the map.

Also avoid creating very steep inclines with a height difference of more than about 15 metres, as this will badly stretch the terrain textures.

Step 4. '''Assembling the overall terrain map.'''

Run your bitmap editor and create a new file of size: (256 x grid_x_regions) by (256 x grid_y_regions). For example in a 4x2 grid that would be: 1024x512 pixels. Then drop-in the individual region bitmaps you saved in step 3, taking care to match the region seams perfectly.

Put each region bitmap into its own layer, this makes it much easier to move the layers around.

Save this layered file before you continue. Trust me.

Step 5. '''Smoothing the region seams.'''

Flatten the layers of your perfectly arranged region map and then use your colour-copy tool to even-out the grey-scale values on the region seams. Save into a new file, keeping the first layered file as a starting point for new versions.

Why this smoothing business? Well, unless you've taken great care in step 3, there will be (small) differences in the gray values on the region seams. This is bad news as they'll show up as sudden height differences on your regions.

Also at this stage, you might want to use the smudge tool to blend gray-scales on mountain sides and other such details. This softens their slope and makes for prettier terrain in most cases.

Step 6. '''Cut the large region map into individual regions.'''

Once your smoothing and smudging is complete, you need to cut the assembled region back into 256x256 pixel squares, one tile per simulator region.

Step 7. '''Upload the textures to your server.'''

Duh.

Step 8. '''Making OpenSimulator use the new textures.'''

You need to now tell OpenSimulator to use the new terrain textures on your grid. For example: if you have 4 regions called Region1, Region2, Region3 and Region4... you need to add a section to your startup_commands.ini that looks like this:

change-region Region1
terrain load path_to_textures/terrain_for_region1.png

change-region Region2
terrain load path_to_textures/terrain_for_region2.png

change-region Region3
terrain load path_to_textures/terrain_for_region3.png

change-region Region4
terrain load path_to_textures/terrain_for_region4.png

Step 9. '''Restart your OpenSimulator instance and fine-tune your terrain height.'''

You should see your glorious new terrains appear on your regions when you restart the simulator, but it's likely that the terrains are too tall or too flat.

You need to add a terrain multiplier factor to each region, to compensate. This looks like so:

change-region Region1
terrain load path_to_textures/terrain_for_region1.png
terrain multiply 0.45

change-region Region2
terrain load path_to_textures/terrain_for_region2.png
terrain multiply 0.45

change-region Region3
terrain load path_to_textures/terrain_for_region3.png
terrain multiply 0.45

change-region Region4
terrain load path_to_textures/terrain_for_region4.png
terrain multiply 0.45

The actual multiplication factor will differ from case to case, so you need to experiment with the factor-value till you get the height you want.

That's it. Go forth and multiply!

== Notes ==

Terrain making

2009-01-05T10:26:13Z

Max Ping: Removed stuff about 90degree rotion of terrain tiles as this is now redundant

This page describes a workflow for creating large, detailed, cross-region terrains. This workflow works for me, but you may find the whole process to be a little baroque. Feel free to provide the community with a sleeker option.

enjoy!

Fu Barr.

For a slightly less baroque technique check out Max Ping's [[Cross-region Terrain Making with L3DT]]

== Overview ==

There are many ways to create heightmaps for terrains. You can use a specialised application with 3D terrain previews, or you can hand-craft each heightmap by drawing the gray-scales with a bitmap editor like the GIMP, Adobe Photoshop or DeLuxe-Paint II.

The workflow described here is based on using a combination of both: a specialised terrain application is used to create each individual heightmap, and a bitmap editor is then used to combine, cleanup and export the maps to OpenSimulator.

The reason for this seemingly convoluted way of doing things is that I like detailed region terrains and the 3D-preview of a terrain editor provides me with more 'control' over what I'm doing compared to using only a bitmap editor.

== Creating a detailed terrain map. ==

Step 1. '''Sketch the contours of your map.'''

This sketch should be a birds-eye view only, 3D-ness should remain in your minds-eye.

I cannot stress enough that the secret to good terrain is imagination, and in my experience the fastest path from imagination to workable idea is pen and paper. So, raid the laserprinter and dont be afraid to sketch several versions to see which one does the most justice to your vision.

Step 2. '''Divide the sketch into squares.'''

Once you have a map you like, draw straight lines across the map as per the number of regions you want this map to span. For example: a 2x2 grid would have two lines cutting the map into 4 equal squares: one going top to bottom and one going left to right.

Sometimes the lines cut your map into odd shapes like very thin slices of slope at the edge of regions, or little bits of river and lake in the corners of regions. If you redesign around these oddities now you'll have an easier time of it when you come to assembling the terrains.

Step 3. '''Use the 3D terrain editor to add detail.'''

Run your terrain editor and draw each square of your map adding in the 3D detail. Save each square as a simple gray-scale bitmap like a PNG or a TIFF.

Take care not to overdo the height thing. A good rule of thumb is not to exceed 60 metres height differential between the lowest and the highest points on the map.

Also avoid creating very steep inclines with a height difference of more than about 15 metres, as this will badly stretch the terrain textures.

Step 4. '''Assembling the overall terrain map.'''

Run your bitmap editor and create a new file of size: (256 x grid_x_regions) by (256 x grid_y_regions). For example in a 4x2 grid that would be: 1024x512 pixels. Then drop-in the individual region bitmaps you saved in step 3, taking care to match the region seams perfectly.

Put each region bitmap into its own layer, this makes it much easier to move the layers around.

Save this layered file before you continue. Trust me.

Step 5. '''Smoothing the region seams.'''

Flatten the layers of your perfectly arranged region map and then use your colour-copy tool to even-out the grey-scale values on the region seams. Save into a new file, keeping the first layered file as a starting point for new versions.

Why this smoothing business? Well, unless you've taken great care in step 3, there will be (small) differences in the gray values on the region seams. This is bad news as they'll show up as sudden height differences on your regions.

Also at this stage, you might want to use the smudge tool to blend gray-scales on mountain sides and other such details. This softens their slope and makes for prettier terrain in most cases.

Step 6. '''Cut the large region map into individual regions.'''

Once your smoothing and smudging is complete, you need to cut the assembled region back into 256x256 pixel squares, one tile per simulator region.

Step 7. '''Upload the textures to your server.'''

Duh.

Step 8. '''Making OpenSimulator use the new textures.'''

You need to now tell OpenSimulator to use the new terrain textures on your grid. For example: if you have 4 regions called Region1, Region2, Region3 and Region4... you need to add a section to your startup_commands.ini that looks like this:

change-region Region1
terrain load path_to_textures/terrain_for_region1.png

change-region Region2
terrain load path_to_textures/terrain_for_region2.png

change-region Region3
terrain load path_to_textures/terrain_for_region3.png

change-region Region4
terrain load path_to_textures/terrain_for_region4.png

Step 9. '''Restart your OpenSimulator instance and fine-tune your terrain height.'''

You should see your glorious new terrains appear on your regions when you restart the simulator, but it's likely that the terrains are too tall or too flat.

You need to add a terrain multiplier factor to each region, to compensate. This looks like so:

change-region Region1
terrain load path_to_textures/terrain_for_region1.png
terrain multiply 0.45

change-region Region2
terrain load path_to_textures/terrain_for_region2.png
terrain multiply 0.45

change-region Region3
terrain load path_to_textures/terrain_for_region3.png
terrain multiply 0.45

change-region Region4
terrain load path_to_textures/terrain_for_region4.png
terrain multiply 0.45

The actual multiplication factor will differ from case to case, so you need to experiment with the factor-value till you get the height you want.

That's it. Go forth and multiply!

== Notes ==

Build Instructions

2008-11-09T21:08:02Z

Max Ping: /* Running */

[[Category:Users]]
This page covers building OpenSim from source code on multiple platforms. Please help us keep this page up to date as the project progresses.

==Download from SVN==
Check out the [[Download]] Section

==MS Windows==

OpenSim requires either the .Net framework version 2.0, or the latest Mono. It supports the following compilers:
* [http://msdn2.microsoft.com/en-us/express/aa700756.aspx Microsoft Visual C# Express Edition] (note: not Visual C++)
* [http://www.mono-project.com/ mono]

Note for people who just downloaded the sources from http://dist.opensimulator.org/ (the "Downloads" link on the left) be advised that some important things are missing (like MySQL template scripts). For such features, you must download using svn!

Additional note: any Microsoft C# Express edition should work (2005 or 2008)

=== Building ===

* In the top-level directory, run the '<tt>runprebuild.bat</tt>' file. This will create a VS2005 solution file, a nant build file and a '<tt>compile.bat</tt>' file.
* If you prefer VS2008, run the '<tt>runprebuild2008.bat</tt>' instead.

* Open the resulting sln file with visual studio and build it there, or
* Run the '<tt>compile.bat</tt>' file. This will build the executable using MSBuild.
* if you prefer to use nant, run nant in the same top-level directory. This will build the executables.

If you don't care about physics (walking on prims, etc), ignore the rest of this section.

=== Running ===

Recent versions of OpenSim come without an <tt>OpenSim.ini</tt> file. Copy the <tt>OpenSim.ini.example</tt> file to <tt>OpenSim.ini</tt> before making any changes.

Double-click on the <tt>OpenSim.exe</tt> executable file in the <tt>bin</tt> directory. This will start up OpenSim in standalone mode.

The debugger in VS2005 C# may be used to step through the code. For those that use a Cygwin shell, you may find that one or more dll's have permissions that cause problems running. Most find that a "<tt>chmod 777 *</tt>" from the <tt>bin</tt> directory solves this.

Physics can be invoked by adding the appropriate line to the [Startup] section of <tt>OpenSim.ini</tt>. For ODE, that would be:

physics = OpenDynamicsEngine

You can also add a command line option to a shortcut, or run from a command prompt with:

-physics=OpenDynamicsEngine

'''''Windows Vista'''''

To run on Windows Vista, you must first disable Windows Firewall. Under the new "Start" button of Vista, select "Control panel". Then double-click "Windows Firewall". In the window that pops up, on the left column, select "Turn Windows Firewall on or off". You will have to give permission for this to run, then select the option "Off (not recommended)". Click "OK" and exit from the Windows Firewall window.

If you have McAfee SecurityCenter, see the description below.

Once all the security features are disabled, right click on <tt>OpenSim.exe</tt> and select "Run as administrator". This will pop up a window asking permission, select "Allow". Your OpenSim server should run in a DOS-like window and accept connections.

'''''McAfee Security'''''

McAfee Security does not allow applications to listen on ports not explicitly specified. You have two options: 1) disable firewall protection all together, 2) enable <tt>OpenSim.exe</tt> to be able to open ports.

''Disable firewall''

Open McAfee SecurityCenter. Select "Internet & Network". In the lower left corner is a small link to "Configure...". Select this. In the right side of the window, select the bar that says "Firewall protection is enabled". Here you can select "Off".

''Enable <tt>OpenSim.exe</tt> to open ports''

Open McAfee SecurityCenter. Select "Internet & Network". In the lower left corner is a small link to "Configure...". Select this. In the right side of the window, select the bar that says "Firewall protection is enabled". Select the "Advanced..." button. This will pop up a new window.

In the new window, on the left side, select "Program Permissions." In the middle on the right side of the window, select the "Add Allowed Program" button. Use the browser that pops up to find the OpenSim executable and select it.

Finally, select "OK" and exit the McAfee SecurityCenter window.

==Linux/Mac OS X/FreeBSD==

The easiest plaform to get running on the Linux side is Ubuntu 8.04, 32bit. This is what most of the developers running Linux use. If you are looking for the quick path, start there.

=== Ubuntu 8.04 / 8.10 ===

For Ubuntu 7.10 users '''you need''' to upgrade your mono to 1.9.1.

You can use the built in packages for mono. However, for better performance, you may want to [http://xyzzyxyzzy.net/2008/05/08/updated-mono-build-script-for-hardy-heron-and-mono-191/ upgrade mono to 1.9.1] ([http://tempvariable.blogspot.com/2008/04/installing-mono-191-on-ubuntu-804-hardy.html Other simple method])

sudo apt-get install subversion nant mono-gmcs libmono-microsoft8.0-cil \
libmono-system-runtime2.0-cil libgdiplus libmono-i18n2.0-cil ruby
svn co http://opensimulator.org/svn/opensim/trunk opensim
cd opensim
./runprebuild.sh
nant

=== openSUSE 10.3 and 11 ===

Install an openSUSE 11 or 10.3 with its default options, add the online repositories
when finished installing do an online update with all the latest packages.

In yast install these packages, for running Opensim in standalone mode.
(there is a slight diffrence between 10.3 and 11 but following should be same)
subversion
nant
mono-jscript
- check that mono-core is installed

If you just want to use SQLite then jump to last section
within this post.

* Optional mysql - for Opensim running in Grid mode:
Install these mysql packages via yast
mysql
mysql-client
mysql-administrator
mysql-gui-tools
mysql-query-browser

Before building create the mysql database.
/etc/init.d/mysql start
mysql -u root -p -h localhost
(when asked for password just hit enter)

mysql> create database opensim;
mysql> quit

set the configuration in bin/mysql_connection.ini
Or on later builds set the connection string inside bin/OpenSim.ini

Build after installation of above in bash terminal. i save it in /opt

su -
cd /opt
svn co http://opensimulator.org/svn/opensim/trunk opensim
cd opensim
./runprebuild.sh
nant

After this you should be able to continue on starting the diffrent Servers, look in the mysql-config section,or
just run your OpenSim as a Standalone. By - eagleFX

=== Mac OS X 10.5/10.4 ===
* OpenSim is now working on PowerPC Macs! Thanks to DrScofield and those who helped him. Current nightly builds for PowerPC are not working, not sure about Intel so use the 0.5 Build. OpenSim works on Intel Macs. I'm testing on PowerBook G4. Tested these step on 10.5, but not 10.4 but should work --[[User:Mokele|Mokele]] 22:36, 14 February 2008 (PST)
* Install XCode Developers Tools from DVD/CD Installation Disk or download from http://developer.apple.com/. You have to create an Apple account to access the downloads if you don't have an Apple account.
* Install X11 for 10.4 from the Optional Install from the DVD/CD Installation Disk. X11 for 10.5 is installed by default.
* Install Mono 1.2.5 from http://ftp.novell.com/pub/mono/archive/1.2.5/macos-10-universal/5/MonoFramework-1.2.5_5.macos10.novell.universal.dmg and in Terminal or X11 edit the .profile file and add the following line:
export PKG_CONFIG_PATH="/Library/Frameworks/Mono.framework/Versions/Current/lib/pkgconfig/:${PKG_CONFIG_PATH}"
* Compile OpenSim
svn co http://opensimulator.org/svn/opensim/tags/0.5.0-release opensim
cd opensim
./runprebuild.sh
nant

* Download and Compile libopenjpeg-libsl-2.1.2.0.dylib and libsecondlife.dll
* libopenjpeg-libsl-2.1.2.0.dylib:
svn co http://opensimulator.org/svn/opensim-libs/libsl1550 opensim-libs
cd opensim-libs/openjpeg-libsl
make -f Makefile.osx
cp libopenjpeg-libsl-2.1.2.0.dylib ../../opensim/bin
* Note: The Makefile that creates the libopenjpeg-libsl-2.1.2.0.so does not compile on PowerPC, but works properly on Intel Macs. Looks like a gcc issue with compile options.

* libsecondlife.dll: (for PowerPC Only, see details on this step [http://xyzzyxyzzy.net/2008/02/12/installing-opensim-on-powerpcor-of-eggs-and-virtual-worlds installing OpenSim on PowerPC…or: of eggs and virtual worlds])
cd .. (back into opensim-libs)
nant
cp bin/libsecondlife.dll ../opensim/bin

* Edit the libsecondlife.dll.config (PowerPC Only). Remove the cpu="x86" tag in the last dllmap line.

=== FreeBSD 6.2 ===
su
cd /usr/ports/devel/subversion/ && make install clean (you may also need to rebuild apr-svn if this step fails)
cd /usr/ports/lang/mono/ && make install clean
cd /usr/ports/devel/nant/ && make install clean
cd /usr/ports/databases/sqlite3/ && make install clean
cd /usr/ports/x11-toolkits/libgdiplus/ && make install clean
cd /opensim/installation/directory/
svn co http://opensimulator.org/svn/opensim/trunk opensim
cd opensim
./runprebuild.sh
nant

Note: [http://opensimulator.org/wiki/OpenSim:FAQ#System.DllNotFoundException:_..2Flibopenjpeg-libsl-2.1.2.0.so|Follow the instructions on the FAQ to fix the]
"System.DllNotFoundException: ./libopenjpeg-libsl-2.1.2.0.so" issue, but use "gmake" instead of "make"

For ODE Physics you must do the following:
cd /usr/ports/graphics/libGL/ && make install clean
cd /usr/ports/graphics/libGLU/ && make install clean
cd /opensim/installation/directory/
svn co http://opensimulator.org/svn/opensim-libs/trunk opensim-libs
cd opensim-libs/unmanaged/OpenDynamicsEngine2/
sh autogen.sh
./configure --enable-shared --enable-release --disable-demos
make
mv ./ode/src/libode.so /opensim/installation/directory/opensim/bin/

=== RedHat Enterprise Linux 4 ===
sudo vi /etc/yum.repos.d/mono.repo

[mono]
name=Mono for rhel-4-i386 (stable)
baseurl=http://ftp.novell.com/pub/mono/download-stable/rhel-4-i386/
enabled=1
gpgcheck=0

sudo yum install mono-complete monodoc-core nant
svn co svn co http://opensimulator.org/svn/opensim/trunk opensim
cd opensim
./runprebuild.sh
nant

=== RedHat Enterprise Linux 5 ===

The instructions below also work on other RedHat Linux flavors such as CentOS or maybe Fedora.

1. Put the [http://download.opensuse.org/repositories/Mono/RHEL_5/Mono.repo Mono.repo] file in the /etc/yum.repo.d/ directory:
$ sudo su -
$ cd /etc/yum.repo.d/
$ wget http://download.opensuse.org/repositories/Mono/RHEL_5/Mono.repo
Naturally use the most [http://download.opensuse.org/repositories/Mono up-to-date link for your distribution].

2. Install Mono and related tools with yum:
$ yum install mono nant mono-jscript mono-nunit
Make sure to use nunit-console2 to run your tests.

=== Fedora 5 ===
* I needed to build latest mono and nant from sources to build OpenSim successfully, the ones available in yum repository didn't work so I had to uninstall and build and configure the packages.

For detailed instructions go [http://ruakuu.blogspot.com/2008/06/installing-and-configuring-opensim-on.html here]

=== Debian 4 ===

The following packages and their dependencies are required to run OpenSim on a default Debian 4 netinstall:
* mono
* libmono-corlib2.0-cil
* libmono-sqlite2.0-cil
* libmono-system-web2.0-cil
* libmono-microsoft8.0-cil
* libmono-system-runtime2.0-cil

=== 64bit ===
Please note that only 32bit binaries are provided in the bin/ directory of subversion. If you want to use 64bit, you'll need to rebuild these shared objects. See [[Installing and running on x86-64]]

=== Physics (Open Dynamics Engine ODE) ===
As installed from svn, ODE will work on most 32 bit platforms. If you get an ODE-related crash, and/or a libode.so not found type of error, you will need to build libode from source.

Remove <tt>libode.so</tt> from the <tt>./bin</tt> folder. (Note that subsequent svn updates may replace it again; best fix is to copy your built <tt>libode.so</tt> to <tt>bin</tt>). Do NOT remove <tt>ode.net.dll</tt>! Download the latest source from:

svn co http://opensimulator.org/svn/opensim-libs/trunk/unmanaged/OpenDynamicsEngine

OpenSim requires a couple of patches on top of ODE which are not yet included upstream. When compiling, make sure to use the following configure options:

--with-trimesh=gimpact
--enable-shared

Make sure the configure script confirms these choices, and always compile with single precision (I believe that's the default). Try <code> make -k </code> if you get errors relating to drawstuff, test*, or openGL. <code> make install </code> should put <tt>libode.so</tt> in the proper place (usually <tt>/usr/local/lib</tt>), and it should be seen by opensim (<tt>ode.net.dll</tt>)

===Running===
Recent versions of OpenSim come without an <tt>OpenSim.ini</tt> file. Copy the <tt>OpenSim.ini.example</tt> file to <tt>OpenSim.ini</tt> before making any changes.
<code>
cd bin
mono OpenSim.exe
</code>

Note: if you are running a 32bit Server such as Ubuntu 8.0.4 you need the alternative launcher:

<code>
mono OpenSim.32BitLaunch.exe
</code>

* To invoke ODE, add the option:
-physics=OpenDynamicsEngine
to the <tt>mono OpenSim.exe</tt> line

or add <code> physics = OpenDynamicsEngine </code> to the [Startup] section of <tt>OpenSim.ini</tt>. Same deal for other physics engines, when available.

On mono 1.2.6, some distributions may see
Unhandled Exception: System.NotSupportedException: CodePage 1252 not supported
on startup when using mysql. This can be resolved by installing the package libmono-i18n2.0-cil (see http://bugs.mysql.com/bug.php?id=33938).

=== Additional Items ===

* [[GC_NO_EXPLICIT|GC NO EXPLICIT]] - Enable Large Heap in Mono, this has been known to help performance and stability

[[Category:Users]]

Build Instructions

2008-11-09T21:07:12Z

Max Ping: /* Running */

[[Category:Users]]
This page covers building OpenSim from source code on multiple platforms. Please help us keep this page up to date as the project progresses.

==Download from SVN==
Check out the [[Download]] Section

==MS Windows==

OpenSim requires either the .Net framework version 2.0, or the latest Mono. It supports the following compilers:
* [http://msdn2.microsoft.com/en-us/express/aa700756.aspx Microsoft Visual C# Express Edition] (note: not Visual C++)
* [http://www.mono-project.com/ mono]

Note for people who just downloaded the sources from http://dist.opensimulator.org/ (the "Downloads" link on the left) be advised that some important things are missing (like MySQL template scripts). For such features, you must download using svn!

Additional note: any Microsoft C# Express edition should work (2005 or 2008)

=== Building ===

* In the top-level directory, run the '<tt>runprebuild.bat</tt>' file. This will create a VS2005 solution file, a nant build file and a '<tt>compile.bat</tt>' file.
* If you prefer VS2008, run the '<tt>runprebuild2008.bat</tt>' instead.

* Open the resulting sln file with visual studio and build it there, or
* Run the '<tt>compile.bat</tt>' file. This will build the executable using MSBuild.
* if you prefer to use nant, run nant in the same top-level directory. This will build the executables.

If you don't care about physics (walking on prims, etc), ignore the rest of this section.

=== Running ===

Recent versions of OpenSim come without an <tt>OpenSim.ini</tt> file. Copy the <tt>OpenSim.ini.example</tt> file to <tt>OpenSim.ini</tt> before making any changes.

Double-click on the <tt>OpenSim.exe</tt> executable file in the <tt>bin</tt> directory. This will start up OpenSim in standalone mode.

The debugger in VS2005 C# may be used to step through the code. For those that use a Cygwin shell, you may find that one or more dll's have permissions that cause problems running. Most find that a "<tt>chmod 777 *</tt>" from the <tt>bin</tt> directory solves this.

Physics can be invoked by adding the appropriate line to the [Startup] section of <tt>OpenSim.ini</tt>. For ODE, that would be:

physics = OpenDynamicsEngine

You can also add a command line option to a shortcut, or run from a command prompt with:

-physics=OpenDynamicsEngine

'''''Windows Vista'''''

To run on Windows Vista, you must first disable Windows Firewall. Under the new "Start" button of Vista, select "Control panel". Then double-click "Windows Firewall". In the window that pops up, on the left column, select "Turn Windows Firewall on or off". You will have to give permission for this to run, then select the option "Off (not recommended)". Click "OK" and exit from the Windows Firewall window.

If you have McAfee SecurityCenter, see the description below.

Once all the security features are disabled, right click on <tt>OpenSim.exe</tt> and select "Run as administrator". This will pop up a window asking permission, select "Allow". Your OpenSim server should run in a DOS-like window and accept connections.

'''''McAfee Security'''''

McAfee Security does not allow applications to listen on ports not explicitly specified. You have two options: 1) disable firewall protection all together, 2) enable <tt>OpenSim.exe</tt> to be able to open ports.

''Disable firewall''

Open McAfee SecurityCenter. Select "Internet & Network". In the lower left corner is a small link to "Configure...". Select this. In the right side of the window, select the bar that says "Firewall protection is enabled". Here you can select "Off".

''Enable <tt>OpenSim.exe</tt> to open ports''

Open McAfee SecurityCenter. Select "Internet & Network". In the lower left corner is a small link to "Configure...". Select this. In the right side of the window, select the bar that says "Firewall protection is enabled". Select the "Advanced..." button. This will pop up a new window.

In the new window, on the left side, select "Program Permissions." In the middle on the right side of the window, select the "Add Allowed Program" button. Use the browser that pops up to find the OpenSim executable and select it.

Finally, select "OK" and exit the McAfee SecurityCenter window.

==Linux/Mac OS X/FreeBSD==

The easiest plaform to get running on the Linux side is Ubuntu 8.04, 32bit. This is what most of the developers running Linux use. If you are looking for the quick path, start there.

=== Ubuntu 8.04 / 8.10 ===

For Ubuntu 7.10 users '''you need''' to upgrade your mono to 1.9.1.

You can use the built in packages for mono. However, for better performance, you may want to [http://xyzzyxyzzy.net/2008/05/08/updated-mono-build-script-for-hardy-heron-and-mono-191/ upgrade mono to 1.9.1] ([http://tempvariable.blogspot.com/2008/04/installing-mono-191-on-ubuntu-804-hardy.html Other simple method])

sudo apt-get install subversion nant mono-gmcs libmono-microsoft8.0-cil \
libmono-system-runtime2.0-cil libgdiplus libmono-i18n2.0-cil ruby
svn co http://opensimulator.org/svn/opensim/trunk opensim
cd opensim
./runprebuild.sh
nant

=== openSUSE 10.3 and 11 ===

Install an openSUSE 11 or 10.3 with its default options, add the online repositories
when finished installing do an online update with all the latest packages.

In yast install these packages, for running Opensim in standalone mode.
(there is a slight diffrence between 10.3 and 11 but following should be same)
subversion
nant
mono-jscript
- check that mono-core is installed

If you just want to use SQLite then jump to last section
within this post.

* Optional mysql - for Opensim running in Grid mode:
Install these mysql packages via yast
mysql
mysql-client
mysql-administrator
mysql-gui-tools
mysql-query-browser

Before building create the mysql database.
/etc/init.d/mysql start
mysql -u root -p -h localhost
(when asked for password just hit enter)

mysql> create database opensim;
mysql> quit

set the configuration in bin/mysql_connection.ini
Or on later builds set the connection string inside bin/OpenSim.ini

Build after installation of above in bash terminal. i save it in /opt

su -
cd /opt
svn co http://opensimulator.org/svn/opensim/trunk opensim
cd opensim
./runprebuild.sh
nant

After this you should be able to continue on starting the diffrent Servers, look in the mysql-config section,or
just run your OpenSim as a Standalone. By - eagleFX

=== Mac OS X 10.5/10.4 ===
* OpenSim is now working on PowerPC Macs! Thanks to DrScofield and those who helped him. Current nightly builds for PowerPC are not working, not sure about Intel so use the 0.5 Build. OpenSim works on Intel Macs. I'm testing on PowerBook G4. Tested these step on 10.5, but not 10.4 but should work --[[User:Mokele|Mokele]] 22:36, 14 February 2008 (PST)
* Install XCode Developers Tools from DVD/CD Installation Disk or download from http://developer.apple.com/. You have to create an Apple account to access the downloads if you don't have an Apple account.
* Install X11 for 10.4 from the Optional Install from the DVD/CD Installation Disk. X11 for 10.5 is installed by default.
* Install Mono 1.2.5 from http://ftp.novell.com/pub/mono/archive/1.2.5/macos-10-universal/5/MonoFramework-1.2.5_5.macos10.novell.universal.dmg and in Terminal or X11 edit the .profile file and add the following line:
export PKG_CONFIG_PATH="/Library/Frameworks/Mono.framework/Versions/Current/lib/pkgconfig/:${PKG_CONFIG_PATH}"
* Compile OpenSim
svn co http://opensimulator.org/svn/opensim/tags/0.5.0-release opensim
cd opensim
./runprebuild.sh
nant

* Download and Compile libopenjpeg-libsl-2.1.2.0.dylib and libsecondlife.dll
* libopenjpeg-libsl-2.1.2.0.dylib:
svn co http://opensimulator.org/svn/opensim-libs/libsl1550 opensim-libs
cd opensim-libs/openjpeg-libsl
make -f Makefile.osx
cp libopenjpeg-libsl-2.1.2.0.dylib ../../opensim/bin
* Note: The Makefile that creates the libopenjpeg-libsl-2.1.2.0.so does not compile on PowerPC, but works properly on Intel Macs. Looks like a gcc issue with compile options.

* libsecondlife.dll: (for PowerPC Only, see details on this step [http://xyzzyxyzzy.net/2008/02/12/installing-opensim-on-powerpcor-of-eggs-and-virtual-worlds installing OpenSim on PowerPC…or: of eggs and virtual worlds])
cd .. (back into opensim-libs)
nant
cp bin/libsecondlife.dll ../opensim/bin

* Edit the libsecondlife.dll.config (PowerPC Only). Remove the cpu="x86" tag in the last dllmap line.

=== FreeBSD 6.2 ===
su
cd /usr/ports/devel/subversion/ && make install clean (you may also need to rebuild apr-svn if this step fails)
cd /usr/ports/lang/mono/ && make install clean
cd /usr/ports/devel/nant/ && make install clean
cd /usr/ports/databases/sqlite3/ && make install clean
cd /usr/ports/x11-toolkits/libgdiplus/ && make install clean
cd /opensim/installation/directory/
svn co http://opensimulator.org/svn/opensim/trunk opensim
cd opensim
./runprebuild.sh
nant

Note: [http://opensimulator.org/wiki/OpenSim:FAQ#System.DllNotFoundException:_..2Flibopenjpeg-libsl-2.1.2.0.so|Follow the instructions on the FAQ to fix the]
"System.DllNotFoundException: ./libopenjpeg-libsl-2.1.2.0.so" issue, but use "gmake" instead of "make"

For ODE Physics you must do the following:
cd /usr/ports/graphics/libGL/ && make install clean
cd /usr/ports/graphics/libGLU/ && make install clean
cd /opensim/installation/directory/
svn co http://opensimulator.org/svn/opensim-libs/trunk opensim-libs
cd opensim-libs/unmanaged/OpenDynamicsEngine2/
sh autogen.sh
./configure --enable-shared --enable-release --disable-demos
make
mv ./ode/src/libode.so /opensim/installation/directory/opensim/bin/

=== RedHat Enterprise Linux 4 ===
sudo vi /etc/yum.repos.d/mono.repo

[mono]
name=Mono for rhel-4-i386 (stable)
baseurl=http://ftp.novell.com/pub/mono/download-stable/rhel-4-i386/
enabled=1
gpgcheck=0

sudo yum install mono-complete monodoc-core nant
svn co svn co http://opensimulator.org/svn/opensim/trunk opensim
cd opensim
./runprebuild.sh
nant

=== RedHat Enterprise Linux 5 ===

The instructions below also work on other RedHat Linux flavors such as CentOS or maybe Fedora.

1. Put the [http://download.opensuse.org/repositories/Mono/RHEL_5/Mono.repo Mono.repo] file in the /etc/yum.repo.d/ directory:
$ sudo su -
$ cd /etc/yum.repo.d/
$ wget http://download.opensuse.org/repositories/Mono/RHEL_5/Mono.repo
Naturally use the most [http://download.opensuse.org/repositories/Mono up-to-date link for your distribution].

2. Install Mono and related tools with yum:
$ yum install mono nant mono-jscript mono-nunit
Make sure to use nunit-console2 to run your tests.

=== Fedora 5 ===
* I needed to build latest mono and nant from sources to build OpenSim successfully, the ones available in yum repository didn't work so I had to uninstall and build and configure the packages.

For detailed instructions go [http://ruakuu.blogspot.com/2008/06/installing-and-configuring-opensim-on.html here]

=== Debian 4 ===

The following packages and their dependencies are required to run OpenSim on a default Debian 4 netinstall:
* mono
* libmono-corlib2.0-cil
* libmono-sqlite2.0-cil
* libmono-system-web2.0-cil
* libmono-microsoft8.0-cil
* libmono-system-runtime2.0-cil

=== 64bit ===
Please note that only 32bit binaries are provided in the bin/ directory of subversion. If you want to use 64bit, you'll need to rebuild these shared objects. See [[Installing and running on x86-64]]

=== Physics (Open Dynamics Engine ODE) ===
As installed from svn, ODE will work on most 32 bit platforms. If you get an ODE-related crash, and/or a libode.so not found type of error, you will need to build libode from source.

Remove <tt>libode.so</tt> from the <tt>./bin</tt> folder. (Note that subsequent svn updates may replace it again; best fix is to copy your built <tt>libode.so</tt> to <tt>bin</tt>). Do NOT remove <tt>ode.net.dll</tt>! Download the latest source from:

svn co http://opensimulator.org/svn/opensim-libs/trunk/unmanaged/OpenDynamicsEngine

OpenSim requires a couple of patches on top of ODE which are not yet included upstream. When compiling, make sure to use the following configure options:

--with-trimesh=gimpact
--enable-shared

Make sure the configure script confirms these choices, and always compile with single precision (I believe that's the default). Try <code> make -k </code> if you get errors relating to drawstuff, test*, or openGL. <code> make install </code> should put <tt>libode.so</tt> in the proper place (usually <tt>/usr/local/lib</tt>), and it should be seen by opensim (<tt>ode.net.dll</tt>)

===Running===
Recent versions of OpenSim come without an <tt>OpenSim.ini</tt> file. Copy the <tt>OpenSim.ini.example</tt> file to <tt>OpenSim.ini</tt> before making any changes.
<code>
cd bin
mono OpenSim.exe
</code>

Note: if you are running a 32bit Server such as Ubuntu you need the alternative launcher:

<code>
mono OpenSim.32BitLaunch.exe
</code>

* To invoke ODE, add the option:
-physics=OpenDynamicsEngine
to the <tt>mono OpenSim.exe</tt> line

or add <code> physics = OpenDynamicsEngine </code> to the [Startup] section of <tt>OpenSim.ini</tt>. Same deal for other physics engines, when available.

On mono 1.2.6, some distributions may see
Unhandled Exception: System.NotSupportedException: CodePage 1252 not supported
on startup when using mysql. This can be resolved by installing the package libmono-i18n2.0-cil (see http://bugs.mysql.com/bug.php?id=33938).

=== Additional Items ===

* [[GC_NO_EXPLICIT|GC NO EXPLICIT]] - Enable Large Heap in Mono, this has been known to help performance and stability

[[Category:Users]]