Texture

Texture Patch

Release: Texture, v0.5

Release Type: Production
Version: 0.5
Release Notes

This is an update to the Texture Plugin for Leopard. Procedural texture generation courtesy of the libnoise project.

Texture Patch This version is functionally identical to the 0.4 release, except that it runs on Leopard only.

Release: Texture, v20071110

Release Type: Beta
Version: 20071110
Release Notes

More cleanups. Now runs under 64-bit Leopard runtime. Fixed the TexturePort so it no longer needs a category on QCPatch. Working on a progressive or multithreaded texture renderer (nothing stable yet, so it's not in this build).

Release: Texture, v20071031

Release Type: Beta
Version: 20071031
Release Notes

Texture Patch v0.5 for Leopard. Updates include:

  • Small memory leak fixed.
  • Editor namespace changes
  • Registration guard
  • Works on leopard :)

This version doesn't work on Tiger (or, at least, it shouldn't) due to some leopard-specific calls. I'll try to isolate these to make a 10.4/10.5 build before final release.

Release: Texture, v0.4

Release Type: Production
Version: 0.4
Release Notes

Texture Patch

This is the first public release of our "Texture" patch --- a set of 26 patches for procedural texture generation, using techniques derived from Perlin Noise.

This is pretty much a 1-to-1 translation of the excellent libnoise project, so the standard libnoise documentation applies verbatim.

Unlike other patches, this patch is LGPL consequent to libnoise being LGPL.

Known issues:

  • module::Curve and module::Terrace haven't yet been translated as they require some additional interface elements not currently present in Quartz Composer.
  • The new "KinemeTexture" QCPort type doesn't properly handle cable removal --- so the Texture port is left hanging with a stale object. If you try to save the composition while a Texture port is disconnected, QC will throw the following exception:
    -[KinemeTexturePort stateValue]: Function not implemented
    (This exception isn't the problem itself, just a side-effect. Any ideas about how we can catch the cable removal action?) When this happens, don't panic --- you should be able to recover from the exception, attach a cable, and save the composition properly.

[ More info on this patch ]