20,741
edits
Compositor: Difference between revisions
Jump to navigation
Jump to search
→Features
m (→Status) |
|||
| Line 98: | Line 98: | ||
* Although independent, its aim is to be fully compatible with the current rendering framework in FG. This includes the Effects system, CameraGroup, Rembrandt and ALS (and obviously the Canvas). | * Although independent, its aim is to be fully compatible with the current rendering framework in FG. This includes the Effects system, CameraGroup, Rembrandt and ALS (and obviously the Canvas). | ||
* Its functionality overlaps Rembrandt: what can be done with Rembrandt can be done with the Compositor, but not vice versa. | * Its functionality overlaps Rembrandt: what can be done with Rembrandt can be done with the Compositor, but not vice versa. | ||
* Fully configurable via | * Fully configurable via an XML interface without compromising performance (ala Effects, using PropertyList files). | ||
* Flexible, expandable and compatible with modern graphics. | * Flexible, expandable and compatible with modern graphics. | ||
* It doesn't increase the hardware requirements, it expands the hardware range FG can run on. People with integrated GPUs (Intel HD etc) can run a Compositor with a single pass that renders directly to the screen like before, while people with more powerful cards can run a Compositor that implements deferred rendering, for example. | * It doesn't increase the hardware requirements, it expands the hardware range FG can run on. People with integrated GPUs (Intel HD etc) can run a Compositor with a single pass that renders directly to the screen like before, while people with more powerful cards can run a Compositor that implements deferred rendering, for example. | ||