| 8 | The central Data Input/Output module is the only module you cannot disable in osgVisual. The parameter "enabled" is ignored, because dataIO is mandatory for the visual system to place object etc. |
| 9 | |
| 10 | You have to define in which Network setup ("clusterrole") osgVisual should work: |
| 11 | * master: In this role osgVisual recieves all relevant information via the extLink implementation and sends it via cluster implementation to the slave nodes. |
| 12 | * slave: In this role osgVisual recieves all relevant rendering information via the cluster implementation. |
| 13 | * standalone: In this role osgVisual recieves all relevant data via the extLink and renders it. No cluster functionality is used. |
| 14 | |
| 15 | You can subclass the cluster or extLink interface file to create your own cluster implementation (e.h. ethernet UDP based). Therefore you have to specify which implementation should be used. |
| 16 | Each implementation has it's own set of attributes you have to specify. |
| 17 | |
| 18 | The XML configuration is as followed: |
| 27 | |
| 28 | === cluster implementation 'enet' === |
| 29 | To use the UDP based 'enet' implementation for osgVisual, you have to specify the network details (IP, port) and if you want eNet to use the zLib compressor to reduce the transfered data size. |
| 30 | The parameter hardsync is currently not in use (version 0.6) |
| 31 | {{{ |
| 32 | #!xml |
| 33 | <cluster implementation="enet" hardsync="yes" master_ip="10.10.10.10" port="1234" use_zlib_compressor="yes" ></cluster> |
| 34 | }}} |
| 35 | |
| 36 | === extLink implementation 'VCL' === |
| 37 | To use the proprietary VCL implementation for osgVisual, you have to specify the VCL configuration file in the attribute "filename". |
| 38 | {{{ |
| 39 | #!xml |
| 40 | <extlink implementation="vcl" filename="osgVisual.xml"></extlink> |
| 41 | }}} |
| 42 | |