Hi!
I have an issue with a RBD shatter animation that I am trying to solve with no luck.
I shatter the glass on impact but pretty much every single crack flickers through the animation which is something I don't want of course. I have tried RBD Connected Faces / Disconnect but that removes the connected sides, thus removing the cracks which is something I also don't want.
Any ideas how to solve this would be greatly appreciated!
Cropped render attached (play it looped )
Thank you!
Found 7 posts.
Search results Show results as topic list.
Technical Discussion » Flickering RBD glass cracks
- Beatnutz
- 7 posts
- Offline
Houdini Lounge » Some Threadripper results
- Beatnutz
- 7 posts
- Offline
tricecold
You need to be careful on how to squeeze the maximum performance from your hardware. Test both with openCL on and off, write straight to disk as bgeo.sc, never render your simulations without caching. Why, because you may want to play with shading, lightning etc. TR will make even more gap with higher-resolution simulations, why because you will keep threading busier longer instead of occupying CPU with thread management.
It was the same case when small simulation times compared between dual Xeons vs one fast I7. There is no magic button that makes everything faster. Especially with compile workflow TR will be so much faster in Houdini, why because Compile SOP compiles your many small SOPs into a an imaginary SOP that multithread so much better. I've had sped improvements 5 to 10 times after converting old tools with compile sop on same CPU
Grain solver works best with a fast GPU, so make your comparisons with it turned on and off
Thank you for your insights. Good to know!
I've done renders with and without OpenCL, it was faster with. But I never did the original tests (5820K) with it so hard to say how big the difference is.
I also tried using OpenCL CPU but that slowed things down by a lot.
I never really use cache since I'm sending my Alembics over to C4D ususally, but I'll try some comparisons there too.
Houdini Lounge » Some Threadripper results
- Beatnutz
- 7 posts
- Offline
aRtye
These are very basic scene file tests so I wouldn't put too much value on them for real-world performance. Things to improve the tests are turning on OpenCL CPU and turning on OpenCL in the solvers, use file caches instead of going straight out to abc.
In the end if you aren't using threading well then CPUs haven't really got faster in 7 years
OK, wasn't aware that would make such a huge impact if they are both simulated the same way. If u have another HIP and your sim time I'd be happy to try it out so we can check the difference.
Houdini Lounge » Some Threadripper results
- Beatnutz
- 7 posts
- Offline
Skybar
You are testing a lot of GPU stuff for benchmarking a CPU. What about a Mantra test?
Yeah I mainly wanted to test it in software that I work/play in frequently. Regardless of GPU/CPU. The C4D test was mainly to see how well it handles large simulations from Houdini in Cinema 4D with 8K materials. So lots of polys etc and big VDB files to load etc.
I also tried caching an X-Particles sim but I had to ditch it since it gave me such poor results. It seemed to be single threaded which is strange. I'm going to check with them about it.
Never used Mantra to be honest, I always send Alembics/Digital assets over to C4D/Octane.
Edited by Beatnutz - Aug. 31, 2017 11:21:25
Houdini Lounge » Some Threadripper results
- Beatnutz
- 7 posts
- Offline
twod
The pyro sim results show the biggest improvement of any of those benchmarks, even the non Houdini ones. You don't consider that impressive?
To be honest, that is the smallest improvement I was expecting. TR has 10 extra cores over my old CPU. Twice as fast is very nice indeed, but anything below is not enough.
If I was only doing pyro then this would have been amazing. But now I'm a bit pissed (not blaming SideFX or anything) about spending all that money and having a slower machine . Next time I'll just wait for other peoples benchmarks. But it would be nice to see a fix for this in the future.
Houdini Lounge » Some Threadripper results
- Beatnutz
- 7 posts
- Offline
ndickson
Could you post a HIP file and a description of what you were testing? It could be that whatever you were testing currently doesn't thread much, which we might be able to do something about. There have also been a few reports of Threadripper having poor performance or even crashing under moderately heavy load, (e.g. compiling the Linux kernel), due to heating issues, but I don't have one, so I haven't independently tested that.
I also had the crashing. But I think that is only with the MSI X399 motherboard. If you turn off a setting in the BIOS then the crashes go away. It is a solution until a new BIOS version comes out.
Here are the HIP-files. I exported them as Alembic (all 240 frames) and timed it.
Houdini Lounge » Some Threadripper results
- Beatnutz
- 7 posts
- Offline
So I just got my TR CPU and was doing some tests. Must say the results were not impressive at all in Houdini. I thought something might be wrong so I ran other more common tests (Realbench etc) and my score there was on par with other benchmarks I've seen.
Anybody else got similar experience?
Anybody else got similar experience?
-
- Quick Links