Friday Flashback #273

Experience XSI 4: The Official Softimage XSI 4 Guide to Character Creation
A look at the new book by Aaron Sims and Michael Isner which guides you through the production process of a digital creature from start to finish.
July, 16th, 2004by Raffael Dickreuter


When you go to the bookstore you find tons of books focusing on 3d, modeling, animation and all kinds of different software packages, but very few were written for XSI. Finally there is another one, and it’s a really good one.

This book is written by industry experts Aaron Sims and Michael Isner. Aaron Sims is a character creator at Stan Winston Studios. He has been involved in projects like Terminators 3 and Steven Spielberg’s A. I. Michael Isner is the head of Softimage Special Projects and one of the key people behind XSI’s character tools. They have teamed up to explain the production process from start to finish. Sims and Isner together means a collaboration of art and technology knowledge.

The book in general is written for an audience that is already familiar with the concepts of 3d and XSI. However it contains a few pages that will help users from other packages quickly adapt to the XSI interface and workflow. This also might help users who are somewhere between a beginner and intermediate level.

Authors Michael Isner (left), Softimage Special Projects and Aaron Sims of Stan Winston Studios in front of the T1 from Terminator 3 inside Stan Winston Studios.

Chapter 1 is a quick introduction to the interface and contains a hotkey list. It makes it ideal for experienced artists to find the most important commands within XSI quickly.

Chapter 2 gets you started with designing and modeling a character.

Aaron explains the thought process that is used when designing a 3d character, such as: how it has to be appealing for the audience and that you have to really know how you intend to animate the character, if it’s flying, walking, swimming etc…

Initially there is a quick overview of the modeling features where you will start with a sphere to model a basic shape of your creature. Later on you learn how to add lots of detail and gradually the shape turns into a stunning dinosaur. Altough you can see modeling process in the images, it doesn’t explain the exact concepts how details were added.

Chapter 3 deals with using the texturing tools in XSI.
After a quick overview of how to use the most important features like bump mapping, displacement mapping, texture layers etc… You learn how to use different subprojections to texture a human face. The knowledge you get during this process is then used in the more complex task of texturing the dinosaur. After applying the textures onto the mesh you learn to mix the color maps, specularity maps, bump maps and transparency maps together. Aaron also shows you how to texture the nails and the eyes of the dinosaur.
Your character is now ready for the Skeleton setup. The book also offers a website where you can download the mesh, textures and scripts. People who want to compare their mesh with the original, learn from it or simply skip some chapters can benefit a lot from the accompanying materials.

Chapter 4 dives into character setup. Michael Isner shows how to use guides that let you easily define the proportions of a setup. There is a section that shows how to use the new character tools of XSI version 4 to quickly add more fingers, toes or tails. Step by step you go through the process of creating a proper rig for the dinosaur, including creating marking sets, symmetry maps and weight painting. You will also get accustomed to the new constructions modes that were introduced in version 4 and let you divide the working stack.

The first part of this chapter deals with the most important rigging features. The second part goes way deeper and explains the fundamental mechanics of character setup tools in the XSI software. Besides constraints you get a glance at scripted operators, springs and how to use different character components such as the spine, tail, legs. The portion that shows you how to solve flipping problems and takes an in-depth look at enveloping algorithms is very interesting. Later in this chapter you will learn how to use control splines for proper shape deforming, how to model different shapes and use them for shape animation. The chapter also reveals information about character engineering at a production scale and how you can use scripting for improving your rigging process and explains the fundamentals of the rigging SDK.

Modeling and texturing of a dinosaur.

Chapter 5 demonstrates how to create a walk cycle for your dinosaur. Aside from creating poses you learn how to use the controls you built earlier, such as the footroll control, to create a smooth animation. Step by step you go through the F-Curve Editor and the Dopesheet. You continue to store your animation so you can use it with the Animation Mixer for non-linear animation. At the end you modify your dinosaur with shape modeling, which lets you close and open the eyes of your character.

