-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
D3D vsync prevents unthrottle from working right (plus, fixed hotkey bug) #7929
Comments
maybe you could try this |
I always try the lasted version of anything before posting. When vsync is enabled and direct3d9 is used while running the cube.iso demo,the unthrottle\alternative speed does nothing |
The hotkey problem sounds really strange, I'll take a look soon. D3D vsync problem is known, although I forgot about it, will see what I can do, might be tricky due to how D3D works. We might have to resort to the same type of unthrottle we use on Android, that is, to actually skip frames instead of just drawing them faster. |
I've tried to reproduce the hotkey problem but have so far failed... It seems normal. |
This is what I just did. Now pressing F2 anywhere outside a game,ppsspp will display the language selection list. It's possible to see what ppsspp tries to do while pressing the hotkey(what code is trying to execute) |
Tagged to investigate for 1.8.0 |
Found the language menu issue, committing fix. |
I'm bumping the D3D9 problem up to 1.9.0, many more issues have higher priority... |
1.If you set any hotkey for "Save State",pressing F2 anywhere except the game pause screen,it will bring the language selection menu(I check the source but I didn't find anywhere anything about hotkey and that many)
2.If VSync is enabled while the video backend is Direct3D9,the unthrottle\alternative speed will be limited to 200% on 30fps games and 100% on 60fps games and to disable the vsync effect,you have to disable it and restart ppsspp(it won't work by just disabling it).
In my nvidia control panel,vsync is set to "Use the 3D application settings")
The text was updated successfully, but these errors were encountered: