Softimage mailing list – Year in Review


2013_xsilist_wordcloud

12060 posts
1388 discussions
460 different posters

Top Ten discussion threads
Number of posts in bold.

  1. Softimage 2014 190
  2. Octane render 177
  3. Announcing Redshift – Biased GPU Renderer 154
  4. Why did I pay support?? Why did I buy a suite ? I want my money back! 118
  5. softimage.tv – Hello World! 78
  6. Future of Naiad 72
  7. Unofficial Softimage user voice 69
  8. Softimage 2015 User Survey 67
  9. Difference between a force and a velocity ? 63
  10. SI 2014 sneak peek 62

Top Ten posters
Number of posts in bold.

The top 10 posters accounted for 23% of all posts; the top 25 for 40%.

  1. Alan Fregtman 396
  2. Matt Lind 382
  3. Raffaele Fragapane 380
  4. Eric Thivierge 341
  5. olivier jeannel 308
  6. Steven Caron 297
  7. Stephen Blair 277
  8. Sebastien Sterling 223
  9. Luc-Eric Rousseau 189
  10. Ponthieux, Joseph G. 185

Century club

  1. Alan Fregtman 396
  2. Matt Lind 382
  3. Raffaele Fragapane 380
  4. Eric Thivierge 341
  5. olivier jeannel 308
  6. Steven Caron 297
  7. Stephen Blair 277
  8. Sebastien Sterling 223
  9. Luc-Eric Rousseau 189
  10. Ponthieux, Joseph G. (LARC-E1A)[LITES] 185
  11. Chris Chia 161
  12. Paul Griswold 158
  13. Mirko Jankovic 157
  14. Sergio Mucino 156
  15. Szabolcs Matefy 153
  16. Christopher 152
  17. Stefan Kubicek 147
  18. Rob Chapman 136
  19. adrian wyer 133
  20. Alok Gandhi 126
  21. Sandy Sutherland 125
  22. Leonard Koch 124
  23. Grahame Fuller 123
  24. Dan Yargici 122
  25. Emilio Hernandez 120
  26. Eugen Sares 116
  27. Andy Moorer 115
  28. Morten Bartholdy 107
  29. Angus Davidson 105
  30. Peter B 103

Top 5 most active days

  • 26 March, 149 posts, “Softimage 2014”
  • 28 February, 121, “SI 2014 sneak peek”
  • 20 December, 103, “positivity” and “rumor, Soft dead within the next year”
  • 13 February, 102, “Difference between a force and a velocity ?”
  • 17 July, 101, “I can’t believe there is no tutorial for Softimage on Autodesk webiste”
  • Friday Flashback #152


    Kaboom! “In SOFTIMAGE|3D, the Effects > Kaboom custom effect in the Motion module allows you to explode complete hierarchies using dynamics and collision detection. Now you too can create your own earth-shattering kabooms!”

    1997 screenshot
    kaboom

    Exploding Hierarchies with Kaboom

    The Effects > Kaboom custom effect in the Motion module allows you to explode complete hierarchies using dynamics and collision detection. Now you too can create your own earth-shattering kabooms!

    Features include:

    • Speed.
    • Complete interactivity. Move the source of the blast around and the pieces rearrange themselves.
    • Collision detection: bouncing and sliding.
    • Hierarchies: explode a whole hierarchy instead of individual objects.
    • Non-polygon mesh objects are treated as solid objects.

    Using the Kaboom Effect

    The Kaboom effect explodes the currently selected hierarchy. Dynamic calculations are done on the object, including gravity, wind, and collision detection with a ground plane. Objects can collide with the ground plane (from either side), bounce, and slide (continuous contact). Polygon mesh objects can be exploded into their constituent polygons.

    Here’s an example of how to use the Kaboom effect:

    1. Get a primitive cube.
    2. Choose the Effect > Subdivision command in the Model module to subdivide the cube into polygons. Use the default values: 4, 4, 4.
    3. Choose the Polygon > BreakUp command in the Model module to “separate” the cube into polygons.
    4. Translate the cube upward so that it is completely above Y=0.
    5. Get a primitive grid.
    6. Choose the Effects > Kaboom command in the Motion module. The Kaboom dialogue box appears:
    7. Accept the default values and click Ok.
    8. You are prompted to select the ground object (click the grid).
    9. You are prompted to select the hierarchy to explode (click the cube).
    10. Play back the animation. The cube explodes and collides with the ground.

    For a full description of parameters, see this command’s description in the Reference Guide.

    Tips for Using the Kaboom Effect

    • If you are exploding polygon meshes, make sure to use the Polygon > BreakUp command in the Model module on them first (or PolygonDetach); otherwise the polygons stay connected.
    • If the Explode Meshes option is selected, polygon meshes are exploded into individual polygons. If Explode Meshes is deselected, polygon meshes are treated as solid objects. All other object types (NURBS, patches, nulls, etc.) are always treated as solid objects.
    • Don’t worry about deselecting Collision Detection for greater speed: it doesn’t slow things down much (if at all).
    • Deselect Tumble Rate unless it is required: it slows things down by at least half.
    • Polygon grouping is logical, not topological. This means that polygons are grouped according to their order in the model, not according to the geometry of the model.
    • The Collision Detection for the ground is based on the Y height of the object selected for the “ground” object: the plane at this height is used as the ground plane. The collision detection is not based on actual geometry.
    • The ground plane is double-sided-you can bounce an object off it from above or below.

    Things to Try

    • Use a strong Pull value with a slow speed: it tears objects apart.
    • Move the Kaboom effect icon around and watch the blast rearrange interactively.
    • Use a negative value for the Falloff power: the blast strength increases with distance from the icon.
    • Use no Blast Strength (value of 0) and a slow Speed to “collapse” your model.
    • Create a strong blast with a 0 distance Falloff, high Bounce, some Tumble, and very little Slide, and place it above an object that is close to the floor. You’ll get a nice “splashing” effect.

    Fixing DLL problems


    If you ask me, these are all bad ideas:

    • Downloading missing DLLs from some DLL download site you found via a web search
    • Copying DLLs to your system32 folder
    • Copying DLLs from one version of Softimage to another

    Fixing DLL problems involves doing some troubleshooting to figure out the root cause of the problem. Often, an error message about a DLL is just a symptom.

    For missing DLLs, don’t download the DLL from some dll-download site. Usually a re-install of your software package, or an install of the appropriate redistributable package, will fix the problem.

    Copying a DLL from one version of an application to another is a little crazy. You’re just asking for trouble 😉

    Scripting FBX export and import


    You can use the FBXExport command to create the ExportFBXOptions property, and then use either the OM or SetValue to set the FBX options. For example, this Python snippet creates the FBX property by calling FBXExport( “option” ), and then sets the FBX SDK version (for which there is no separate FBXSetExport command).

    si = Application
    si.FBXExport( "option" )
    o = si.Dictionary.GetObject( "ExportFBXOptions" )
    o.Parameters( "FBXSDKVersion" ).Value = "FBX201300"
    

    You can do the same thing for FBXImport with FBXImport( “option” ), but I always got an error, even if the property was created.

    si = Application
    
    try:
    	si.FBXImport( "option" )
    except:
    	o = si.Dictionary.GetObject( "ImportFBXOptions" )
    	
    si.LogMessage( o )