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

Remove CountPerOp=1 for Vigilante games #533

Merged
merged 1 commit into from Feb 13, 2018

Conversation

loganmc10
Copy link
Member

The Vigilante games are very demanding on the CPU. Having CountPerOp=1 makes this even more pronounced.

@AmbientMalice you seem to know a lot of the history behind these settings. Do you know why the Vigilante games have CountPerOp=1? I assume we just copied it over from PJ64

I tested the games briefly and they seem to work the same using CountPerOp=2, but much less CPU usage.

@AmbientMalice
Copy link
Contributor

Nothing comes to mind, sorry.

@richard42 richard42 merged commit e343e5f into mupen64plus:master Feb 13, 2018
@loganmc10 loganmc10 deleted the patch-3 branch December 3, 2018 03:50
inactive123 added a commit to libretro/parallel-n64 that referenced this pull request Jan 21, 2020
setting Vigilante 8 games to CountPerOp 1 was apparently a bad idea,
performance greatly increased with default framerate setting
inactive123 added a commit to libretro/parallel-n64 that referenced this pull request Jan 21, 2020
setting Vigilante 8 games to CountPerOp 1 was apparently a bad idea,
performance greatly increased with default framerate setting
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

Successfully merging this pull request may close these issues.

None yet

3 participants