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

Render Duplicate Frames to 60hz not working in Skip Buffers Effects (Non-Buffered, Faster) #12724

Closed
ghost opened this issue Mar 18, 2020 · 3 comments · Fixed by #12743
Closed
Labels
GE emulation Backend-independent GPU issues
Milestone

Comments

@ghost
Copy link

ghost commented Mar 18, 2020

Default Settings Buffered Rendering
Render Duplicate Frames to 60hz is ON
PowerStone Collection
Screenshot_20200318-103513
Skip Buffers Effects (Non-Buffered, Faster)
Render Duplicate Frames to 60hz is ON
Screenshot_20200318-103905

Solution

Grey Out The Render Duplicate Frames to 60hz when set to Skip Buffers Effects so user well not enable it during skip buffers mode?

@unknownbrackets
Copy link
Collaborator

Well, "skip buffer effects" means that we ignore what the game tries to do, and just draw everything directly to the screen.

As a side effect, when the game draws nothing - we draw nothing. If we flip nothing, the display will flicker black every other frame in 30 FPS games.

We would have to use a buffer (that's the thing this disables) to remember what we drew last frame and draw it again so we can flip it.

-[Unknown]

@hrydgard
Copy link
Owner

Yeah this is not possible unfortunately. We might want to gray out the option.

Also I've been wanting to kill non-buffered mode for a long time ....

@hrydgard hrydgard added the GE emulation Backend-independent GPU issues label Mar 18, 2020
@ghost
Copy link
Author

ghost commented Mar 20, 2020

Not added to Milestone v1.10.0?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
GE emulation Backend-independent GPU issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants