Vz:Doc:Running
From M1Research
(Difference between revisions)
| (One intermediate revision not shown) | |||
| Line 1: | Line 1: | ||
Starting of <b>VZ</b> is very simple. | Starting of <b>VZ</b> is very simple. | ||
| - | Make sure your shortcut's | + | Make sure your shortcut's <code>Start in:</code> point to <b>VZ</b> folder - all plugins and output drivers searched from current directory. |
<b>VZ</b> has to parameters to run: | <b>VZ</b> has to parameters to run: | ||
| Line 9: | Line 9: | ||
During running <b>VZ</b> produce a lot of messaging information. Sometime it's cause performance degradation. To avoid this its possible to redirect outputs to files: | During running <b>VZ</b> produce a lot of messaging information. Sometime it's cause performance degradation. To avoid this its possible to redirect outputs to files: | ||
<pre>vz.exe >log_std 2>log_err</pre> | <pre>vz.exe >log_std 2>log_err</pre> | ||
| + | |||
| + | Another usefull things is running <b>vz</b> from batch file, for example batch file <code>task1.bat</code> starts <b>vz</b> with defined scene and config: | ||
| + | <pre>vz.exe -f ./task1/project.xml -c ./task1/no_video.conf >log_std 2>log_err</pre> | ||
Latest revision as of 18:39, 24 March 2007
Starting of VZ is very simple.
Make sure your shortcut's Start in: point to VZ folder - all plugins and output drivers searched from current directory.
VZ has to parameters to run:
-fdefine scene to load aftervz.exestartup (usefull for automatic scene load)-coverrides config file used. By default usedvz.conffile from current location - using this option its able to override used config file.
During running VZ produce a lot of messaging information. Sometime it's cause performance degradation. To avoid this its possible to redirect outputs to files:
vz.exe >log_std 2>log_err
Another usefull things is running vz from batch file, for example batch file task1.bat starts vz with defined scene and config:
vz.exe -f ./task1/project.xml -c ./task1/no_video.conf >log_std 2>log_err
