Skip to content

ImageEngine/qLib

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

qLib

A procedural asset library for SideFX Houdini.

Download the dev branch (the very-latest) here: https://github.com/qLab/qLib/archive/dev.zip

About

qLib is a digital asset library for SideFX's Houdini. It is a collection of tools designed to work flawlessly with each other and Houdini's native toolset. It is driven by (and used in) real production environments, but at the same time it fully respects and conforms to all the important Houdini concepts.

Strong emphasis on the following things:

  • Backwards-compatibility: old scenes will not break over time
  • Performance: we press for VEX/multithreading as much as possible
  • Usability: our tools avoid the "in-house" look-and-feel

qLib is open source software licensed under the New BSD license. It's developed by VFX professionals from several studios working on feature films, game cinematics and commercials.

Tools

  • Generation, manipulation and visualization of geometry attributes and groups
  • Boundary geometry generation and manipulation
  • A complete deformer suite, implemented through a common deformer framework
  • Reimplemented high-performance versions of certain original Houdini OPs
  • Workflow-related tools
  • A large collection of gallery items (node and subnet presets)
  • Shelf tools
  • Experimental extras

More details here: https://www.facebook.com/notes/qlib/qlib-summary-highlights/726676570699463

Quick Installation

  • Download the latest dev-branch (see link above)
  • Extract and move it into your Houdini config directory
  • Append the provided houdini.env example file to your own houdini.env

(Note that the provided env file example is for linux.)

Installation

The installation process involves two steps: getting the contents and setting up the environment for Houdini.

1. Getting the contents

You can either grab a compressed archive file (as mentioned above), or you can clone the official repository with git.

The archive way is the easiest, but using git has additional benefits, such as instant updates, easy access to older versions, other development branches, etc.

2. Adding it to the Houdini environment

For Houdini to access qLib components, the following environment variables are to be set up:

  • HOUDINI_OTLSCAN_PATH: the assets themselves
  • HOUDINI_GALLERY_PATH: gallery items
  • HOUDINI_TOOLBAR_PATH: shelf tools
  • HOUDINI_SCRIPT_PATH: support scripts (optional)

(This is entirely optional, as by design there's almost zero dependency between qLib assets. You can experiment with assets by loading them manually, without setting up anything.)

The easiest way to do this is to put the following lines into your houdini.env file (linux):

QLIB=<<path to qLib install>>
QOTL=$QLIB/otls

# (linux)
HOUDINI_OTLSCAN_PATH = $HIH/otls:$HIH/otls/wip:$QOTL/base:$QOTL/future:$QOTL/experimental:@/otls
HOUDINI_GALLERY_PATH = $QLIB/gallery:@/gallery
HOUDINI_TOOLBAR_PATH = $QLIB/toolbar:@/toolbar
HOUDINI_SCRIPT_PATH = $QLIB/scripts:@/scripts

Note that on Windows you should use semicolons instead of colons:

QLIB=<<path to qLib install>>
QOTL=$QLIB/otls

# (windows)
HOUDINI_OTLSCAN_PATH = $HIH/otls;$HIH/otls/wip;$QOTL/base;$QOTL/future;$QOTL/experimental;@/otls
HOUDINI_GALLERY_PATH = $QLIB/gallery;@/gallery
HOUDINI_TOOLBAR_PATH = $QLIB/toolbar;@/toolbar
HOUDINI_SCRIPT_PATH = $QLIB/scripts;@/scripts

Further readings and other places of interest

qLib comes with documentation. All assets have help cards (even with example images and whatnot), providing all the related important details.

Other aspects of the library are covered in the Wiki.

We appreciate bug reports, RFEs (Request For Enhancement), or feedback of any kind. Our issue tracker is here.

If you need help, have a question or just want to keep up with the news regarding qLib, feel free to join us on our Google Groups page.

Thank you for your interest in qLib!

The qLib Team

Packages

No packages published

Languages

  • Python 94.2%
  • Shell 3.6%
  • Batchfile 2.2%