Jump to content
[[Template core/front/profile/profileHeader is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]]

Community Reputation

0 Neutral

About gridMoth

  • Rank

Personal Information

  • Name
  • Location

Recent Profile Visitors

748 profile views
  1. Crash H17.5 w/signal 11 - Linux

    Figured it out. Needed to install the opencl nvidia driver seperately.
  2. Crash H17.5 w/signal 11 - Linux

    First off, thanks for responding. I am definitely not overclocking, and will look into the stress test and the bios adjustment. Update: Let the Prime95 test run for about 2 hours and all was clean. Feel like that is enough to be confident in the machine's stabiity. This just seems very centered around Houdini not picking up on my other cards, or being able to determine an OCL device. Doesn't seem like I'd be able to crush—literally a 5 million particle sim for over 2 minutes with it running great, and then have it crash due to lack of power for an "About Houdini" window pane, or doing a simple erosion and a basic terrain, ya know?
  3. So, I'm hoping someone can help me figure out why Houdini is crashing so much with this. This is a high end workstation with dual Xeon scalables and RTX cards. Linux is picking up all three of my cards it seems just fine, but Houdini is not. Definitely not able to connect the OCL variable, and even changing the misc.preference, as well as the .env to use CPU, it fails to change the crashing behaviour. Firstly, the biggest notice is trying to open the About Houdini pane. Fast crash. But then, certain pyro sims will seem okay, but then a wave container might crash. Haven't really dialed in all the variances because it's all likely due to the same thing. Any sort of erode in a heightfield is a crash, but if I load the crash file back up, it looks to have been at least partially sim'd, but middle clicking on the node to see the output is a crash as well. I've read a couple other threads on odforce and elsewhere about Nvidia drivers and possilby even Realtek audio drivers etc., but not sure how to disable or update the intel driver from my motherboard yet. Using Nvidia 430.26 hgpuinfo: Finds my 2080ti as GPU, but fallback on the OCL_DEVICE to CPU (which doesn't seem to really work either). I've got two RTX Titans as well in there, so I've tried setting the OCL_VENDOR to Nvidia Corp, and DEVICENUMBER to 0,1,2 respectively. Anyone else have this type of behaviour, or can give me a bit more insight based on that error output? Guessing this is likely the Nvidia driver, but really not sure. Also tried this on the 17.5.173 build. Would rolling back the Nvidia driver be beneficial perhaps?... that's my next attempt, but wanted to get this post up sooner than later. Much appreciated
  4. Xeon 3175

    Great to know, thanks
  5. Xeon 3175

    No, I get that. Thought there was some general understanding of how these releases work with tech enthusiasts. Didn't mean to presume you had insider insights or anything. Seems a bit odd to not have any info about which Xeons are going to be upgraded @4 weeks out. There was talk of that Gold 6154 in this thread, and imho it seems crazy to purchase those, if ones with Spectre and Meltdown improvements will be on the market in December.
  6. Xeon 3175

    @lukeiamyourfather Is a version of this chip expected to be launched as Cascade Lake SP with some of the vulnerability fixes, and Optane support? Or, is it the only processors listed on the wiki page set for December?
  7. Upcoming Build- future AMD vs Intel

    Wanted to get back right quick to say thanks for the replies @malexander & @lukeiamyourfather. Have a couple follow up questions myself, but will have to revisit this in a couple days. Might be able narrow my focus anyhow after marty's question.
  8. Upcoming Build- future AMD vs Intel

    Thanks for the links&nuggets @marty. Good stuff. Reading up on the compiled blocks now, and looking forward to diving into all the AVX-512 more this weekend. Will also look into the pcie lanes, but I think you may be partially right. That is another area I really want to look at is latency type stuff. Feeling pretty good about the direction I'm headed after your input. I have so many more questions that I hope you and other smart folks in the forum will help me with in the coming weeks/months. But, I've done enough pestering for one day I think. Super grateful .
  9. Upcoming Build- future AMD vs Intel

    For sure, I'm afraid Intel will drop prices the day after I purchase from them...but a win in the long run hopefully. Thanks for the reply
  10. Upcoming Build- future AMD vs Intel

    Must research this...thanksAppreciate ya taking the time to respond—truly. It's all so conflicting in many ways. My goal is to have both, GPU and CPU goodness. I have around a 10k budget that I absolutely can't afford to go wrong here. I'd like to be able to render in Arnold OR Redshift both ideally—depending on the project/time constraints etc. I sorta thought Houdini was edging closer to more ops really taking advantage of more multi-threading... I see your point with openCL and GPU moving forward. In some aspects, I want computationally heavier algorithmic stuff to become fluid in my workflow. I want RnD type stuff to get results fast and not be bogged down, yet still have most of generalized perks you speak of with single core higher clock rates. So, I won't keep buggin' ya....but to clarify, given what I've mentioned; you think it may be more beneficial going with a good i7 and loading up on GPU instead of running dual Xeons & GPU? I had planned on running dual E5-2690's, starting off with 2 1080ti's and 1 980ti... Not that I won't do my own homework, but if you have a good link or two on houdini's future dev and/or openCL etc. that you think I should read, please drop me a line. Thanks again.
  11. Upcoming Build- future AMD vs Intel

    Oh wow, not sure if I glossed over that somehow. For some reason I was under the impression that information was not out yet. I know higher core counts for server based chips typically have slower clock speeds, but that is not at all what I thought Naples was going to be. Might be okay for a headless render box one day, but...back to sticking my gut about Intel being the wise decision I suppose. If others read this and can add any useful information in general about building a machine in 2017, or can add a bit of perspective with maybe holding off for a bit for Intel to drop prices, OR perhaps if the E5-2690 v4 may not be the best choice. Please do. I could really use some sidefx opinions so to speak. The 2690 seemed to me like a good balance or trade-off with clock speeds/all core boost speed of 3.2, core count, and thermal output for the $. [using this as a partial reference] http://bit.ly/2na7Gks
  12. Okay, so let me start off by saying I know it is way too early to speak in hypothetically about this stuff... but just looking for some general knowledge/opinions for a build. For the past few months I've been targeting running dual Xeon E5-2690's. Then news of Naples from AMD. Is the general consensus Intel is still going to perform better and be much more stable...say running Arch Linux for example? Those cores with presumably a friendlier price point...just curious what someone with more experience thought about this moving forward—as I'm looking to get into an expensive workstation. Like I said, I know we shouldn't really speculate, but if anyone has a bit of insight as to how Intel crunches data for simulations and whatnot, the stability/reliability for updates in firmware vs what may be attractive with all the Naples cores expected etc., I love to hear some thoughts on the architectures running Houdini, and overall workstations. Much appreciated, and apologies if this isn't in the right thread.
  13. Houdini Master Sluggish/Python Error

    Yeah, thanks Atom (I really like your work). I mean, I always have the web version open, but I'd still like to figure this out as it can be very convenient while working with a deadline. Being a local connection, I'd think it'd be blazing fast. Also, considering sidefx just re-designed the help layout and structure in H15.5, I highly doubt it's intended to be this sluggish and throwing errors.
  14. Hey guys, so my Houdini help is super slow at times, others not. I've set my PYTHON_LIB path to my homebrew install of /usr/local/Cellar/python/2.7.11/bin/python Setting the path to that of Homebrew version seemed to work at first as Houdini was tossing up errors in confusion with the system Python(I believe). Now I keep getting this broken pipe with the Socket Server: Attached... This is what happens on launch of the Help: May 23 16:17:07 rP-macPro.local houdinifx[50735] <Warning>: void CGSUpdateManager::log() const: conn 0x4b3ff: spurious update. Do I also need to set other env variables such as PYTHON_BIN? etc.? If anyone can help me resolve this, I'd be super appreciative... Screen Shot 2016-05-22 at 3.50.43 AM.tiff