Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Badges

First Anniversary500 Comments100 CommentsName Dropper10 CommentsPhotogenicFirst Comment

malbrecht ✭✭✭

About

Username
malbrecht
Joined
Visits
3,367
Last Active
Roles
Fabric for Houdini
Points
204
Posts
752
Badges
7
  • Fabric Engine and RealityCapture

    Moin,

    I came across this article - interesting, because I am currently using FE to do some photogrammetry tests myself! :)

    https://www.capturingreality.com/Article-RealityCapture-And-Fabric-Engine

    Video:

    Marc

  • Re: Installation?

    Moin,

    @th_designs : Sounds like you are addressing two different issues there. Windows10 for sure is fully capable of running Canvas and/or Fabric.
    For canvas to run properly, the environment variables have to be set up correctly, which you can get by executing environment.bat before starting canvas.py.
    There should be a "canvas.bat" batch file that does just that: Call environment.bat, then start canvas through Python.

    As for the license code - when in doubt, do write to support, they are usually very quick and get you sorted out!

    Marc

  • Re: WIP: Fluid-O-Matic - question(s)

    V2 is in the works. I have rewritten almost everything to be more modular, stackable and, if needed, noodleble. Meaning: You can use a one-node-does-it-all function (the "Solver" node), but instead you can create your own simulation now, having access to advection, diffusion, reprojection and the fields.
    There's still some debugging to do, obviously, but I think this is looking neat enough already to show off here:

    The Solver only needs a timeline input. You can simply tick "reset on zero", so you don't have to setup a reset-function or a variable yourself, it's all being taken care of already. The Solver also outputs a reset signal, so you can chain in your own reset-features simply by hooking up to the reset-out.
    The solver can be disabled, allowing you to play with the static fields without any calculations being done, speeding up experiment setups.
    Calculations are only done when the timeline actually changes. If the timeline does not change, the solver returns immediately.

    The "creative functions" are those that you will actually want to use. Both density-injector and velocity-injector allow for sub-blocks, meaning: You could just voxelize a teapot, ignoring the actual size of the simulation, and blob the voxel field into the simulation. Same goes for velocities.
    The "fill velocity" function has a randomizer, so you can create a "natural" initial noise field.
    The "hardcore functions" can be re-used to add heat fields or e.g. dampen down velocities, whatever.

    I hope to get it working this week and, maybe, find someone who's interested in playing along ... my goal obviously is to publish this thingy for general use ...

    Marc

  • Re: Feed Forward Neural Networks

    Thanks so much for sharing your learning progress!

    Marc

  • Re: Hybride Technologies: The Visual Effects of Warcraft - Creating the Horde

    Wow, thanks for this insight into the pain of production pipelines! I love seeing problems solved.

    And wow ... I really did not know that the Dollar allows for overrides! (Quote from EricT: "Similarities to what USD offers where you can apply overrides.")

    Marc