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.

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

Bug: With BurnIn (persistence) enabled, setting effect FPS set to "Max" causes effect to not fade. #836

Open
bradtchapman opened this issue Feb 27, 2024 · 2 comments

Comments

@bradtchapman
Copy link

Summary: with BurnIn (Persistence) enabled, Effect FPS at Maximum, the burn-in effect does not fade away properly.

Notes:

  • The app starts with a default fps of 30 and a burnin quality of 50%
  • The user must intentionally raise effect fps to max, and adjust the burnin quality setting to 100%.
  • If "Blinking Cursor" is enabled, the persistence effect fades at 2fps (the rate of cursor blinking).
  • If "Blinking Cursor" is not enabled, the persistence effect will not fade until a change occurs in the terminal (i.e.: a user types something, or a program displays new information on screen)

Workarounds (both required):

  • set effect FPS below max (e.g.: 60 fps)
  • set burnin quality below 100%

Similar reports: #831 and #816

@jleaders
Copy link

jleaders commented May 2, 2024

On M2 Macbook Pro I noticed the burn-in eventually freezes and stops fading -- in this screenshot it stays like this forever (I didn't change any default settings, I just scrolled up and down a bunch)
image
image

@Commander1024
Copy link

Can confirm for Fedora 40.

I can also confirm, the workaround working, which makes me happy. :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants