View Full Version : HELP!! Bip01 error when moving keys
Sizzlenuts 05-08-2002, 04:51 PM Anyone out there using biped for character animation run into the problem of it not letting you move keys in the timeslider or track editor due to some bip01 error that says you cant move keys due to 3 reasons which are not necessarily the case.
This happens to me all the time!
|
|
Ibanezhead
05-08-2002, 07:35 PM
Make sure you have the lattest updates for MAX and CS. Next, save before you move keys :)... It is very frustrating, I know...
Vic
Iain McFadzen
05-08-2002, 08:02 PM
Try this:
1)Region-select the whole BIP in the viewport.
2)Come out of the Motion Panel (i.e. go into the Create/ Modify/ Hierarchy/ Display/ Utilities panel).
3)Click in a bit of empty space on the track bar.
What's happening is you still have Biped COM keys selected, but because CS only lets you select a single COM track (vertical/horizontal/rotate) at any time you can't actually see the keys you have selected. By leaving the Motion panel you can make Max show all the biped keys at the same time, and so you can deselect them all.
Another approach I use to the release the selected COM keys is to turn on modify subtree in trackview, click in open space to deselect, then turn off modify subtree and re-aquire the selection to be moved.
BTW - Frame snap should be off if you have sub-frame keys.
-Shea
www.Ls3D.com
:cool:
Sizzlenuts
05-08-2002, 10:44 PM
I may not understand, but I tried the things in both emails and neither of them make it work. Even if I go into the track view and just try to move one key in one track of the bip01 node (vertical, horizontal, rotation) or just a key in the spine or head it still gives me the error. This only happens occasionally say 25% of the time. Sometimes a file will not move even one key on one track and the error pops up saying:
bip01
This operation is not possible because it results in illegal timing. Some of the restrictions are:
1 cant have keys before the first or after the last footstep
2 cant overlap keys
3 cant move keys below the 0 frame
none of those are true.:airguitar
Biped01 is the tricky one, it has three slots in the trackview editor: Horizontal, vertical, rotate (4 if you add a visibility track ;) )
if you select whole biped or just biped01 object or with other biped objects in normal viewport, Max don't not regonize which transformation track of the biped01 object you a selecting and will not let you slide the keys in time slider. What you can do is:
- Click on any empty space to make sure you dis-select all the keys. Then select all three slot of transforamtion keys of the Biped01 object in trackview (or with other keys of biped object if need) , and you should be able to move the keys by now.
Since other biped object have only 1 track, and they don't have the problem of what the biped01 has.
Hope this will help
:)
Sizzlenuts
05-09-2002, 03:18 PM
I can't move one of the tracks or all of the tracks of the horizontal, vertical, or rotation. I can't move all of the keys of the entire biped or one of the keys anywhere on the biped except for a few tracks like the feet. It doesn't matter whether I am using the track view or the time slider and it doesn't matter whether I select any keys of the Bip01 node or not.
Still gotcha stumped? If you figure this one out you win the smartest Max user on the planet award.
This is not an easy one trust me...
ok, try this out...select the keys you want to move, copy them to where you originally move, then delet the keys at the origin position. So the procedure is copy first and delet. This definetly not the proper way, but it seems you are running out of option.
Sizzlenuts
05-09-2002, 04:28 PM
but not in this case. Max refuses to even let me copy one or all of the keys of the bip01 node or most any of the other nodes and gives me the same error.
Max is the buggiest crappiest software ever! Particularly Character Studio.
Nice try though. Usually that doesn't work anyway because to edit time I would need to move keys around on tracks that if I had to copy it would pass or sit over the top of other keys.
I wish someone at Discreet could tell me how this begins to happen in the first place. You know like a why it happens and how to prevent it, cause sooner or later in a lot of files that use the same character it starts to happen. Some worse than others. The only work around I have found is to go in the track view and start moving some tracks that will allow it then try and find the right other tracks that will move. It's ridiculous and a waste of time but sometimes I have no other choice.
Maya Rocks!:buttrock:
I hear ya, Sizzlenuts. Character Studio is a bug based plugin of Max. You can't animate with the function curve for CS and thats already a major failure. But their bone system sucks more than what you can imagine.
Sizzlenuts
05-09-2002, 04:57 PM
Yea, I hear ya.
Although I have to tell you I've had way better luck with the bones and Ik in max than I've had with Character Suckass. Once I found how to freeze the rotations of bones so in the track view they all start at 0 it wasn't too bad. My biggest frustration there is just the track editor, which is a joke, and general interface in that it takes 15 clicks to do anything.
I hear they now have the people who did a lot for Maya working for them now and they are re-vamping the track editor in 5 so I think there is a lot to look forward to. Unfortunately they aren't doing anything with character suckass in Max 5.
Thanks for the replys
-D
hum....since I shift between Max and Maya, so I am not really depend on neither Max bone or CS. Max is still good on polygon modeling as its poly tool (to me) is better. But I will definetly work in Maya when I do rigging and animating characters.
For about Max 5, I will just sit tight and see what is going on with it. OH, and maybe I will wait until their 5.5 verson to come out.:wip:
i think youll find your answer on the CS forum deeseeceereet runs, theres some great users there that help out for almost no extra charge.
I dont know if you solved your "illegal timing" problem yet, but i had the same problem. It seems when keyframing a key is sometimes in conflict with another. If this happens, and you get the "illegal timing" thing again. Then just go into the biped tab and use commands Ctrl+Alt+F this should search for timing problems and fix it, and you should be able to clone keyframes again. I found this out in the MAX help files, which is another good example in searching the MAX help files first.
CGTalk Moderation
01-13-2006, 05:00 AM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.
vBulletin v3.0.5, Copyright ©2000-2012, Jelsoft Enterprises Ltd.