Up till now most aspects of the training were directly connected to the dinosaur. In chapter 6 Michael Isner goes a bit off and gives you very good introduction into scripting. People who are not familiar yet with programming or have just a basic understanding will find this straightforward chapter very helpful as he guides you through passing variables, looping, collecting selections, arrays, creating vectors etc… After some basic exercises you learn to create helpful tools and find solutions for problems that can only be solved with scripting. After this chapter you will also know how to create geometry entirely with scripting. You might start as a beginner and leave at an intermediate level, just by working through this chapter.

Chapter 7 then goes back to the dinosaur where you will add Lights and an environment to your scene. Several different lighting types, different rendering techniques such as raytracing, scanline rendering, global illumination, final gathering and caustics are examined throughout this chapter. The rendering of the dinosaur will be split up into different render passes and composited together in the FX Tree, where you can apply color correction and finish your composition.

Rigging, Animation, then rendering in passes and compositing.Chapter 8 covers the most important concepts of exporting your character to Softimage|Behavior, creating actions for crowds animation and bring the crowds back to XSI for rendering. For a person entirely new to Behavior this might be a bit difficult to understand what really is going on, but you will get an idea of the potential of the software.

Chapter 9 shows some of the stunning work that Aaron Sims and Michael Isner created during their careers.

Experience XSI 4 is a great book. You learn from start to finish how to create a complex character by using advanced features within XSI. It doesn’t try to explain every feature that there is, it just focuses on what you need for the specific task. Scripting, that might have been a bit difficult to get into for people with not too much experience in this area, is very well laid out and gets people a quick start who want to dive into it. This book lets you quickly learn new concepts that you can use for your own work. A must have for every enthusiastic XSI user, or experienced users, that want to switch quickly and easily from another package.

The Authors inside Stan Winston Studios
Pictures taken with permission inside Stan Winston Studios.

Friday Flashback #217

Interview With Alain Laferrière
The Program Manager of Softimage Japan talks about his career at Softimage, the Japanese Industry and XSI 4.0.
June, 28th, 2004, by Raffael Dickreuter, Will Mendez

Alain Laferrière,
Program Manager,
Softimage Japan.

How did you get started in the cg industry?
I got interested in computer imagery from a young age, playing with the first video game consoles and personal computers and following the evolution of CG with a deep interest. The “demo scene” development communities for both C-64 and Amiga computers also brought a lot of innovation in realtime graphics synthesis.
At University of Montreal I studied computer graphics and did a M.Sc. in human-computer interfaces ( agents ). There, I met Réjean Gagné, Richard Laperrière and Dominique Boisvert, who would later implement the Actor Module in SI3D, and many other friends who were, or are still working at Softimage today. After I completed my studies I got a job interview at Softimage and was hired ; it was a dream come true ! I started in the modeling team, then moved on to motion capture & control, then headed the new Games team and now Special Projects Japan.

What do you do on your spare time?
I love music very much and I’ve been DJ’ing on and off since the age of 13, so I buy records and practice mixing. I also like programming personal projects, reading, cooking, nature, going out with friends, going to the gym, etc.

