Snes9x.com

Either install the newest DirectX through the webinstaller, or go to Sound->Settings and select a different sound driver.

As a side note: some punctuation in your questions might increase the number of people willing to help you...

Why not just change the fps counter to that minimum value, and put "make FPS counter more accurate" in the changelog? Would anyone complain if the FPS counter were calculated differently? The two counters display different things: the old one states "of the last 60 frames, X were ren...

"Show frame rate" now shows a thing like "60 fps" in addition to the traditional "60 / 60". What's weird is that often the two fps counts are different. Why have both, and why are they calculated differently? 60/60 is the old framerate display that shows how many of th...

Did you actually try it? Hi-Res filter support has been available for quite some time now... Check the Hi-Res filter box in the display configuration.

Spinning left or right works just fine in snes9x, but to get across the sawblade you'll have to keep the y button pressed, otherwise you're not fast enough.

I'm guessing you are using the windows port:

Open snes9x.conf with your favorite text editor, look for [Settings\Win\Files] and delete all lines starting with Rom:RecentGame.

Here's a new testbuild: snes9x_testbuild_13112010.zip OpenGL should work on older cards (PBOs are optional) Synchronizes the Win7 jumplist with the recent roms list Support bSNES-style XML-based .shader files Updated menu structure Drag&Drop support for ROMs Various small fixes Shaders can be fo...

It will be fixed in the next version.

I've added a config file option to always center the unstreched image (win port).

Frame advance capability is currently limited to the windows port.

epman5g wrote:

the_randomizer wrote:only problem I found with the snes9x re-recording versions is that you must run them under recent versions of Windows as they won't work under Win9x. need a minimum of Win2000, XP or greater to use snes9x-rr.

The same is true for normal snes9x - it's a limitation of Visual Studio 2008.

Save states on windows are named ROM_NAME.000 to ROM_NAME.009 - simply rename your freeze file to that format and it should work.

.srm is the SRAM container, not a freeze file.

Note that any savestates made without the command line switch will still flicker with the switch present.

(from here).

Notice how you made the same typo there camo_yoshi?

That's because the command is "-hdmatiming 84"

It's a known issue. Until the next version is released you can start snes9x with "-hdmatiming 84" to remove the flickering.

The srm file needs to have the same name as the rom and needs to be placed in the SRAM directory - check in options->settings where that is in your case.

I was only referring to the usage in the win port.

The new APU in 1.52 also has a new SPC dumping feature, I simply missed that when I updated the windows port.

When frameskip is set to fixed 0, the only thing limiting the speed is audio sync. If you disable that you will have constant turbo, regardless of the turbo button.

Increasing/decreasing speed only works with auto frameskipping and audio sync disabled.

The windows version doesn't expose it atm. I only removed the (rather dubious) dumping from 1.51. I'll readd the option in the next version.

That depends on your preference. With 4:3 you get the AR as it would look on your tv, 8:7 gives you the pixels as the SNES produces them.