Jump to content

LucaScheller

Members
  • Content count

    10
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

Community Reputation

9 Neutral

About LucaScheller

  • Rank
    Peon

Contact Methods

  • Website URL
    www.lucascheller.de

Personal Information

  • Name
    LucaScheller
  • Location
    Munich

Recent Profile Visitors

221 profile views
  1. LYNX | Free & OpenSource VFX Pipeline Tools

    Hi everyone, The official v1.0 Release is now online! Available to download for free here: https://github.com/LucaScheller/VFX-LYNX Main features and improvements since the initial release are: - All Houdini Assets now have complete Houdini native documentation available. - Demo Files from the demos and tutorial videos are also on GitHub to get your started quickly - Bug fixes, performance improvements and improved UX LYNX_force_general: Pin the transform to any polygon geometry or slide it along a curve. New gradient force let's your sim flow along the gradient of your geometry. Noise now supports all noise types, curl noise sdf influence and "noise as strength". "Hide on Playback" support for guides Full support for curves with helpful visualizers. LYNX_fabric: LYNX_fabric_color let’s you tweak your Cd/Alpha/width attributes in a layered based fashion Support for custom normals and the scale attribute across all nodes. Improved performance and UX experience with useful presets. LYNX_velocity: You can now set the attribute to manipulate to be a custom one Visualizers are now handled by the .hda to handle custom attribute support Full release logs are available on GitHub and on my website Enjoy! Can't wait to hear your feedback! Here are the updates covered in two videos:
  2. LYNX | Free & OpenSource VFX Pipeline Tools

    Hey guys, just a quick update on the tools: All Houdini Assets now have complete Houdini native documentation available. LYNX_fabric has a new LYNX_fabric_color node to control the color/Alpha/width attributes in a layered based fashion. LYNX_fabric_resample (LYNX_fabric_thread uses this heavily) is up to 5 times faster & LYNX_fabric_weave up to 2 times Full install instructions are now available on GitHub . The download is now also only via Github and not via my website anymore. Various bug fixes & performance improvements on LYNX_force_general, LYNX_fabric, LYNX_velocity.
  3. Hey Filip, it's possible via this expression: `ch("number_"+substr($CH,rindex($CH,"_")+1,1000000))` In order for this to work you have to name you parameter "label_#". The expression slices the string based on the last "_". That way you get the current index with which you can look up other parameters. See the attached file for more info Cheers, -Luca parameter_current_index.hip
  4. LYNX | Free & OpenSource VFX Pipeline Tools

    Thanks guys:) There have been quite a few improvements since the HUG Munich Presentation. Be sure to get the latest version (see the github repository for the latest updates, just fixed a bug in the force field a couple of minutes ago ) Let me know if you have any questions / problems, documentation is currently wip, should be coming soon
  5. Hey folks, proud to present LYNX Tools, a collection of production proven open source tools to accelerate your workflows! All mentioned tools are free to download via the links below and are licensed with a full HoudiniFX license. All Houdini Assets have complete Houdini native documentation available. Repository: https://github.com/LucaScheller/VFX-LYNX Lastest stable release: https://github.com/LucaScheller/VFX-LYNX/releases Please give them a test drive, so we can improve them further Roadmap | https://trello.com/b/f8Pgip7s/lynxpipeline So far there are three tools: LYNX_force_general | Tweak your sims with this all purpose & intuitive force field. Built to mimic force fields in other DCC applications, but with support for more features and a natural Houdini user experience. https://www.lucascheller.de/vfx/2019/03/24/vfx-lynx-houdini-force-general-asset/ LYNX_fabric | Create fabric/weave patterns with ease. Perfect for creating that holiday sweater you never wanted. https://www.lucascheller.de/vfx/2019/03/16/vfx-lynx-houdini-fabric-asset/ LYNX_velocity | Get control of your velocities via an intuitive UI or groom them for absolute fine tuned control. https://www.lucascheller.de/vfx/2018/11/01/vfx-lynx-houdini-velocity-asset/ More info on my website, including full release logs: https://www.lucascheller.de/blog/ Houdini User Group Munich Presentation: https://vimeo.com/334887452
  6. Mantra Light Path Expressions(LPE) Exclude Coat

    Mh doesn't seem to work in Mantra. I've also tried RenderMan lpe:CD[S]+<L.> --> Mantra lpe:CD[G]+<L.> as described here. Also doesn't seem to work. I guess it's because caustics are not part of the path tracing process? So we can't access them via lpe? "Soft caustics" (enabling "Allowable paths" on your mantra node) works with lpe:C<RD>G+L or lpe:CD[G]+<L.> though, since it is then path traced. Or is there a custom lpe type we can access for caustics?
  7. Mantra Light Path Expressions(LPE) Exclude Coat

    Is it possible to have a lpe for caustics only?
  8. Mantra Light Path Expressions(LPE) Exclude Coat

    Ah I understand the syntax now. Works like a charm Thanks
  9. Hi guys, I'm trying to write a light path expression that excludes the default custom bsdf label "coat" To have only the coat layer is: lpe:C<...'coat'>.* To have all reflections but the coat I would expect it to be: lpe:C<RG[^...'coat']>.* This gives a syntax error and doesn't seem to work. Has anyone tried this before and knows the correct syntax or is this a bug? Cheers, Luca
  10. Hi, I am currently trying to use mantra in distributed rendering mode. (mantra -H machine1,machine2) It all works as expected, but as soon as I connect something into a cached shader (for example a constant into the principled shader), the error “No Code Generator Available for opshader_path_xyz” pops up and it doesn't render at all anymore. It also happens with custom cached shader assets. All works well in non distributed rendering mode. If I unlock the asset, then it seems to work again since the asset is then "in the file", but this is unfortunately not useful in production. Additional Info: I am using windows and the “Force VEX Shader Embedding” checkbox is on. Has anyone experienced this error before? If no I'll submit a bug report. Cheers, Luca
×