Tell us a bit about the highlights of your 11 year career at Softimage

  • April 14th 1993 – my first day at Softimage !
  • solving a data loss problem with an Ascension “Flock of Birds” motion capture system not working properly with a Onyx computer, which was being used at a Jurassic Park theme park at Unviersal Studios. I implemented a fix in Montreal and I was sent to Los Angeles to configure the system. I had a chance to meet the movie actors and Steven Spielberg made an appearance, it was a very impressive “Hollywood” type first experience for me.
  • then I worked on an interesting project : one of our customers was using a Waldo-like hand manipulation device to radio-control the facial expressions of the robotic heads used for the Teenage Mutant Ninja Turtles movies. The actors had to wear the Turtle heads while servo-motors moved metal blades around their face to flex and animate the head latex skin ; as well as a radio receiver backpack which was hidden in the turtle shell. Since the facial animation had to be redone live at each shot , it was not possible to produce a constant facial animation quality. First, I wrote a motion capture driver for the Waldo device and a designer modeled the turtle head in SI3D and connected the Waldo inputs to its facial animation shapes. Now we were able to record a live facial animation using the Waldo device, then perfect it in SI3D by editing the animation curves. After that, I modified the motion capture communication protocol to support motion control, and wrote a control driver to radio-broadcast the data which was previously motion captured and edited in SI3D. With this pipeline it was possible to author a perfect animation sequence which could be played back identically at each shot. The project had an extra dimension of danger, since there were urban legends of actors getting mutilated by the blades attached inside the robotic heads. Something that keeps your mind busy when your head is inside.. 😉
  • Fall of 1994, I went to Japan with Daniel Langlois for a 2 weeks business trip, which mutated into a large effort between Softimage and SEGA to create a first generation of 3D game authoring tools. I was called to stay there for nearly 3 months in the first trip, and to frequently pay visits to Japan afterwards. I supervised the project and other developers helped me designing and implementing the features ( 3D paint, color reduction, SEGA Saturn Export / Import and Viewer, raycast polygon selection, etc). It was a very intense and exciting coding experience. Following this, SI3D quickly became the standard for 3D game authoring in Japan.
  • RenderMap – a project which I started after talking to a Japanese game designer, who explained me how he was planning to use clay models to create the characters of his next game. They would scan the clay models into high-resolution polygon mesh models with colors at vertices, and then transform into texture data by rendering front and back view images and re-projecting them on the low-resolution model. With this method there is no control over how the texture is being distributed on the geometry, and although it works for polygons facing the camera, the texturing quality quickly degrades as polygons face at an increasing angle. Instead, I thought it would be better to fire rays along the surface to capture the color information and if those rays could hit a high-resolution version of the object, then we could carry the texturing data from high-res to low-res. RenderMap solved this by using mental ray to fire rays at the intersection of triangles and texels ( according to their location on the object ) and accumulating the weighted color contributions to a final color per texel. You could carry the high-res data to a low-res model, by placing the high-res model in the same location as the low-res one, but making it slightly bigger. Since it uses Mental Ray, it also allows to burn procedural effects into texture maps, generate vertex colors, normal maps, etc. My colleague Ian Stewart implemented the much improved version in XSI.

    Manta model before applying RenderMap – we can see the results of rendering using mental ray in the render region.

    Texture data after being pre-rendred with mental ray using RenderMap.

    Manta model after applying RenderMap.
  • dotXSI file format – an initiative which I launched over 7 years ago, at a time when our customers were asking us to design a high-level 3D data interchange solution. After much discussions with my colleagues in the Games team, we finally opted for using the Microsoft .X format concept, with many new data templates to support a lot of features which were not covered in basic .X files. Since that time, the format has become very popular in the cg and games markets as a generic data interchange solution between authoring tools and pipelines. I was initially hoping to see a good level of popularity one day, but it has now reached well beyond those early expectations. This was also an opportunity for us to understand the fundamental differences between a high-level generic format and an optimized “memory image” data format which can be loaded and used directly by a game engine without further optimizations. From this, we derived our strategy behind the dotXSI file format and the FTK ( File Transfer Kit ), which is a library to read and write dotXSI files and which can be used to write converters between dotXSI files and optimized memory image formats tailored to any custom game engine ( or between any other format and dotXSI ). I came up with the “.XSI” name suffix, which was later adopted by the marketing team for the name of the XSI product itself, although I had no involvement with this decision.
  • April 99 – moving to Japan
  • various Special Projects with Japanese clients
  • misc. SI3D features like vertex colors, generic user data, GC_ValidateMesh, SI3D 4.0 ; and now XSI tools

