Difference between revisions of "Orulex"

From OrbiterWiki
Jump to navigation Jump to search
(Added category.)
 
(29 intermediate revisions by 7 users not shown)
Line 1: Line 1:
 
{{Addon|
 
{{Addon|
 
1=http://orbides.1gb.ru|
 
1=http://orbides.1gb.ru|
2=Artlav
+
2=Artyom "Artlav" Litvinovich
 
}}
 
}}
[[Image:oru-39.jpg|200px|thumb|right|Io]]
+
[[Image:Oru-080401-1.jpg|200px|thumb|right|Earth in Orulex 1.0]]
[[Image:oru-23.jpg|200px|thumb|right|Venus]]
+
[[Image:Oru-080401-2.jpg|200px|thumb|right|Brighton Beach Crater on the Moon in Orulex 1.0]]
[[Image:oru-35.jpg|200px|thumb|right|Callisto]]
+
[[Image:Oru-080401-3.jpg|200px|thumb|right|Venus in Orulex 1.0]]
[[Image:oru-36.jpg|200px|thumb|right|Europa]]
+
[[Image:Oru-080401-7.jpg|200px|thumb|right|Nereid in Orulex 1.0]]
[[Image:oru-37.jpg|200px|thumb|right|Ganymede]]
 
[[Image:oru-38.jpg|200px|thumb|right|Mercury]]
 
[[Image:oru-er.jpg|200px|thumb|right|Earthrise from the Moon]]
 
  
'''Orulex''' is a dynamic landscape generator add-on for Orbiter which allows you to add a global landable meshes to the planets.
+
'''Orulex''' is a dynamic landscape generator add-on for Orbiter which allows users to add a global landable mesh to planets.
 +
Simply said, it turns flat planets into mountainous planets.
  
==Basic features (0.7.1)==
+
Latest stable version is 1.0
* Run-time generation of planet-wide meshes based on given mathematical expression.
+
Latest development version is 1.2_080527
* Supported functions are perlin noise, ridged perlin, sine and cosine terrain, i/o curve, crater, auxiliarys.
 
* Global and local heightmaps
 
* Automatic carving of surface bases into craters.
 
* Partially compatible with Visosad collision detection system.
 
 
 
==Known bugs/issues (0.7.1)==
 
* Static textures all over the planet.
 
* Blinking of the texture at night and with clouds.
 
* No mesh visible in windowed mode on some GPUs.
 
  
 
==Basic features (1.0)==
 
==Basic features (1.0)==
Line 29: Line 18:
 
* Easily downloadable textures and heightmaps data for Earth, and other planets.
 
* Easily downloadable textures and heightmaps data for Earth, and other planets.
 
* Lv11 global Orbiter and Lv6-Lv22 local downloaded textures (LandSat, USGS) support.
 
* Lv11 global Orbiter and Lv6-Lv22 local downloaded textures (LandSat, USGS) support.
 +
* Collision detection support possibilities and SDK interface
 +
 +
==System Requirements:==
 +
'''Out of the box:'''
 +
* 256Mb RAM + what Orbiter and OS takes.
 +
* 1.5+Ghz CPU, good video card (if it runs Orbiter Lv10+NASSP with good FPS it will run Orulex as if nothing is here).
 +
 +
'''Hi-quality:'''
 +
* 1Gb RAM + what Orbiter and OS takes + what local maps you will download.
 +
* 2-3Ghz CPU, ~1Gb of disk space, Fast Cheap internet (Lv9 heightmap is 466Mb download).
 +
 +
==Performance Guidelines (1.0)==
 +
* If you got a multi-core CPU, it is almost always better to keep multithread mode on.
 +
* If you got single-core CPU and Orulex feels slow on response or pre-computation takes longer than 10-15 seconds, try turning multithread mode off.
 +
* Reducing polygon count may help if you got an old video card.
 +
* Reducing LevLimit may give a more stable-looking landscape, but dropping quality exponentially.
 +
* If you got FPS jerks on older/single-core PC's, look on texture timings.
 +
