Mod Tool: Difference between revisions

Mod Tool (view source)

Revision as of 14:11, 17 September 2012

1,082 bytes removed , 17 September 2012

m

no edit summary

Paradox-01

8,452

edits

@@ Line 41: / Line 41: @@
-'''how to install addons (.xsiaddon)'''
+'''how to install add-ons (.xsiaddon)'''
 * A) drag'n'drop the file into the so-called viewport (it's simply the window where you can see 3D objects), then restart Mod Tool
 * B) if drag and drop doesn't work, goto "File" > "Add-On" > "Install"
@@ Line 47: / Line 47: @@
-'''[http://softimage.wiki.softimage.com/sdkdocs/cus_addons_WalkthroughBuildinganAddon.htm building .xsiaddon]'''
+'''[http://softimage.wiki.softimage.com/sdkdocs/cus_addons_WalkthroughBuildinganAddon.htm building add-ons]'''
-* So far building an addon file seems to be the most difficult among those 'extension' files but for the end user it's best because it can hold all other files: toolbars, plugins, etc.
+* So far building an addon file seems to be the most difficult among those 'extension' files but for the end user it's best because it can hold all other files: toolbars, plugins (scripts), etc.
+* File > Add-On > Package... doesn't work with ModTool "Add-Ons cannot be created with Softimage Demo Version."
-'''new notes [in progress]'''
+* '''putting scripts simply into folders doesn't work, they must be "plugins" (file extension can be the same e.g. "vbs")'''
-* so, simply putting scripts into folders didn't worked, they must be "plugins" (file extension is the same e.g. vbs but they do also something else)
+** a script can run on another computer if its content is found under a command, and plugin register that new command(s)
-* a script can run on another computer if its content is found under a command, and plugin register that new command(s)
+** e.g. use those commands in your toolbar's script buttons
-* [...]
+* images can be put into any folder of the add-on, get them with '''''XSIUtils.ResolvePath("$XSI_USERHOME/") & "Addons\'''Addon_name\your_img_folder\img.png"''
+* The problem with embedded code: commands like ''CreatePrim'' can call an property page (PPG)
-'''old notes'''
+** But those popups can be disabled. Search for "disabling PPG popups" on this page.
-* It Seems not to work with script file (but embedded code does), the [http://xsisupport.com/2012/04/30/packaging-toolbars-and-script-commands-into-addons/ alternate method] (File > Add-On > Package... ) doesn't work at all with ModTool ... "Add-Ons cannot be created with Softimage Demo Version."
-* The problem with embedded code:
-: Let's say you want to integrate a toolbar into the xsiaddon file. The toolbar button was created as '''Script Button''' and holds: ''CreatePrim "Cube", "MeshSurface"''
-: When using that button it will also call the cube's property page. Imagine what happens if you make a script that creates hundreds of objects. Right, the user would have to close all those property pages.
-: The property pages (PPG) will not open if the button was created as '''Script Command''' linking to an external script file. But xsiaddon seems unable to ship the script file's location as relative path. The relative path is needed because other user could have Mod Tool installed in a different location. What now?
-: '''''ExecuteScript XSIUtils.ResolvePath("$XSI_USERHOME/")''' & "Addons\Oni_TRGV_tools\Application\Plugins\add_TV.vbs"'' This example use ''ExecuteScript'' to lunch a script file and ''XSIUtils.ResolvePath("$XSI_USERHOME/")'' to get the first part of it's location. The rest of the path depends how the author stores the files on the system where the addon was created.
-: That combination of embedded code and extern script file could create the cube without opening the PPG.
@@ Line 871: / Line 864: @@
 ====script ideas====
+* automatic cam position update if user selects an object
+* import/export of flag collection
+* import/export of patrol path collection
+* import/export of weapons collection
+* import/export of powerup collection
+* [...]
 * drag and drop support for specific xml/oni files
 * autoheal discontinuities (blue lines) of overlaying edges (for repairing google sketchup objects that weren't yet textured)
@@ Line 885: / Line 884: @@
 |}
-* Oni to ModTool
+* status: done
-** conversion of oni to xml [done]
+* release date: Christmas ?
-** import of TV collection [done]
+: I don't see a demand for it, so I will wait and see if I can add other tools to the add-on.
-** adding a new TV [done]
-** transparent textures for TVs [-]
-** TV properties form (PPG) [done]
-* ModTool to Oni [done]
-* xsiaddon file [done] (working beta)
-release date: Christmas ?
-: I don't see a big demand for it atm, so I will wait and see if I can add other tools to the add-on.