- Citra emulator too fast drivers#
- Citra emulator too fast driver#
- Citra emulator too fast full#
- Citra emulator too fast Pc#
Except for saves and shader presets that is (which i’ll backup somewhere).
Citra emulator too fast Pc#
I’m trying to diagnose what is causing my speed issues.īTW, i’m going to try to remove as much of Retroarch as possible from my PC and start from scratch.
Citra emulator too fast drivers#
Drivers seem okay and i’ve done some clean reinstalls for the nvidia stuff too.
I actually did a complete and clean reformat and reinstall of Windows about a month or so ago. Theoretically if it works in standalone Dolphin, should it also work in Retroarch? Indicating some sort of config problem with Retroarch on my end? I’ll try to see what’s going wrong on my end then with F Zero, thanks for the confirmation that it SHOULD work.
Citra emulator too fast driver#
Even the apparently demanding Beetle PSX with quite a few enhancements like high resolution, PGXP and overclocking (though the GL driver is faster than Vulkan, so I dunno if that’s supposed to be). I’ve not tested the Dolphin core extensively yet, but I seem to be getting pretty excellent performance out of the other cores. I don’t THINK this issue is affecting other cores, or that there’s anything wrong with my PC. I also went into the Nvidia control panel and changed all of the settings to favor performance.
Citra emulator too fast full#
I even did a full wipe of my Retroarch directory and started over to make sure there wasn’t a setting I ticked somewhere that was causing the issue. I’ve been going through all the menus and options I can think of to try to find a setting that could fix this.
Windowed mode and fullscreen yield the same performance for me. I think there must still be some GL implementation issues going on somewhere. It was for some reason far faster in windowed mode than fullscreen. I did notice one thing though when I last tried Citra Libretro. I have also heard opposite conclusions, where Citra Libretro was actually faster than standalone. There must be another explanation for this. Any overhead for 圆4 PIC cores is entirely negligible. RetroArch cannot add such overhead to the extent you describe. If this is an issue that should be reported, i’m unsure where to do it. So what (if anything) should my next option be? I’m open to any advice on the matter. But it’s also slightly faster than the Libretro core is at native 1x resolution…Īfter sharing my results, j-selby stated that he believes the problem to be related to overhead in Retroarch itself and that there was nothing that could be done on the core’s end. The funny part is looking at 10x resolution (4000x2400), Citra standalone is still achieving almost twice the game’s full speed. And even at a very conservative 2x resolution bump, the libretro core is now failing to achieve full speed, while the standalone emulator chews through it with 4 times the performance. They’re quite apparent even compared at native res. I’m not trying to run this at 8 or 10 times resolution, but I still noted and documented the speed discrepancies.
For this particular test I used Kingdom Hearts 3D, which is a native 30fps game. This happens with other games as well, though I need to do some more testing before I can compile a thorough comparison list. I also disabled vsync, and btw vsync being enabled seems to further break performance in 30fps 3DS games too, so that’s another issue. I’ve done my best to ensure my comparisons are using identical settings and tested in identical areas with the same conditions onscreen. I commented on the issue as well, having the same problem despite my PC being significantly more powerful (4670k 8GB DDR3 RAM and a GTX 1060 6GB).
0 kommentar(er)
