i do recommend using old versions of RA cores since they're stable, also if you want latest updates of cores but being stable, i recommend grabbing the ones i post here.Hello Saul, I have a question, are for you, the cores that you are publishing in that section, the best versions of each of them, I have always preferred to play only with Wiimote, knowing this, would there be some reason to use versions of the cores more modern ones like 1.12, 1.15, like 1.8.4.
What is your opinion on which are the best versions of each core.
Thank you in advance and for your tremendous work in the Wii community.
Beetle PCE fast Retro Arch 1.7.6 14042024.Which PCE Fast core are you using?
Oh so it will work on RA 1.7.6, ill try itYes, i also had issues with both PCE retro recompiles. 1.10.1 is the best (Fast) core i have ever tested/used. I'll link here if you want to test/use, it has been hex edited to work with all other cores.
Sidenote: There's no "version of RetroArch" but instead versions of cores. So if you load a core from 1.10.X it will run RetroArch 1.10.X independently from whatever version other cores are from.Oh so it will work on RA 1.7.6, ill try it
Post automatically merged:
Nope, neverminded, didnt worked, put the core on RA 1.7.6 and when it loads it does so in 480i and after re-setting the aspect ratio, and i select a game, PCE, i just get NO CORES AVAILABLE.
Nope, this time i used RA 1.10.0 after i tried the hacktip you gave me for 1.7.6 and then 1.10.0OK, ill try again.....wish me luck.
Having CHD support requires the NeoCD core (and some other supported cores) to be recompiled on latest RA Wii frontend versions.Amazing, I tried the new version and everything seems to be working great, sound is good, some bugs like on Fatal Fury 3 the Franco Bash stage where the chair is bugged out, now it looks properly (the only bug I remember seeing).
Only thing is that the CHD game I had (KOF95) did not start. But maybe it was incorrectly compressed.
And the last thing I can say is that the core feels less laggy or more responsive, maybe I am imagining things, but latency seems better.
So thank you @SaulFabre and @ploggy, I am happy that I awaken the masters![]()
You now where about the issues started in the newer RA versions so why not try to bisect and find what caused the issues, then you can make an issue to the RA devs and see if they can fix the latest RA versions? That must be better than recompiling from older RA builds for every new Core update?Having CHD support requires the NeoCD core (and some other supported cores) to be recompiled on latest RA Wii frontend versions.
Unfortunately i really don't trust on latest RA Wii versions since they introduce more bugs and crashes which on previous outdated versions didn't happen...
Maybe try using @ploggy's NeoCD Libretro Wii recompile on latest RA Wii for CHD?
But don't know if it has Wiimote only support or audio has no static buzzing/crackling audio.
I understand and I agree 100% percent, the RA Wii versions are bugged and we cannot rely on them. But please see what Ploggy said in the post above. It really would be ideal. Still, for me CHD support is not so needed, but yes, it would be nice.Having CHD support requires the NeoCD core (and some other supported cores) to be recompiled on latest RA Wii frontend versions.
Unfortunately i really don't trust on latest RA Wii versions since they introduce more bugs and crashes which on previous outdated versions didn't happen...
Maybe try using @ploggy's NeoCD Libretro Wii recompile on latest RA Wii for CHD?
But don't know if it has Wiimote only support or audio has no static buzzing/crackling audio.