ggg
04-06-2003, 12:00 AM
Seems its wishlist season again.
http://www.xsibase.com/forum/index.php?board=9;action=display;threadid=5039
______________________
GUI/Workflow/Interface
----------------------
-network object/operator view with ability to interactively wire I/Os between (perhaps also with interOPs between to modify data before use, more accessible than linked paramters and expressions)
-a much fuller expression language including many more functions and scene and object/element variables
-better OP control, here is a comparison between XSIs OP stack and Houdinis network:
http://www.xsibase.com/forum/index.php?board=1;action=display;threadid=199
-groups that are more than selection sets more than a place to share materials, allow geometry groups of objects and/or components that can have operators applied.
-3d widgets for operators in 3D viewer to control parameters of OPs as well as in FXtree, ie pull on normal for extrude
-ability in edit layout to assign one view as always on bottom and one view as always on top in GUI
-a quick way to keep some "display info" params in view for non-slected objects
-in explorer and hopefully network view to come, allow us to create folders under models for everything or at least have folders for annotations to organize, with a toggle view normal or with folders
-a way to show annotations only in explorer
-differnt types of annotaions, perhaps a viewer type annotation that can be displayed in the 3D viewer and the object selectable by clicking on the text.
-option to toggle/show hidden objects in object view
-display component index numbers in 3D views
-object view select any camera view too
-layout memory for all floating views when you start up again
-option for no title bar on custom toolbars
-an xsi taskbar that doesn't bump your layout to the right
-option for active splitter bars even when not in edit layout mode
-viewer order ie one type defined as always on bottom and one type such as PPGs always on top in GUI
-when you set BG to black wireframe should obviously not be black, better yet list user scene custom color sets in menu
-option to include scene color sets in layout save
-fix layout addons so like earlier versions, layouts show up or at least can be installed for different rez, otherwise one must package each rez layouts seperately
-short annotation or displayinfo of text parameters on selected or all unselected objects surfaces or center instead of flush with view plane
-ability to mouse-drag-select nothing in explorer view and have objects, node etc deselect
-allow easier defualt setting creation eg for default camera creation, kinematics, lens etc. the default camera 2 units up is maybe for demonstrators not users
-start/stop that works with exponential camera fog depth cue
-where is the depthcue type property accessible? for eg to add to an overide
-when a view containing sliders, such as for custom PPGs, rather than have the slider turn to value field if the view is too narrow or the name too long, put the slider on a row below instead
-show the "constrainer" name in the constriant PPG and allow one to change the constrainer object in the PPG or via an OP network GUI connecion to another object with or without offset/compensation.
-Show relations is cool, perhaps also Show the constainer in the constrain OP PPG and highlight it and the effected objects.
-scroll bar in synoptic editor
-dragndrop commands into auto synoptic hot spots
-OP stack dragndrop onto other objects/components or reuse or multiple use of OP stacks in a network GUI so fx or tools don't have to be redone/rebuilt every time
-forward<>backward through images in image clip viewer and ability to split view in there if for example suing it for ref pics to model form instead of having a gazillion image clip views open
-filmstrip storyboard viewer, with abiltiy to order/edit clips in animation mixer, perhasp have it use the .mov format so that anootaions per clip or timecode can be added as well as triggers for other events.
-ability to put image clips into a "reference" folder so they will not be deleted by "delete unused clips". these are images that will be used for rotoscoping, modeling refs etc.
-allow ordering of models in explorer, actions etc based not just on creation order or alpha numeric but also on a flag or ID o rmaybe a mode that allows auto id while user custom reorders their stuff.
-allow F to work in XIS explorer evenwhen object is not he one displayed in there, ie for use when ref or higher subD'd clone object is displayed in XSI explorer while selecion an dowrk is doen on original in another view.
-allow raycast shaded to work in xray mode as it should
-option to not have OP folders open when secting them for exmaple when selecting along movecompoent folder to freeze it, no one would wan it to open here
-definable zoom amount pref setting per component type
-make all display options animatable even boolean ones for quick and easy custom pset dragndrop paramter connection
-imageclip scrollbars or "Z" and "S" navigation
-a way to DL all of netview as a local copy to navigate on ones laptop for example.
-middle bar collapse for XSI explorer should be able to go both ways, an option to collapse the explorer or the viewer, perhasp add another arrow pointign the other way just below existing one.
-an estimate of file size while working at top of XSI
-display OP memory usage
-allow BG color different in different viewports
-view mode for both sides of XSI explorer
-"F" or frame all in aniamtion view, maybe I'm missing a setting but it doesn't work consitently
added:
-when XSI window is minimized, put scroll bars on sides
-ability to set side for scroll per view
-a view for "show all parameter values" in explorer, not just marked
-rather than just saving out seperate scenes, an easy to use and organize scene viewer and organizer via layer/pass/mixer settings by shot.
--perhaps tie it in with storyboard viewer
--allow time shifting of the entire shot including all its param keys, mixer clip placement etc
-add a netview that can subscribe to the xsi list and
-improved transformaion handles
--one handle that includes, scale transform and rotation controls with ctrl option list of align pivot to anoterh surface point origin etc
--keyable handles that effect selected objects paramters accordingly
-although method to adjust same OPs of different models works, also good would be ability to have "shared" OPs and per model variables to insert in OP param fields
-as well as the ability open a multi PPG also have one that opens a that OP seprately in sanme view fro each model/object
-a way to move top menus to right screen
-like in Adobe Imageready a full screen menu view with menu bar
-get rid of ANNOYING resolution pop up at XSI start up!
-add a text editor view, even just the basic MS notepad in a view, jot for irix, etc
-in 3D view, add a user view from last camera
added2:
-ability to view at any point in stack with XSI object viewer and also at different time.
_________________________
Modeling
------------------------
-bezier handle control on SubDs, 4 handles
-ability to quickly and easily duplicate/clone using animation, maybe using SCOPs if an example could be put up somewhere
-3D widgets control for all tools and OPS in viewer, ie pull on normal to extrude in extrude mode
-option in prefs to set what transform mode component default selection and "m" move points goes into instead of local and view which they repsectively do now. I would rather have both go into local personally and know others might have other prefs.
-ability to move some OPs center effect position on surface and animate position in UV, with fall off or component selection area (via BBox or proximity etc) also moving with it instead of specific cluster component #s
-have component/object-group selection bounding box and or proximity field work with weight maps too to modify their values and have their positions animatable.
-extract poly keeps local center orientaion and position opition
--also an option to have cluster center orient locally to original components on creation would be cool versus the default orientation globally.
-ability to turn off points view in "T" point mode so that point tweaking transorming can take plac ein one view while seeing an unobstructed view of shaded model in another. or perhasp an option to only turn on point view when T or shift (while in point mode) is pressed
-if possible have fog effect component selectability too, such while working on a poly hull cage points
-subD bezier handles :)
--some advantage would be the obvious ability to to move the handles and change the curvature bewteen it and the next point on the surface,
--could also be useful if the handles length could be changed and handles broken to define creases/hardness and surface direction, would be cool if they were animatable too, using clusters of handles to animate would be OK.
like the idea of direct point manipulaion on surface, it could only show points at the level you are subdividing though as manipulaion of points inbetween would require a physical subdivison to that level.
--another method of SUbD interpolation, actually passing suface through points would also be cool, so that curves and surfaces passed through the points or at least appeared to for easier navigation and manipulation, or a definable amount using point weight, not like crease, keeping curvature
--as suggested by many, a way to move components on the actual subD surface. would likely require a way to propegate the effect back up to be recorded on the actual hull
--would also be nice to have Bounding box, array, proximity, expression or other type of flexible selection group (not hard numbered clusters currently used for OP input) that could be animated such as BBox position so that the area locally subdivided could be moved as needed
-match symettry tool, ie select a component on one side of geo and component on other side of axis snaps to exact mirrored location. often when working in symmetry mode one will switch it off to give differnce to each side of the model and may want to fix one side to match the other, copy flipping xyz values is too slow for many points
-fix symmettry its often breaking and not reflecting the same point selection on other side of object
-proporional modeling points on another surface being modified incorrectly show in in XSI explorer view displaying another object
-weight maps that include effect on other components than versitces and paint properties, such as edge so that ti can be used to paint hardedge/crease fro subDs and have edges crease, not just points, so that it is useful for most needs.
-animatable profiles such as in buldge defomer
-perhsaps exists already, a mirror cluster or mirror select points
-point weight, for NURBS. And for SubDs perhaps allow the property to remain with the point even when topology # or order changes
added:
-procedural Lsystems
-since Houdini has more advanced procedural modeling and interface, perhaps via channels or an I/O node to connect XSI params to Houdini Select params would be useful
-ability to lock points in position with option for which axis. Useful for when mirror modelling.
-allow weight paint mixing on cage deformers for overlapping cages etc
-a limit on points to deform ony in their initial normal direction ( for muscle simulation etc)
-put same primitive type under one OP ie both nurbs and poly sphere under same OP so that it can be swtiched from one to the other without havng to rebuild following OP stack. As it work sin another app parmaters that are exclusive ot one type are greyed out when swtiching from poly to mesh to nurbs to imlicit etc.
_____________________________
Scripting/Expressions/SCOPS
----------------------------
-the intermediate technical user is left out, the OPs seem to getting more canned and the scripting language more robust while OP stack inflexibility and a limited expression language with very few variables makes it very diffucult, for the artist that just knows a little programming/scripting, to push the software. Combining OPs to make new tools shoul be made much easier with a more extenisve expression languange and abiltiy to reorder OPs and and pipe OP i/os together in a network GUI.
-a much fuller expression language including many more functions and scene and object/element variables
-abiltiy to use expression language in parameter input fields, more than the few math operations
-network GUI for script and OP creation, ie actual script bits and pieces of code and math OPs to piece together in a network piping between the nodes I/Os and then being able to complile it into an new tool/OP
--Visual Programming, a node network to pipe codebits into each other
-line numbers in script editor
-script color coding
-drop down hints of methods and properties while script writing like in MS Studio
-much more scripting examples
--a new category on netview for "scriptbits", it small functions an short simple script examples such as list layers and categorize them
--add the many examples in the reference manual to scriptbits in categories on netview
-expose all userprefs for scripting
-give us lots and lots of SCOP examples, from simple to complex
--list commands that work in SCOPS, its a f'n mystery right now
--make SCOPs easier to reuse with other objects, quick I/O connecions perhaps in an OPnetwork view where they can be wored to gether
--better than SCOP and OP creaion network view with OP bits of code and operators that cna be piped togethewr to make an OP with inout nodes and an output node liek fxtree, this would eb a very very powerful tool and would perhaps aid in making shaders
added:
-rclick on toolabr button opiton ot edit externally
-if not more than one script editor openable at least allow more than one script view open
____________________________
OPs
----------------------------
-expose all operators I/O for scripting and for visualy piping together in the GUI
--and for swtiching inputs so the proceduralism is flexible so we don't have to rebuild a stack when we want to change the source geometry, and so its easy to animate the switch/input
-a *real* procedural Copy OP,
--with aniamtable paramters such as copy number
--an input for template surface or particles to copy to
--with stamping of input OPs parameters for variation in each copy so that paramters upstreema are modifed based on copyOp varibles or parameters.
--include transform panel ppg in copyOp to duplicate or instance multiple input objects, to mirror over chosen plane, tansform compies, transform cumulatively etc or use local variables or variables referrencing stamped parmas of previous OPs an a per copy or per copy value/param basis
--here is a basic tutorial for the copyOP in Houdini that will make it clearer:
http://www.grahamdclark.com/Studentresources/tutorials/copyOP/index.html
--a copyOP would aslo allow one easier mirror model instead of my stupid netview scripts:
http://www.softimage.com/xsinet/displaydetails/Addon_display_detail.asp?family=XNET&software=XSI&parent=32&id=1967&child=Duplication%2FInstances
or
http://www.softimage.com/xsinet/displaydetails/Addon_display_detail.asp?family=XNET&software=XSI&parent=32&id=1968&child=Duplication%2FInstances
-text value animatable, ie dragndrop param icon onto from another param and use of varaibles such as FC, and much faster update
-improvement and more control of modeling tools such as boolean and bevel
--improve normal control, perhaps an OP with two inputs, the object and another object to derive normals from as in Jeromes script but with more control over how the object derives its normals from the other one such as proximity or point-at, so for eg point 1 on object A points at point 1 on object B which is a clone of object A and could be scaled out from it etc and animated as a normal direction guide.
---transform OPs work on normal vectors, make normal vectors accessible geometry components
--bevel, option to add more divisions
--boolean option to mark hard edge at edge intersection
--boolean option to toggle contributing objects with result hidden on/off
-A point OP would be nice, with normals control on selection area, and with two inputs for current object normals and refernce object normals to copy or point at or average between etc. Does not require but would be better if bounding box and other ways to collect/group elements was implimented for OP input and application.
-expose movecomponent OP to allow change of its values and change of input in anetwork gui or dragndrop resuse on other components/objects (requires change of input and/or selection sets/groups)
-component # reorder OP, random, BBBOX, up, 2nd input proximity etc.
-shape OP should be exposed allowing further tweaking of ref shapes and switching out of input ref shapes to other ones to be procedural, it is not currently procedural
-make transform align an OP, not a on off canned function so that it can be animated. perhaps better if there was a local bounding box variable available in expressions to use within OPs
-allow more than one cluster shape combiner so that some can be normalized while others not with an option to normailze overlaps with itself and if possible with another combiner OPs clusters. Perhaps organize by havign compound clips for each each combiner.
added:
-please expose OPs! ie allow user input and geo adjustment of inpout lattice into softbody OP, allow adjustment of weights on cage deformer etc.
-when group applying OPs offer option for per object or all for default center pivot position of effect, add collecion methods to groups such as by exprerssion (requiring a far more roboust expression language), bbox etc.
____________________
Paint
-------------------
-in addition to exsiting vertex paint add:
-surface texture paint
-3d paint(paintfx, peopl do use it,in motion graphics etc.)
-fxtree paint, with vectotr paint and replaceable stroke types
http://www.xsibase.com/forum/index.php?board=9;action=display;threadid=5039
______________________
GUI/Workflow/Interface
----------------------
-network object/operator view with ability to interactively wire I/Os between (perhaps also with interOPs between to modify data before use, more accessible than linked paramters and expressions)
-a much fuller expression language including many more functions and scene and object/element variables
-better OP control, here is a comparison between XSIs OP stack and Houdinis network:
http://www.xsibase.com/forum/index.php?board=1;action=display;threadid=199
-groups that are more than selection sets more than a place to share materials, allow geometry groups of objects and/or components that can have operators applied.
-3d widgets for operators in 3D viewer to control parameters of OPs as well as in FXtree, ie pull on normal for extrude
-ability in edit layout to assign one view as always on bottom and one view as always on top in GUI
-a quick way to keep some "display info" params in view for non-slected objects
-in explorer and hopefully network view to come, allow us to create folders under models for everything or at least have folders for annotations to organize, with a toggle view normal or with folders
-a way to show annotations only in explorer
-differnt types of annotaions, perhaps a viewer type annotation that can be displayed in the 3D viewer and the object selectable by clicking on the text.
-option to toggle/show hidden objects in object view
-display component index numbers in 3D views
-object view select any camera view too
-layout memory for all floating views when you start up again
-option for no title bar on custom toolbars
-an xsi taskbar that doesn't bump your layout to the right
-option for active splitter bars even when not in edit layout mode
-viewer order ie one type defined as always on bottom and one type such as PPGs always on top in GUI
-when you set BG to black wireframe should obviously not be black, better yet list user scene custom color sets in menu
-option to include scene color sets in layout save
-fix layout addons so like earlier versions, layouts show up or at least can be installed for different rez, otherwise one must package each rez layouts seperately
-short annotation or displayinfo of text parameters on selected or all unselected objects surfaces or center instead of flush with view plane
-ability to mouse-drag-select nothing in explorer view and have objects, node etc deselect
-allow easier defualt setting creation eg for default camera creation, kinematics, lens etc. the default camera 2 units up is maybe for demonstrators not users
-start/stop that works with exponential camera fog depth cue
-where is the depthcue type property accessible? for eg to add to an overide
-when a view containing sliders, such as for custom PPGs, rather than have the slider turn to value field if the view is too narrow or the name too long, put the slider on a row below instead
-show the "constrainer" name in the constriant PPG and allow one to change the constrainer object in the PPG or via an OP network GUI connecion to another object with or without offset/compensation.
-Show relations is cool, perhaps also Show the constainer in the constrain OP PPG and highlight it and the effected objects.
-scroll bar in synoptic editor
-dragndrop commands into auto synoptic hot spots
-OP stack dragndrop onto other objects/components or reuse or multiple use of OP stacks in a network GUI so fx or tools don't have to be redone/rebuilt every time
-forward<>backward through images in image clip viewer and ability to split view in there if for example suing it for ref pics to model form instead of having a gazillion image clip views open
-filmstrip storyboard viewer, with abiltiy to order/edit clips in animation mixer, perhasp have it use the .mov format so that anootaions per clip or timecode can be added as well as triggers for other events.
-ability to put image clips into a "reference" folder so they will not be deleted by "delete unused clips". these are images that will be used for rotoscoping, modeling refs etc.
-allow ordering of models in explorer, actions etc based not just on creation order or alpha numeric but also on a flag or ID o rmaybe a mode that allows auto id while user custom reorders their stuff.
-allow F to work in XIS explorer evenwhen object is not he one displayed in there, ie for use when ref or higher subD'd clone object is displayed in XSI explorer while selecion an dowrk is doen on original in another view.
-allow raycast shaded to work in xray mode as it should
-option to not have OP folders open when secting them for exmaple when selecting along movecompoent folder to freeze it, no one would wan it to open here
-definable zoom amount pref setting per component type
-make all display options animatable even boolean ones for quick and easy custom pset dragndrop paramter connection
-imageclip scrollbars or "Z" and "S" navigation
-a way to DL all of netview as a local copy to navigate on ones laptop for example.
-middle bar collapse for XSI explorer should be able to go both ways, an option to collapse the explorer or the viewer, perhasp add another arrow pointign the other way just below existing one.
-an estimate of file size while working at top of XSI
-display OP memory usage
-allow BG color different in different viewports
-view mode for both sides of XSI explorer
-"F" or frame all in aniamtion view, maybe I'm missing a setting but it doesn't work consitently
added:
-when XSI window is minimized, put scroll bars on sides
-ability to set side for scroll per view
-a view for "show all parameter values" in explorer, not just marked
-rather than just saving out seperate scenes, an easy to use and organize scene viewer and organizer via layer/pass/mixer settings by shot.
--perhaps tie it in with storyboard viewer
--allow time shifting of the entire shot including all its param keys, mixer clip placement etc
-add a netview that can subscribe to the xsi list and
-improved transformaion handles
--one handle that includes, scale transform and rotation controls with ctrl option list of align pivot to anoterh surface point origin etc
--keyable handles that effect selected objects paramters accordingly
-although method to adjust same OPs of different models works, also good would be ability to have "shared" OPs and per model variables to insert in OP param fields
-as well as the ability open a multi PPG also have one that opens a that OP seprately in sanme view fro each model/object
-a way to move top menus to right screen
-like in Adobe Imageready a full screen menu view with menu bar
-get rid of ANNOYING resolution pop up at XSI start up!
-add a text editor view, even just the basic MS notepad in a view, jot for irix, etc
-in 3D view, add a user view from last camera
added2:
-ability to view at any point in stack with XSI object viewer and also at different time.
_________________________
Modeling
------------------------
-bezier handle control on SubDs, 4 handles
-ability to quickly and easily duplicate/clone using animation, maybe using SCOPs if an example could be put up somewhere
-3D widgets control for all tools and OPS in viewer, ie pull on normal to extrude in extrude mode
-option in prefs to set what transform mode component default selection and "m" move points goes into instead of local and view which they repsectively do now. I would rather have both go into local personally and know others might have other prefs.
-ability to move some OPs center effect position on surface and animate position in UV, with fall off or component selection area (via BBox or proximity etc) also moving with it instead of specific cluster component #s
-have component/object-group selection bounding box and or proximity field work with weight maps too to modify their values and have their positions animatable.
-extract poly keeps local center orientaion and position opition
--also an option to have cluster center orient locally to original components on creation would be cool versus the default orientation globally.
-ability to turn off points view in "T" point mode so that point tweaking transorming can take plac ein one view while seeing an unobstructed view of shaded model in another. or perhasp an option to only turn on point view when T or shift (while in point mode) is pressed
-if possible have fog effect component selectability too, such while working on a poly hull cage points
-subD bezier handles :)
--some advantage would be the obvious ability to to move the handles and change the curvature bewteen it and the next point on the surface,
--could also be useful if the handles length could be changed and handles broken to define creases/hardness and surface direction, would be cool if they were animatable too, using clusters of handles to animate would be OK.
like the idea of direct point manipulaion on surface, it could only show points at the level you are subdividing though as manipulaion of points inbetween would require a physical subdivison to that level.
--another method of SUbD interpolation, actually passing suface through points would also be cool, so that curves and surfaces passed through the points or at least appeared to for easier navigation and manipulation, or a definable amount using point weight, not like crease, keeping curvature
--as suggested by many, a way to move components on the actual subD surface. would likely require a way to propegate the effect back up to be recorded on the actual hull
--would also be nice to have Bounding box, array, proximity, expression or other type of flexible selection group (not hard numbered clusters currently used for OP input) that could be animated such as BBox position so that the area locally subdivided could be moved as needed
-match symettry tool, ie select a component on one side of geo and component on other side of axis snaps to exact mirrored location. often when working in symmetry mode one will switch it off to give differnce to each side of the model and may want to fix one side to match the other, copy flipping xyz values is too slow for many points
-fix symmettry its often breaking and not reflecting the same point selection on other side of object
-proporional modeling points on another surface being modified incorrectly show in in XSI explorer view displaying another object
-weight maps that include effect on other components than versitces and paint properties, such as edge so that ti can be used to paint hardedge/crease fro subDs and have edges crease, not just points, so that it is useful for most needs.
-animatable profiles such as in buldge defomer
-perhsaps exists already, a mirror cluster or mirror select points
-point weight, for NURBS. And for SubDs perhaps allow the property to remain with the point even when topology # or order changes
added:
-procedural Lsystems
-since Houdini has more advanced procedural modeling and interface, perhaps via channels or an I/O node to connect XSI params to Houdini Select params would be useful
-ability to lock points in position with option for which axis. Useful for when mirror modelling.
-allow weight paint mixing on cage deformers for overlapping cages etc
-a limit on points to deform ony in their initial normal direction ( for muscle simulation etc)
-put same primitive type under one OP ie both nurbs and poly sphere under same OP so that it can be swtiched from one to the other without havng to rebuild following OP stack. As it work sin another app parmaters that are exclusive ot one type are greyed out when swtiching from poly to mesh to nurbs to imlicit etc.
_____________________________
Scripting/Expressions/SCOPS
----------------------------
-the intermediate technical user is left out, the OPs seem to getting more canned and the scripting language more robust while OP stack inflexibility and a limited expression language with very few variables makes it very diffucult, for the artist that just knows a little programming/scripting, to push the software. Combining OPs to make new tools shoul be made much easier with a more extenisve expression languange and abiltiy to reorder OPs and and pipe OP i/os together in a network GUI.
-a much fuller expression language including many more functions and scene and object/element variables
-abiltiy to use expression language in parameter input fields, more than the few math operations
-network GUI for script and OP creation, ie actual script bits and pieces of code and math OPs to piece together in a network piping between the nodes I/Os and then being able to complile it into an new tool/OP
--Visual Programming, a node network to pipe codebits into each other
-line numbers in script editor
-script color coding
-drop down hints of methods and properties while script writing like in MS Studio
-much more scripting examples
--a new category on netview for "scriptbits", it small functions an short simple script examples such as list layers and categorize them
--add the many examples in the reference manual to scriptbits in categories on netview
-expose all userprefs for scripting
-give us lots and lots of SCOP examples, from simple to complex
--list commands that work in SCOPS, its a f'n mystery right now
--make SCOPs easier to reuse with other objects, quick I/O connecions perhaps in an OPnetwork view where they can be wored to gether
--better than SCOP and OP creaion network view with OP bits of code and operators that cna be piped togethewr to make an OP with inout nodes and an output node liek fxtree, this would eb a very very powerful tool and would perhaps aid in making shaders
added:
-rclick on toolabr button opiton ot edit externally
-if not more than one script editor openable at least allow more than one script view open
____________________________
OPs
----------------------------
-expose all operators I/O for scripting and for visualy piping together in the GUI
--and for swtiching inputs so the proceduralism is flexible so we don't have to rebuild a stack when we want to change the source geometry, and so its easy to animate the switch/input
-a *real* procedural Copy OP,
--with aniamtable paramters such as copy number
--an input for template surface or particles to copy to
--with stamping of input OPs parameters for variation in each copy so that paramters upstreema are modifed based on copyOp varibles or parameters.
--include transform panel ppg in copyOp to duplicate or instance multiple input objects, to mirror over chosen plane, tansform compies, transform cumulatively etc or use local variables or variables referrencing stamped parmas of previous OPs an a per copy or per copy value/param basis
--here is a basic tutorial for the copyOP in Houdini that will make it clearer:
http://www.grahamdclark.com/Studentresources/tutorials/copyOP/index.html
--a copyOP would aslo allow one easier mirror model instead of my stupid netview scripts:
http://www.softimage.com/xsinet/displaydetails/Addon_display_detail.asp?family=XNET&software=XSI&parent=32&id=1967&child=Duplication%2FInstances
or
http://www.softimage.com/xsinet/displaydetails/Addon_display_detail.asp?family=XNET&software=XSI&parent=32&id=1968&child=Duplication%2FInstances
-text value animatable, ie dragndrop param icon onto from another param and use of varaibles such as FC, and much faster update
-improvement and more control of modeling tools such as boolean and bevel
--improve normal control, perhaps an OP with two inputs, the object and another object to derive normals from as in Jeromes script but with more control over how the object derives its normals from the other one such as proximity or point-at, so for eg point 1 on object A points at point 1 on object B which is a clone of object A and could be scaled out from it etc and animated as a normal direction guide.
---transform OPs work on normal vectors, make normal vectors accessible geometry components
--bevel, option to add more divisions
--boolean option to mark hard edge at edge intersection
--boolean option to toggle contributing objects with result hidden on/off
-A point OP would be nice, with normals control on selection area, and with two inputs for current object normals and refernce object normals to copy or point at or average between etc. Does not require but would be better if bounding box and other ways to collect/group elements was implimented for OP input and application.
-expose movecomponent OP to allow change of its values and change of input in anetwork gui or dragndrop resuse on other components/objects (requires change of input and/or selection sets/groups)
-component # reorder OP, random, BBBOX, up, 2nd input proximity etc.
-shape OP should be exposed allowing further tweaking of ref shapes and switching out of input ref shapes to other ones to be procedural, it is not currently procedural
-make transform align an OP, not a on off canned function so that it can be animated. perhaps better if there was a local bounding box variable available in expressions to use within OPs
-allow more than one cluster shape combiner so that some can be normalized while others not with an option to normailze overlaps with itself and if possible with another combiner OPs clusters. Perhaps organize by havign compound clips for each each combiner.
added:
-please expose OPs! ie allow user input and geo adjustment of inpout lattice into softbody OP, allow adjustment of weights on cage deformer etc.
-when group applying OPs offer option for per object or all for default center pivot position of effect, add collecion methods to groups such as by exprerssion (requiring a far more roboust expression language), bbox etc.
____________________
Paint
-------------------
-in addition to exsiting vertex paint add:
-surface texture paint
-3d paint(paintfx, peopl do use it,in motion graphics etc.)
-fxtree paint, with vectotr paint and replaceable stroke types
