Blue_Ninja0 wrote:I've tried Mednaffen with the bsnes core and the same problem from RetroArch arises. There's a very small stutter. Maybe it's something related with the bsnes core?
Yeah, it could be. Try these settings, if you haven't already. I don't know if they are different to the default:
http://i.imgur.com/045in9f.jpg
http://i.imgur.com/ZAUvrUC.jpg
But yeah, I've just had a play around with bsnes on mednafen, and it's a little rough, compared with mess. Thing is with mess and mame, if you disable gsync and vsync entirely, you can see a clean tear rolling up the screen in an orderly fashion. If you take the trouble of creating custom resolution locked into a particular frequency, that's within 3 decimal places (like the 60.098hz), then run mess in that resolution, you can see the tear actually staying exactly where it is. When the mess guys say 60.098hz, they really mean it
It was even better when you created 120.196hz custom frequency, there barely any need for gysnc at all, you have to look really hard for that tear sometimes, given the faster scan. Although I have to say gsync is so convenient
Now, if I look at that tear with bsnes, it's just all over the place. It's like bands of multiple tears onscreen at the same time. This is why I was talking about 'timing', it seems to be wild with most emulators
It's almost like we could do with removing all throttling and capping with something better. Seems strange, but try this:
http://i.imgur.com/FyysjEQ.jpg
I thought that nvidia driver level capping was thoroughly broken, it seems to be quite effective for this?
http://i.imgur.com/XEEqN9s.jpg
http://www.guru3d.com/files-details/rts ... nload.html