Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Bug]: Screenshots with a shader using post-processing tonemapping are incredibly washed out and overexposed #101

Open
steve-the-player opened this issue Mar 2, 2024 · 1 comment
Open

[Bug]: Screenshots with a shader using post-processing tonemapping are incredibly washed out and overexposed #101

steve-the-player opened this issue Mar 2, 2024 · 1 comment

Comments

@steve-the-player
Copy link

steve-the-player commented Mar 2, 2024 •
edited
Loading

2024-03-02_00 25 53
Screenshot 2024-03-02 at 12 26 03 AM

This appears to happen more often with night vision for some reason. Edit: not actually true, it was just the simulated autoexposure being weird when night vision was enabled. It's just as bad without night vision
I'm using Complementary shaders in this screenshot, but I've observed the same behavior from BSL when tonemapping was enabled
@k2helix
Copy link

k2helix commented Jun 14, 2024

This also happens with latest Bliss Shaders. Disabling the Auto-Exposure option and setting it manually helps but the screenshot still feels overexposed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@k2helix @steve-the-player