Toon_Scheur wrote:I think what bfvietnam means is that all serious artists uses more than one softwarepackage. XSI is certainly powerful, but of course it doesn't have everything. In the case you have a $$$ package
Well XSI use cheaper than ever.. It used to be 2000 dollars for foundation,
now its 500 dollars.. Even Cinema 4D, tends to cost more with as much
stuff as is in XSI.. And Blender would take a while to get there.. Blender
is easier for modelling, and faster for rendering.. But the rendering
capabilities of blender are limited.. I've seen everything it can do,
and have exploited most of blenders features.. I'm amazed though,
that XSI doesn't seem to be any better for animation than blender..
I may find out something more.. The first IK package I used, Kinemation,
nothing exists like it anymore.. I think the closest thing to it is sega animanium.. Which is actually easier.. But maybe I've been out of touch
with animation so long that I don't know how people can animate now.. It seems most FK/IK is done with mocap these days, which is short for lazy..
Well maybe I'm assuming XSI will be better for animation than blender,
which is what blender lacks, is an ease of animation.
and you have the choice to use a second (companion) package beside it, it would be a good idea to use Blender. Even at Pixar animators commented that they miss their old package they used to work with because Pixar's software doesn't have certain features. But on the other hand Pixar's software (Marionette for example) has features other packages don't have. I know that Pixar uses other off the shelf packages too.
Well I don't know how pixar works, but I assume they use whatever
their artists are more comfortable with, or whatever is easier.. If they
didn't they would have a hard time retaining talent, if not just for
the pure magnetism of working at Pixar. I imagine they code their own stuff for stuff they need to do..
Even Blender users uses Yafray from time to time. But that is no argument to attack someone because he uses a companion program to complement the other. Yes, Blender could use a bunch of other features, like XSI's shader nodes. That would kick ass. But frankly, you can't keep everybody happy. You can have a gazillion features in your package. But you will need 3 lifetimes to have time to use them all. So is a shader tree like architecture priority number 1 for Blender? Could you make good looking textures already with the native procedural textures, or selfmade images?
That is just one example of course.
Yafray is a nice addition.. Its a bit of a breath of fresh air compared
to blender's rendering.. But blender is better now for rendering that
it used to be.. But you can say color shadows, or have much control over the shading.. Mental ray lets you shade and shape everything, the
speculars, the surface shading, the shadows, refractions, reflections, etc..
Shader Trees may appear within blender in the texturing system.. The
material system could stand to be broken apart.. I mean, you could probably write something that turns blender shaders into mental
ray, but going the opposite direction would be harder..
There is plugins for XSI from "Dark Tree" that will use
shaders from Dark Tree in XSI.. There also exists plugins
for a number of other platforms.. I'm planning on using it for
materials in XSI.. Take a look at some of the materials
from Dark Tree, and you will see some of the surface properties
there that are impossible to simulate in blender.. I don't recall
exactly what, but I remember it has layers that influence layers,
like dynamic rust textures that use decals to simulate
It's is not desireable to demand that someone uses Blender alone if he or she feels that it lacks some things. But one should understand that if you could port a few of the well known features of XSI over to Blender, that there would be a reason less to buy X$I.
I think that it is very interesting to learn of other people opinions who actually uses other packages AND Blender to know what Blender strong points are and where it lacks functionality
Well XSI is written in C++, there is less chance blender would be able to
be that flexible, despite what the coders say.. They know its tough to
maintain.. Though they will argue to save face.. If it was easy to maintain,
blender would have plugins by now.. But they've chosen to go the python route because its less intrusive, and allows them to change the underlying stuff without involving anyone else.. The plain truth is objects just make
things easier.. The only mention against it is in the name of efficiency,
but if it end up taking you ten times longer to add a feature in C that
takes you less in C++, what is the value of the efficiency? Its not very time efficient. As everyone must wait for feature X.. And is time, money?
Well I was around since Blender 1.24.. It doesn't bother me to jump around.. Even before I was on Blender, I was using Alias and Wavefront
which at the time sold for 7000 dollars, and had more features.. The reason I started using blender at the time is I could afford the packages,
upon leaving college, and I was hoping it would develop faster, than it has.. But I don't regret learning it.. Its easy to model with,
and the interface and the way things are organized gives one a preference for a way of working. But there are internal organization issues that stint its growth.. Whereas with XSI, many reviews I've read say with each new release many things are being added now.. What impressed be was the ability to model atop Subdivision surfaces, then modelling the sub-surface CV's without loss of the derived polygonal detail.. Maybe I haven't explored this enough to see the downsides to XSI..
Now I'm not completely convinced that XSI will be better, its been steep and hard to learn, reminds me of learning Alias. Wavefront was steep to learn.. Maya is a pain compared to the previous packages because, frankly, its a hack that condensed 15+ packages from three previous companies, who were competitors (TDI, Wavefront and Alias). So if you ever wondered why Maya is so wierd, that's why.. XSI was the package Microsoft purchased, briefly, that forced SGI to form Maya.. It was a fear tactic. XSI has remained constant, changing.. Like Lightwave and 3DsMax
and Blender, but Maya is strange fish..
XSI is like a vacation from blender.. I will most likely use them in combination, but more using blender to model and organize scenes, and to animate with XSI.. But I'm not a professional, just been spoiled.. I'm hoping XSI will be the primary package I use.. Using combination of packages sometimes can be like compositing different pieces of film..
In effect you feel like you can mix them, but are you doing that for effect or doing that just for bragging rights..
I frankly can't see how someone, or why someone, would move stuff from XSI into blender.. Unless just to speed up a render.. But I do tend to
use VI more that MSWord.. Blender is like the VI of 3D graphics packages.