The compositor execute functions have a `rendering` argument to specify if the compositor is executing as part of the render pipeline. But the render context argument is null if we are not rendering, so the `rendering` arguement is redundant and can be removed. Additionally, we no longer use use_file_output as a hack to detect rendering. Pull Request: https://projects.blender.org/blender/blender/pulls/120659
40 lines
1.2 KiB
C++
40 lines
1.2 KiB
C++
/* SPDX-FileCopyrightText: 2023 Blender Authors
|
|
*
|
|
* SPDX-License-Identifier: GPL-2.0-or-later */
|
|
|
|
#pragma once
|
|
|
|
#include <memory>
|
|
|
|
namespace blender::realtime_compositor {
|
|
class RenderContext;
|
|
}
|
|
|
|
struct bNodeTree;
|
|
struct Depsgraph;
|
|
struct Render;
|
|
struct RenderData;
|
|
struct Scene;
|
|
|
|
/* ------------------------------------------------------------------------------------------------
|
|
* Render Realtime Compositor
|
|
*
|
|
* Implementation of the compositor for final rendering, as opposed to the viewport compositor
|
|
* that is part of the draw manager. The input and output of this is pre-existing RenderResult
|
|
* buffers in scenes, that are uploaded to and read back from the GPU. */
|
|
|
|
namespace blender::render {
|
|
class RealtimeCompositor;
|
|
}
|
|
|
|
/* Execute compositor. */
|
|
void RE_compositor_execute(Render &render,
|
|
const Scene &scene,
|
|
const RenderData &render_data,
|
|
const bNodeTree &node_tree,
|
|
const char *view_name,
|
|
blender::realtime_compositor::RenderContext *render_context);
|
|
|
|
/* Free compositor caches. */
|
|
void RE_compositor_free(Render &render);
|