pmndrs / pmndrs/react-postprocessing

Switching to another renderer when using postprocessing

Open
#126 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
1.4k
Forks
134
Avg merge
4m
Merged PRs (30d)
4

Description

Let's say we have a scene and a GUI switch that enables/disables some postprocessing effects.

The optimal renderer settings depend on whether we use postprocessing or not, for example, an optimal postprocessing workflow requires the following settings among others:

{
	antialias: false,
	depth: false
}

And to render directly to the screen (without postprocessing), we need these values:

{
	antialias: true,
	depth: true
}

As far as I know, renderer settings cannot be changed on the fly.

What is the best practical solution in this situation?
Is it possible to switch renderer back and forth while keeping the same scene?
If so, how to implement it with react-postprocessing and react-three-fiber?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked postprocessing usage guidance and the renderer configuration used by react-three-fiber. Determine whether renderer settings can change while preserving the scene, and document the practical switching approach or constraints for react-postprocessing.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, three.js, typescript
Domain
computer-graphics
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.