Jump to content


  • Content count

  • Donations

    0.00 CAD 
  • Joined

  • Last visited

  • Days Won


Posts posted by schwungsau

  1. On 5/23/2016 at 6:04 PM, Jero3d said:

    Awesome stuff Heribert! It's really motivating to see your work! I started watching the video you posted, it's great to learn how to do fractals. Here is my first attempt, doing the koch snowflake. I'm leaving the hip file in case anyone is interested(Also feedback on my system and how to improve it is very welcome!) :)


    nice, never trired the snowflakes in houdini
    anyway.... this video explains the impact of mandelbrot on cgi


  2. 11 hours ago, ciliath said:

    Sweeeeeeeet!!! Really beautiful.

    Could you give some hindsight of how you produce these fractals?

    some much so explain. fractals --> you start with simpler GEO like curve or cube, copy and translate it randomly a little and repeat this setup over and over again. After you messaure length of splines, calculate density with point clouds and mix together with to ramp colours for multiply it with extrude Parameters etc...
    this is a good Talk, how basic fractals works :


    • Like 3

  3. hi,


    it depends on the render engine you choose.


    If you are comparing a brute force path tracer to irradiance cache then Vray and modo will always be faster, but they take longer to setup to get rid of the splotches. But, I think any path tracer will be slow in interior rendering.  In corona always use Path tracing and HD cache when rendering interior. 


    Take a look at the images I have attached it will give you a really good idea of the difference between pure path tracing and combining it with something like light cache in Vray or HD Cache in corona.


    However the interesting thing in the images is that vray brute force is a lot noiser than corona path tracing with same number of gi bounces in a 5 min render.


    I also recently rendered some particle and fur tests with corona on my machine  - i7 920  roughly 4-5 mins per frame at 720p only path tracing. They are a little noisy but it's a good example of what corona can be capable of once it properly supports particles and fur. 






    as user --> it does matter. what technics are used. important is speed, quality and easy setup..... even if it written blitzbasic.... there so many pathtracer outside there most of them in alpha or beta. most a lack of important feature. so far furryball is only one, which can be called "production" ready. look each student writes he own tracer engine. lets see which ones turns out as "useful".


    so far i like furryball, octane and blender's cycles. cycles is less realistic but really nice look. waiting for sombody make houdini integration for cycles.... :D

  4. retiming fluids is always complicated. speeding fluids up is much more easier. for slowing you need complex calculation to get proper "inbetween" frames.

    slowing down just with simple linear interpolation--> you will get stepping / wired motion.

    in one of my last production we had 2 different method/tools for slowing fluids down. its takes extra calucation time, it was always limited and/or losing a lot of resolution.