Well I must confess that I didn't re-name the prefs and run the runonce but this was spotted by a colleague on a different workstation and was subsequently re-created on a number of different machines. So I'm pretty sure that's not it. Working under a model when rigging seems solid enough advice but when you create a spine using the built in tools it puts the newly created spine under the scene root by default. (unless I'm missing something)

On 02/10/2012 12:29, Simon Anderson wrote:
oo.. runonce and remove your user preference(rename the folder), those also are very good, good one Eric

On Tue, Oct 2, 2012 at 9:28 PM, Simon Anderson <[email protected] <mailto:[email protected]>> wrote:

    brain fail... what I mean to say was

    1.) I found the best way was to create a spine component yourself
    and bring it in when needed
    2.)Work under a model(not scene root) when you are creating a rig,
    that way any alterations will get applied to the mixer of the rig
    model that you will be exporting.




    On Tue, Oct 2, 2012 at 9:25 PM, Simon Anderson
    <[email protected]
    <mailto:[email protected]>> wrote:

        Hey, Dont think I have ever encountered this problem, but have
        had a problem with some of the pre built softimage tools like
        spine and tail. What usualy happens is as your building your
        rig in soft, you are working in the scene root and some soft
        tools modify the mixer in the model, and then when you put
        everything under a new model export it and bring it it, the
        rig freaks out as what it relies on in your mixer no longer
        exists, I found the best way was to create a spine component
        youself and bring it in when needed of work under a model when
        you are creating a rig, that way any alterations will get
        applied to the mixer of the rig you will be exporting.

        Not sure if this will fix your problem, but its just something
        to keep in mind sometimes.

        cheers
        Si


        On Tue, Oct 2, 2012 at 8:38 PM, Gerbrand Nel
        <[email protected] <mailto:[email protected]>> wrote:

            Hey Matt
            This one bit me and Darren a couple of years ago. 2010 or
            2009 maybe.
            We couldn't figure out a perfect fix for this, but we also
            noticed that the problem was more likely to occur on
            reloading a scene rather than starting softimage clean.
            At the time I was convinced that it was a linux exclusive
            problem, but I've seen it in win7 a few times over the years.
            The neck in the xsi rig also does this from time to time.
            Nowadays I'll just recreate the spine and head of an xsi
            character if I'm forced to use that rig.
            Sorry I can't give you a fix, but at least you know you're
            not alone.. All people from South Africa gets this problem ;)
            G

            On 2012/10/02 11:14 AM, Matt Lowery wrote:

                Hi all,

                I've rigged up a character using very traditional XSI
                tools, no plug-ins, and I've discovered a very strange
                problem. If I launch xsi and import the model of my
                character he works as expected. However if a do a
                File>New_scene and then import the same model file the
                spine on that imported model is broken. The spine in
                this case literally being the spine of the character
                and created using the Skeleton>Create Spine command in
                XSI. I have figured a work around this but has anyone
                else experienced a similar problem? The Rig was built
                in 2012 SAP but the problem is also present in 2013.

                m@



                -----
                No virus found in this message.
                Checked by AVG - www.avg.com <http://www.avg.com>
                Version: 2013.0.2677 / Virus Database: 2591/5803 -
                Release Date: 10/01/12






-- -------------------
        Simon Ben Anderson
        blog: http://vinyldevelopment.wordpress.com/




-- -------------------
    Simon Ben Anderson
    blog: http://vinyldevelopment.wordpress.com/




--
-------------------
Simon Ben Anderson
blog: http://vinyldevelopment.wordpress.com/


Reply via email to