OpenSimulator - User contributions [en]

Mesh

2011-12-16T21:17:44Z

Sarah Kline: /* Viewers with Mesh support */

{{quicklinks}}
{{content}}
== Introduction ==
OpenSimulator supports the use of collada meshes. It must be noted that at the time of this writing, mesh support is still under development at Linden Labs, and they make changes to that all the time. Therefore, we can not guarantee that the current implementation of mesh support in OpenSim will be 100% compatible to the final version on SecondLife, once that gets rolled out. If you plan on using OpenSim to develop meshes for SecondLife, make sure you update Opensim frequently.

== Enabling mesh support ==
To make sure that your OpenSim server has mesh support enabled, edit OpenSim.ini, and look for the lines that should read:
[Mesh]
; enable / disable Collada mesh support
; default is true
AllowMeshUpload = true
If you do not have that section in Opensim.ini, then you can safely add it yourself.

== Free Software to make meshes with ==
==== Windows ====
* [http://www.wings3d.com/ Wings3D]
* [http://www.blender.org/ Blender]

==== MacOS ====
* [http://www.wings3d.com/ Wings3D]
* [http://www.blender.org/ Blender]

==== Linux ====
* [http://www.wings3d.com/ Wings3D]
* [http://www.blender.org/ Blender]

== Viewers with Mesh support ==
* [http://wiki.secondlife.com/wiki/Linden_Lab_Official:Alternate_Viewers#Second_Life_Project_Viewers LL Project Viewer] - An experimental mesh supporting viewer by Linden Labs
* [http://www.kirstensviewer.com/ Kirsten's Viewer] - A v2 based viewer with heavy emphasis on nice graphics.
* [http://www.singularityviewer.org/ Singularity] - A V1 based viewer, with the good stuff from v2 added. Supports mesh, [[OSSL]], and more.
* [http://sldev.free.fr/ Cool VL Viewer] - one of the oldest Third Party Viewers around (former name: Cool SL Viewer), fully OpenSim compatible.
* [http://www.phoenixviewer.com/ Firestorm Viewer] - A V2 based viewer,Supports mesh viewing and uploading, grid menu for Opensim, also Pheonix Viewer - V1 viewer with mesh view and upload, grid Manager.

'''Working on including Mesh support'''
* [http://blog.kokuaviewer.org/ Imprudence and Kokua] - Imprudence is v1 based, Kokua is v2 based. Both are develped by the same team.

== Other Meshes ==

You may not realize it, but sculpties too are meshes. One important difference with sculpties on Secondlife, is that in OpenSim, you can completely disable the bounding box (the invisible wall that you bump into, when you have a large sculptie). This will allow you to make working sculptie stars, without having to use tricks like invisible prims. By default, this feature is turned on, so no need to worry about that.
However, should you find that you keep running into bounding boxes anyway, you may want to edit OpenSim.ini, and look for the following lines:

[ODEPhysicsSettings]
;# {mesh_sculpted_prim} {[Startup]physics:OpenDynamicsEngine} {Mesh sculpties so they
collide as they look?} {true false} true
;; Do we want to mesh sculpted prim to collide like they look?
;; If you are seeing sculpt texture decode problems
;; (messages such as "Decoded image with unhandled number of components: 0 shortly followed by a physcs exception")
;; then you might want to try setting this to false.
; mesh_sculpted_prim = true
The current default for this is "true".

Since in OpenSimulator, prim size is set to a maximum of 256 meters by default, it can be worthwhile to use sculpties instead of collada mesh, especially if the mesh you need is a relatively simple one.

Mesh

2011-12-16T21:16:11Z

Sarah Kline: /* Viewers with Mesh support */

{{quicklinks}}
{{content}}
== Introduction ==
OpenSimulator supports the use of collada meshes. It must be noted that at the time of this writing, mesh support is still under development at Linden Labs, and they make changes to that all the time. Therefore, we can not guarantee that the current implementation of mesh support in OpenSim will be 100% compatible to the final version on SecondLife, once that gets rolled out. If you plan on using OpenSim to develop meshes for SecondLife, make sure you update Opensim frequently.

== Enabling mesh support ==
To make sure that your OpenSim server has mesh support enabled, edit OpenSim.ini, and look for the lines that should read:
[Mesh]
; enable / disable Collada mesh support
; default is true
AllowMeshUpload = true
If you do not have that section in Opensim.ini, then you can safely add it yourself.

== Free Software to make meshes with ==
==== Windows ====
* [http://www.wings3d.com/ Wings3D]
* [http://www.blender.org/ Blender]

==== MacOS ====
* [http://www.wings3d.com/ Wings3D]
* [http://www.blender.org/ Blender]

==== Linux ====
* [http://www.wings3d.com/ Wings3D]
* [http://www.blender.org/ Blender]

== Viewers with Mesh support ==
* [http://wiki.secondlife.com/wiki/Linden_Lab_Official:Alternate_Viewers#Second_Life_Project_Viewers LL Project Viewer] - An experimental mesh supporting viewer by Linden Labs
* [http://www.kirstensviewer.com/ Kirsten's Viewer] - A v2 based viewer with heavy emphasis on nice graphics.
* [http://www.singularityviewer.org/ Singularity] - A V1 based viewer, with the good stuff from v2 added. Supports mesh, [[OSSL]], and more.
* [http://sldev.free.fr/ Cool VL Viewer] - one of the oldest Third Party Viewers around (former name: Cool SL Viewer), fully OpenSim compatible.
* [http://www.phoenixviewer.com/ Firestorm Viewer] - A V2 based viewer,Supports mesh viewing and uploading has grid menu for Opensim, also Pheonix Viewer - V1 viewer with mesh view and uploading & grid Manager.

'''Working on including Mesh support'''
* [http://blog.kokuaviewer.org/ Imprudence and Kokua] - Imprudence is v1 based, Kokua is v2 based. Both are develped by the same team.

== Other Meshes ==

You may not realize it, but sculpties too are meshes. One important difference with sculpties on Secondlife, is that in OpenSim, you can completely disable the bounding box (the invisible wall that you bump into, when you have a large sculptie). This will allow you to make working sculptie stars, without having to use tricks like invisible prims. By default, this feature is turned on, so no need to worry about that.
However, should you find that you keep running into bounding boxes anyway, you may want to edit OpenSim.ini, and look for the following lines:

[ODEPhysicsSettings]
;# {mesh_sculpted_prim} {[Startup]physics:OpenDynamicsEngine} {Mesh sculpties so they
collide as they look?} {true false} true
;; Do we want to mesh sculpted prim to collide like they look?
;; If you are seeing sculpt texture decode problems
;; (messages such as "Decoded image with unhandled number of components: 0 shortly followed by a physcs exception")
;; then you might want to try setting this to false.
; mesh_sculpted_prim = true
The current default for this is "true".

Since in OpenSimulator, prim size is set to a maximum of 256 meters by default, it can be worthwhile to use sculpties instead of collada mesh, especially if the mesh you need is a relatively simple one.

Mesh

2011-12-16T21:12:31Z

Sarah Kline: /* Viewers with Mesh support */

{{quicklinks}}
{{content}}
== Introduction ==
OpenSimulator supports the use of collada meshes. It must be noted that at the time of this writing, mesh support is still under development at Linden Labs, and they make changes to that all the time. Therefore, we can not guarantee that the current implementation of mesh support in OpenSim will be 100% compatible to the final version on SecondLife, once that gets rolled out. If you plan on using OpenSim to develop meshes for SecondLife, make sure you update Opensim frequently.

== Enabling mesh support ==
To make sure that your OpenSim server has mesh support enabled, edit OpenSim.ini, and look for the lines that should read:
[Mesh]
; enable / disable Collada mesh support
; default is true
AllowMeshUpload = true
If you do not have that section in Opensim.ini, then you can safely add it yourself.

== Free Software to make meshes with ==
==== Windows ====
* [http://www.wings3d.com/ Wings3D]
* [http://www.blender.org/ Blender]

==== MacOS ====
* [http://www.wings3d.com/ Wings3D]
* [http://www.blender.org/ Blender]

==== Linux ====
* [http://www.wings3d.com/ Wings3D]
* [http://www.blender.org/ Blender]

== Viewers with Mesh support ==
* [http://wiki.secondlife.com/wiki/Linden_Lab_Official:Alternate_Viewers#Second_Life_Project_Viewers LL Project Viewer] - An experimental mesh supporting viewer by Linden Labs
* [http://www.kirstensviewer.com/ Kirsten's Viewer] - A v2 based viewer with heavy emphasis on nice graphics.
* [http://www.singularityviewer.org/ Singularity] - A V1 based viewer, with the good stuff from v2 added. Supports mesh, [[OSSL]], and more.
* [http://sldev.free.fr/ Cool VL Viewer] - one of the oldest Third Party Viewers around (former name: Cool SL Viewer), fully OpenSim compatible.
* [http://www.phoenixviewer.com/]Firestorm Viewer- A V2 based viewer,Supports mesh viewing and uploading has grid menu for Opensim. Also Pheonix Viewer - V1 viewer with mesh view and uploading & grid Manager.

'''Working on including Mesh support'''
* [http://blog.kokuaviewer.org/ Imprudence and Kokua] - Imprudence is v1 based, Kokua is v2 based. Both are develped by the same team.

== Other Meshes ==

You may not realize it, but sculpties too are meshes. One important difference with sculpties on Secondlife, is that in OpenSim, you can completely disable the bounding box (the invisible wall that you bump into, when you have a large sculptie). This will allow you to make working sculptie stars, without having to use tricks like invisible prims. By default, this feature is turned on, so no need to worry about that.
However, should you find that you keep running into bounding boxes anyway, you may want to edit OpenSim.ini, and look for the following lines:

[ODEPhysicsSettings]
;# {mesh_sculpted_prim} {[Startup]physics:OpenDynamicsEngine} {Mesh sculpties so they
collide as they look?} {true false} true
;; Do we want to mesh sculpted prim to collide like they look?
;; If you are seeing sculpt texture decode problems
;; (messages such as "Decoded image with unhandled number of components: 0 shortly followed by a physcs exception")
;; then you might want to try setting this to false.
; mesh_sculpted_prim = true
The current default for this is "true".

Since in OpenSimulator, prim size is set to a maximum of 256 meters by default, it can be worthwhile to use sculpties instead of collada mesh, especially if the mesh you need is a relatively simple one.

Mesh

2011-12-16T21:09:52Z

Sarah Kline: /* Viewers with Mesh support */

{{quicklinks}}
{{content}}
== Introduction ==
OpenSimulator supports the use of collada meshes. It must be noted that at the time of this writing, mesh support is still under development at Linden Labs, and they make changes to that all the time. Therefore, we can not guarantee that the current implementation of mesh support in OpenSim will be 100% compatible to the final version on SecondLife, once that gets rolled out. If you plan on using OpenSim to develop meshes for SecondLife, make sure you update Opensim frequently.

== Enabling mesh support ==
To make sure that your OpenSim server has mesh support enabled, edit OpenSim.ini, and look for the lines that should read:
[Mesh]
; enable / disable Collada mesh support
; default is true
AllowMeshUpload = true
If you do not have that section in Opensim.ini, then you can safely add it yourself.

== Free Software to make meshes with ==
==== Windows ====
* [http://www.wings3d.com/ Wings3D]
* [http://www.blender.org/ Blender]

==== MacOS ====
* [http://www.wings3d.com/ Wings3D]
* [http://www.blender.org/ Blender]

==== Linux ====
* [http://www.wings3d.com/ Wings3D]
* [http://www.blender.org/ Blender]

== Viewers with Mesh support ==
* [http://wiki.secondlife.com/wiki/Linden_Lab_Official:Alternate_Viewers#Second_Life_Project_Viewers LL Project Viewer] - An experimental mesh supporting viewer by Linden Labs
* [http://www.kirstensviewer.com/ Kirsten's Viewer] - A v2 based viewer with heavy emphasis on nice graphics.
* [http://www.singularityviewer.org/ Singularity] - A V1 based viewer, with the good stuff from v2 added. Supports mesh, [[OSSL]], and more.
* [http://sldev.free.fr/ Cool VL Viewer] - one of the oldest Third Party Viewers around (former name: Cool SL Viewer), fully OpenSim compatible.
* [http://www.phoenixviewer.com/] Firestorm Viewer- A V2 based viewer,Supports mesh viewing and uploading, Grid manager. Also Pheonix Viewer - V1 viewer with mesh view and uploading, Grid Manager.

'''Working on including Mesh support'''
* [http://blog.kokuaviewer.org/ Imprudence and Kokua] - Imprudence is v1 based, Kokua is v2 based. Both are develped by the same team.

== Other Meshes ==

You may not realize it, but sculpties too are meshes. One important difference with sculpties on Secondlife, is that in OpenSim, you can completely disable the bounding box (the invisible wall that you bump into, when you have a large sculptie). This will allow you to make working sculptie stars, without having to use tricks like invisible prims. By default, this feature is turned on, so no need to worry about that.
However, should you find that you keep running into bounding boxes anyway, you may want to edit OpenSim.ini, and look for the following lines:

[ODEPhysicsSettings]
;# {mesh_sculpted_prim} {[Startup]physics:OpenDynamicsEngine} {Mesh sculpties so they
collide as they look?} {true false} true
;; Do we want to mesh sculpted prim to collide like they look?
;; If you are seeing sculpt texture decode problems
;; (messages such as "Decoded image with unhandled number of components: 0 shortly followed by a physcs exception")
;; then you might want to try setting this to false.
; mesh_sculpted_prim = true
The current default for this is "true".

Since in OpenSimulator, prim size is set to a maximum of 256 meters by default, it can be worthwhile to use sculpties instead of collada mesh, especially if the mesh you need is a relatively simple one.

NAT Loopback Routers

2011-11-27T17:09:25Z

Sarah Kline: /* Netgear */

{{Quicklinks}} {{content}}

=INTRODUCTION=

What is NAT Loopback and why is it needed to host a public Opensimulator Region?

Currently (as at August 2010), a hosted region on a home connection with a broadband router needs, what is known as ''NAT Loopback'' functionality.

Many DSL routers/modems prevent loopback connections as a security feature. This means that a machine on your local network (e.g. behind your DSL router/modem) cannot connect to a forward facing IP address (such as 199.149.252.44) of a machine that it also on your local network. Connecting to the local IP address (such as 192.168.2.40) of that same machine works fine.

This is an issue since each region has to be specify an IP address for the client to connect. This is the ExternalHostName parameter in a regions config file (e.g. bin/Regions/Regions.ini). In the absence of NAT loopback, if a forward facing IP address is specified (such as 199.149.252.44) then external clients will be able to connect to the region but clients on your local network will not. If the internal address were put in ExternalHostName instead (e.g. 192.168.2.40) then viewers on the local network will be able to connect but viewers from an external network would not.

This page shows a list of routers supporting NAT Loopback. Please add both known working and non-working routers to the list.

=Working Routers=

==3Com==

*3CRWDR100A-72
*3CRWDR101A-75

==D-Link==

D-Link DGL-4500 series of routers have the largest available nat table of any router on the market.  These routers range from 70$-180$ USD depending on where you live and purchase from.

When considering a purchase, consider performance against cost. Upper end ADSL 2+ routers can add several Mbs to your modems sync speed.

'''Wireless Routers - Access Point Only'''

These routers are Access Point devices, and contain no ADSL modem and hence need a separate adsl modem operating in Bridge mode.

*[http://www.dlink.com/products/?pid=64 D-Link DGL-4500]
*[http://www.dlink.com/products/?pid=530 D-Link DIR-655]
*[http://www.dlink.com/products/?pid=DIR-635 D-Link DIR-635]
*[http://www.dlink.com/products/?pid=DIR-601 D-Link DIR-601]
*[http://www.dlink.com/products/?pid=DIR-600 D-Link DIR-600]
*D-Link DI-524

'''Routers With ADSL modem'''
No items to list currently

Note: The DGL-4100 & DGL-4300 have been discontinued, and the replacement model is the DIL-825 and DIL-855 - Loopback status unknown on these later models. The DGL-4300 may be available second hand.

==Draytek==

* Draytek Vigor 2710n [http://www.draytek.com/user/PdInfoDetail.php?Id=82] does NAT loopback out of the box and seems to be generally an all-round great router.
* Draytek Vigor 120 [http://www.draytek.com/user/PdInfoDetail.php?Id=71] does NAT loopback out of the box and has some nice features. NOTE that if it's using PPPoA (common in UK and New Zealand) there is a bug that stops Opensim (and Secondlife) ping packets from working so you disconnect after 3 minutes. You need to upgrade to firmware 3.2.4.3 (or higher).

==Linksys/Cisco==

*[http://www.linksysbycisco.com/EU/en/support/WAG200G Linksys WAG200G] with Firmware Version: 1.01.09
*[http://en.wikipedia.org/wiki/Linksys_WRT54G_series Linksys WRT54G]
*[http://homesupport.cisco.com/en-us/wireless/lbc/WAG54G Linksys WAG54G v3]
*[http://homesupport.cisco.com/en-us/wireless/lbc/WAG54G Linksys WAG54G v2 - NZ/Australia version]
*Linksys RT31P2
Note: The WAG54G v2 NZ/Australia version has a faster processor, more memory and larger NAT table, and works with OS out of the box. Other market versions may not.

==Netgear==

*NETGEAR WNR834M : ftp://downloads.netgear.com/files/wnr834m_ref_manual.pdf
*NETGEAR WNR2000 : With firmware 1.2.3.7 ( http://kb.netgear.com/app/answers/detail/a_id/11895 ) loopback now enabled 'out of the box'
*NETGEAR WGR614 : has been confirmed to work out of the box
*Netgear RP614 v3
*Netgear DG834G v3 with latest firmware & v4 upto firmware version v5.01.09 (according to [http://forum1.netgear.com/showthread.php?t=42641 this link], a later firmware update of v4 removed NAT loopback) NAT Loopback returned as menu option with latest v5.01.16 firmware for the v4 model. The latest model versions, marked v5 on the unit's label, has significantly different internals and is not currently Loopback capable(the v5 has the wireless aerial on the right, not the left, as looking from the front. The DG834G v1, v2, v3 & v4 are end of line in most markets. The v3 & v4 are proven good performers.
*Netgear DGN1000 worked out of the box. Note this working item reports its firmware version as V2.1.00.19_VG which seems much newer than the version offered for download on netgear.com.

==Thomson==

*Thomson SpeedTouch router-modem TG585, ST-585i (requires Telnet acces to it to Enable Loopback)
*Thomson Speedtouch ST-780, ST-516

==Other routers & Hardware==

*Arris TM502b : http://portforward.com/english/routers/port_forwarding/Arris/TM502b/
*2wire 2701hg-s NOT Loopback capable. but the 2wire 2701hg-B & 2701hg-D Series ARE loopback capable.  (These can be purchased for approximately $50 USD)
*AVM FritzBox (most Models are working perfect, '''except 3790 VDSL Router''', Date Sep 2010) : http://www.avm.de
*Ubee Wireless Cable Router DDW2600  [http://www.ubeeinteractive.com/index.php/products/product-overview/wireless_cable_router1/ http://www.ubeeinteractive.com/index.php/products/product-overview/wireless_cable_router1/]
*BT home hub V2
* If you are using a ZyXEL DSL router/modem from Embarq, please read [[OpenSim:Network_settings#A_solution_for_local_connections_when_you_are_using_NAT_and_Port_Forwarding|this configuration guide]]. This will show you how to reconfigure your DSL router/modem to fix this problem.

=KNOWN non-functional for OpenSim:=

*Netgear Pro Safe VPN FVS318 : [http://www.netgear.com/Products/VPNandSSL/WiredVPNFirewallRouters/FVS318.aspx http://www.netgear.com/Products/VPNandSSL/WiredVPNFirewallRouters/FVS318.aspx]
*NetGear WGR614 does not work with ISP required gateway modems
*Belkin F5D7230-4 (the router might work if 3rd party firmware is used, such as DD-WRT : http://www.dd-wrt.com/ )

<br>

=REFERENCE LINKS:=

More Information Related to Routers and Solutions @: [http://osgrid.org/forums/viewtopic.php?f=8&t=2283 osgrid.org/forums/viewtopic.php]

=Linux specific solutions=
==SETTING UP A LINUX COMPUTER TO ACT AS A ROUTER==

----

For Linux based Netfilter (iptables) routers, you want to set up the NAT table with some extra entries The following script is something to get you started, you'll need to fix up the variables at the top to match your system and network. <source lang="bash">
#!/bin/bash
#
# vvvvv - Fix these! - vvvvv
IPTABLES=/usr/sbin/iptables
LAN_NETWORK=192.168.0.0/24
SERVER_IP=192.168.0.2
INTERNET_IP=100.100.100.100
REMOTING_PORT=8895
REGION_PORT=9000
# ^^^^^ - Fix these! - ^^^^^

# First, the Destination NAT, anything going to the external address on our ports, we redirect to the server
# Note, if you have a double NAT running and this router doesn't actually have the internet IP address, you'll
# need another set of PREROUTING-DNAT lines with the --destination (-d) set to the internet facing private address
$IPTABLES -t nat -I PREROUTING -d $INTERNET_IP -p tcp --dport $REMOTING_PORT --jump DNAT --to-destination $SERVER_IP
$IPTABLES -t nat -I PREROUTING -d $INTERNET_IP -p udp --dport $REGION_PORT --jump DNAT --to-destination $SERVER_IP
$IPTABLES -t nat -I PREROUTING -d $INTERNET_IP -p tcp --dport $REGION_PORT --jump DNAT --to-destination $SERVER_IP

# Second, the Source NAT, we need this so that returning packets to our LAN clients go back through the router first,
# otherwise, the server will try to talk directly to the client and the client will reject them
$IPTABLES -t nat -I POSTROUTING -s $LAN_NETWORK -d $SERVER_IP -p tcp --dport $REMOTING_PORT --jump SNAT --to-source $INTERNET_IP
$IPTABLES -t nat -I POSTROUTING -s $LAN_NETWORK -d $SERVER_IP -p udp --dport $REGION_PORT --jump SNAT --to-source $INTERNET_IP
$IPTABLES -t nat -I POSTROUTING -s $LAN_NETWORK -d $SERVER_IP -p tcp --dport $REGION_PORT --jump SNAT --to-source $INTERNET_IP
</source>

--[[User:Hell Fire|Hell Fire]]

==DNS solution==
It's possible to host your own DNS-server, so you can prevent some of the dns-naming problems mentioned before. If http://example.org resolves to the external ip, and that loopback connection is prevented by your router, you could point your resolv.conf to a local nameserver like:
nameserver 192.168.2.2
Now you need bind/named installed in order to handle the dns-requests. You can find a bind example configfile here.

=openWRT Routers:=

If you use openWRT firmware on your router, check here: [[Users:Thomax:nat-loopback|OpenWRT NATLoopback]]

=Windows XP Work Around:=

Please see this -> http://vio.blpcomputers.info/loopbacknat.php

[[Category:Hardware]]