XSIBlog

JScript tips and techniques.

You would like to submit an article to XSIBlog, whatever the category? Don't hesitate, it might even get you full authorship status to XSIBlog if you do so.

Sometimes when you”re trying your hardest to put together a rig that the animators won”t break, you wish that XSI had something like Houdini’’s digital assets. In case you haven”t come across Houdini yet, “Digital Assets” are a way of encapsulating a group of objects and hiding everything except for certain items that you choose. [...]

How to use a curve to roll something along its edges.

Typical problems when developing a modeling script - revisited.

If your editor supports the launching of external programs and allows you to insert text to the command line based on your current selection, then you can get context sensitive help from the XSI SDK help file. This will work for both the C++ and scripting SDKs. This snippet shows how to perform this in the Crimson Editor but it will work equally well in any other well supported editor that has this feature.

The hyperlinks generated in the Script Editor when an script error is thrown can be very helpful in finding exactly where a problem has occurred. The only issue is that if you are using an external editor, the line number is not communicated to the editor to make it automatically scroll to the line of code that produced the error.

Most standalone text editors allow for a command line parameter to indicate which line number to position the cursor when opening a new file. By making a quick change to one of XSI’’s scripts, we can communicate this to the external editor. To make this change, follow the steps below.