No definitive source, just math.
Oh, I know, I've done it but it doesn't work very well with modern Windows. A pain to use but cool when it works.
Individual games on those systems can still have some built-in latency.
I have some longer answers earlier in the thread, but the short one is no. Not if used as intended (i.e. only removing as many frames of lag as a given game actually had).
The many discussions about emulator latency -- and even display latency for retro games -- and the ways to minimize it we've had over the years indicate that it is a very real problem.
I can't think of any automated way.
Not too bad, then! Seems the negative effects of going too high are fairly apparent. I'll have to experiment when I get home.
I can beat Mike Tyson in Punch Out without being touched on original hardware and crt tv on emulator its near impossible at least for me
I'm really hoping it can for some lighter emulators, at least. SNES9X's core had a fair amount of headroom on the Win 1. Wouldn't expect much beyond 16-bit emulation, nor for it to work with some hyper-accurate emulators like Higan.
I wouldn't even use Retroarch on its own, to be honest. UI is convoluted and annoying as hell to set up. If you're going to put in the effort to configure things beyond controller inputs and cheats, put that effort into setting it up via a frontend like Launchbox. Much, much easier to get games set up to run via specific cores, save states, and whatnot. And with this way, you'd avoid that bullshit of "your rom wasn't ripped in this specific fashion that we like, so your game isn't going to run."
Launchbox is a front end for whatever you want it to be, be it Steam games, SNES, or whatever. What'd you end up doing is pre-configuring your specific ROM set to run on a set emulator (Retroarch in this case), and then you set up to choose which core Retroarch uses for each game type.
You mean it won't be scanned and automatically added to one of the playlist tabs in RA's interface because it doesn't match the database. You can always run stuff that doesn't match the database with Load Content from the main menu tab.
What do you mean by vertical games? I've only tried it on a handful of SNES games (too many new games to play the oldies!) but CRT royale looks so good on my X800D.
I know, I mention that later on in the post. Still a nuisance because Retroarch's UI isn't intuitive and is even worse if you have roms for more than one console.
Which is a complete hassle. You have to navigate 30 years to get to your rom folder for it to scan everything, then you have to try games with specific cores, only for Retroarch to reject that pair, then you have to remove the game from the playlist and try it again with a different core. A person who's just starting out isn't going to know that going to Load Content/Core or creating your own individual playlists is going to get around this issue when they first encounter it, and then getting around this situation is annoying because the UI is annoying. Even without this propping up, scanning and loading games and having them show up in the UI is annoying because navigation itself makes no sense.
There's a new Windowsy point and click UI being built in QT you might like when it's finished.
I don't want a point and click UI (not entirely), I'm already routing all of my PC gaming through LaunchBox/Big Box so on my next build, I can shove it under a TV and have it be accessible by controller or keyboard for anyone who comes across it and wants to sit down and play some shit.
Reminder that the "BSNES" core is based on a very old version of Byuu's emulator.
Seriously? It's basically 2 controller inputs to re-launch a game you have played previously in Retroarch.
This is a ludicrous exaggeration. It takes a few seconds for me to launch a never-before-launched rom in retroarch. Literally.
Sure, it's not hot off the presses -- but clearly it was new to me and most people here! That said, looking at the actual repo, it has only been merged for 20 days, so in terms of being actually usable for people in an easy-to-obtain version of the emulator it's still pretty new.
Well, with modern systems, that can be a result of different input processing, less buffering or simply running faster.
I'd say so -- for everything 32 bit and older.
