What keeps certain cores from being updated?

Is there something in particular that keeps cores like Mupen+GlideN64, Mednafen Saturn and PPSSPP from being up-to-date like other cores that seem to get on par with their standalones in no time?

Is it a matter of difficulty? Meaning that some cores are harder to update than others? Is it just lack of time and author interest? I would expect GlideN64 to be a much more popular update given all the major fixes and updates it gets lately but the libretro version seems like a couple of years out of date at least (judging by the graphics bugs some games still have that were fixed a long time ago).

I’m not an expert and don’t know how updating works but i assume it’s not as hard or time consuming as porting a new emulator? Which is why i personally don’t worry that much about, say, Supermodel. It’s the “it will be ready when it’s ready” kind of thing. But the lack of updates in some existing cores is kind of an issue IMO.

Is there anything that can be done to improve this then? Any way end users may help maybe? Seems like the only thing that holds RetroArch back, excluding how some emulators can’t be ported at all (damn you demul, why do you have to be the best Dreamcast emulator?). Hope i don’t come of as entitled. Just wonder what’s up.

what i learned so far… find issues and patch it yourself…

1 Like

Obviously if i could, i would. But i’m just a stinking end user :stuck_out_tongue:

So what i get from your reply it’s more of a lack of interest in certain cores?

:zipper_mouth_face:

/20 characters

Yeah, try tinkering with files, learn by yourself, compare libretro version with standalone version to figure out what is different and why it is different.

That’s how i started, now the core i’m maintaining is one of the cores that are always up-to-date, and i wasn’t a C/C++ developper.

1 Like