FBAlpha, support Mouse?
-
@barbudreadmon The dats folder from the source repository is automatically added in the installation folder for
lr-fbalpha
in RetroPie. -
@mitu people are supposed to read doc at https://retropie.org.uk/docs/FinalBurn-Alpha/, and the dat there is wrong, i don't think many people will check the sources of what they built for potential dat files
-
@barbudreadmon you can update the wiki to point to the right one if you want. i told the person who mistakenly changed it to the wrong link, but i'm tired of policing the wiki if people won't correct their mistakes :/
-
@barbudreadmon
THX for the DAT file -
@dankcushions said in FBAlpha, support Mouse?:
you can update the wiki to point to the right one if you want
Iirc that's what i did a long time ago, i don't want to do it again considering i am not a retropie user and i have my own projects to work on. This is especially pointless if anyone can replace it by a link to some crappy copy.... you should consider making the wiki not publicly editable...
-
@barbudreadmon that's not my decision to make. i fixed the link - takes 5 seconds.
one thing would be nice if the dat filename itself didn't change every version as it breaks the link. i am not sure there's so much utility in having the name change, anyway, when git tracks the history.
-
@barbudreadmon Making the wiki non-editable by normal users would prevent vandalism, but also contributions from the community. Wikis thrive on the latter, so I would respectfully advise against closing that door.
-
@dankcushions said in FBAlpha, support Mouse?:
one thing would be nice if the dat filename itself didn't change every version as it breaks the link
Your point is valid so i changed this behavior and updated your wiki.
@Clyde said in FBAlpha, support Mouse?:
also contributions from the community
I have also seen some of those "contributions from the community" in arcade compatibility list, basically people with wrong romsets saying "this game doesn't work with emulator XXX", that's when i stopped participating in this kind of docs/lists. Imho, the docs/lists about arcade should be writable only by a handful of people who understand what they do, or at least some kind of validation should be required.
-
@Clyde said in FBAlpha, support Mouse?:
also contributions from the community
I have also seen some of those "contributions from the community" in arcade compatibility list, basically people with wrong romsets saying "this game doesn't work with emulator XXX", that's when i stopped participating in this kind of docs/lists.
I'm also no friend of such lists, they tend to be outdated too quickly if the software in question is still updated regularly. I'm more concerned with general docs and guides that don't change that often, like the Retropie Docs. Those also tend to require more effort to write than a mere list entry, which helps to protect them from "drive-by edits" a little more than lists.
Imho, the docs/lists about arcade should be writable only by a handful of people who understand what they do, or at least some kind of validation should be required.
Both of those approaches put all the work on the shoulders of that handful of people who, in most cases, are doing this in their freetime. That may result in either a poorly maintained wiki and/or overworked maintainers.
I think it's a matter of perspective. While you seem to see greater risks than benefits in an open wiki, I see it the other way around. Maybe we should leave it at that at this point, lest we hijack this thread with our discussion. 😇
-
thanks for changing the filename @barbudreadmon!
i am technically in charge of the compatibility lists but it's a full time job to try and police them and clean out the crud. every time i leave one for a few months I pretty much have to put in a revert back to the beginning. a lot of the bad edits are just misinformed or accidents, but some of them get full of racist crap, also. unfortunately google sheets doesn't give you enough control over protecting parts of the sheets, unless you stop them being edited at all. i don't want to do that but i am tempted.
i think they're a microcosm of the internet - you give people trust and anonymity and they will let you down :)
-
@Clyde I added a second mouse device type, the first one is only using the ball (i think that's what you guys need ?), the second one use the ball and also map buttons to the mouse. That way everyone should be happy.
@OliB Support for analog controls in centipede should be complete today or tomorrow.
-
WOW! THX U so much! So'll wait until you implement it and update fba from source again.
-
@barbudreadmon Thanks, that sounds great. I'll test it today or in the next days. My Pi is doing the update from source right now, but I don't know yet if I'll have the time to test it later today.
AFAIK there should be no need of different mouse devices for trackball/spinner/lightgun, because they all use the same
/dev/input/event…
devices. (Multiple mouse devices may be needed for games with multiple mouse-type devices, though.)Trackballs and lightguns will use both axes of a mouse device, whereas spinners will use only one axis per spinner. For two spinners, that may be X and Y of a single mouse device if they are connected that way. Others, like the USB adapters that come with the SpinTrak spinners, will map them as separate mouse devices and only use their X axes.
https://retropie.org.uk/docs/Spinners,-Trackballs,-Lightguns,-and-other-Mouse-Devices/ describes the different kinds of axis mappings in great detail.
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.