Difference between revisions of "Meshland"

From OrbiterWiki
Jump to navigation Jump to search
m
(Up-to-dating)
Line 9: Line 9:
 
'''MeshLand''' is an [[Orbiter]] [[plugin]] which offers a vessel-terrain and vessel-vessel collision detection and handling for Orbiter. '''MeshLand''' interfaces with ''Visosad'', which is a rigid body physics simulator.
 
'''MeshLand''' is an [[Orbiter]] [[plugin]] which offers a vessel-terrain and vessel-vessel collision detection and handling for Orbiter. '''MeshLand''' interfaces with ''Visosad'', which is a rigid body physics simulator.
  
==Key Features==
+
==Versions and variants==
* Calculates collisions between vessels, based on real physics (beta only).
+
'''MeshLand 1.x''' is based on the original idea collision detection engine. Collision handling utilised the Orbiter's LANDED state and touchdown points modification, which resulted in highly-stable and time acceleration-neutral system, but highly physically inaccurate model.
* Allows to land on terrain meshes, planetary meshes (asteroids) and multi-level structures.
+
 
 +
'''MeshLand 1.1 Apollo version''' is based on the 1.x engine, but with minimal tilting support and well-debuged SDK.
 +
 
 +
'''MeshLand-Visosad vessel-vessel beta''' is based on the new idea engine using forces and shifts to simulate collision handling, thus achiving higher physical accuracy, but lower stability. Only MeshLand version to date to be able to do plausible vessel-vessel collisions.
 +
 
 +
'''MeshLand-Visosad 1.9.x''' is based on the stabilised vessel-vessel collision beta with vessel-vessel part coded out, and vessel-terrain part fixed to presentable level.
 +
 
 +
'''MeshLand-Visosad-[[Orulex]] system''' is based on the 1.9.x version with collision detection removed and collision handling system linked directly to [[Orulex]] terrain function for collision data. Composes the ideas from 2.0 and 1.9, therefore quite unstable.
 +
 
 +
'''MeshLand-Visosad 2.0''' is based on the new idea engine using shifts and vector modifications to simulate collision handling, features high physical accuracy and decent stability. Orulex support is integrated. Expected to be released in april 2007 or in summer 2007 depending on bugfixing rate.
 +
 
 +
==General features==
 +
* Allows to land on terrain meshes, planetary meshes (asteroids less than 20Km for <2.0) and multi-level structures.
 
* Collision detection is largely independent from the sizes and amounts of landscape details.
 
* Collision detection is largely independent from the sizes and amounts of landscape details.
* The performance for engines 1 and 2 is unique.
+
* Generic vessel support allows to use unmodified vessels when landing on the landscape (With small limitations for <2.0).
* Generic vessel support allows to use unmodified vessels when landing on the landscape (With small limitations).
+
 
 +
==v1.1 Key Features==
 
* For advanced features there is Collision SDK.
 
* For advanced features there is Collision SDK.
* Also, a "3D surface" [[MFD]] is included, which is a scratch of [[Surface MFD]] with some Visosad controls.
+
* A "3D surface" [[MFD]] is included, which is a scratch of [[Surface MFD]] with some Visosad controls.
 +
* Project Apollo version allows limited tilting.
  
==Bugs/limitations==
+
==v1.1 Bugs/limitations==
 +
* Physically inaccurate solution.
 
* When vessels (all of them, unless modified) are in generic mode, landing gears are assumed to be in the same state (that of the beginning of the simulation) regardless of their current state.
 
* When vessels (all of them, unless modified) are in generic mode, landing gears are assumed to be in the same state (that of the beginning of the simulation) regardless of their current state.
 
* Bases that uses SPHEREMAPPED feature are not supported.
 
* Bases that uses SPHEREMAPPED feature are not supported.
 
* Configuration and documentation is known to be confusing.
 
* Configuration and documentation is known to be confusing.
 +
 +
==v1.9 Key Features==
 +
* Physically accurate collision solution.
 +
* For advanced features there is Collision SDK
 +
* V-V beta calculates collisions between vessels.
 +
 +
==v1.9 Bugs/limitations==
 +
* When vessels (all of them, unless modified) are in generic mode, landing gears are assumed to be in the same state (that of the beginning of the simulation) regardless of their current state.
 +
* Bases that uses SPHEREMAPPED feature are not supported.
 +
* Configuration and documentation is known to be confusing.
 +
* Little stability on slow systems or high time accelerations.
 +
 +
==v2.0 Key Features==
 +
* Landable terrain meshes, asteroids meshes, dynamic meshes and multi-level structures.
 +
* Physically accurate collision solution.
 +
* Generic vessel support allows to use unmodifyed vessels when landing on the landscape.
 +
* Collision SDK for landscape information and run-time mesh modifications.
 +
* Landing gears support.
 +
* Friction and springiness definition support.
 +
* High stability under higher time accelerations, possibly time accel-neutral scheme.
 +
* Very probably, a good manual-reference.
 +
 +
==v2.0 Bugs/limitations==
 +
N/A
  
 
==Links==
 