TexGen-H defines time slice allocated when there is a lot to generate, TexGen-L defines time slice allocated when there are only small changes, like when you are flying around. Reducing them make Orbiter more responsive and terrain less responsive. Timings are not defined in multithread mode.
  
 
==Known bugs/issues (1.0)==
 
==Known bugs/issues (1.0)==
Line 35: Line 42:
 
* Textures getting colorfully random on some machines (probably Orbiter/DirectX bug on older systems).
 
* Textures getting colorfully random on some machines (probably Orbiter/DirectX bug on older systems).
  
==System Requirements:==
+
==Data download Servers List==
'''Out of the box:'''
+
'''Earth'''
* 256Mb RAM + what Orbiter and OS takes
+
* SRTM global Earth terrain
* 1.5+Ghz CPU, good video card
+
* NASA derived global 30 meters per pixel satellite image mosaic
  if it runs Orbiter Lv10+NASSP with good FPS it will run Orulex as if nothing is here
+
* NASA derived global 15 meters per pixel satellite image mosaic, donated and processed by I-Cubed using equipment from Isilon Systems.
 +
* USGS Digital Ortho
 +
* USGS Urban Area Ortho
 +
* Pseudo color 15m Landsat mosaic provided by MDA Federal, scenes comprised from early 2000s
 +
 
 +
'''Moon'''
 +
* Clementine global Moon terrain
 +
* Clementine 40xx
 +
* Clementine 30xx
 +
 
 +
'''Mars'''
 +
* MOLA global Mars terrain
 +
* Mars THEMIS Color
 +
 
 +
'''Venus'''
 +
* Magellan Imaging Radar (Color)
 +
* Magellan Imaging Radar (Grey)
 +
 
 +
==World Studio==
 +
World Studio is both the Orulex terrain config system and the versatile planet editor. It was first released on April 1, 2008 same with Orulex 1.0.
 +
 
 +
==Generator ideas and function description==
 +
===Configuration===
 +
 
 +
Orulex system configuration are done by World Studio program and config files editing, with options ranging from terrain polygon count to shapes of the worlds.
 +
2 PDF's with full description of world studio and file configuration can be found in the release package.
 +
 
 +
 
 +
 
 +
 
 +
===Basic ideas===
 +
 
 +
Function string in config\terrain\planet_name.cfg
 +
 
 +
* Planet functions is written in postfix notation.
 +
* In postfix, the sign of operation goes after the operands, so a+b will be ab+.
 +
* It have a significant comprehensive advantage, since there is no ()'s.
 +
* a+((b+f)*c+d/e) will be written as a b f+c*d e/++.
 +
* Functions specified the same way - f(x,y,z+w) is x y z w + f.
 +
 
 +
===Terrain function===
 +
 
 +
The terrain is represented by a 3 to 1 function with arguments being the position on the planet and output being the altitude at this position. The concept is similar to the plotting of 1D functions, like sine and cosine - the X axis represents the position, and Y axis represents the altitude:
 +
 
 +
