Taito games not working anymore after update
-
Hi guys,
I've two Retropies at home, both on Raspberry PI 3B, both running 4.4.1 (one installed from 4.0 image, the other from 4.4); the Retropie folder with BIOS and roms is on an external NAS, which both are correctly mounting.
Both were working fine until a couple of day ago, until I did an update from Retropie menu on the first one; after that, some Taito games stopped working ( Rainbow Islands, Volfied...); Verbose logging says that cchip BIOS is missing.
Before updating the second one, I did a full backup, and, after updating, those games stopped working as well.
Of course, after restoring from backup, everything works again perfectly.
Has this happened to anyone ? Any idea about how to fix this ?
Thanks in advance for your help !xGauccix
-
What emulator are you using ? Post the verbose log on pastebin.com to take a look at it.
-
Sorry, forgot to say it's lr-fbalpha.
Later I'll post verbose logging.
Thanks ! -
@xgauccix If you updated from source
lr-fbalpha
, then you got a new version and you possibly need a new compatible ROMset for those games. -
seriously guys there should be a warning. people have a perfeclty running system and updating makes many games unplayable.
people dont know this stuff. They think "hey cool an uptdate, i bet there are some nice new features" and "What the f*** i have to resource my roms that took me years to find a working set" and "what do you mean, clrmamepro, is that something to eat?"
-
@mitu I updated from binary, as always....
-
@robertvb83 said in Taito games not working anymore after update:
seriously guys there should be a warning.
There is a warning in the documentation, exactly under the Updating section.
Before making any major updates it is important to make backups just in case (see backup options below).
-
@mitu yes i know, and thats fine and the documentation is great, but i speak of lets say average users that just mainly want to play games. No way they look into that documentation before updating... maybe a disclamer right before updating would be nice
-
@robertvb83 said in Taito games not working anymore after update:
"What the f*** i have to resource my roms that took me years to find a working set"
Or 2 minutes if you know how to use google search engine.
About the warning, as a developper, i'm confident about the fact people won't read it anyway, except perhaps if it's in a sign held by a cat or something.
-
Where exactly is the the information which romset I need after updating?
-
@rsn8887 see https://github.com/retropie/retropie-setup/wiki/FinalBurn-Alpha#lr-fbalpha
that has the source code to the emulator that is retrieved when you update via source. i don't know what version the binary update uses.
we state the romset in the wiki but it's out of date. it's not as simple as updating the numbers - there are many things in the wiki to update for each version, and i've yet to do this.
-
@rsn8887 said in Taito games not working anymore after update:
Where exactly is the the information which romset I need after updating?
From a game you are able to launch, open retroarch menu, the version of fbalpha is at the bottom left.
-
@rsn8887 Simplest is the recommendation given by @barbudreadmon , but you could also look in the verbose logging file and it should state the
lr-fbalpha
version. Since your FBAlpha ROMs are from the version included in RetroPie 4.0 - almost 2 years ago - there's a high chance your problem is using an outdated ROM. -
@robertvb83 said in Taito games not working anymore after update:
but i speak of lets say average users that just mainly want to play games. No way they look into that documentation before updating
I disagree. This is not a plug and play solution that is meant to hold your hand every step of the way. It's a learning tool and the docs are essential. If people don't want to study them and I do mean study them not read them, they have chosen the wrong hardware and software combination.
-
@barbudreadmon said in Taito games not working anymore after update:
@robertvb83 said in Taito games not working anymore after update:
"What the f*** i have to resource my roms that took me years to find a working set"
Or 2 minutes if you know how to use google search engine.
About the warning, as a developper, i'm confident about the fact people won't read it anyway, except perhaps if it's in a sign held by a cat or something.
you are probably right, i'm just saying, not everyone is a geek and learns all this stuff easily. some people just want to play.
so can anyone please input a big warning screen with a cat holding a warning sign before updating things that will make your setup unplayable for sure
-
You know, this is an unbelievably awesome project that people have donated their free time to build and have asked nothing in return. Retropie is just as much a work in progress as it is a success. It is ready to go out of the box in general, but there's tons of extras that are always being worked on, or that you need to tinker with yourself to get them working. That's the fun of it for a lot of us, you get what you put in.
More on topic, you should never update anything on any system unless you are explicitly familiar with what changes are being made to your system. I don't disagree that it would be nice to see more info about what updates are available, but keep in mind again that this is a free project and the community support is there if you do upgrade and have an issue. I treat my system as if it's always in beta...backup backup backup. Not just because of what may come down from the devs, but because I've made enough stupid mistakes that backed me into a dark, dark, corner.
-
Yes, it is a great project and a lot of work. But I support the OP's statement. Updates should always be transparent. Currently, the updates in RetroPie are completely opaque.
What I mean is that there should be a changelog and users should be able to read this log to get an idea what an update will do BEFORE performing the update. This non-existing changelog should have mentioned that updating fba will require an update of all the roms.
In my opinion, this is a basic usability feature that is currently missing, among many other basic ease-of-use features, from the RetroPie project.
There's nothing wrong with recognizing and mentioning shortcomings and possible improvements.
But yes, it is a great project. Now that I am using my RPi 3 again, I am really appreciating RetroPie and how far it has come.
However, there are many problems with RetroPie, mostly in terms of usability, and I think most of them are simply due to the underlying OS being a masterpiece of user-unfriendliness (as Linux has always been in my opinion).
-
@rsn8887 said in Taito games not working anymore after update:
However, there are many problems with RetroPie [..]
Just because your expectations are not met by the software does not make it a 'problem' for RetroPie.
Since the project itself mainly re-packages software from different sources, it's almost impossible to provide a complete changelog for what changes when new packages are updated - especially if you update from source. That doesn't mean updates are not documented
- RetroPie specific changes are always available in the project's repository (github.com/retropie/RetroPie-Setup)
- Point releases are detailed in the news page when they're released.
EDIT: I do agree that some updates might seem 'opaque', how do you think this should be handled ?
-
@rsn8887 said in Taito games not working anymore after update:
What I mean is that there should be a changelog and users should be able to read this log to get an idea what an update will do
You mean this: https://retropie.org.uk/2018/04/retropie-4-4-is-released/ or am I missing something?
-
@rbaker It sounds like he is asking for a detailed list of updates, probably something similar that pops up when you do Windows updates stating specifically fixed issues and versions.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.