lukeiamyourfather

The team I work with has an opening. Feel free to ask questions and I'll do my best to answer. https://www.lockheedmartinjobs.com/job/grand-prairie/vfx-generalist/694/63473512848 Some of the projects we've done in the last few years are linked below. Most of the work isn't public but it's challenging and rewarding work.

That has nothing to do with the memory or stability. If anything you're better off with ECC memory which Intel doesn't support on consumer platforms but AMD does (including the Ryzen 3900X you already have). Intel doesn't have a magic wand to make sketchy memory more stable. I've had bad DDR4 memory module that memory tests never found an issue with. If you have more than one DIMM then I would try working with only one of them for a day, or half of them for a day, until you can narrow down which one is crashing. It could be the processor or motherboard but the memory modules are more likely candidates. If you end up needing to buy more memory out of warranty you might consider ECC memory this time around. While a bad DIMM is a bad DIMM that needs to be replaced at least you'd get warnings and logs of corrected memory errors instead of hard crashes.

Try increasing stochastic samples (by a lot).

This. It can be faster if the synchronization between the slices doesn't take longer than the single threaded parts would take on their own. Doing this doesn't turn 64GB of RAM into 512GB of RAM. All of the slices still need to be running concurrently so they can be synchronized after each timestep. If anything it would use even more RAM running a distributed simulation on one machine compared to a single simulation. Here's some cool reading if this stuff is interesting to you. https://en.wikipedia.org/wiki/Amdahl's_law

There's an option on the Table Import node to convert latitude and longitude to position on a sphere. Table Import (sidefx.com) The math can be done elsewhere if you want but that node makes it pretty easy.

Login at their website, click on your profile in the top right, services, manage your licenses. It'll be on the top right.

You should use the render in background button on the ROP. The percentage for a single frame will show up in the render scheduler dialog (which it should prompt to open when creating a background task). The scheduler is also available from the render menu at the top.

The team I work with is looking for a compositor and Houdini experience is a plus. It's a small team and our primary 3D application is Houdini. The position requires US citizenship. Multimedia Design Engineer (Grand Prairie, Texas) at Lockheed Martin Corporation (lockheedmartinjobs.com) If it's a good fit check it out. If not, I hope your search goes good. There's a lot of great places in Texas!

The team I work with is looking to add someone to the team in Suffolk, VA. We use Houdini as our primary 3D application along with a mix of other stuff. It's a generalist type position with opportunities to grow in areas of interest to the candidate. I'm not the hiring manager but I'm happy to answer questions. The job listing is linked below. https://www.lockheedmartinjobs.com/job/suffolk/engineering-visualization-engineer-3d-generalist/694/9209867248 This is the facility where the new team member would be working. The job would be on site. There's team members at a few locations that work together on projects. https://www.lockheedmartin.com/en-us/capabilities/research-labs/center-for-innovation.html This video is representative of the kind of work the team does. We tell engineering stories like how something works, how something is made, how something is different, etc. Unfortunately most of the work isn't public, hence the pretty old video link, but what we're doing is pretty cool stuff! https://www.youtube.com/watch?v=h449oIjg2kY We might have another video that we can share with the public soon. If that's the case I'll share it here when it's online.

It's likely that some of the code can't be executed in parallel. Lots of things will affect this in Houdini like the type of objects, size, and complexity of the simulations. In theory you want a single core CPU with unlimited frequency. In reality it's not that simple. https://en.wikipedia.org/wiki/Amdahl's_law

Arch will occasionally break. I personally wouldn't use Arch for VFX and animation production. The benefits of Arch aren't relevant to production. Those are from their wiki. https://wiki.archlinux.org/index.php/System_maintenance#Upgrading_the_system

It would be easier/faster/cheaper to get more computers to distribute the workload or get one computer that's better. I realize money isn't infinite but neither is time to kludge stuff. You can get a used workstation with 24 cores and 256 GB of memory for less than $2,000. https://www.theserverstore.com/dell-precision-t7810.html A machine like that would be plenty of power to learn with and create some impressive demo material. There are lots of other options but my point is to address the hardware problem if there's a hardware problem rather than looking for other less efficient ways to solve the problem.

Looking at your previous posts, I would say it's your questions rather than the topics that are leading to no replies. In my opinion your time would be best spent on tutorials and checking out the documentation to get a better handle on the fundamentals of Houdini. That would enable you to ask better questions that would be more helpful to you and more efficient use of time for everyone else. In general I wouldn't start the process of learning Houdini via complex topics like FLIP simulations and dynamics. https://www.sidefx.com/learn/getting_started/ Master the basics and then everything else will be much easier. The beginner stuff might seem boring but it's essential to understanding the more complex topics.

I would try the Ubuntu forums since the issue doesn't involve Houdini at all. https://ubuntuforums.org/

If you're using Maya then you're limited to RHEL 7 or CentOS 7 for now. They're not great... https://knowledge.autodesk.com/support/maya/learn-explore/caas/sfdcarticles/sfdcarticles/System-requirements-for-Autodesk-Maya-2020.html There are ways to install it on other distributions but if you're new to Linux, I don't recommend going down that road as an introduction to Linux. If you drop Maya from that list then you have a lot more options like Ubuntu and any Ubuntu derivatives like Linux Mint. I would go with Ubuntu 18.04 LTS or 20.04 LTS assuming there's no Maya.