[[Image:Functions in Orulex 1.jpg|800px|thumb|center|Imagine the same thing in 4D, and that's how it is done in Orulex.]]
 +
 
 +
===List of terrain functions===
 +
 
 +
====Perlin noise====
 +
[[Image:Terrain Functions.jpg|100px|thumb|left|Classic perlin noise ground function.]]
 +
;Syntax:<nowiki>perlin(xd,yd,zd,band,scale)</nowiki>
 +
;xd,yd,zd:Distortion values for x,y,and z coordinates respectively.
 +
;band: The amount of noise bands to be used - the more of them the more detailed terrain is, but slower.
 +
;scale: The horizontal scale of the thing. It is roughly equivalent to the size of the pattern shown in viewer on the actual planet, i.e. if scale is 10000 then the pattern will be spread across 10 kilometers.
 +
 
 +
Output is in -1..1 range.
 +
 
 +
====Ridge noise====
 +
[[Image:Terrain Functions 2.jpg|100px|thumb|left|Ridged perlin noise ground function. ]]
  
==Configuration==
+
;Syntax:<nowiki>ridge(xd,yd,zd,band,scale)</nowiki>
'''Main configuration''' can be found in visosad\orulex.cfg
 
* Enabled - Enable/disable the system
 
* Debug - Enable/disable the debug string
 
* Collisions - Collision support on/off
 
  
 +
;Syntax:<nowiki>perlin(xd,yd,zd,band,scale)</nowiki>
 +
;xd,yd,zd:Distortion values for x,y,and z coordinates respectively.
 +
;band: The amount of noise bands to be used - the more of them the more detailed terrain is, but slower.
 +
;scale: The horizontal scale of the thing. It is roughly equivalent to the size of the pattern shown in viewer on the actual planet, i.e. if scale is 10000 then the pattern will be spread across 10 kilometers.
  
'''Default parameters''' (used if planet cfg is empty of them):
+
Output is in -1..1 range.
* MaxPolyCount - Maximum polygon count for ground mesh. The bigger the nicer, but slower. (default=8000, gives FPS=100 here)
 
* Altlimit - Altitude of camera above ground for drawing cut-off.
 
* prit - Time step size for second cycle in us. Try lowering this, if you got big performance problems.
 
* sect - Time step size for second cycle in us. Try lowering this, if you got big performance problems.
 
* txtres - Mesh texture resolution. The higher, the more squarely the texture will look, the lower, the grayer the landscape will look.
 
  
'''Textures''' can be found in visosad\orulex\tex (planet_name.BMP, 1024x1024, 4 thru 32bit, fractalisible)
+
====Sea level====
 +
[[Image:Terrain Functions 3.jpg|100px|thumb|left|Sea level function with Perlin noise]]
  
'''Planets configuration''' can be found in visosad\orulex\planet_name.cfg
+
;Syntax:<nowiki>sealevel(f,min)</nowiki>
  
The parameters are same as above, but for planet only. Additional:
+
Same as <nowiki>min2(min,f)</nowiki>. Returns <math>f</math> if <math>f>=min</math> and <math>min</math> if <math>f<min</math>.
* seed=15777 The Number, that defines the planet.
 
* radius=1.738e6 Radius of mesh. Better be near radius of planet.
 
* texture - texture name.
 
  
==Planet functions==
+
Useful to truncate below the sphere part of the terrain function into flat valleys. Almost always should be removed if planet have ocean. If your planet have an ocean, make sure thet the underwater part of the function is not truncated!
'''Function=... in visosad\orulex\planet_name.cfg'''
 
  
Planet function, written in postfix notation. Better not to edit if you don't know what postfix notation is.
+
====Sinusoidal terrain====
 +
[[Image:Terrain Functions 4.jpg|100px|thumb|left|Sinusoidal terrain]]
  
'''Visosad\funcdrw program''' can display functions 3D graph. Requires OpenGL.
+
;Syntax:
 +
<nowiki>sintf(xd,yd,zd,scale)</nowiki>
  
 +
;xd,yd,zd:Distortion values for x,y,and z coordinates respectively.
 +
;scale: The horizontal scale of the thing. It is roughly equivalent to the size of the pattern shown in viewer on the actual planet, i.e. if scale is 10000 then the pattern will be spread across 10 kilometers.
  
'''Operators:'''
+
Output is in -1..1 range.
* sbcrater(scl) - defines surface base craters with scl height.
 
* perlin(xd,yd,zd,band,scale) - perlin noise ground function
 
* ridge(xd,yd,zd,band,scale) - ridged perlin noise ground function
 
* curv(n,f,x1,y1,x2,y2,...,x(n-1)/2,y(n-1)/2) - Input/Output curve for f by points of xi,yi, lagrange interpolated.
 
* sealevel(level) -sphere level cutoff function
 
* +, -, --, *, /, sin, cos, max2, max3, min2, min3 - arithmetics.
 
* ax,ay,az - world coordinates.
 
* trim(f,min,max) - trims f into min<f<max.
 
  
'''Heightmaps'''
+
====Cosinusoidal terrain====
 +
[[Image:Terrain Functions 5.jpg|100px|thumb|left|Cosinusoidal terrain]]
  
heightmap=Testmapmoon        |000041.025|000041.225|-0033.8375|-0033.6375|00002000|0
+
;Syntax:<nowiki>costf(xd,yd,zd,scale)</nowiki>
  
Heightmap definition. Can be several of them.
+
;xd,yd,zd:Distortion values for x,y,and z coordinates respectively.
 +
;scale: The horizontal scale of the thing. It is roughly equivalent to the size of the pattern shown in viewer on the actual planet, i.e. if scale is 10000 then the pattern will be spread across 10 kilometers.
  
All fields have fixed widths - 20|10|10|10|10|8|1
+
Output is in -1..1 range.
  
First is filename relative to visosad\orulex\hmap, then longitude of start, longitude of end, latitude of start, latitude of end, vertical scale, function
+
====Curve function====
 +
;Syntax:<nowiki>curv(n,f,x1,y1,x2,y2,...,x(n-1)/2,y(n-1)/2)</nowiki>
  
  
Where function is:
+
Input/Output curve for f by points of xi,yi, lagrange interpolated. It is a very powerful tool, allowing to map the inputs to according to specific curve to the output, changing gradients and similar things. The I/O curve is too big a topic for this manual.  
* 0 - addition (height-map)
+
For example: Callisto
* 1 - multiplication (mask-map).
 
* 2 - replacation (plain height-map)
 
  
Heightmap file is a grayscale BMP with black as 0 and white as vertical scale altitude. 8bit BMP's seems to give errors.
 
  
 +
====Other operators/functions====
 +
;ax,ay,az:world coordinates
 +
;+, -, --, *, /, sin, cos, tan, ln, pow, round, trunc, sqr, sqrt max2, max3, min2, min3: Arithmetics and basic math
 +
;trim(f,min,max): trims f into <math>min<f<max</math>
  
'''Run-time configuration''', found on page 2 of Orulex 3D Surface MFD:
+
==See Also==
* Enabled - Enable/disable the drawing of the mesh.
+
[[Meshland]]
* Debug - Enable/disable the debug string
 
* Collisions - Collision support on/off
 
  
==Links==
+
==Download Links==
 
[http://orbides.1gb.ru/orulex.php Orulex's Homepage by Artlav]
 
[http://orbides.1gb.ru/orulex.php Orulex's Homepage by Artlav]
  
[http://www.orbithangar.com/searchid.php?ID=2686 Download at OrbiterHangar]
+
[http://www.orbiter-forum.com/showthread.php?t=2007 Development version Orbiter forum thread]
 +
 
 +
[https://www.orbiter-forum.com/resources/orulex_land_gen-v1-2.2390/ Orulex_Land_Gen-v1.2] Orbiter Forum/Resources.
 +
 
 +
[http://www.orbiter-forum.com/showthread.php?t=999 1.0 Orbiter forum thread]
 +
 
 +
==Additional links==
 +
 
 +
'''Extensions'''
 +
 
 +
[http://orbides.1gb.ru/orbf/MLVS-WIP-080327.zip WIP MeshLand 2, Collision Detection support for Orulex, Unstable]
 +
 
 +
[http://orbides.1gb.ru/orbf/OrulexSDK-allvers.zip Interface SDK (Delta-Glider samples included)]
 +
 
 +
'''Pre-composed heightmaps'''
 +
 
 +
[http://orbides.1gb.ru/orbf/earth-hmap-lv8.zip Earth Lv8 heightmap (84Mb)]
 +
 
 +
[http://orbides.1gb.ru/orbf/mars-hmap-lv8.zip Mars Lv8 heightmap (82Mb)]
 +
 
 +
[http://orbides.1gb.ru/orbf/moon-hmap-lv8.zip Moon Lv8 heightmap (81Mb)]
 +
 
 +
[http://orbides.1gb.ru/orbf/everest_lv11.zip Everest Lv11 textures and heightmaps (5.3Mb)]
 +
 
 +
[http://orbides.1gb.ru/orbf/grand_canyon_lv13.zip Grand Canyon Lv13 textures and heightmaps (9Mb)]
 +
 
 +
'''Demonstaration video'''
 +
 
 +
[http://orbides.1gb.ru/orbf/oru-flight-080321-x264.avi China flying in Gregburch's Swift1 (x264, 21 MB)]
  
[http://www.orbitersim.com/Forum/default.aspx?g=posts&t=15133 Orbiter forum thread]
+
[http://orbides.1gb.ru/orbf/oru-flight-080321-xvid.avi China flying in Gregburch's Swift1 (xVid, 31 MB)]
  
 +
[[Category: Articles]]
 
[[Category:Add-ons]]
 
[[Category:Add-ons]]
[[Category:Celestial body add-ons]]
 

Latest revision as of 11:49, 15 October 2022

Project home: http://orbides.1gb.ru
Author: Artyom "Artlav" Litvinovich
Current version: Unknown
Compatibility: Unknown


Earth in Orulex 1.0
Brighton Beach Crater on the Moon in Orulex 1.0
Venus in Orulex 1.0
Nereid in Orulex 1.0

Orulex is a dynamic landscape generator add-on for Orbiter which allows users to add a global landable mesh to planets. Simply said, it turns flat planets into mountainous planets.

Latest stable version is 1.0 Latest development version is 1.2_080527

Basic features (1.0)[edit]

  • Generates planet terrain in Orbiter on the fly, using real data or fractal functions.
  • Easily downloadable textures and heightmaps data for Earth, and other planets.
  • Lv11 global Orbiter and Lv6-Lv22 local downloaded textures (LandSat, USGS) support.
  • Collision detection support possibilities and SDK interface

System Requirements:[edit]

Out of the box:

  • 256Mb RAM + what Orbiter and OS takes.
  • 1.5+Ghz CPU, good video card (if it runs Orbiter Lv10+NASSP with good FPS it will run Orulex as if nothing is here).

Hi-quality:

  • 1Gb RAM + what Orbiter and OS takes + what local maps you will download.
  • 2-3Ghz CPU, ~1Gb of disk space, Fast Cheap internet (Lv9 heightmap is 466Mb download).

Performance Guidelines (1.0)[edit]

  • If you got a multi-core CPU, it is almost always better to keep multithread mode on.
  • If you got single-core CPU and Orulex feels slow on response or pre-computation takes longer than 10-15 seconds, try turning multithread mode off.
  • Reducing polygon count may help if you got an old video card.
  • Reducing LevLimit may give a more stable-looking landscape, but dropping quality exponentially.
  • If you got FPS jerks on older/single-core PC's, look on texture timings.

TexGen-H defines time slice allocated when there is a lot to generate, TexGen-L defines time slice allocated when there are only small changes, like when you are flying around. Reducing them make Orbiter more responsive and terrain less responsive. Timings are not defined in multithread mode.

Known bugs/issues (1.0)[edit]

  • Windows Vista random CTD.
  • Dislocated patches when flying with multithreaded mode on.
  • Textures getting colorfully random on some machines (probably Orbiter/DirectX bug on older systems).

Data download Servers List[edit]

Earth

  • SRTM global Earth terrain
  • NASA derived global 30 meters per pixel satellite image mosaic
  • NASA derived global 15 meters per pixel satellite image mosaic, donated and processed by I-Cubed using equipment from Isilon Systems.
  • USGS Digital Ortho
  • USGS Urban Area Ortho
  • Pseudo color 15m Landsat mosaic provided by MDA Federal, scenes comprised from early 2000s

Moon

  • Clementine global Moon terrain
  • Clementine 40xx
  • Clementine 30xx

Mars

  • MOLA global Mars terrain
  • Mars THEMIS Color

Venus

  • Magellan Imaging Radar (Color)
  • Magellan Imaging Radar (Grey)

World Studio[edit]

World Studio is both the Orulex terrain config system and the versatile planet editor. It was first released on April 1, 2008 same with Orulex 1.0.

Generator ideas and function description[edit]

Configuration[edit]

Orulex system configuration are done by World Studio program and config files editing, with options ranging from terrain polygon count to shapes of the worlds. 2 PDF's with full description of world studio and file configuration can be found in the release package.



Basic ideas[edit]

Function string in config\terrain\planet_name.cfg

  • Planet functions is written in postfix notation.
  • In postfix, the sign of operation goes after the operands, so a+b will be ab+.
  • It have a significant comprehensive advantage, since there is no ()'s.
  • a+((b+f)*c+d/e) will be written as a b f+c*d e/++.
  • Functions specified the same way - f(x,y,z+w) is x y z w + f.

Terrain function[edit]

The terrain is represented by a 3 to 1 function with arguments being the position on the planet and output being the altitude at this position. The concept is similar to the plotting of 1D functions, like sine and cosine - the X axis represents the position, and Y axis represents the altitude:

Imagine the same thing in 4D, and that's how it is done in Orulex.

List of terrain functions[edit]

Perlin noise[edit]

Classic perlin noise ground function.
Syntax
perlin(xd,yd,zd,band,scale)
xd,yd,zd
Distortion values for x,y,and z coordinates respectively.
band
The amount of noise bands to be used - the more of them the more detailed terrain is, but slower.
scale
The horizontal scale of the thing. It is roughly equivalent to the size of the pattern shown in viewer on the actual planet, i.e. if scale is 10000 then the pattern will be spread across 10 kilometers.

Output is in -1..1 range.

Ridge noise[edit]

Ridged perlin noise ground function.
Syntax
ridge(xd,yd,zd,band,scale)
Syntax
perlin(xd,yd,zd,band,scale)
xd,yd,zd
Distortion values for x,y,and z coordinates respectively.
band
The amount of noise bands to be used - the more of them the more detailed terrain is, but slower.
scale
The horizontal scale of the thing. It is roughly equivalent to the size of the pattern shown in viewer on the actual planet, i.e. if scale is 10000 then the pattern will be spread across 10 kilometers.

Output is in -1..1 range.

Sea level[edit]

Sea level function with Perlin noise
Syntax
sealevel(f,min)

Same as min2(min,f). Returns if and if .

Useful to truncate below the sphere part of the terrain function into flat valleys. Almost always should be removed if planet have ocean. If your planet have an ocean, make sure thet the underwater part of the function is not truncated!

Sinusoidal terrain[edit]

Sinusoidal terrain
Syntax

sintf(xd,yd,zd,scale)

xd,yd,zd
Distortion values for x,y,and z coordinates respectively.
scale
The horizontal scale of the thing. It is roughly equivalent to the size of the pattern shown in viewer on the actual planet, i.e. if scale is 10000 then the pattern will be spread across 10 kilometers.

Output is in -1..1 range.

Cosinusoidal terrain[edit]

Cosinusoidal terrain
Syntax
costf(xd,yd,zd,scale)
xd,yd,zd
Distortion values for x,y,and z coordinates respectively.
scale
The horizontal scale of the thing. It is roughly equivalent to the size of the pattern shown in viewer on the actual planet, i.e. if scale is 10000 then the pattern will be spread across 10 kilometers.

Output is in -1..1 range.

Curve function[edit]

Syntax
curv(n,f,x1,y1,x2,y2,...,x(n-1)/2,y(n-1)/2)


Input/Output curve for f by points of xi,yi, lagrange interpolated. It is a very powerful tool, allowing to map the inputs to according to specific curve to the output, changing gradients and similar things. The I/O curve is too big a topic for this manual. For example: Callisto


Other operators/functions[edit]

ax,ay,az
world coordinates
+, -, --, *, /, sin, cos, tan, ln, pow, round, trunc, sqr, sqrt max2, max3, min2, min3
Arithmetics and basic math
trim(f,min,max)
trims f into

See Also[edit]

Meshland

Download Links[edit]

Orulex's Homepage by Artlav

Development version Orbiter forum thread

Orulex_Land_Gen-v1.2 Orbiter Forum/Resources.

1.0 Orbiter forum thread

Additional links[edit]

Extensions

WIP MeshLand 2, Collision Detection support for Orulex, Unstable

Interface SDK (Delta-Glider samples included)

Pre-composed heightmaps

Earth Lv8 heightmap (84Mb)

Mars Lv8 heightmap (82Mb)

Moon Lv8 heightmap (81Mb)

Everest Lv11 textures and heightmaps (5.3Mb)

Grand Canyon Lv13 textures and heightmaps (9Mb)

Demonstaration video

China flying in Gregburch's Swift1 (x264, 21 MB)

China flying in Gregburch's Swift1 (xVid, 31 MB)