Ppsspp upstream initialization function(s) are either duplicated correctly for the libretro core framework so no more problems like this happen or the original code used somehow. There's probably other things not initializing the Config class is doing wrong too.' Expected behavior ' However, because libretro (for some reason?) bypasses all our configuration initialization code, this doesn't happen there.
This comment by unknownbrackets is alarming hrydgard/ppsspp#13115 (comment) Hardcoding seems ok if you're never going to use RA libretro to play multiplayer ppsspp, but you'd think this would be a core option.Īnd while you're at it, check if any other piece of initialization data that exists in ppsspp was 'skipped' in the creation of this core. My problem with this is that this hack original problem comes from the libretro port not using the same config files (fair enough) and not replacing it by anything in the libretro core startup (not good). Namely this one 'fix', which is basically a hack: Yes, i know the ppsspp core is upstreamed, this doesn't mean that upstream is going to fix bugs that only occur in the libretro port. I posted this here because libretro/ppsspp doesn't have a bug report tab. This is not a forum or a help section, this is strictly developer oriented.Only RetroArch bugs should be filed here.
0 kommentar(er)
