skillsaw / mupen64plus

Automatically exported from code.google.com/p/mupen64plus
0 stars 0 forks source link

Support variable r4300 clock speed for simulated 'overclocking' #319

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
I'm quite the newbie to Google Code, so I unfortunately don't know how to
apply the "Enhancement" label.

Simply put, implement an option to render at a true 60fps.

There was a mod for 1964 that had this option, see here:
http://www.emutalk.net/showthread.php?t=40311
Unfortunately along with the dead download link the source has gone missing
- all there is to rely on is the not-so-"documentation" in that thread.

I bring this up here because the author of that mod has gone missing, and
PJ64 (which was implementing it as well) practically seems dead.  Hopefully
someone can implement it and then maybe it'll spread to other emulators
like wildfire (hello RE4 @ 60fps).

Original issue reported on code.google.com by nintendo...@gmail.com on 19 Jan 2010 at 11:07

GoogleCodeExporter commented 8 years ago

Original comment by richard...@gmail.com on 19 Jan 2010 at 3:17

GoogleCodeExporter commented 8 years ago
Here is a similar overclock mod, and it is amazing. I only have trouble doing 
fraps on it, it is buggy.

http://www.retrocopy.com/forumthread/414-1/1964-ultrafast---60fps-n64-emulator.a
spx

Original comment by prysz...@gmail.com on 20 May 2011 at 8:05

GoogleCodeExporter commented 8 years ago
This could be a fix for Hydro Thunder (according to Ari64). A new command for 
the core could be necessary

<Ari64> Re issue 319: Easy to do, just needs UI.  How should the UI tell the 
core that it wants the CPU overclocked?  And this is more of a bug than an 
enhancement since the current settings break at least one game.
<Richard42> Ari64: probably add a new command in CoreDoCommand, something like 
M64CMD_SET_CPU_SPEED

Original comment by sven@narfation.org on 9 Jul 2011 at 6:13

GoogleCodeExporter commented 8 years ago
I don't know what they did but mupen64plus-core has a CountPerOp setting. And I 
would guess they are using something like it and called it "overclocking".

So I would mark this as fixed. If you have other information how this should be 
done then please add this here and I will reopen the bug.

PS: I haven't really read the threads because it immediately switched to 
another topic and only some posts later it developed to a flamewar like 
situation. 

Original comment by s...@narfation.org on 18 Dec 2013 at 11:06

GoogleCodeExporter commented 8 years ago

Original comment by s...@narfation.org on 18 Dec 2013 at 11:06