Working in Japan: Was it difficult to adjust to a new location and culture?
Not really. I got a good experience of Japan during my first trip ; having a routine and working on-site at SEGA was a chance to feel how life would be living here. I came back again on business trips about a dozen times, my interest growing until I relocated in April 99. Adapting to the Japanese culture is a life-long effort, but Japan is very welcoming so this can be relatively painless. Of course I always miss my friends and family, but fortunately I go back a few times a year and we stay conneced by mail and phone.

What is the biggest difference when working for a company in Japan compared to Canada?
Since I work from home the differences for me are very low. But traditional Japanese companies are more hierarchical than american ones so you have to be aware of that. Also, your ability to connect with a team will completely depend on your ability to communicate in Japanese.

Do companies in Japan and Northern America work closely together on projects?
Many Japanese companies have branch offices in North-America, however I don’t know how much is new production work, regional adaptation or collaboration on a joint project.

How do Japanese customers differ from Canadian customers?
The main difference of course is the language. And Japanese companies employ many designers and programmers, so there are many sources of feedback to report issues and submit suggestions for improvements. Sometimes there are misunderstandings, missing information in order to reproduce a problem or understand what a specific request is about or why it’s important, so I keep an eye on all incoming feedback from Japan and work with our support teams in Japan and Montreal and our Japan resellers to make sure we have all the information needed to fully understand and address customer requirements.

Another difference is related to the fact that most customers in Japan are game developers. It is normally easier for film companies to switch pipelines from one 3D application to another than for game companies, because the final output for film is a rendered movie while for games is most often data which needs to be compatible with a run-time game engine. A large portion of our customers in Japan are game developers, so they tend to migrate pipelines at a slower pace than for customers in other markets since they need to validate the workflow and data compatibility with a new pipeline before they can adopt it in production. Japanese customers are very thorough in their analysis of new technologies and do not migrate without serious consideration. XSI has already been used in production for a while by many Japanese companies, and its popularity is now accelerating. This is very exciting to see !

When dealing with high profile gaming companies how do you meet their demands for new features that are not implemented?
We gather all incoming feedback from Japan, prioritize according to severity, popularity and amount of work involved and then plan the next version features. In cases where a customer requires something which is specific to them, like special training ( features, SDK ), assistance to setup / migrate a pipeline or custom development, then there is always the possibility of purchasing R&D time from Softimage through our Special Projects team.

Part of your job is “managing escalation of critical issues”. can you give us an example?
If a customer reports something very bad like a production showstopper or something which prevents the adoption of XSI in production, then we may escalate the issue internally and implement a fix which is provided to the customer as a QFE ( Quick Fix Engineering ). This is a service available to customers under maintenance. QFEs done in answer to issues in our last released product are always integrated in the next public release : either a point release ( Service Pack ) or the next main version.

Softimage 3D has been a long time favorite by Japanese companies and we are seeing some migration to XSI, Why has it been so hard for them to move to XSI more quickly ?
There is a cost involved in migrating since you need to train designers and port your pipeline ( workflow, plugins ) from one application to another. We released our first generation of game tools in SI3D at the time where the 1st generation of game consoles were coming out : SEGA Saturn, Sony PlayStation, Nintendo 64. Since we designed this in conjunction with SEGA, it quickly became the de-facto standard for 3D game authoring in Japan. Then, Alias released Maya in 1998. Although the first version was not ready for production use ( Japanese customers called it “mada”, i.e. “not yet” ), Alias had 2 years to work on Maya until we released XSI 1.0. Of course, we lost some users from SI3D to Maya during this period. It was a hard time for us, but we wanted to build a solid architecture from the beginning rather than something we would need to patch along the way. Now we can see this bet is paying off, as our development speed has greatly improved and is now imposing a pace of innovation which is getting difficult for our competitors to follow. With XSI 4.0 which includes the new poweful and affordable Foundation product, and many new advanced features throughout our product line, we have everthing we need to accelerate the expansion of our user community.

