Package for Foundry Katana software.
Proof of concept on how to integrate the OpScript workflow in a version-controled pipeline. OpScript code should not live in the scene in a studio environment, and should only import code stored in the pipeline arborescence.
This package offer tools and conventions to facilitate the integration of such workflow.
Most of the content is just linking dependencies and documenting how they work together.
Future update on this package will be to add new custom nodes I created in the opscriptlibrary.
2 Low level lua package for OpScripts:
- luakat : api to interact more easily with Katana
- luabased : because everyone needs to extend the base lua
See the katananodling package. It's a simple API to create
and register a custom type of node called "CustomNode".
We will use it to register a subclass of it called OpScriptCustomNode.
Included as an example, but also for use, is my collection of existing OpScriptCustomNode I made. Check the opscriptlibrary package.
Only have Katana and all the packages visible in this directory as dependencies.
Or see the ./doc directory.
Apache License 2.0
See LICENSE.md for full licence.
- ✅ The licensed material and derivatives may be used for commercial purposes.
- ✅ The licensed material may be distributed.
- ✅ The licensed material may be modified.
- ✅ The licensed material may be used and modified in private.
- ✅ This license provides an express grant of patent rights from contributors.
- 📏 A copy of the license and copyright notice must be included with the licensed material.
- 📏 Changes made to the licensed material must be documented
You can request a specific license by contacting me at monsieurlixm@gmail.com .
