Welcome to od|forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

Whatsinaname

Members
  • Content count

    95
  • Joined

  • Last visited

  • Days Won

    1

Community Reputation

3 Neutral

About Whatsinaname

  • Rank
    Peon

Personal Information

  • Name Ernest
  • Location Hole in Ground
  1. Telling from your description, it feels like there is something going wrong with your packed promitive workflow. Just watch the following video, as far as I remember, they are more or less exactly explaining your problem and what you can do about it:
  2. This is very good to know, Thanks a lot. It also seems like OpenCL issues are affecting Flipbooks (= Flipbook crashing) on some constellations (speaking about Xeons running Linux).
  3. I presume the machines on the farms are mostly Xeons, running on Linux.
  4. In H16.0.573 I created a terrain using Heightfields without caching the end result, as everything computed fairly quick. Unfortunately, that scene didn't seem to work on the farm due to an OpenCL issue, clCreateProgramWithSource() failed. The machines on the farm do not have graphics cards, so OpenCL won't work in this environment. Therefore I debugged my scene and it seems like some Heightfield SOPs are using OpenCL. I was too lazy to inspect the individual nodes, but it was great if it was easier to see if a certain node will try using OpenCL, as this won't work on many farms.
  5. Look inside the Dopnet, there should be a source volume node, which has a Scale Source Volume parameter. Increasing that one should do the job.
  6. Are you using stickyness? If so, try deactivating it and try again.
  7. Well, if it is working in your test scene, most certainly there is a glitch in your original scene. go through all your nodes and check how the data is changing. But without seeing that original scene of yours it is almost impossible to tell you want went wrong.
  8. Actually, Particle Seperation should be your major control regarding resolution. Radius scale can be used to so some minor changes, but I usually try to leave it as is.
  9. Justr out of interest...what do you mean by SDF liquid, can you clarify that? Signed Distance Field liquid makes no sense to me.
  10. Heya, It seems like I'm getting nuts with this one... I have a fast moving fluid and I''m trying to get some detail into the leading edges using disturbance, which simply won't work or at least not in a satisfying manner. In 99% of the cases, Disturbance kicked in at my fluid's tail, where there is little density left, moving a lot more slowly than the leading edge where i want the effect to happen. The result is low density areas being pushed too heavily resulting in beautiful streaky artefacts and no disturbance whatsoever in the leading edge. I'm applying my disturbance directly to the velocity field and first I tried using temperature as control field. In order to be doing so, I measured my max temperature, which is highest in the first frames at the fluid's leading edge, and remapped the control field to apply some really nuts amount of Disturbance to just that area. Result: Nothing. So I played with that curve, but all I came up with was the tail being disturbed and the leading edge being a boring smokepuff. Therefore, I added in a speed field, writing just the length of my velocities into it and used that in order to control Disturbance. Although it seems to be working slightly better than temperature, I still cannot grab my leading edge. It feels I'm still missing anything and don't know what it is. Maybe also worth mentioning I have a min/max substep setting inside my solver of 1/10 and additionally applied a gas repeat microsolver to the pyro solver to make the whole thingy move faster. Deactivating the Gas Repeat seems not to have any influence on Disturbance in my scene. Any ideas? EDIT: It might have something to do with the scale of my emitter. It is rather small (sphere- ish, scaled to 0.1), scaling it up to 1 works better, but my Disturbance block size is also small enough to work on a smaller smoke plume. Strange. disturbance_check_v001.hiplc
  11. Strange. I am getting these artifacts, too. But without using any disturbance (just density, vel and temperature with a tad of dissipation). It also feel like these areas are not behaving correctly, as the smoke just stays there while the rest of that smoke is getting pushed upwards by density. It was great to know what exactly is causing these streaks, not only that it happens when there is too much dissipation (which I already knew), but what is happening under the hood that is leading to those artifacts. Any ideas?
  12. I've got a simiar issue here. I was wondering if there was any more efficient way of copystamping instances as I created a scene where I've got millions of points and instanced some packed primitives onto these points. Rendering a frame is taking ages, as well as baking the instance part. My setup is slightly different than the one posted by Matt, but it basically it does more or less the same (the main difference is I am not using any alembics and I'm randomising my instances using a stamp on a switch node's input value). The thing is, it feels rather slow. Does anybody have an idea how to make it any more efficient? Here's a basic example of what I'm doing using a less complex setup: packedInstances_v01.hiplc
  13. Heya, Crating a wide ocean surface using Houdini Ocean Waves, I encountered an issue where my ocean surface is being intersected by the underlying ocean volume (see image). I was wondering what might be causing this, maybe my wave displacement is too extreme (even though it doesn't feel that strong), or is there maybe a way toimprove the overall volume sampling for the ocean volume shader in order to get rid of these issues? Thanks for any suggestions.
  14. To put it plain and simple, I'd go for a cloud solution and as soon as I got more and more jobs coming in, I might find it makes more sense to switch to my own renderfarm. Maybe get yourself one (or two if you can afford it) extra machines for flexibility reasons. Especially when starting a new business you never know how it is going to develop in the long run, so there is no point in investing into a farm you probably do not need. You can buy your own machines as soon as your business makes enough money you actually can afford a farm. As long as you cannot, a cloud makes more sense to me.
  15. Simple setup: I wanted to create a color gradient on a grid inside a PointVOP. In order to do so I fed P into a length operator and plugged that into a fit and finally into Cd. Result: Gradient around origin, as length gets larger the further away P in question is from that origin. Now, I wanted to have the same gradient but coming from an arbitrary point. So I created a sphere (primitive, so It has only got one point), moved it slightly in X and plugged it into the PointVOP's second input. To get the distance from P to that sphere's P, I created an Import Point Attribute fed and OpInput2 into its file input, set it to vector and attribute to P. The I subtracted this (sphere) P from the original (grid) P, to get the distance and then plugged that into length in order to colour the grid relative to the (sphere) P. As a result I get the very same gradient around the origin as I had in the first example, which made me think P (sphere) is somehow interpreted as being 0,0,0 so I am wondering what I'm missing. color_length.hipnc