What features that you originally developed for SI3D have found their way into XSI?
Polygon raycasting, vertex colors, generic user data, polygon reduction, dotXSI support, RenderMap, pipeline tools ( export, viewing ), etc. These were implemented in XSI by my colleagues in Montreal. I wrote a few things for XSI like a User Normal Editing interactive tool and some realtime shader examples which I published on XSINet. Now I am studying the new Xgs and CDH features of XSI 4.0 ( which I think are really cool btw ! ).

What features excel in XSI for game companies?
Character modeling and CDK ( Character Development Kit ), polygonal modeling, polygon reduction, texturing, RenderMap / RenderVertex, CDH ( Custom Display Host ) and Xgs ( Graphics Synthesizer ), Realtime Shaders, dotXSI pipeline and FTK, ability to attach generic user data to scene elements and have it automatically supported through the dotXSI pipeline, general ease and flexibility of customization using the XSI Net View, Relational Views, Synoptic Views, and finally, the XSI SDK itself which is rich and now provides strong support for UI customization, among many new things in 4.0.

Will 4.0 change the gaming industry in Japan , and gaming industry in general?
Definitely. The low price point of our new Foundation product is opening up access to XSI to middle and low-end segments of cg production. It will also become easier for 2nd and 3rd parties to collaborate with high-end clients using XSI on joint projects.

As for the features of 4.0, there are many innovations which bring exciting new opportunities to our users. For example, the new rigid body dynamics are based on ODE ( Open Dynamics Engine ), an open source royalty-free solution. It is possible for game users to adopt ODE in their run-time engine and create realtime simulations which are entirely compatible with how things behave in XSI ( or you could simply plot / bake and export the animation if you do not want to recompute it in the game engine ). Also, the CDK ( Character Development Kit ) brings all the tools needed for making custom character animation rigs.

The CDH ( Custom Display Host ) allows an external application to communicate with XSI and display its output into a XSI view. It is possible for XSI to drive an external application and vice-verca ; this external application could be a game engine synchronized with XSI, or any custom tool which can be interacted with from within XSI. The Xgs ( XSI Graphics Synthesizer ) allows to create scene-level realtime rendering effects and can communicate with realtime shaders for advanced effects.

The Polygon Reduction tool in 4.0 is simply amazing, Texture Layers provide a very powerful workflow for multi-texturing management, Material Libraries simplify material management and the SDK is both rich and powerful.

XSI v4.0 is our biggest release ever since v1.0. It contains many other interesting features which are not listed here, as well as a large number of fixes for issues which were reported by our customers around the world.

What advice would you give to an artist of Northern America or Europe who wants to start working in Japan?
Learn the whole package. Designers in Japan do not tend to specialize in one thing, but instead are called to work on many different aspects of production : modeling, character design, animation, texturing, custom data editing, etc. The more flexible and proficient you are with the package, the easier you will connect with a Japanese production team.

Learn Japanese. Even though you can usually always find a few Japanese persons in each company who can speak a good level of English, it is more an exception than the rule and it would be better not to rely on that to bridge the gap with your Japanese colleagues. The better you understand and speak Japanese, the more chances you will have to connect with the team and contribute to the project. An american friend of mine who worked in a game company in Tokyo learned conversational Japanese very quickly because he was completely immersed in a Japanese working environment, but if you can learn some before heading to Japan it will make things a lot smoother and expand your opportunities.

Friday Flashback #198

Interview with Chinny Brynford-Jones: The XSI Product Manager of Softimage talks about version 4, the cg industry and his past career as a comedian — May, 12th, 2004, by Raffael Dickreuter, Bernard Lebel, Ed Harriss


