Inside Sabertooth
Learn how Sabertooth uses 3ds Max to create 3D interactive projects, including HBO Go’s Game of Thrones interactive experience
  • 1/3
You are here: Forum Home / Autodesk® MotionBuilder® / Autodesk MotionBuilder 2009 / bug with trying to share the same frame as a stop and start in multiple takes
  RSS 2.0 ATOM  

bug with trying to share the same frame as a stop and start in multiple takes
Rate this thread
 
24558
 
Permlink of this thread  
avatar
  • s a m
  • Posted: 25 March 2009 03:35 AM
  • Total Posts: 1
  • Joined: 25 March 2009 08:43 AM

Has anyone run into the problem with multiple takes not being able to share an end frame(Local stop) in one take and a start frame(Local start) in another take in one fbx?
ex: using the same animation(s), model(s) (or you can even do this with nothing in the scene), Take 001 set to start at frame 0 and end at frame 60. Take 002 is set to start at frame 60 and end at frame 120. If you go back to Take 001 everything seems ok, go back to Take 002, either in the Transport Controls or in the Navigator, and the start frame number sets itself to 59.
This will prove to be a hassle when making a master motion take then copying it off and setting start and stop frames in subsequent takes to break it down for export purposes but still needing to share identical in and out frames.
This was never a problem in Motion Builder versions until 2009.

Thanks from Tokyo!



Attachment Attachment
Replies: 0
avatar

ug.. yeah same bug here, reporting it to autodesk. I hope they can hotfix it.



Brad Clark
Co-Founder: Rigging Dojo-Teaching the art and science of character rigging
Author: Inspired 3D Advanced Rigging
The Character Animator Toolkit for Motionbuilder :available now:

Replies: 0
avatar
  • raitch
  • Posted: 25 March 2009 08:18 PM

While an investigation is going on about this bug, I offer you a possible workaround that uses the comments field of the takes to store the values you want.  Here is the script:

from pyfbsdk import *

def SetCommentsFromTakeValues():

    
lTakes FBSystem().Scene.Takes

    
for Take in lTakes:
        print 
Take.Name
        LocalStartFrame 
Take.LocalTimeSpan.GetStart().GetTimeString()
        print 
"LocalStartFrame: " LocalStartFrame
        LocalEndFrame 
Take.LocalTimeSpan.GetStop().GetTimeString()
        print 
"LocalEndFrame: " LocalEndFrame
        ReferenceStartFrame 
Take.ReferenceTimeSpan.GetStart().GetTimeString()
        print 
"ReferenceStartFrame: " ReferenceStartFrame
        ReferenceEndFrame 
Take.ReferenceTimeSpan.GetStop().GetTimeString()
        print 
"ReferenceEndFrame: " ReferenceEndFrame
        
        NoteString 
""
        
NoteString NoteString.join("StoredTakeValues," LocalStartFrame "," LocalEndFrame "," ReferenceStartFrame "," ReferenceEndFrame)
        print 
NoteString
        Take
.Comments NoteString
        

def RestoreValuesToTakes
():

    
lTakes FBSystem().Scene.Takes

    
for Take in lTakes:
        
        
NoteString Take.Comments
        NoteStringSplit 
NoteString.split(",")
        
Take.LocalTimeSpan FBTimeSpan(FBTime(0,0,0,int(NoteStringSplit[1])),FBTime(0,0,0,int(NoteStringSplit[2])))
        
Take.ReferenceTimeSpan FBTimeSpan(FBTime(0,0,0,int(NoteStringSplit[3])),FBTime(0,0,0,int(NoteStringSplit[4])))
        print 
Take.Name " restored from Comments Values."

It will allow you to setup the real values that you want to use in the Takes interface, then store them in the Comments field by running the first function.

After it is set, you can then restore those values any time with the second function.  I am assuming at file save time…

Anyway, post any further questions or issues about this.

Thanks!

P.S. Yes, this is un-commented, probably redundant in many ways but I wanted to post it as soon as I had it working…



Attachment Attachment
Replies: 0
avatar

nice on both bug hunting and workarounds.



Brad Clark
Co-Founder: Rigging Dojo-Teaching the art and science of character rigging
Author: Inspired 3D Advanced Rigging
The Character Animator Toolkit for Motionbuilder :available now:

Replies: 0