10/30/2023 0 Comments Nestopia controller response timeI think there is a difference between retroarch + nestopia and just nestopia by itself, but it’s less than a frame. I redid the test and the difference was a lot smaller, like 20ms. I don’t want to give up on RA because I like having all the emulators in one place and the shaders are awesome.ĮDIT: okay, I think I just need a new testing method Does RA somehow prevent triple buffering? I have it forced on through my graphics card with triple buffering so this should result in NO lag compared to simple double buffering. I have no idea where lag could be introduced, I don’t even have vsync turned on in RA. My response time with Nestopia is around 250 ms, with retroarch it is closer to 300. ![]() Well, I admit that my test is pretty “subjective.” I use Blargg’s reflex timer and do 20 tests and find the average for nestopia, then I do the same for nestopia in retroarch, then I go back and repeat this process 3 times- so I have 3 averages for nestopia and nestopia in retroarch, then I find the average of those averages. How are you measuring latency? RetroArch shouldn’t be introducing excessive latency anywhere, much less almost 4 frames worth. What could be the cause of my input lag with RA? I’m running windows 7 64 bit, if that helps. As it stands nestopia by itself is the closest thing, but the scanlines look whack because the internal aspect ratio is not correct, so you have to use a dumb billinear filter to get the scanlines looking halfway decent. All I want is to be able to play NES in full screen with no screen tearing, minimal input lag, smooth scrolling, the correct aspect ratio, full controller support and evenly spaced scanlines. I’m really bummed now because RA is the only program that I know of that will do full screen mode with evenly spaced scanlines. My cpu isn’t good enough for hard sync, which is the only suggestion I could find online. How does this make any sense? Aren’t they essentially the same program? I just have no clue what could be causing this lag. ![]() ![]() With nestopia on retroarch I get around 50ms more of input lag compared to the latest build of nestopia for windows. Well, I thought everything was running smoothly, so I did some tests of the nestopia core and found that there was significantly more input lag vs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |