Integrated FSR as Post-Processing Pass

I’ve been working on a new post-processing pass called RenderFSRPass, which is inspired by the RenderPixelatedPass. The idea was to leverage the techniques from web-fsr and convert it into a post-processing pass for THREE.js.

While the results are somewhat interesting, I must admit that the performance optimization isn’t as significant as I had hoped. This might be due to my implementation, and I believe there is still room for improvement.

For those interested, you can check out the current state of the project here: fsr.alicerun.pages.dev.

Additionally, I’ve shared the source code on GitHub: RenderFSRPass.ts.

I would love to hear your feedback and suggestions on how this can be further optimized. Cheers :stuck_out_tongue:

Hello,
Your work on the RenderFSRPass sounds intriguing! Leveraging techniques from web-fsr for a post-processing pass in THREE.js is a great idea. While the performance optimization isn’t as significant as expected, there’s always room for improvement. I recommend profiling and analyzing bottlenecks to fine-tune your implementation. Keep iterating, and best of luck.
Official Site
Best Regards
esther598