Jeremykendall Posted April 17, 2018 Share Posted April 17, 2018 Hello, Recently I had been having a issue of taking a file I was working on at home..built on a old first gen i7 cpu to at work current 10 core xeon chip. The constraints were not acting the same way. I also had done the file in 16.07 at home vs 16.5 at work. Then I got a new I9 10 core for at home and was having the same issue. Constraints just ripping them selves apart and not holding like they should. Bullet packed prims... I thought this was due to the cpu chips being different maybe they had different floating point math instructions etc. Then I found out that in 16.5 they removed the single threaded constraint solver option. Now everything is running in parallel, solves are happening faster. But not acting the same way. Even in the help doc they mention that the solvers act different.. like friction and so on. What are you doing workflow wise to ensure files work the same? Thanks Jeremy Quote Link to comment Share on other sites More sharing options...
StepbyStepVFX Posted April 17, 2018 Share Posted April 17, 2018 I think in production they tend to freeze the updates of the softwares when they start the projects to be sure the pipeline will remain stable. I think the only solution in your case is to see if they kept the old solver node in 16.5.. 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.