Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


DaJuice last won the day on October 2 2016

DaJuice had the most liked content!

Community Reputation

22 Excellent

About DaJuice

  • Rank
    Houdini Master
  • Birthday 03/01/1982

Personal Information

  • Name
  1. Hi, try just hitting Enter in the viewport (with the correct node selected). Does that bring the handle back? If not then maybe the handle display got turned off. Hold or right click the handle button and make sure the handle you want is checked. See attached image.
  2. Flip Fluid Collision Problems

    Change Collision Detection on your cup static object to "Use Volume Collisions". The Surface Collisions are in fact generating some polygons at the top of the cup.
  3. Flip Fluid Collision Problems

    Basically what Sean said. Give the cup some thickness. In your cup Static Object, make sure you have an adequate collision representation. Uncheck Display Geometry and turn on the Collision Guide, and adjust the Division Size under Collisions > RBD Solver > Volume. Once that looks good you'll want to make sure that the FLIP Object is creating adequate collision geometry from that. Turn on the Collision guide. To increase the resolution of the collision geometry created by the FLIP Object you can decrease Particle Separation, or enable Collision Separation and give it a value not tied to Particle Separation. Beyond that if you notice wonky behavior, like a few particles penetrating anyways, try increasing your substeps on the FLIP Solver. If trouble persists, please upload a file.
  4. [SOLVED]Removing InLine Points?

    You can append a Facet SOP and turn on Remove Inline Points. The results are not always perfect though.
  5. Is AMD potentially risky? (Threadripper)

    Hey Marty, CPU OpenCL does work on TR, it just wasn't as fast as the GPU. Unless you mean it's a suboptimal implementation. It will use only one card. If you have something like GPU-Z installed you can choose which card to monitor, and during OpenCL only one of mine was under load.
  6. Is AMD potentially risky? (Threadripper)

    @Diorn, Okay PorcelainSops_V1 scene took 15m 28s. Same settings as before: TR 1950x, at 3.8GHz, memory at 3,200MHz.
  7. Is AMD potentially risky? (Threadripper)

    @marty, sorry I'm on Win10 as well. @Diorn, I will try to run your benchmark in the next couple of days.
  8. Is AMD potentially risky? (Threadripper)

    That's exactly right Diorn.
  9. Is AMD potentially risky? (Threadripper)

    @VFXArabia, okay back with some numbers. Threadripper 1950x @ 3.8GHz, memory @ 3,200MHz Pyro @ 0.02: 14m 55s Pyro @ 0.05: 54s Pyro @ 0.1: 24s Grain @ 0.01: 6m 58s Grain @ 0.02: 49s FLIP @ 0.05: 45m 10s FLIP @ 0.15: 1m 39s Interesting to see the CPU utilization at different resolutions. For example the FLIP scene had distinct spikes and dips at regular intervals at 0.05 particle separation, whereas at 0.15 it was a pretty even ~50% CPU utilization. Heh, I expect so too but I'm curious if Cinebench is really that accurate an indicator of CPU rendering performance. For some reason I don't think the gap will be as big with Mantra.
  10. Is AMD potentially risky? (Threadripper)

    Ah that makes sense. Also Marty and Diorn, if you are getting unexpectedly short completion times for the boolean sphere scene, check and make sure that all 45 frames have actually been rendered to the output folder. With some of my unstable overclocks, I was seeing 100% in the Render Scheduler but the sequence had stopped short. Cool, I will give these a whirl. I believe around 82C is the max I've seen from playing around with various overclocks. This is with a Corsair H115i (280mm radiator). The coldplate on those is a bit inadequate for the size of the IHS on Threadripper, but at the time there weren't any coolers available designed specifically for TR. Now there's the Enermax Liqtech TR4 and the Noctua stuff, and more to come I would assume. IMO to go beyond 4GHz on TR you'd really want custom water cooling, and the power draw will be ugly. If anyone feels like adding another benchmark to the mix, here is one that's purely Mantra. Reflection/refraction + displacement + SSS + volume rendering + instancing = good times. Probably not the kind of thing Mantra excels at. It's an older 15.5 scene so it may give you a load warning, just ignore it. Hit 'Render to MPlay' and note the completion time in the Render Scheduler or in the MPlay window. tabasco.zip (33MB) I got: 3.4GHz (CPB enabled): 18:06 ~62C 3.8Ghz: 16:35 ~79C I attempted 3.9 and 4GHz as well, but they weren't stable when rendering this scene.
  11. Is AMD potentially risky? (Threadripper)

    That 7900x is looking really good Diorn. What kind of temps are you seeing with that overclock on your 360? I've updated my original post with the boolean sphere scene to include an external link, since downloading of attachments seems wonky at the moment. Here are some numbers with a revised overclock. The relevant specs: Threadripper 1950x @4.00GHz 32GB HyperX Predator (4x8GB) @ 3,200MHz | 16-18-18-36 2x Nvidia 1070 FE (relevant to OpenCL scenes I would assume) Boolean Sphere: 15:02 Grain: 1:45 Pyro: 6:09 Fluid: 0:33 Cinebench: 3411 Cinebench Single Core: 164 Couple of side notes: It seems like the latest beta BIOS (1.52) for the MSI board fixed the Core Performance Boost crashes. With CPB enabled I observed the core frequencies bouncing between 3.4GHz and 4.00GHz in HWiNFO during the boolean sphere scene, averaging around 3.7GHz, with a completion time of 16:12. Regarding OpenCL, I'm finding that GPU OpenCL is faster for me than CPU. For the purposes of these benchmarks it might be better to disable OpenCL or to make sure it's running on the CPU to take the video cards out of the equation.
  12. Is AMD potentially risky? (Threadripper)

    Thank you, I will run them later although I don't suspect the results will be much different from yours. Not sure about OpenCL either, I didn't see any load on the GPU with GPU-Z when I was testing some FLIP stuff (OpenCL enabled on the solver). Here is the boolean sphere scene in case anyone else has trouble accessing it: https://drive.google.com/open?id=0B0BbxninBS49aEVYa21TR3JYclU
  13. Is AMD potentially risky? (Threadripper)

    I don't think IPC has changed much in the last few generations, so the 5820k should still perform great in single-threaded ops compared to processors with tons of cores that are clocked lower. @Beatnutz, are you able to upload the hip files somewhere else? I'd like to give it a whirl but the forum is telling me I don't have access to them for some reason.
  14. Is AMD potentially risky? (Threadripper)

    EDIT - Link to the boolean sphere file, in case anyone has trouble downloading the attachment: https://drive.google.com/open?id=0B0BbxninBS49aEVYa21TR3JYclU ----------------------------------------------------- Hi Marty, I don't know if you have anything specific in mind but here's a quick scene I threw together that renders a short 45-frame sequence. A dense poly sphere that gets booleaned, converted to VDB, back to polys and rendered via Mantra. Open a Render Scheduler tab if you don't have one open and hit "Render to Disk in Background" in the Mantra ROP. The work is split roughly 30/70 between SOP cooking and rendering. This machine completed the sequence in 15min 53sec (1950x @ 3.75GHz, Memory @ 3200MHz). Curious what you get on your machine, and also feel free to share any scenes you want me to run. booleanSphere.hip
  15. Is AMD potentially risky? (Threadripper)

    I believe Core Performance Boost can dynamically apply a minor overclock across all cores and boost four cores up to 4.2GHz (In AMD lingo: "Precision Boost" and "XFR" respectively). Somebody more knowledgeable please correct me if I'm wrong. Couple of Cinebench numbers: CPB on: 2961 CPB off: 2938 Pretty minor dip but that's probably not representative of more single-threaded applications, where that 4.2GHz boost would be more helpful. If you overclock the processor it looks like CPB is disabled regardless. At the moment I have it overclocked to 3.75GHz across all cores (3199 in Cinebench).