CompuServe Thread

#Bones problems in stage

3 messages in this thread
#81061From: May 4, 1994 12:45 AM
I just got my Im 3.0 for the Amiga. My first experiment with bones is puzzling… In DETAIL editor… I made a tube, added 2 bones, created 3 states (following the hand tutorial): 1 – Default, tube standing on edge (I tacked my texture here) 2 – Straight, same as default, but the manual said I needed this for tweening 3 – Bent, each bone bent at 30 deg or so. I then quick rendered in straight position. Worked fine. I then quick rendered in bent position. VERY COOL, worked great, wrinkles and all. Moving to the STAGE, I brought in the object, state set to BENT. The tube came in, with the BONEs bent (sticking right out of the side of the tube), but the tube's skin was in the straight/default position, no bends. I reentered the DETAIL editor, loaded the object, set the state to BENT and it was bent with the skin bending with the bones as expected. Whats up? What am I doing wrong? Why is it working in the detail editor, but not stage? Thanks in advance, Jeff
#81072From: Stan Kalisher (Impulse)May 4, 1994 7:47 AM
Jeff, Dont use the default state as a bone set up, it needs to be left alone, if you use it in the stage it might do as you say., If you want the state of the default to be used, in the detail editor, set it to default and then create a new one called something else. Its a quirk of the bones system. Mike
#81336From: May 6, 1994 10:03 PM
Mike, I figured out the problem. There seems to be a minor glitch: On the Amiga, if I bring an object into the stage and set a state in which the bones have 'bent' the original object. The bones show up in the correct locations, but the object skin is left in the 'last saved' state of the object (possibly the default state, I'm not sure). If I reselect the current frame with 'RA-C=#' then when the stage refreshes the 'skin' has moved into the correct shape. If the object was save with 'SHAPE' checked in each state it works fine, but the manual suggests this will take up extra space. So I guess it's a bug, but not really troublesome, it only affects freshly loaded objects in the stage editor and RA-C-# cleans it right up. Jeff