What is your history with Softimage?
Over seven years of fun and an additional 40lbs of weight, I would like to think of it as additional charisma but I have a feeling I am just kidding myself. I started, weirdly enough, in 1996 in the Pitcher and Piano in Dean street London, sitting next to Adrian Hill (formerly Special Projects now Cinegroupe) at Ben White’s (formerly Softimage now Framestore) leaving do. I asked Adrian if I could come into the softimage office and learn SI3D. I thought it looked like the dog’s bollocks. He said yes and my window to weight gain had begun. An expense account, 100 flights a year around the world demoing Softimage 3D, then XSI, just sounded like a bloody good laugh. After five years of that with the odd spell in production, I met my current girlfriend. Montreal being such a crushingly superb place, I decided it was time to make the move. After years of experience in the field one thing followed another and now I am the XSI product manager. Funny how thing work out.

Can you tell us something about your past comedic career?
Mostly a disaster – the rest was just plain awful. I have tried doing a spot of stand-up in mainly friends type venues and having never been so nervous or embarrassed in my life. So I switched tack and started to write, although no matter how serious the subject matter it ends up as comedy. (Or “words” as others say) I guess always seeing the funny side of life has it good points. What has been fun tough is that Softimage has always allowed (even encouraged) me to entertain people during my demos. So the marriage of my two loves, comedy and XSI seems to be made in heaven.

You are also known as “Chinny”, what can you tell us about that name?
A friend Nick Savvy (another animator, sheesh do I know anyone else) in London and I used to write comedy stuff together -(which now sits in drawers gathering dust) He had 3D Studio release 4 installed (all legit – cough – of course) and after a year of teasing me that I should “try it” I did. I thought it looked waaaaay too complicated for my poor brain, but it really was absorbing and I was totally hooked. I conned my old man into springing for a computer, next was simply installing all the necessary software (cough, choke, splutter), which was naturally completely over my head. Although I could use 3DS4 I could not even change my login name and password. Which had been setup by Nick as login “Chinny”, password “Chin Chin”. He used to make fun of of my chin it seems. When I went to Softimage Adrian asked me for a login name, so I said, err I dunno…”Chinny”. There was a Justin King (Now EA) in the Softimage office and I used to get his calls, oddly it seems that Justin and Jason are apparently too similar. So I said why not call me Chinny and stop the confusion. The rest they say is the rest.

How challenging is your new title?
The title itself is not too challenging – but the job sure is. It takes up almost my every waking moment. In addition to all my regular duties, I really love to use the software, so doing both takes up all my time.

Now that you’ve been promoted, will you still do demos?
Fewer and fewer. I have little time to do it these days, except for the big occasions. Although preparing for them is still is an excellent way to keep my hand in using the software. Without using the software and interacting with customers one can not expect to really be a good product manager.

What do you do on your spare time?
(Embarrassed smiley) I work. Mainly making my own tools etc in XSI, but also writing marketing blurb, and future design ideas. I generally sit with my girlfriend in front of the TV with my laptop on top of my lap (how ironic). She says it’s a bit pathetic. (Another embarrassed smiley) as I am writing this interview as in the manner described above. Actually watching a DVD series called “Firefly” which is really rather good.

What impact does Special Projects have on the development of XSI?
As special projects is the ultimate in front line support, many specific production issues and requests get elevated to the top of the development cycle. This can have a direct bearing on future features and workflow being implemented inside XSI.

What is the exact nature of the relation between Softimage and Avid? Does Avid having any input in XSI’s development?
Very little. In version 4.0 there were a few items such as Mojo support, (very cool direct output which mostly does away for needing a DDR) but generally the XSI development is balanced between customer requests and our own innovations. Whilst all the time they are balanced as to what will make us money. We are a business after all. But one thing I have noticed is that since David Krall took over as head of Avid, I have seen more and more people prepared to lay down their life for him. He is a brilliant leader and a genuinely lovely guy. This has a huge impact on all of us. Never in my working career has one man so enriched a company of this size.

Now that Avid has bought NXN, will we be seeing some of that Alienbrain tech making its way into XSI?
Officially I can not comment on any future development. But if we were to look at past trends, it would fit nicely into Avid’s plans for all types of pipelines

