{
  "$type": "site.standard.document",
  "path": "/t/january-2026-monthly-wip-screenshot-thread/49362?page=3#post_41",
  "publishedAt": "2026-02-04T19:19:45.000Z",
  "site": "https://hub.jmonkeyengine.org",
  "textContent": "I’m currently evaluating how the _GlowIntensity_ parameter behaves when combined with the `BloomFilter` in the `FilterPostProcessor`.\n\nMy goal is to understand how far the outline can push real HDR values (above 1.0) and how the bloom reacts to those values—whether it amplifies them correctly or if any unwanted saturation or artifacts appear. I’m experimenting with different setups, including:\n\n  * HDR framebuffer (`RGBA16F`)\n  * bilinear filtering for upscaling\n  * higher-than-normal `GlowIntensity` values\n\n\n\nI’m trying to determine the most consistent behavior and the best settings to achieve a clean, stable glow around outlined objects. If anyone has experience with emissive outlines or `BloomFilter` behavior in an HDR pipeline, I’d really appreciate your insights.\n\nI’m wondering whether it makes sense to change the default framebuffer format of the `FilterPostProcessor`. Right now I’m testing this setup:\n\n\n    FilterPostProcessor fpp = new FilterPostProcessor(assetManager);\n    fpp.setFrameBufferFormat(Image.Format.RGBA16F); // HDR\n\n    fpp.addFilter(dlsf);\n    fpp.addFilter(outline);\n    fpp.addFilter(bloom);\n    fpp.addFilter(new ToneMapFilter(new Vector3f(1, 1, 1)));\n    fpp.addFilter(new FXAAFilter());\n    viewPort.addProcessor(fpp);\n\n\nFor those who have worked with HDR pipelines or BloomFilter interactions, do you think switching the FPP to `RGBA16F` is a good idea, or is it better to keep the default format `RGB111110F` unless strictly necessary?\n\n",
  "title": "(January 2026) Monthly WIP Screenshot Thread"
}