Download: Visosad 1.9

Visosad 1.9

Collision detection for Orbiter space flight simulator.. ( ORBITER is written and maintained by Martin Schweiger http://www.orbitersim.com )

Contents

Description...1 Installation/Usage...2 Scenario options...3 Making your terrain collision-aware...3 Making your vessel collision-aware...4

Description

Visosad is a rigid body physics simulator library. MeshLand is Orbiter plugin, providing interface for Visosad. MeshLand/Visosad is a is a collision detection system for Orbiter space flight simulator. Features: Collision detection for terrain meshes. Including bases, landscapes, planetary meshes like Mars3D, asteroids – Phobos, Deimos and so on. Collision detection between vessels. Phisically accurate collision model. Performance guarantee: Whatever the size and amount of terrain meshes in the scenario, there will be no performance loss due to collision detection. (Within rational limits) Terrain collision support can be generic – it will work even if you don't change anything in the vessel code. For total control there is a versatile config system and Visosad SDK. Presets for some popular add-ons are included. Bugs/limitations: 1.9 doesn't features 2.0 vessel-vessel collision engine. ©2006 Artyom Litvinovich 1/5,

Installation/Usage

Installation: 1. Unpack all into Orbiter directory 2. Activate MeshLand module 3. For a quickstart run any “Visosad Presets” scenarios No additional user interference is required for collisions to work. In-sim controls: 3D surface MFD, started by Shift+V. Shows some surface-relative parameters. Calcs means :: Switch pages with PG or Shift+P. Second page shows feature list Vessel-Vessel enables collision between vessels. Vessel-Terrain enables collisions between vessels and planets. PTP-Friction enables terrain friction. PTP-rotation enables vessel torques. Gravity enabls The Gravity. Use Shift+< or > to select, Shift+E to change. ©2006 Artyom Litvinovich 2/5,

Scenario options

Visosad can be controlled from the scenarion files. It also uses scenario file to save system state. Scenario save is achived by using new Orbiter 2006 fiunctionality. Scenario file can be used to specify enabled fetures and a list of locations required for this scenario. TERRAIN list is added to the master config files list. BEGIN_MeshLand VESSEL 1 Vessel-veessel collisions TERRAIN 1 Vessel-terrain collisions ROTATION 1 PTP-rotation FRICTION 1 PTP-friction GRAVITY 1 The Gravity BEGIN(TERRAIN) Begin operator (for bases) Moon:Sayo Every string is one location Moon:Copernicus Crater : Phobos:Phobos Case insensitive, no extra chars END(TERRAIN) End operator (for bases)

END

Replacing TERRAIN with TERRAIN_ONLY will completely override master config files.

Making your terrain collision-aware

©2006 Artyom Litvinovich 3/5, Global collision configs: \visosad\\manifest.mlres Control program: \controls\mlcontrol.exe To enable or disable a global surface base use the control program or dit *.mlres files. Collision config format: ;Comment 1 //Test base points Comments {Comment 3} base-lon=-18 Longitude of reference point (Surface base) base-lat=-20 Latitude of reference point (Surface base) POS=000Standart POS parameter ROT=0 Standart ROT parameter SCALE=111Standart SCALE parameter psa=40 Lowest altitude of effect pea=60 Higest altitude of effect !pstr Start polygon definition operator p0=9.9,-23 p1=9.9,-57 Polygon points as vector(x,z,y) p2=-19.8,-40 !pend End polygon definition operator !surface Defining surface base !planet Defining planet mesh mesh=Sayo Mesh file (root at meshes\, no ext) After setting psa, pea, base-*, POS, ROT, SCALE variables, they are applyed to every polygon till next setting. Elevation of every point is (y+palt or y+POS.y). !pstr and !pend format is best for bases and multi-level pads definition. Mesh is best for terrain. If !planet is set, psa, pea, base-*, POS, ROT, SCALE variables is ignored. Every mesh after !planet is added to planet mesh till !surface.

Making your vessels collision-aware

©2006 Artyom Litvinovich 4/5, Global collision configs: \vessels\\manifest.mlres Control program: N/A All files in \vessels\ directory are aliases. ptp.cfg: rot=1 N/A fric=1 N/A !ptp Operator to use PTP model pt=0,-2.53,10 pt=-3.53,-2.53,-3 Define collision vertex (x,y,z) pt=3.5,-2.53,-3 ©2006 Artyom Litvinovich 5/5]

15