This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
private:framed2017:introduction [2017/06/19 12:48] – created lightwolf | framed2018:introduction [2017/12/27 10:40] (current) – ↷ Links adapted because of a move operation lightwolf | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Introduction ====== | ====== Introduction ====== | ||
- | frameD is a plugin for LightWave3D to create, load and manage image sequences defined by text files. ((Gratuitous footnote. We'll try to make the following ones more informative. ;) )) | + | frameD is a plugin for LightWave3D to create, load and manage image sequences defined by text files((Gratuitous footnote. We'll try to make the following ones more informative. ;) )). |
- | The main usage scenarios are image sequences that contain duplicate images (such as mouth shapes mapped on a character' | + | The main usage scenarios are image sequences that contain duplicate images (such as mouth shapes mapped on a character' |
These text files are treated by LightWave3D as animation files. However, they point to individual images which are loaded as frames of the “virtual” animation. | These text files are treated by LightWave3D as animation files. However, they point to individual images which are loaded as frames of the “virtual” animation. | ||
- | Since the individual images are loaded through the frameD plugin, it can perform additional processing or even not load from disk at all. This is leveraged by providing the option to load proxy images (which are created automatically) and by using available memory to cache images. | + | Since the individual images are loaded through the frameD plugin, it can perform additional processing or even not load from disk at all. This is leveraged by providing the option to **load proxy images** (which are created automatically) and by using available memory to **cache images**. |
frameD supports both standard “IFL” based sequences as well as its own proprietary “XFD” format. The latter is XML based and allows for more attributes to be saved than simple IFL files allow for. | frameD supports both standard “IFL” based sequences as well as its own proprietary “XFD” format. The latter is XML based and allows for more attributes to be saved than simple IFL files allow for. | ||
+ | ===== Basic Workflow ===== | ||
+ | |||
+ | Single frames or image sequences are assembled in the [[framed2018: | ||
+ | |||
+ | One loaded by the animation loader in LightWave 3D, the images of the sequence will be cached and the timing can be manipulated using various looping options as well as a re-timing curve in the [[framed2018: | ||
===== Features ===== | ===== Features ===== | ||
Line 26: | Line 31: | ||
===== Compatibility ===== | ===== Compatibility ===== | ||
- | frameD is compatible with LightWave3D | + | frameD is compatible with LightWave3D |
It currently runs with the Windows and MacOS versions of LightWave. | It currently runs with the Windows and MacOS versions of LightWave. | ||
Please visit http:// | Please visit http:// | ||
- | <-^|^|^-> | + | <-acknowledgements| ^|^setting_up|-> |