______________________ GUI/Workflow/Interface ---------------------- added2: -ability to view at any point in stack with XSI object viewer and also at different time. -find next sleceted node, filter: in group -allow views to be displayed as transparency over 3Dview such as custom ppg with sliders. -"6' or view>layer panel doesn't work if layer panel is floated in a view such as for a custom layout. -if a view in 3d view manager is set to horizontal and ones sets anothe view to vertical then have it restore/slide the horizontal view to the side ( and visa versa) -fix models exporting its VERY VERY buggy, exporting models is a serious issue. It takes great deal of time ot track down a models reliance on other models and even when there seem to be NONE it still crashes in save attempts. --make a tool to evalute model dependencies outside of itself. added3: -improve scop/scripted op docs and videos. Micheals scop examples are excellent as usual but the voice over is a loose overview with just a little explaination. But I did find Michaels reference to other packages dispersed expressions compared to centralized scops funny and I agree, except this same high level coding with littel help for begineers, is what scares people to use Houdini and there expressions are far eassier to use and manage parts of than scops. If Michael is too busy to explain them fully wich is understandable with all he's doing, perhaps someone in support can do so at SI. I don't want to be spoonfed but there's a reason there are fewer XSI scop examples by users (not SI employees) than there are expression examples from Houdini users. The irony is XSi with its ease to use interface and tools is not easy to use due to documentation. -in explorer view, an option to view scops only, and other op type only -Improve Docs to work with netview (yes they can now be opened in netview without tricks but I mean in function) there is so much oportunity to have the docs intesct withte app to help instruct the user, especailly in the area of scripting and scops -sometimes node selection in explorer opens nothing, like kine should open both local and global in a PPG but sometimes does nothing :/. -ability to make our own keyboard shortcuts "sticky" like srt and other tools like "m" etc. would be especially useful when we need to make our own toggle keyboard shortcut for a custom command for edgesnapping for example and others. -instead of having to open upkeyboard mapping, add an option on rick n any toolbar button to assign to keyboard keys selected while holding rmbutton down ( or if too much an option have the keyboard mapping view popup from there and it goes straight to select that command in list so user can then quickly drag it onto the key.) -transalation manipulator to place pivot, or allow transformation modes for pivots too instead of just view. -add a "match transform to a components space" Perhaps it would require a reverse workflow -copy paste of properties between open XSIs export import is too time consumiong and exporting importing models ovewrites other things and saveing of presets onky seems ot be possible a the lowest smallest base property level. -font size for Display Info parameters. -make model default or active model so that when adding a new primitive it is added under it. -option to F find next marked parameter in explorer -please turn off the xfrom default of dupicate instantiate, I knwo e can turn it off but its always coming back on and its irritating, we know the feature is there without having to make us notice it. -ability to play gifs. at eaither next image next frame or use the image time set in gif for each image. -add modifier key + F on explorer to find next marked parameter -XSI explorer view with a view for properties -tiny request for option to center names display in viewports -allow sub-folders of constraints so that we can access them in scripts to manage their parameter values enmass per model ie with synoptics etc.(since constraints are un-namable) -an option to put sliders in explorer under each parameter. The PPGS take up too much room. -an explorer with scope(not sure of right word) would also be nice, yes we have groups but cannot put OPs in them, so way to just select cerain OPs and/or mark certain params and then have them only show in a "scope" view of perhape xsi explorer. Perhap liek groups have "scopes" listed under explorer to slect and just they show up in xsi explorer view. -add rotoscope to xsi explorer view _________________________ Modeling ------------------------ -allow freeze of transform on implicits -file input OP for object sequences requires more extensive expression language too -allow option to include user normal properties in shape blending and in storage of actions -ability to share weight maps between objects -something like zbrush to aid in detailed normal map creation, (they didn't give us the time of day at last SIGGRAPH but certain aspects of the product would be useful in XSI.) _____________________________ Scripting/Expressions/SCOPS ---------------------------- -fro cluster and otehr collecion method groups add a mix PPG to form new group form exsitng groups ie with booleans and + etc. -add channel reference(to relate more than one direct channel link easily) -local variables for FX r g b pixel values y location at each FXOP to acces wwith expresssion and a channel link (for more than one channel to ref) -mentioned before, but ot make it clearer, add drop dwon hints in scriptor of properties methods etc thatare available liek in MS studio, sort of like in XSI expression editor with drop down fro params and functions but have right next to the text like in Ms studio. -like xsi combo box, add another XSIUIToolkit property for User to make 3D view widgets for their Scripts and SCOPs, ie user SELECTABLE and MODIFIABLE handles for eg. beziers, amplitude of an effect etc. -ability to script annotaion view size for user -ability to have mnore than one scripter operator editor view open for different scops to compare. -allow scops i/o to see and use text values such as the text field of a custompset -have selected nodes with SCOPS attached show relations in viewport like constraints do even if the objects are not listed in I/O and are accessed in SCOP using "for each in" or getobject etc. -silly small thing but perhaps put a recyle button on SCOp editor so when we select other SCOPs in explorer we can update the editor without right click. -add a command list to onslection chnage and other events, and perhasps event combos -also nice would be a "onunselecting" command to toggle things on off -script container folders to associate with models, like synoptic but faster to setup. Perhaps it could be a folder under the model, click on the node and a PPG opens with a list of buttons for each script in the folder. The advantage is like synoptics, the sripts woud be transportable to other models, but also the advtaage of easily finding the scripts associated with use to that model. Synoptics just take a little too long to set up for things like this. -expose ability view>name has to locate name to track object in view so that we can assign out our own noations to track certain objects in view. Feedback of name and values of affected elemnts while testing scripts is very important. -extend relations view to show scop on any parameter. -option in script editor to save as "myscript"+"BU"+"automaticnext#" -allow wildcards * in scop I/O or some other dynamic collection method, this is really inflexible> I heard the statment made that scops have advantage of having allyour code inone place versus other apps with expression all ove the place in differnt fileds but at least he inputs can be changed into them makignthis arguement mute as ascop by comparison to the extensive ecpression lanuguafge and abiltiy to chang eop type and swtich inputs is far more flexible, procedural and non-linear. -if a toolbar is already open and thus greyed out in list, shen clicking on it have it come to front of views rather than doing nothing, and we have to move views around until we can find it. -scop flag for force update on frame change prereder as fro some reason the Fc excpression on a scop param does not always work. sometimes the expression gets deleted :/ -instead of messages and interupting popups, or user haivng toleave open the sxcript editor to read logmessages, add a field in XSI interface to logmessages for user. -a small feature to be able to comment out all selected text in editor for long sections we wish to comment out. ie add 'infront in VBS or //in jscript. -would be nice to have included, another more full featured editor inside XSI view. -add an object browser like in MS visual Studio fro XSI AND abiltiy to access other libraries outside of XSI. -make some methods to check an objects Rtree for all images and as the current code required is an f'n mess. Its very tough to read other coed that have had to bud such a script so its not just me. -a way to re-order selectionlist order of members of groups. ie when we select memebers of groups now it is very cool! when we list them that they return in original order selected before being put grouped but it woudl also be nice to be abl eot access this and change it if possible. ____________________________ OPs ---------------------------- -we can multiple edit params of selcted OPs, could ther also be a way to multi slect objects then open the PPG of one of one of th eobjects OPs and edit to change that param in all same OPs of selcted objects, Expanding the hierarchys is a slowdown sometimes. -allow shape input switching fro cluster combiner OP so that we cna switch out source shape faster and more straightforward than replace uner the menus. This would make it easier to track contributing shapes and allow easier switching out when for example duplicating models and needing to modify the contibuting shapes before they are used. -since we can't lock OPs like in HO*** can we have bypass flags eg for poly extract OP to ref shape at a certain stage ie to get shape of another object including deforms but not envelope deform efffect -ability to name OPS, with a view mode in explorer for scriptname and user assigned names for OPs -reminder for an OP graph interface, even partcle flow fro Max now sort of has one: http://www.particlefx.com/education/PFlow/PF_Overview09.html -shared OPs,it would seem it would perfporm better and faster to apply one OP to a group of elements instead of one for each or is this not possible in XSI architecture? again groups and differnt collection method than jsut picked clusters for Operator application so that operator ordere is not an issue and procediuralism can be maintained with toplolgogy number specific OPs like transform, add edge etc. -please expose "hidden cluster creation operators". add a view in explorer called view>hidden cluster creation operators -as we can just export sequential geometry in XSI but cannot import sequences or on an as needed basis yet, a "file source Operator" would be nice -just to reiterate please transform OPs, versus closed transform nodes in history stack. there are so mamny uses some being, a stack of a few transform ops (with additon of variable element collection grouping) is far more powerful and reusable than a stack of nulls used as deformers; used upstream with expressions on to pronounce an effect (would also be great with the copyOp) -ability to mute instead of deleting SCOP in and outs for testing purposes -again being able to aply Ops tp grpups woudl help in so far as reordering Ops for multi objects -OP parameter manipulators in 3DS view, ie pull normal for extrude, corner for rotate, slide on sides for subdivs -ability to copy paste OPs between objects AND open XSIs (this is possible in Houdini. Infact we caneven copy paste entire networks and attach them to another object! here fro Op networks are liek tools nto like in Xsi where thety a stuck aplied to that object in a linear stack.) -ease of reordering contraints! as in flexible and non-linear proceduralism -add option for time control set to current timeline span of timeline or mixer timeline start end. ____________________ Paint ------------------- -integration with MR like MR contour shader, yes I know what paint is but I'm looking forward not at the early 90's ___________________________ FXtree --------------------------- -allow us to make our own spdls/FXOPs -local variables for FX r g b pixel values y location at each FXOP to acces wwith expresssion and a channel link (for more than one channel to ref) -import eps as shapes for masks -vector out put render of scen like svg or flash etc, with ability to import he contour to use as masks in fxtree. a resample OP and point order OP woiuld also aid in the management of these rotosplines. -like above an bitmap image alpha to vector shape mask function or better as FXOP -prevent FXtree shape/mask overlaping edge interiors from inverting effect. ie all area bound by edges is masked regardless of edge overlap. -handles/widgets fro 3d transform -camera view matching for 3d transform -3D layers in OGL -ability to maintian psd layers and choose layer/plane throughout tree -ability to render out psd layers as defined by a "pass order" -curves for marker values in gradient, would help with creating abetter mor controlabe falloff. right now there seems to be no way to control falloff excpet by adding a silly # of markers and positioning them for eg exponentially. perhaps adding mid-points like in gradientt avialable in render tree -view multiple output at same time, ie split fxview into sections for each output selected. -"shift" and drag should lock xy scale in tranform fxop - more tie in with render tree to for example have a way to have an image map looked at, at a different texture coordinate based on camera incidence. Or if image map coordinates to look up can’t be driven by incidence then is there a way to drive image/clip map frame number to look up based on incidence. Perhasp a way to dive the retimerfro clip for reference in rendnertree. __________________________ Animation ------------------------ -allow weighting of cage deformers, use vertex coloring. Even with an exact same topology poly cgae as the surface it si deforming, it doe snot follow it exactly, there is an irritating lag. -iwth softbody applied, I undertand that undoing a deletecomponent will crash XSI, and perhaps why XSI also crashes when deleting a movecomponent but its a bit of pain. -clip lock together like in premiere -is there a way to solo only shape or only animation tracks -make emute fro softbody keyable so ewe can store it as an action to enable different sofbody OPs -option to keep and use in-out timeline guides available for use even when not in cycle -ability to add our own preset weights to drop down menu in mixer for clips, like 0>0.5 0.5>0 etc. -as well as existing command to slect constrained objects, add an option to select constrained parameters -fix mixer so when you put a clip on a muted track it stays muted -reflect values of fcurve to anotehr curve, ie liek 0>1 preset has opposite of 1>0 preset for a mix between two clips, have a featre that allows one to take their own keys and fcurvce and "reflect" the values into another curve -allow export and import of mixer sahpe and animation tracks SPERATELY especially for some shape things that are used throughout a project timleien such as link deofm withori or other shape adjustments. -a way to display all animation sources rahte than having to open a folder of each model mixer. perhasp in brackets beside each ones name put model owner name so we know where they are coming from especially if duplicates. -allow entry value higher than 1 in constant preset weight input fro mixer clips -fix frame all so it works and so when clips outside of timeline area it doesn't bug out on frame all and show 0 to 26 thousand -allow parameters in PPG to be marked even when associated node is not selected so that manyy PPGS can be left open and their params marked. -ability to copy paste animation between open XSIs ( this is possible in Houdini) -connection template for stored mixers, in case clips have been renamed -OPTION TO IMPORT MIXER WITHOUT OVERWRITING NEWER ACTIONS> OLIVUERS SCRIPT ON NETVIEW DID NOT DO THIS, THIS IS VERY IRRITATING. -optin to export mixer and onl actions of clips currently used in mixer ( or currently in start stop of timeline) -undo copy paste of animsources from one mixer in explorer view to another doesn't undo, is bug -option when copy pasting actions from one mixer to another to not have any repeats if same name already existed and ask to overwrite or copy name1 copy name 2 etc likeit already does. if we have lots of actions in a mixer its a PITA to compare them, guess I could write a script. The other issue is even if you copy an action from one mixer to another it appends 1 to the end of the name, i don't want this fro scripting reasons so I have ot manually remove the 1 at end after each copy. -expose the mixer timeline in and out values in scripting so we can change it. -in mixer and PPGs having th ebutton toggleing key and remove animation seems counter intuitive -SKeleton: to chain PPG add option for upvector to = effector rotation, so when effector rotation>effected by last bone is set to false/off the effector can rotate freely and be constrained by pose ori etc to another object, AND th eoption to have the bone rotate in same way can be activated. Currently the work around is to: after turning off "effector rotation>effected by last bone" 'get a null 'transform>match all transforms, to effector 'translate null in local mode in one axis perpendicular to bone, likely Y 'parent the null as child to the effector 'select bone, skeleton>chain up vector and pick the null -fix weight maps so that when the original geo is changed all the info is not lost when toplogy changes, ie why if I change soemthing oh lets say accidentally like # of subdivsions in U the vertx info colors are scrambled and undoeing doesn't fix it. -add an exponetial value or UI ramp curve fro fall off of amplitude values. eg. so that a weight map value of 0.5 would not alway sbe half way between the first un weighted points and fully weighted points. but rather postioned by UI ramp curve between zero and full weight. Right now its just linear. Woudl aslo be nice if it were an animatable curve -better control of weight map mixing, seems to not work. -bridge for shapes -animation, show keys in start stop sliders of store mixerPPG and have snapping of the sliders to them. -ability to manipulate clip mix curve too. yes we have preset curves and we can manipulate the weight curves but they don't translate in timeline like the mix between two clips does. (would be nice to be able to store these as presets too.) -we have, lock and recycle buttons now in animation editor, and add would also be helpful. add and add curves button to aniamtion editor so if we have a few slectitmes displayed, we can just slect an itme to add rahte than digging thr explorer or mixer to relsect all clips or parmaters we want to display in mixer. ______________________ Rendering ---------------------- -add a keyable switcher OP to switch sources in FXtree -FXtree ability to covnert poly shapes to bezier and back -in mask, simulataneously select point slected in FXview in explorer as wellso we know which one it is for scripting etc. -in mask ability to directly set point position value -add view>select all clips -a countour geometry output to sequential dxf or eps -a sequntial countour ouput as an xsi object, dxf, svg and flash. and ability for fxtree to sequentially read it for shape masks. -relate selection of nodes in rtree to explorer for user freindliness -ability to render passes as psd layers with masks, by rendering to existing psds adding current pass to a layer or by rendering all passses then putting into psd layers perhaps with options for blending modes -switch node to animate switch of inputs from one branch to another, ie for switching from constant to blinn, and an option to still allow both to have the same branch inputs -a way to have an image map looked at, at a different texture coordinate based on camera incidence. Or if image map coordinates to look up can’t be driven by incidence then is there a way to drive image/clip map frame number to look up based on incidence ___________________________ Sound ----------------------------