How is Softimage structured?
Well Softimage is a business first and foremost. It just so happens that it is also a passion for the vast majority of us. Come in at the weekends or walk the halls late at night and count the people. They often have brilliant ideas which they just have to test.
As a software company we are driven by the release cycle and to a less extent major trade shows. We have all the usual suspects. Dev, support, marketing, sales, finance etc etc etc. It is a team, no… more a family. Everyone is 100% dedicated to bringing the best product to market that they can.

How different is Softimage from when you first started with them?
More experienced, more tight, more passionate.

How important are demo artist and product specialist to Softimage?
They are the well known faces of Softimage. They are the soldiers who charge into battle waving the flags, They work and play like they demo. Without them, the message would not reach the right people. But they are still as important a part as the rest of the amazing family “Softimage”

What do you see as version 4’s best new features?
Construction modes
Character Development Kit
Rigid Body Dynamics
Custom Display Host
Mental Ray v.3.3
Animator Audio tools
Vector and Raster Paint
Reference Animation
Material Library
UV Unwrapping
Programmable shaders
Etc etc etc

What are the most drastic changes within XSI from version 3.5 to 4?
Construction modes

How much have the particles/simulation tools changed in XSI 4?
Not much, the core is still there, but there are new customizable controls and goals.

How easier will it be in XSI 4 for people to create custom layouts and property pages?
Just as easy, but waaaaay more options and controls. For instance any layout can have a direct relation which can also trigger scripts. And if you want you could put an entire HTML front end onto XSI

In what areas do you think XSI is way ahead of the competition?
Real-time shaders
Hair (even with Maya’s half-hearted attempt)
Almost all types of animation
Polygon modeling

What are your thoughts when looking back to XSI 1.0 and what it has now become with version 4?
It is roughly as predicted but I certainly did not see all the innovations coming. My boss Gareth Morgan did though, he is a visionary at Soft.

What do you think of the XSI community as a whole and from what is was then to what it is now?
I love itthem. They are my extended family. I am amazed at how quickly it has matured, just seeing the rapid rise in the number of members of XSI Base is testament to what has become an explosion of XSI users (particularly after v3.0). With the huge numbers of projects being done, I am very impressed at how well they (the community) push the software. For most people 3D is now almost a religion, so imagine what it is like here at Softimage. XSI is our child. It is why there is so much passion surrounding it.

If you compare the European and the Canadian markets, what things are different, what things are similar?
Commercial production is a common tread. Although there is more money in Europe (especially London) for a range of different broadcast projects. So people who want to do high profile work often have to go to one of only a few major cities. As for the work culture, I find the differences often in the teams. In Soho they work very very hard, but play equally as hard. They socialize together more than I have seen anywhere else. Even from my own experience I used to go on regular snowboarding holidays with large gangs of animators. It often made for very boring conversations in local bars always talking about work, but that is what we did. With a huge number of post houses in one square mile I guess it more easily makes for a community. It is like food courts, all your specialist needs in one place. I would be interested if that type of community is exists elsewhere.

What’s your advice to a person that is starting in the industry?
It depends on what they want to do – So generally I would say ask around, look on the net and drop Ed a line  – better still buy How to get a Job in Computer Animation: If you want to be an animator etc, then make a showreel. Look for local companies and ask if you learn there or just go and show them your stuff, the catch is if you will probably have to do it for free. But working in a real production house really pays off in the long run. Think of it simply as slavery.

What skills are needed to join the XSI development team?
Programming is a must, but more than they have to be the best. Softimage has an incredibly talented bunch of devs. Which is why they manage to make such wonderful software

What are some skillsets that you believe studios are looking for these days?
TD’s always. From to character rigging to rendering and lighting. In film and longform projects, TD’s outnumber animators. In broadcast and commercials generally a good all-rounder will go far. And in games, modelers-texturers-animators make up the bulk compared to programmers. But simply if you can do one thing really really well then you can find a home, it just means you might have to travel

Where do you see the 3D industry 5 years from now?
From my private moon in the shape of an enormous pie.