search

erwincoumans / dynamica

Automatically exported from code.google.com/p/dynamica
8 stars 3 forks source link

Framerates other than 24 disable RB initial position at frame 1 #11

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Set the scene framerate to anything but 24
2. Create an active rigid body primitive (sphere or cube)
3. Press play

What is the expected output? What do you see instead?
RBs should fall via solver gravity and reset to their initial positions when 
the frame is set back to 1. Instead objects fall but never reset to their 
initial positions when the frame is set back to 1. When the scene is played 
back again, the RBs remain frozen until the frame of their last movement, then 
resume.

What version of the product are you using? On what operating system?
Dynamica v 2.76, Maya 2010, winXP x32

Please provide any additional information below.

Original issue reported on code.google.com by mbb...@gmail.com on 8 Sep 2010 at 4:09

Attachments:

GoogleCodeExporter commented 9 years ago 

Haven't checked your file, but could you test if the problem still exists in 
the newest Dynamica for Bullet 2.77?

http://dynamica.googlecode.com/files/Dynamica-2.77-Windows_AllVersions.zip

Original comment by erwin.coumans on 16 Nov 2010 at 12:15

GoogleCodeExporter commented 9 years ago 
The problem is "fixed". However, there is another issue:

The solver node (dSolver1) supports a user changeable Start Time field. The 
value of this field will be updated if the scene frame rate is changed. If the 
user then changes the starting frame value on the time slider (which is often 
desirable to avoid values greater than or less than 1.0), the Dynamica solver 
not update the Start Time to this new value - resulting in a mismatch of the 
scene start frame and the solver Start Time - thus, the sim is never reset.

The solution is to ensure that the solver Start Time matches the scene start 
frame.

Original comment by mbb...@gmail.com on 16 Nov 2010 at 6:57

GoogleCodeExporter commented 9 years ago 

Thanks for the explanation. Do you have a solution for this, such as a patch?

Thanks,
Erwin

Original comment by erwin.coumans on 16 Nov 2010 at 9:17

GoogleCodeExporter commented 9 years ago 
I *believe* this can be fixed via the dynamicaUI script with a scriptJob (which 
allows script execution via a Maya event - such as time slider range changed). 
I have added this to my fix list.

Original comment by mbb...@gmail.com on 17 Nov 2010 at 3:19

GoogleCodeExporter commented 9 years ago 
issue fixed in current dynamicaUI.mel

Original comment by mbb...@gmail.com on 3 Jan 2011 at 7:11