|
@@ -1,6 +1,6 @@
|
|
|
<H2>DESCRIPTION</H2>
|
|
|
|
|
|
-The <EM>d.nviz</EM> program allows the user to easily create a script
|
|
|
+The <EM>m.nviz.script</EM> program allows the user to easily create a script
|
|
|
that can be run in NVIZ to fly through a terrain.
|
|
|
|
|
|
The NVIZ flight path can be chosen interactively from the GRASS
|
|
@@ -11,7 +11,7 @@ be loaded into the <EM>Keyframe Animation</EM> panel for fine
|
|
|
tuning or editing.
|
|
|
|
|
|
<p>
|
|
|
-The script generated by <EM>d.nviz</EM> can be run from the NVIZ
|
|
|
+The script generated by <EM>m.nviz.script</EM> can be run from the NVIZ
|
|
|
command line (nviz script=script_name) or after NVIZ is started by
|
|
|
selecting <EM>Scripting->Play Script</EM>.
|
|
|
|
|
@@ -88,7 +88,7 @@ the scene, run the following:
|
|
|
<div class="code"><pre>
|
|
|
g.region rast=elevation.dem
|
|
|
d.rast elevation.dem
|
|
|
-d.nviz -ik input=elevation.dem output=nviz.script dist=2400 ht=1220 frames=1000
|
|
|
+m.nviz.script -ik input=elevation.dem output=nviz.script dist=2400 ht=1220 frames=1000
|
|
|
</pre></div>
|
|
|
In the above the example the user is prompted to select the route from the GRASS monitor.
|
|
|
The output script, 'nviz.script.nvscr', can then be run in NVIZ:
|
|
@@ -100,7 +100,7 @@ nviz elevation=elevation.dem script=nviz.script.nvscr
|
|
|
The user must select at least four key-frame locations (points)
|
|
|
otherwise an error is generated.
|
|
|
<p>
|
|
|
-If the GRASS region is changed the <EM>d.nviz</EM> command must be re-run.
|
|
|
+If the GRASS region is changed the <EM>m.nviz.script</EM> command must be re-run.
|
|
|
<p>
|
|
|
The current GRASS region and the user supplied parameters are included
|
|
|
as a comment at the top of the output script. This information can be
|
|
@@ -118,16 +118,16 @@ the <EM>dist=</EM> parameter or increase the current region.
|
|
|
The user can run the script at arbitrary resolution. To re-run it at
|
|
|
higher spatial resolution or different settings, the user first loads
|
|
|
the surface and sets the resolution, lighting, etc. Then internally
|
|
|
-the script generated by <em>d.nviz</em> is run. Alternatively, the
|
|
|
+the script generated by <em>m.nviz.script</em> is run. Alternatively, the
|
|
|
user can run nviz with a previuosly saved state and the
|
|
|
-<em>d.nviz</em> generated script:
|
|
|
+<em>m.nviz.script</em> generated script:
|
|
|
|
|
|
<div class="code"><pre>
|
|
|
nviz state=saved.state script=nviz.script.nvscr
|
|
|
</pre></div>
|
|
|
|
|
|
<h3>Keyframe animator script</h3>
|
|
|
-Running the script generated by d.nviz within NVIZ, a new script for
|
|
|
+Running the script generated by <em>m.nviz.script</em> within NVIZ, a new script for
|
|
|
kanimator (keyframe animator) is created. The kanimator panel offers
|
|
|
fine tuning of the speed (frame rate) as well as editing individual
|
|
|
frames or inserting new frames. This new kanimator script has to be
|