If you’re going to stick points to an enveloped mesh, you don’t necessarily need to emit them (I don’t think???). Just generate your own sample set and add the points to those locations (in the Modeling stack). Then the points will stick as the mesh deforms.
As requested in the comments, here’s a visual explanation of Arnold licensing, to go along with the Softimage version I posted last week.
Suppose you had five Arnold licenses. With those five licenses, you can have five machines using Arnold to render. For example, you might have two artist workstations and three render nodes (but you can have any combination of workstations and render nodes that adds up to five).
Arnold licenses are checked out when you actually render, not when you start Softimage or load a scene. If a workstation isn’t doing a render region, or a render preview, or rendering frames, then there’s no Arnold license being used. So maybe it is more accurate to think of it like this:
Arnold licenses are per machine, so all processes on the same machine share the same license. Note that you can limit the number of threads per render if you want to run multiple renders on one machine.
Since I left Autodesk, I’ve been asked a few times whether there’s a secret way to reset expired trials 🙂 The short answer is No. Even for Autodesk employees, that’s how it is. Zero-filling your hard drive is pretty much the only way to reset a trial license.
Storing lights in a channel
by kosyan
Modeling using Deform by UV
by SI_UserNotes
related video:
Particle display percentage
by Mr Core
EMFluid as a 2D emitter
Softimage key reducter
by moxmotion
This snippet gets the local properties of anything in the selection list that has local properties.
from win32com.client import constants as C for o in Application.Selection: localProps = (o.LocalProperties if o.IsClassOf( C.siSceneItemID ) else None) if localProps != None: for p in localProps: print p
LocalProperties is a property of any SceneItem, so all you have to do is check whether the selected object implements the SceneItem interface.
T-shirt design circa 2008 for XSI 7 (new, with ICE!).
Front:
Back:
A couple of weeks ago on si-community, there was a discussion of Softimage licensing and someone wished there was a graphic that explained Softimage licensing…
A network license includes one Softimage license, and five Batch licenses.
Each instance of xsi.exe and xsibatch.exe can use up to four satellite computers for satellite rendering.
You can run multiple copies of xsi.exe or xsibatch.exe on the same computer. A license is shared as long as processes are running under the same user account and on the same host (aka computer).
You can run an unlimited number of xsibatch -processing jobs. With xsibatch -processing, you can do anything except render. Typically you use it to run script jobs on scene files.
And finally, you can also use the Softimage license to run xsibatch.
Update: As requested in the comments, here’s six render nodes, each using four satellite computers:
How do you get the ICE Tree view in a menu callback? For example, if you add a menu item to the ICE Tree > User Tools, how does the menu item callback get the ICE Tree view?
The answer is actually in code I posted before, but that was in a blog post titled Getting the selected ICE nodes. So, with that title, you wouldn’t necessarily think to look there.
So what’s the answer? Uses Context.GetAttribute( “Target” ). For custom menus in the views like the ICE Tree view, the Fcurve Editor, and the Material Manager, the Target attribute is the View object. And once you have the View object, you can get the View attributes.
#
# Callback added to the menu item with Menu.AddCallbackItem
#
def My_menuItem_Callback( in_ctxt ):
# Get the ICE Tree view
oView = in_ctxt.GetAttribute("Target")
#
LogMessage( 'View: ' + oView.Name )
# get the selected nodes
nodes = oView.GetAttributeValue('selection')
LogMessage( 'Selected nodes: ' + nodes )
Soapbox alert…
This post illustrates why indexes are a good thing…with them, you can find information no matter what page or heading contains the information.
For ICE trees, you’d have index entries something like this:
This isn’t a common error, at least not in recent memory. In the past, you may have seen this if you tried to open a scene that wasn’t in a valid project, but Softimage no longer has a problem with that. To reproduce this error, I had to delete the system folder while I had a scene open.
eX-SI 