User Tools

Site Tools


visual3d:tutorials:pipeline:meta_command_creation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
visual3d:tutorials:pipeline:meta_command_creation [2025/07/09 18:10] sgrangervisual3d:tutorials:pipeline:meta_command_creation [2025/07/09 18:16] (current) sgranger
Line 10: Line 10:
  
 Here is an extremely simplistic example: \\ Here is an extremely simplistic example: \\
-Script1 below prompts you to enter a number, and script2 prints it out. \\+Script1 below prompts you to enter a number, and Script2 prints it out. \\
  
-<small>(**Note:** Naturally, these scripts will not run separated like this – the input value would have to be stored somewhere. Using a Call_Script command also fails because it does not pass data.)</small>+**Note:** Naturally, these scripts will not run separated like this – the input value would have to be stored somewhere. Using a Call_Script command also fails because it does not pass data.
  
 <code> <code>
Line 21: Line 21:
  ;    ;  
 </code> </code>
- 
-\\ 
- 
  
 <code> <code>
Line 34: Line 31:
 </code> </code>
  
-Here is a process to modify the scripts so that they work together:\\+Here is a process to modify the scripts so that they work together:
  
 +  - Convert the second script to a meta-command
 +  - Save the new meta-command in the proper Visual3D directory
 +  - Edit the first script to call the meta-command
  
-  - Convert the second script to a meta-command\\ +Edit **Script2.v3s** and change it to the following, and save it as **number_game.v3m**. \\ 
- +Note that the meta-command syntax is simply a few lines as a header, and then changing any input parameter names to match. For the syntax of the header see [[Visual3D:Documentation:Pipeline:Meta_Commands:Meta_Commands_Overview|Pipeline_Commands:Meta_Commands]].
-  - Save the new meta-command in the proper Visual3D directory\\ +
- +
-  - Edit the first script to call the meta-command\\ +
- +
- +
-\\ +
-Edit **Script2.v3s** and change it to the following, and save it as **number_game.v3m**. //Note that the meta-command syntax is simply a few lines as a header, and then changing any input parameter names to match. For the syntax of the header see [[Visual3D:Documentation:Pipeline:Meta_Commands:Meta_Commands_Overview|Pipeline_Commands:Meta_Commands]].//+
  
 <code> <code>
Line 62: Line 55:
 </code> </code>
  
-Copy the file **number_game.v3m** to the meta-command directory: Possibly: C:\Program Files (x86)\Visual3D v5\ Plugins\Meta-Commands +Copy the file **number_game.v3m** to the meta-command directory: Possibly: C:\Program Files (x86)\Visual3D v5\ Plugins\Meta-Commands \\
- +
-\\+
 Edit **Script1.v3s** and change it to the following: Edit **Script1.v3s** and change it to the following:
  
Line 79: Line 70:
 </code> </code>
  
-That’s it. Restart Visual3D and run the new **script1.v3s**.+That’s it. Restart Visual3D and run the new **script1.v3s**. \\
  
 Note also that if you copy script1.v3s to C:\Program Files (x86)\Visual3D v5\Plugins\Scripts then the script will show up in the box on the workspace tab in Visual3D for easy access. Note also that if you copy script1.v3s to C:\Program Files (x86)\Visual3D v5\Plugins\Scripts then the script will show up in the box on the workspace tab in Visual3D for easy access.
visual3d/tutorials/pipeline/meta_command_creation.1752084636.txt.gz · Last modified: by sgranger