Jump to content


  • Content count

  • Donations

    0.00 CAD 
  • Joined

  • Last visited

  • Days Won


DaJuice last won the day on April 29 2020

DaJuice had the most liked content!

Community Reputation

51 Excellent

1 Follower

About DaJuice

  • Rank
    Houdini Master
  • Birthday 03/01/1982

Personal Information

  • Name
    Siavash Tehrani
  1. dealing with open geometry

    Have you tried the Convex Decomposition SOP? It can close up holes, at the cost of sacrificing some of the original shape if you push too hard on Max Concavity.
  2. address behind the hip Project

    If you're in one of the Shot_* folders, ../abc will get you there.
  3. importing abc files

    By default the geometry is coming in as Alembic Delayed Load Primitives. Take a look at the "Load As" drop-down menu on either the File > Import > Alembic Scene dialog or the Alembic SOP. You can choose to unpack the geometry there.
  4. Subdivision render artifact

    The star-shaped subdivision is the expected result with your topology. To get rid of the visible shading "artifacts", select the large ngon in the center, append a PolyExtrude SOP and increase the Inset parameter a little bit. Increase the divisions to 2 as well. That will provide a sort of anchor where the sides meets the face and still give you rounding along those edge.
  5. New Color Schemes

    Hi @davidyannick The lines you'll want to tweak are: PRESSED_HIGH PRESSED_LOW SELECTION_BASE MenuSelectedBG
  6. ACES Rendering output

    In COPs you can use the OCIO Transform VOP inside a VOP COP2 Filter to convert images from ACEScg to srgb or rec709. The DMNK tools also provide a couple of convenient HDAs to streamline that: https://github.com/DominikLingenover/DMNK-Tools As far as external tools, PYCO is very nice: https://mrlixm.github.io/PYCO/standalone/ColorspaceConvert/home/
  7. I would guess the AMD system will be faster at everything, single-threaded and multi-threaded. The Xeons are probably somewhere in the neighborhood of 2.2-2.5GHz base and 3GHz boost, versus the 16-core TR CPUs which can be overclocked to around 4GHz all-core with adequate cooling. And that's setting aside architectural/generational differences and just looking at clock speeds. Also you can use ECC RAM with Threadripper (look at Unbuffered UDIMMs).
  8. It's possible that Pixar will implement their own output LOP (I believe RS and 3Delight already plan to) but for now I think you have to use a USD Render ROP LOP in conjunction with the Render Settings LOP.
  9. Redshift Render Settings Slow?

    Have you tried the automatic sampling in 3.0? You can enable it in the System tab.
  10. LOP's/USD workflow worth it?

    I think a lot of the shortcomings of Solaris at this stage are really more about the current state of USD. If you subscribe to the USD Google group you get an idea of just how much things are in flux on the rendering side.
  11. I don't believe those numbers in the TR specs are hard limits, more like what AMD will guarantee works with appropriately fast memory. For example the "System Memory Specification" for 1st gen was only 2667MHz, but I had no trouble running the HyperX kit (not the same as you linked) at the rated 3200MHz just using the XMP profiles. I did some comparisons of different memory speeds with Cinebench renders when I first built the system, but nothing comprehensive and nothing with Houdini sims. Those kinds of benchmark will probably be hard to come by. It did make a little bit of difference in Cinebench and I think that was comparing the stock 2400MHz speed vs the 3200MHz overclock. I feel like the difference for Houdini sims will be pretty negligible if we're talking 2666 vs 2933.
  12. Yup, that's the one. MSI hasn't bothered updating the specs (nor the BIOS in quite a while), but they have continued to expand the QVL at least. At the time 16GB DIMMs were the largest size available for mainstream and HEDT platforms. Now that has been bumped to 32GB, allowing for 256GB on motherboards with 8 DIMM slots, though I couldn't tell you for sure that all TR mobos support it. According to this forum post, the Taichi does: http://forum.asrock.com/forum_posts.asp?TID=12298&title=256gb-ram-on-x399-professional-gaming-motherboard As for use cases, when we were doing solves with Maya/PhoenixFD, heavier pyro and fluid sims often had to be scaled back because they would eventually creep past 128GB. I'd like to get into more sim stuff in Houdini for learning/personal projects and didn't want to run into that. Hope that helps
  13. I'm using this now: https://www.corsair.com/us/en/Categories/Products/Memory/VENGEANCE-LPX/p/CMK256GX4M8A2666C16 I chose it because... well, it was the only 256GB kit on my motherboard's QVL (MSI X399 Pro Carbon something something). 1st gen TR can be picky with memory and I didn't want to take chances with a non-QVL kit. I've only had it a couple of weeks ago but performance-wise it seems to be doing it's job. The HyperX ran at 3200MHz vs 2666MHz on this set, but in day-to-day tasks I can't tell a difference by feel alone.
  14. Are they both on the QVL for the Taichi? Assuming the HyperX kit is on the QVL it should be fine, and I don't feel like the tighter timings on the other RAM will make a big enough difference to justify the price. For what it's worth, before upgrading to a larger kit I had a 32GB HyperX kit in my 1st gen TR system and it worked without issues (although it was Hynix rather than Samsung b-die).
  15. Studio Workstation

    What Atom said, that amount of memory is inadequate for a workstation nowadays. Everything else looks okay,