(PC and laptop monitors are widely known to be practically as resonsive as CRT screens. The way I had it calculated, the PC setup was darn near perfect on its own LCD display. (I mean a few milliseconds difference, if any.) But the minute I plug the HDMI out and into my Sceptre (which has no game mode) there's about a frame or so of display lag added to that perfect setup. On my laptop I can get almost the exact same button input to display time as my original SNES into a CRT using Retroarch and SNES9X. I cannot attest to the N3DS, but it is very possible that system would feel more responsive compared to the SNES Classic largely because of the added display lag an HDMI television introduces. Much like the NES cores, the Megadrive/Genesis cores can all be useful if you keep your expectations moderate. Overall I like the colors better on the Picodrive. I think this happens with the Widescreen Genesis Plus GX as well. So far the only issue I've noticed is Sonic's elbow seems on the wrong layer on the title screen. Not bothering with the frame delay because the run-ahead is a better use of resources. On the Genesis Extreme GX I can set it to 32, with Hard GPU Sync enabled, and 1 runahead frame. On the Picodrive and Genesis Plus GX I had to keep the Audio Latency at 40 or 50 to avoid audio breakup. (I'm sure this is awesome when the system is overclocked, but for me 200% sped up and slowed down very noticeably.) So long as you go into the core Options menu and take the CPU speed from the default 200% back to 100% this hot-rodded core really opens up to pushing in the latency menu. There is a variant, Genesis Extreme GX, that I had overlooked until today. I did notice the Genesis cores on the minis are significantly slower reacting than Lakka Genesis Plus GX on my Dell Optiplex 745 or Retroarch Genesis Plus GX on my Dell laptop. Without proper slow-motion captures I can't be sure. (Might be a tie even with Genesis Plus GX not doing run-ahead). I am uncertain whether this actually results in any performance change on the SNES Classic once both cores are optimized. With Sonic the Hedgehog I can enable run-ahead frames on Picodrive, but cannot do so with the regular Genesis Plus GX. I agree the Picodrive should probably be the first choice given the hardware limitations of the SNES Mini. No slow-motion capture, but this is how my experience has been.ĭisclaimer: I am not testing this with any overclock on the SNES Classic for the benefit of people whose systems can't do it. This has been rattling around in my head for a while and I got a chance to try new ideas out today. Hey I know it's a bit late to the discussion, but this thread had me experimenting off and on the last few weeks with a few Sega Genesis games and the cores on the minis. So, the TL:DR version:ġ- Which cores are better and have less input lag?Ģ- Does using hard sync with GPU or run ahead emulation make any difference on the SNES mini considering it's an underpowered device? What options are better for reducing lag?ģ- Why does Retroarch on the New 3ds feels faster than on the SNES mini?Ĥ- Am I going crazy? Maybe there's no perceptible input lag. I don't get why Retroarch on my New 3DS feels so much more immediate considering it's also an underpowered device. Contra feels fast and light, while Contra Hard Corps on the Megadrive doesn't. On the other hand, I don't feel any lag with the NES core. In general, Megadrive games feel a bit heavier compared to Retroarch on PC, but I don't know if this is just me being biased for assuming there would be more input lag on a less powerful device. After adding Retroarch to my SNES Mini, I was unsure what cores to use, so I went for the Xtreem versions because i assumed they were optimized for the device.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |