Jump to content

Thomas Helzle

  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by Thomas Helzle

  1. Too much contrast, how to tweak indirect lighting

    @AntoineSfx Check Diffuse Depth in the Mantra ROP. Great Link @Skybar. Has anybody converted those LUTs to something Houdini/Redshift can use directly? I'll have to dig deeper into this I think. :-) Thanks and cheers, Thom
  2. I don't think topology changes at all in the case of the SideFX ident, just the form. Could be a mixture of deforming noises running through the structure or other parameters being animated. Didn't look at your scene yet, but you could always project your end-result (high-resolution) back onto your first steps with a ray node and also transfer the normals from the low-res mesh, so that the rendering looks similar or the same and then morph between those projected states - simple since they have the same topology. Cheers, Tom
  3. Too much contrast, how to tweak indirect lighting

    Looks like you maybe need more GI bounces, but it's also a normal problem in reality that if your camera captures the sun on the floor and makes it look well balanced (like in your image), the room around it will be too dark. And if you balance out the room, the sun will be too bright. The human eye (= how you remember it) is much more flexible there and makes it look "good" automagically. CG != "Reality". Tonemapping can help in this situation too. Cheers, Tom
  4. 16.5 edgetransport

    Well, in this specific case I think it's easier to just enable "curveu" in the resample node and use that instead of @distance, but for more complex cases I also look forward to using this node a lot! Cheers, Tom
  5. Fabric Engine no longer being developed

    XSI was my main software for about 10 years and I actually bought Shake from the dead Apple, so I am fully aware of this. ;-) And no, I did not enjoy either. Cheers, Tom
  6. Fabric Engine no longer being developed

    I find this kind of thing really sad each time it happens. No matter if they went bust or got bought out, it always leaves a crater of frustration with everybody who was using the software before and invested time and money into it. So in the future, people will be less willing to trust a new and small company, which makes the already rather monoish-culture in the field even stronger. Especially if it would have been bought by AD, it really would be a sad day seeing another hopeful contender for a fresh approach getting sunk into that black hole. Would feel like that old carcass Maya getting another injection of fresh blood from a youth... I keep my fingers crossed that it is something at least halfways non-necromantic... ;-) And that everybody involved is well... Cheers, Tom
  7. 16.5 drums

    Good stuff! "Quick marks are now saved with the scene file." Hallelujah :-) I may even use them now... No changes to the code editor though it seems... :-( Well, there's always Houdini 17 to hope for a decent editor... Still the Nr. 1 feature I'm missing each and every minute I use Houdini... Funny how devs can be blind to something they use probably 24/7... Cheers, Tom
  8. I use the same and it works. #Redshift: PATH = "C:/ProgramData/Redshift/bin;$PATH" HOUDINI_PATH = "C:/ProgramData/Redshift/Plugins/Houdini/16.0.705;&" Check if you have the Redshift toolbar. Cheers, Tom
  9. Renderfarms renderers and plugins

    Used FoxRenderfarm a while ago: http://www.foxrenderfarm.com/ They are one of the few who support Houdini and GPU rendering with Redshift. Not Europe though - China/Shenzen No plugin for Houdini, only Max/Maya. Wrote down some of my experiences here: https://www.redshift3d.com/forums/viewthread/14391/ They are actually looking for feedback and took even my critique very positive. Cheers, Tom
  10. Houdini 16.5 Sneak Peek

    A built in code editor with tooltips for command syntax and some other things to make VEX more fun. :-)
  11. Houdini 16.5 Sneak Peek

    Looks all awesome. Let's hope the VEX editor saw some love too finally - still the biggest flaw in the whole application.... ;-) Funny to see a pretty much 1:1 copy of Lulu xXX work with the flow field , for instance: Check his other work for inspiration - great stuff! :-) "The planned released date for Houdini 16.5 is November 7, 2017." Nice, Christmas comes early this year :-) Cheers, Tom
  12. Toms "Learning Houdini" Gallery

    "Feathers" Working on building a feather-designing tool from scratch... Rendered in Redshift. Cheers, Tom
  13. Toms "Learning Houdini" Gallery

    Over the last couple of weeks I started to learn Houdini, partly from tutorials by Entagma and others, partially by implementing things I worked on in Grasshopper for Rhino (which is single threaded and rather slow for larger assets) over into the Houdini world. This one started out from the Entagma tutorial on differential growth but I then first extended it to avoid the text areas and today implemented a first version of a threading solution to make it look more like yarn: This one is similar to an older test I once did in Softimage XSI and Arnold, but this time with Houdini, exported as FBX and rendered with my favourite renderer Thea Render: And the last one for today was a study on how one can visualise noise in Houdini. It uses a solver and the trails node. I found it hard to make it look really subtle in Mantra, so in the end I created poly wires and also exported it to Thea Render via FBX: Thanks everybody on Odforce for knowledge and inspiration!!! Cheers, Tom
  14. Toms "Learning Houdini" Gallery

    "Cubicles" Same structure as above but rendered semi-opaque in Redshift: And a detail view: Cheers, Tom
  15. Toms "Learning Houdini" Gallery

    Then I thought I should take it to the third dimension and came up with a funny solution: This is about 12 divisions from a cube. My idea was, that I would pack the initial cube, check the boundingbox in primitive mode in my loop and if it contained at least one point, "subdivide" it by scaling it down by 0.5, unpack it and place one still packed downscaled cube on each point of the resulting unpacked cube with copy to points. If the cube contains no points, it would not be in the "do" group so I would not scale or unpack it and place only one packed cube at the centroid point - redundant but works compiled where a merge does not. I guess there are better algorithms out there, but I enjoyed the compact simplicity of this one. Compiled it's still rather fast, although no longer realtime as the 2D one. Cheers, Tom
  16. Toms "Learning Houdini" Gallery

    "X" Another one in the series with 16 levels: Again rendered with Redshift using rather strong DOF for the depth blur. Cheers, Tom
  17. Toms "Learning Houdini" Gallery

    Not being convinced by the approach Entagma took for their quad-tree tutorial, I changed it from using a radial distance search to a min-max evaluation in each direction, so I'd catch all the points and compiled it. While working on this I did some test images: All rendered with Redshift. Cheers, Tom
  18. Controlling Focus Distance

    Cool - have to try it with Redshift as soon as the current job is done! :-) So far I always used this in the focus distance field: // Camera focus distance to a null called focus: vlength(vtorigin(".","../focus")) But it's a bit clumsy to navigate the null. Tom
  19. Controlling Focus Distance

    Thanks symek - have to try that. I guess that will only work with Mantra, right? Cheers, Tom
  20. Controlling Focus Distance

    What I really miss is a way to click into the rendering to set the focus distance. This is very nice for quickly finding the sweet spot for stills. Love it in Thea Render etc. Is there a way to do this as a viewport action in Houdini with some raytracing from the mouse? Cheers, Tom
  21. Toms "Learning Houdini" Gallery

    "Hex Grid" An experiment with very finely detailed hexagonal geometry for deformation. All geometry, no fat ;-) Cheers, Tom
  22. Toms "Learning Houdini" Gallery

    "The Shell of Light" An exploration of extreme DOF in Redshift. The basis is a wire-shell, but rendered with massive DOF. This creates the most fascinating and somehow otherworldly structures. Art Prints here: https://fineartamerica.com/profiles/thomas-helzle.html Cheers, Tom
  23. I ended up using this (with "@class" being the per-object attribute from the connectivity node): float searchrad = chf("Searchradius"); int maxpts = chi("MaxPoints"); int nearpnts[] = nearpoints(0, @P, searchrad, maxpts); int maxlines = chi('MaxLines'); int cnt = 0; foreach(int pnt; nearpnts){ if(@class != pointattrib(0, 'class', pnt, 1)) { if (cnt >= maxlines) { break; } int line = addprim(0, "polyline"); addvertex(0, line, @ptnum); addvertex(0, line, pnt); cnt += 1; } } While this works fine, I still wonder if it wouldn't be faster to have a fitting group expression directly in nearpoints... ? Cheers, Tom
  24. I wondered the same thing recently and wrestled with the "group" parameter in nearpoints, but somehow did not grok how to write a group expression that does this. Using pcopen feels much clearer there, although one will probably still have to have a large maxpoints number to be sure to hit something on the other curves and then maybe limit the result manually in the while loop. I was searching for only one closest point on any curve different from the current, using the "class" attribute from the connectivity node... Cheers! Tom
  25. Is AMD potentially risky? (Threadripper)

    Interesting thread, thanks everybody! Reading about those 18 core TRs or new intel cpus made my mouth water initially, but what I read here doesn't exactly make me want to jump in right away. My 6 core i7 3930 from 2013 overclocked to 4.1 Ghz (costing about 500 Euro back then) with 64 GB GDR 3 RAM @1600 takes 30 minutes for the Boolean Sphere scene - not too shabby. So while you guys get almost twice the speed, that still isn't exactly as earth shattering as I would have expected. Cinebench Single Core is 139 here, so basically nothing much has changed in that department. So it's only really worthwhile for CPU rendering (I only score 1034 in Cinebench with 6 cores / 12 threads) but I use the GPU for that anyway. I think I'll wait some more with getting a new machine and let things settle down a bit regarding drivers, prices and bioses... :-) Cheers, Tom