slayerk Posted March 25, 2011 Author Share Posted March 25, 2011 I resolve problem with EmptyData DOP + FetchData DOP. Now SOP Solver operates with new data and don't recalculates SDF. Big thanks! Quote Link to comment Share on other sites More sharing options...
Sifis Posted March 25, 2011 Share Posted March 25, 2011 I resolve problem with EmptyData DOP + FetchData DOP. Now SOP Solver operates with new data and don't recalculates SDF. Big thanks! Hmm, can you share your hip to take a look? Quote Link to comment Share on other sites More sharing options...
slayerk Posted March 25, 2011 Author Share Posted March 25, 2011 (edited) here... SOPSolver_test.hip Edited March 25, 2011 by slayerk Quote Link to comment Share on other sites More sharing options...
slayerk Posted March 25, 2011 Author Share Posted March 25, 2011 (edited) sorry... how to remove post on this forum? Edited March 25, 2011 by slayerk Quote Link to comment Share on other sites More sharing options...
Macha Posted March 26, 2011 Share Posted March 26, 2011 (edited) No sdf, but I really don't understand why you did that. You created a new data and copy an attribute with the point positions in it, and object merge that into sops? The oldp attribute is identical to the Geometry P. Why don't you just grab that with a dopimport. No need for a sopsolver in the first place. Am I missing something? Edited March 26, 2011 by Macha Quote Link to comment Share on other sites More sharing options...
slayerk Posted March 27, 2011 Author Share Posted March 27, 2011 No sdf, but I really don't understand why you did that. You created a new data and copy an attribute with the point positions in it, and object merge that into sops? The oldp attribute is identical to the Geometry P. Why don't you just grab that with a dopimport. No need for a sopsolver in the first place. Am I missing something? ok. i'm deskribe idea: as you know (i think) solvers in MultipleSolver executes in order of connection input number (my english so bad!). 1st SOPsolver saves Position on start of simulation step. before RigibBody Solver changed it. RigidBodySolver changed Position Data. 2nd SOPSolver getting changed (by RigidBodySolver) Position Data and substract from it oldP. In another words: (P-oldP)/TimeStep=v. Where is P - current Position Data (Position Data in the end of timestep), oldP - Position Data in the start of Timestep. true per point velocities generates on "New" data. my object merge in "box_object1" merge "New" data with right per-oint velocities. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.