==Links==
* [http://www.orbithangar.com/searchid.php?ID=1396 Current version: 1.9.2.1 on Orbithangar]
+
* [http://www.orbithangar.com/searchid.php?ID=1396 Current version: 1.9.2.1_ml-060606 on Orbithangar]
* [http://cmc107.big-bossa.com/files/etc/ml-270206.zip Beta version (vessel-vessel collisions): ml-270206]
+
* [http://www.rumaxclub.ru/etc/ml-270206.zip Vessel-vessel beta version: ml-060227]
* [http://www.orbitersim.com/Forum/default.aspx?g=posts&t=4163 Beta thread at Orbiter forum]
+
* [http://sourceforge.net/project/downloading.php?groupname=nassp&filename=ProjectApollo_Meshland_20060717.zip&use_mirror=mesh Project Apollo version: 1.1_ml-060120]
* [http://artlav.land.ru Author main site (development status, etc)]
+
* [http://www.rumaxclub.ru/etc/meshland-1.1.zip MeshLand 1.x last release: 1.1_ml-060115]
 +
* [http://www.rumaxclub.ru/etc/visosad-2-10x.avi 2.0 preview video (20Mb, 3min, DivX5)]
 +
* [http://www.orbitersim.com/Forum/default.aspx?g=posts&t=13717 2.0 preview thread at Orbiter forum]
 +
* [http://www.orbitersim.com/Forum/default.aspx?g=posts&t=4163 Vessel-vessel beta thread at Orbiter forum]
 +
* [http://artlav.land.ru Author main site (development status, etc) (Beware of parasitic pop-ups)]
  
 
[[Category:Add-ons]]
 
[[Category:Add-ons]]
 
[[Category:Miscellaneous add-ons]]
 
[[Category:Miscellaneous add-ons]]

Revision as of 22:16, 21 April 2007

Project home: [N/A]
Author: Artlav
Current version: Unknown
Compatibility: Unknown


Jumping over rock
Driving over Fra Mauro
Landed at Vallis Dao rocks

MeshLand is an Orbiter plugin which offers a vessel-terrain and vessel-vessel collision detection and handling for Orbiter. MeshLand interfaces with Visosad, which is a rigid body physics simulator.

Versions and variants

MeshLand 1.x is based on the original idea collision detection engine. Collision handling utilised the Orbiter's LANDED state and touchdown points modification, which resulted in highly-stable and time acceleration-neutral system, but highly physically inaccurate model.

MeshLand 1.1 Apollo version is based on the 1.x engine, but with minimal tilting support and well-debuged SDK.

MeshLand-Visosad vessel-vessel beta is based on the new idea engine using forces and shifts to simulate collision handling, thus achiving higher physical accuracy, but lower stability. Only MeshLand version to date to be able to do plausible vessel-vessel collisions.

MeshLand-Visosad 1.9.x is based on the stabilised vessel-vessel collision beta with vessel-vessel part coded out, and vessel-terrain part fixed to presentable level.

MeshLand-Visosad-Orulex system is based on the 1.9.x version with collision detection removed and collision handling system linked directly to Orulex terrain function for collision data. Composes the ideas from 2.0 and 1.9, therefore quite unstable.

MeshLand-Visosad 2.0 is based on the new idea engine using shifts and vector modifications to simulate collision handling, features high physical accuracy and decent stability. Orulex support is integrated. Expected to be released in april 2007 or in summer 2007 depending on bugfixing rate.

General features

  • Allows to land on terrain meshes, planetary meshes (asteroids less than 20Km for <2.0) and multi-level structures.
  • Collision detection is largely independent from the sizes and amounts of landscape details.
  • Generic vessel support allows to use unmodified vessels when landing on the landscape (With small limitations for <2.0).

v1.1 Key Features

  • For advanced features there is Collision SDK.
  • A "3D surface" MFD is included, which is a scratch of Surface MFD with some Visosad controls.
  • Project Apollo version allows limited tilting.

v1.1 Bugs/limitations

  • Physically inaccurate solution.
  • When vessels (all of them, unless modified) are in generic mode, landing gears are assumed to be in the same state (that of the beginning of the simulation) regardless of their current state.
  • Bases that uses SPHEREMAPPED feature are not supported.
  • Configuration and documentation is known to be confusing.

v1.9 Key Features

  • Physically accurate collision solution.
  • For advanced features there is Collision SDK
  • V-V beta calculates collisions between vessels.

v1.9 Bugs/limitations

  • When vessels (all of them, unless modified) are in generic mode, landing gears are assumed to be in the same state (that of the beginning of the simulation) regardless of their current state.
  • Bases that uses SPHEREMAPPED feature are not supported.
  • Configuration and documentation is known to be confusing.
  • Little stability on slow systems or high time accelerations.

v2.0 Key Features

  • Landable terrain meshes, asteroids meshes, dynamic meshes and multi-level structures.
  • Physically accurate collision solution.
  • Generic vessel support allows to use unmodifyed vessels when landing on the landscape.
  • Collision SDK for landscape information and run-time mesh modifications.
  • Landing gears support.
  • Friction and springiness definition support.
  • High stability under higher time accelerations, possibly time accel-neutral scheme.
  • Very probably, a good manual-reference.

v2.0 Bugs/limitations

N/A

Links