Jump to content

malexander

Members
  • Content count

    805
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

  • Days Won

    41

malexander last won the day on June 19

malexander had the most liked content!

Community Reputation

339 Excellent

1 Follower

About malexander

  • Rank
    Houdini Master
  • Birthday 03/06/1974

Contact Methods

  • Website URL
    sidefx.com

Personal Information

  • Name
    Mark Alexander
  1. Houdini 17 Wishlist

    Nvidia's Optix library is probably the most accessible way to get at those new RT cores from a non-GPU renderer. CUDA targets the existing shader cores, though I suspect there's probably a CUDA lib which handles dispatching to the RT cores (there is one such lib for dispatching to the Tensor cores).
  2. Ah, the days when a $5000 Quadro 6000 seemed like a lot...
  3. New Threadripper 2 - Core Speed vs Core Count

    I'm not saying the 2990WX is bad, just that you should temper your expectations of a 32x speedup in rendering
  4. New Threadripper 2 - Core Speed vs Core Count

    The 24/32 core parts are odd beasts. They're made of four 8 core modules (24 core has 2 cores disable per module). Unlike the server Epyc processor, only 2 of those modules have access to main memory (each have access to half of it via dual memory controllers), and the other two modules must hop through one of the mem-attached modules to get at main memory. So they'll scale well for low-bandwidth, high-compute workloads (rendering), but start to suffer in cases where memory bandwidth is important (massive sims). The 16 core part has 2 modules and each has access to half the memory. AMD's designed the scheduling such that the modules connected to memory are populated with threads first, then the mem-isolated modules. I'm curious how that works for SMT (fill 16 threads on the mem modules, then 16 threads on the other modules, then populate the 33rd+ thread on the loaded cores; or load up the mem-modules to 32 threads first). I'd be more tempted to go for the 16 core version (2950X) myself. Thread efficiency starts to drop off at high core counts as well, so you really don't want to be losing even more performance in your top 16 cores. The memory bandwidth issue would also make me think twice about launching multiple processes using a lower thread count too. Pretty in-depth analysis here: https://www.anandtech.com/show/13124/the-amd-threadripper-2990wx-and-2950x-review
  5. Multithreading

    Probably, since most modern CPUs use a higher boost frequency when only 1-2 threads are running. That being said, even the viewport display has highly multithreaded parts in it (generating normals, transfering data, convexing, etc).
  6. Houdini 17 Wishlist

    With the amount of ideas presented in this thread, I think wishlists for Houdini 18, 19, 20 and 21 have already been started!
  7. What driver is the Help > About Houdini, Show Details window reporting? Is the Vendor Nvidia?
  8. Show curve thickness in viewport

    This is what the Hairgen object enables to get the ribbon effect for curves. You can also change "Display As:" to "SubD Surface/Curves" to get the smooth curves as well.
  9. Houdini 17 Wishlist

    That sounds oddly specific... And only 17 point one for a total SOP rewrite? 8-o
  10. Creating custom palette from image in COPs

    The Lookup COP is probably a good starting point. If you have a colorful noise COP input and "wander" your lookup samples around the noise image (or slowly modify your noise) you can get a source of interesting morphing random colors.
  11. New eGPU for Macs

    Apparently the GPU isn't upgradeable, which sort of defeats the purpose of a external GPU enclosure, IMO. Sort of par for the course for Apple lately though. Still waiting on that upcoming upgradeable mac pro.
  12. MOPs: Motion Graphics Operators for Houdini

    We can't do both?
  13. color prims by attribute

    The color SOP with the group set to "@P=0" and class set to Primitive is probably the easiest, though you could use a primitive wrangle if you wanted to get a bit more fancy with the condition.
  14. I would try adding a CPU temp monitoring app (might be one in the motherboard software package) to see if you temps are getting high (>80C under heavy load). If it is high before it crashes (80-90C), try reseating the heatsink. With thermal paste you only want a tiny smear - you should still be able to see the copper beneath, looking slightly greyish. Then, if the temp is okay, try testing your RAM. You might have got a bad stick. You can do this by pulling some RAM sticks and retesting, and narrow it down to the bad stick, or use memtest86 (https://www.memtest86.com/). Also, you can try changing stuff in your EFI config (formerly known as BIOS): Disable memory EMP profiles Disable any CPU boost option, or overclocking Good luck!
  15. Building a new station

    The days of bad AMD graphics drivers are over. They've been just as good as Nvidia drivers for several years now. Hard to shake that bad rep though.
×