Jump to content

Fireandsmoke

Members
  • Content count

    68
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

Community Reputation

3 Neutral

About Fireandsmoke

  • Rank
    Peon

Personal Information

  • Name
    JHeks
  • Location
    Sydney, Australia
  1. Hi. I have an interesting problem I've been trying to solve for the last few days but still haven't managed to find a good solution. I have a sequence of geo which has been captured with a depth sensor. One of the issues with the sequence is that the point numbers change positions every frame. Whilst there is a rough order to the point numbering per frame, its not very consistent. I'm wondering if there would be a way to homogenise the layout of the point numbers by reordering, or to somehow re-mesh the geometry sequence to create a new version with more of an ordered structure? I've attached a short bgeo sequence as a sample if anybody would be interested in having a look. Thanks for any advice VolumetricTest.rar
  2. Script to resume crashed render

    Thanks for everybodys input. Ive ended up going with the free version of Royal Render, and it has been relatively easy and effective to setup on a single machine, and I have very minimal networking skills. For whatever reason, I was finding that the rrSerivce was not resuming my renders on a system restart, so I placed the win__rrClient.bat into the Windows startup directory to force it to start.
  3. Script to resume crashed render

    Thanks. Do you know if the free version of Deadline has this functionality?
  4. It's quite common that Ill set off a render at night only to find out in the morning that it has crashed at some point a short way through. Generally, if I simply restart houdini and render from where it got up to, it will continue without problem. Not sure why this happens, but it does mean over night renders are often a gamble. What I'm wondering is, would it be possible to have some kind of script which detects a crash, reboots houdini with the working project and takes off from the last rendered frame? Would such an idea even be possible?
  5. Convert tris to quads

    As a side note to this which may help someone in the future: if youre wanting to render a wireframe quad look (which is what I was after), using Redshift selecting Rendering an object as Strands will automatically render the wire frame as quads.
  6. Convert tris to quads

    Cool, thanks for the help
  7. Convert tris to quads

    Hi, Im wanting to render a wireframe look of a scan captured asset, but Id prefer to lose all the diagonals and have it in quads.. is there a simple way to convert tris to quads in Houdini 17.5, I cant seem to find it? Thanks
  8. Redshift Proxy Workflow in Houdini

    So does that make the above instruction now irrelevant?
  9. Flickering colours in slow Coloured Smoke

    Ha..! I will have more of a look tonight as well. Very easy to replicate the problem, just lay down a coloured smoke (via shelf), and gas upres it (also via shelf). Youll see straight away that the upres smoke is black. -J
  10. Flickering colours in slow Coloured Smoke

    Thanks Jesper. Nice try but no cigar unfortunately!
  11. Flickering colours in slow Coloured Smoke

    Well Ive worked out where the problem was coming from, but damned if I know why.. maybe its a bug. For Redshift to render coloured smoke, you have to convert the volume to a VDB (among other things). And basically I'm getting the error if I cache out to VDB and then load the VDB back in and render. If I cache to Bgeo, and then do a the conversion to VDB at render time, no problems. Iv'e been playing all even with the GasUpRes... I LOVE it! It's the first tool I've used in Houdini that makes timescaling a sim do what I want, I wish I'd looked into it ages ago. One question I have, which maybe by chance you can answer... I'm trying to use Gas UpRes with the Colored Smoke shelf tool. but the color is not transferring to the upressed volume. The volumes are created but the Cd values are black. I found a hacky way to use Volume Mix to mix back in a frame with colour from the low res smoke, but I'm wondering if there's a better fix...?
  12. Flickering colours in slow Coloured Smoke

    Will do! It currently imports a reasonably heavy vdb and requires redshift, but the sim is still in there so you can see the settings I used. Thanks Jesper, much appreciated. Ill start looking into Gas Upres and substeps tonight.
  13. Flickering colours in slow Coloured Smoke

    Its at home so I can't double check but 95% sure it was temp
  14. Flickering colours in slow Coloured Smoke

    Ah ok, excellent. I will have a look at that, thanks. When you say cache out subframes, does this have to be done as a .sim, or can you cache subframes into .bgeo or .vdb? My understanding was that a large purpose of the Retime was to avoid having to do all this, relying instead on the method of interpolation (aided by advection), so I'm still curious as to why I'm getting such severe errors (basically its jumping back to some kind of rest state at 5 frame intervals (retiming at a 0.2 speed)). Not to hijack my own thread, but whilst a Retime approach may work, I'm still also curious as to why my original problem is occuring with the flickering color, if anybody has a theory about that...?
  15. Flickering colours in slow Coloured Smoke

    Well I would have thought so, but I've been having plenty of issues with the new Retime node.. I posted about it on sidefx forum but nobody has replied, I keep getting very jittery results such as this: https://giphy.com/gifs/69EhNTJHxxpfE6vHU8 My post is here: https://www.sidefx.com/forum/topic/59932/ One thing I have not been doing though is adding extra substeps to my initial sim. Is that a requirement for a velocity advected retime? And is so is there a relationship between the number of substeps required and the desired retimed speed? Any advice would be helpful, I haven't been getting very good results so far!
×