npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

screen-space-reflections

v2.5.0

Published

Screen Space Reflections implementation in three.js

Downloads

32,186

Readme

three.js Screen Space Reflections

Implements performant Screen Space Reflections in three.js.

Demos

react-three-fiber demos:

Usage

If you are using react-three-fiber, you can also use the SSR component from react-postprocessing. Check out the react-three-fiber demos to see how it's used there.

Basic usage:

Install the package first:

npm i screen-space-reflections

Then add it to your code like so:

import { SSREffect } from "screen-space-reflections"

const composer = new POSTPROCESSING.EffectComposer(renderer)

const ssrEffect = new SSREffect(scene, camera, options?)

const ssrPass = new POSTPROCESSING.EffectPass(camera, ssrEffect)

composer.addPass(ssrPass)

Options

const options = {
	intensity: 1,
	exponent: 1,
	distance: 10,
	fade: 0,
	roughnessFade: 1,
	thickness: 10,
	ior: 1.45,
	maxRoughness: 1,
	maxDepthDifference: 10,
	blend: 0.9,
	correction: 1,
	correctionRadius: 1,
	blur: 0.5,
	blurKernel: 1,
	blurSharpness: 10,
	jitter: 0,
	jitterRoughness: 0,
	steps: 20,
	refineSteps: 5,
	missedRays: true,
	useNormalMap: true,
	useRoughnessMap: true,
	resolutionScale: 1,
	velocityResolutionScale: 1
}

| Name | Type | Description | | ----------------------- | -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --- | | intensity | Number | intensity of the reflections | | exponent | Number | exponent by which reflections will be potentiated when composing the current frame's reflections and the accumulated reflections into a final reflection; higher values will make reflections clearer by highlighting darker spots less | | distance | Number | maximum distance a reflection ray can travel to find what it reflects | | fade | Number | how much reflections will fade out by distance | | roughnessFade | Number | how intense reflections should be on rough spots; a higher value will make reflections fade out quicker on rough spots | | thickness | Number | maximum depth difference between a ray and the particular depth at its screen position before refining with binary search; higher values will result in better performance | | ior | Number | Index of Refraction, used for calculating fresnel; reflections tend to be more intense the steeper the angle between them and the viewer is, the ior parameter sets how much the intensity varies | | maxRoughness | Number | maximum roughness a texel can have to have reflections calculated for it | | maxDepthDifference | Number | maximum depth difference between a ray and the particular depth at its screen position after refining with binary search; higher values will result in better performance | | | blend | Number | a value between 0 and 1 to set how much the last frame's reflections should be blended in; higher values will result in less noisy reflections when moving the camera but a more smeary look | | correction | boolean | how much pixels should be corrected when doing temporal resolving; higher values will result in less smearing but more noise | | correctionRadius | boolean | how many surrounding pixels will be used for neighborhood clamping; a higher value can reduce noise when moving the camera but will result in less performance | | blur | Number | how much the blurred reflections should be mixed with the raw reflections | | blurKernel | Number | kernel size of the Box Blur Filter; higher kernel sizes will result in blurrier reflections with more artifacts | | blurSharpness | Number | exponent of the Box Blur filter; higher values will result in more sharpness | | jitter | Number | how intense jittering should be | | jitterRoughness | Number | how intense jittering should be in relation to a material's roughness | | steps | Number | number of steps a reflection ray can maximally do to find an object it intersected (and thus reflects) | | refineSteps | Number | once we had our ray intersect something, we need to find the exact point in space it intersected and thus it reflects; this can be done through binary search with the given number of maximum steps | | missedRays | boolean | if there should still be reflections for rays for which a reflecting point couldn't be found; enabling this will result in stretched looking reflections which can look good or bad depending on the angle | | useNormalMap | boolean | if roughness maps should be taken account of when calculating reflections | | useRoughnessMap | boolean | if normal maps should be taken account of when calculating reflections | | resolutionScale | Number | resolution of the SSR effect, a resolution of 0.5 means the effect will be rendered at half resolution | | velocityResolutionScale | Number | resolution of the velocity buffer, a resolution of 0.5 means velocity will be rendered at half resolution |

❗ Highly recommended: Use a GUI to tweak the options

Since the right options for an SSR effect depend a lot on the scene, it can happen that you don't seem to have an effect at all in your scene when you use the SSR effect for the first time in it without any configuration. This can have multiple causes such as `` being way too low for your scene for example. So to find out which SSR options are right for your scene, you should use a GUI to find the right values easily. The example already comes with a simple one-file GUI SSRDebugGUI.js that you can use in your project like so:

  • First install the npm package of the module used for the GUI:
npm i tweakpane
  • then just copy the SSRDebugGUI.js to your project and initialize it like so in your scene:
import { SSRDebugGUI } from "./SSRDebugGUI"

const gui = new SSRDebugGUI(ssrEffect, options)

That's it, you should now have the GUI you can see in the example scene. The options parameter is optional for the SSRDebugGUI and will default to the default options if no options parameter is given.

Run Locally

If you'd like to test this project and run it locally, run these commands:

git clone https://github.com/0beqz/screen-space-reflections
cd screen-space-reflections/example
npm i --force
npm run dev

Features

  • Temporal Reprojection to re-use the last frame and thus reduce noise
  • Jittering and blurring reflections to approximate rough reflections
  • Using three.js' WebGLMultipleRenderTarget (WebGL2 only) to improve performance when rendering scene normals, depth and roughness
  • Early out cases to compute only possible reflections and boost performance
  • Box Blur to reduce noise

What's new in v2

  • Introduced Temporal Reprojection to reduce noise for the reflections when moving the camera by reprojecting the last frame's reflections into the current one
  • Implemented accumulative sampling by saving and re-using the last frame's reflections to accumulate especially jittered reflections over frames
  • Made all SSR-related options (e.g. thickness, ior, ``,...) reactive so that you now just need to set ssrEffect. = value for example to update values
  • Fixed jittering so that it's actually correct from all angles (it used to be less intense the higher you were looking down at a reflection)
  • Changed the SSR implementation from a pass to an effect to improve performance
  • Optimizations regarding computation of required buffers and reflections

Tips

Getting rid of artifacts

If you are getting artifacts, for example:

Then try the following:

  • increase thickness
  • increase maxDepthDifference
  • decrease ``and increasesteps if reflections are cutting off now
  • increase refineSteps

Keep in mind that increasing these values will have an impact on performance.

Hiding missing reflections

Since SSR only works with screen-space information, there'll be artifacts when there's no scene information for a reflection ray. This usually happens when another objects occludes a reflecting object behind it. To make missing reflections less apparent, use an env-map that can then be used as a fallback when there is no reflection. Ideally use a box-projected env-map.

Here are two implementations for three.js and react-three-fiber:

Getting updated reflections for animated materials

By default, the SSR effect won't really update reflections if the camera is not moving and no mesh in the view is moving. However, it will check if a mesh's material's map is a VideoTexture and will keep its reflections updated each frame. If your material is not using a VideoTexture but is still animated (e.g. it's a custom animated shader material), then you can get updated reflections for it by setting mesh.material.userData.needsUpdatedReflections = true. This will make the SSR effect recalculate its reflections each frame.

Server Side Rendering and window being undefined

If you are using Server Side Rendering and don't have access to the window object then the SSR effect won't be able to set the correct width and height for its passes. So once you have access to the window object, set the correct width and height of the SSR effect using:

ssrEffect.setSize(window.innerWidth, window.innerHeight)

Todos

  • [ ] Proper upsampling to still get quality reflections when using half-res buffers

Credits

Resources

Screen Space Reflections in general

Temporal Reprojection