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

Screen tearing #355

Open
tom-seddon opened this issue Jul 11, 2024 · 1 comment
Open

Screen tearing #355

tom-seddon opened this issue Jul 11, 2024 · 1 comment
Labels
UI/UX something user-facing, contributing to a suboptimal experience

Comments

@tom-seddon
Copy link
Owner

tom-seddon commented Jul 11, 2024

b2 produces output at the PC refresh rate. In theory, you get good responsiveness, but at the possible cost of some visible screen tearing. The results have always been a mixed bag: the responsiveness is pretty good (though not perfect...), but the tearing is actually quite noticeable.

Can b2 do better? It's probably never going to be perfect, with 50 Hz BBC output and 60 Hz PC output. But any tradeoffs should at least be more configurable.

@tom-seddon tom-seddon added the UI/UX something user-facing, contributing to a suboptimal experience label Jul 11, 2024
@cardboardguru76
Copy link

More info:
Running the horizontal scrolling demo from here, on macOS, the tearing is pretty bad. Doesn't make any difference whether --vsync or --timer.
http://www.retrosoftware.co.uk/wiki/index.php?title=How_to_do_the_smooth_vertical_scrolling

Running the same image on BeebEm has no tearing. It's not perfectly smooth, but no tearing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
UI/UX something user-facing, contributing to a suboptimal experience
Projects
None yet
Development

No branches or pull requests

2 participants