Fresh impressions from someone that used several Emulation frontends over the years.
-
Two more UI experience additions, before I react to the the reactions - because I guess thats what millenials do these days...
First - make the Emulation Station Menu "endless" (i.e. pressing up on the first item moves you down to the bottom one), second - make "shutdown" the last option in the menu , NOT "quite to command line". Because - guess who uses the quit to command line option in the main menu in the grand scheme of things - NO ONE. (I quess, people that cant press F4 on a Keyboard they are about to use, for the command line anyway... (dont get rid of it, move it to a less prominent place).
As far as the reactions are concerned, you are just the NES controller loving, self aggrandising 45 year olds, that have lost touch with modern UI sensibilities, I might have imagined you to be... ;) Screenshot sharing as a feature (although present in all modern consoles as a standard) - is seen as sacrilege. UI and user experience f*ck ups are internalized as "funny quirks" -
and "if you had looked hard enough, you'd found a way to configure..." nerds are trying to help non existent users - because UI defaults and "configuration posibilities" arent the same.
Just for the record though - I've used Retroarch for many years, I'm familiar with its base settings and at least the better part of ithe individual core options, and I have no Illusions, that the fork ripoffs that are out there have done nothing more, than to customize some of Retroarchs defaults.
What I am saying is - that you should think about defaults -
UI, control schemes (hotkeys), feature set, streamlining settings instead of adding one block on top of the seven others, ...
Because of a "90% of facebook users never look at the settings" type of argument.
You drag with you really arcane concepts and sensibilities, have a tendency to want to stick to "the familiar", even when Retroarch itself has left you behind in terms of seeing the need for better UI design, and the "default" to you is an afterthought.
(The bios folder doesnt get copied over using the USB fsync method, sync is uni directional, ssh on the current stable image doesnt work out of the box (key creation issue on part of that build of raspian), new emulators dont get added to emulation station (I guess when "only scan for "rom" files" is enabled), ...)
And you have never experienced the "console centric" emulation plattforms that came before. Or at least you havent internalized their findings.
Instead I read interviews you give that talk about morale and enthusiasm being down, or getting "that one core you love to work" (ATTENTION, the ScummVM Core is unusable for the better part of a year now, because of jumps in analogue stick mouse emulation - Im sure that has been forwarded across a dozen of github issue trackers by now - but who among you really cares... It shouldt be such a simple fix, but its never fixed...) while not identifying the most basic of issues -
you have a usability and accessibility problem.
Fresh eyes, criticism. Thats all I'm offering. I find a better experience with the multitude of commercial emulators, and Retroarch on android based plattforms - so its not for a lack of alternatives...
(Want to know whats funny to me? That your defaults currently drive people away from ppsspp as an emulator, and tell people thats more "easy" to use lr- ppsspp, because it comes "preconfigured" with retroarch inputs.... While PPSSPP actually WIPES THE FLOOR with Retropie UI and menu navigation wise (offering visual representations for savestates, having a legable interface...) - AND is the better emulator in the first place, making PSP games "boarderline playable" on a Pi3 in the first place... I wonder who is managing the project - making those kinds of decisions...)
That said, I like the retroarch concept, because of the "all in one place" nature of it. Thought I could point out, where it fails horribly , went out to take names, instead of making pals.
The answers showed an absolute lack of interest. So I guess that the issues are unresolvable.
Also, of course I will not donate hours of work to this project, theres no use.
In case someone sees value in the criticism and the logical inconsistencies I've pointed out - you are welcome. Please run with them, as you see fit.
-
@notimp said in Fresh impressions from someone that used several Emulation frontends over the years.:
In case someone sees value in the criticism
I see. Suggestions for improvements are welcome here. Making demands is not.
Maybe you would get more attention from the devs with a more polite speech. Maybe suggesting things rather than dictating what you think that must be done.
If you know how to implement the stuff you want to see on RetroPie, submit a Pull Request. This is a welcome action.
I would like to suggest you to try recalbox. It seems to be a project with the same goals as you are trying to impose to RetroPie.
-
Then help me understand.
(Also, no - because Recalbox as a fork is not where I see the "public interest" converging. The Linux principle of "just fork, bro" is something thats alien to me as well, because it ensures, that "unsolvable differences" and prolonged in a cavalcade of projects that are more and more thinly supported and hardly ever accumulate traction to get them anywhere. (ie. in the end everyone is worse of for not speaking out and just "doing their own thing"))
Reading between the lines, except for the "screenshot sharing feature" which would require a substntial amount of workhours and API integrations I can see not everyone agreeing with - all the "suggestions" are changes in default UI behavior/UI.
If not even the need to get away from a DOS (DOS!) style interface thats unlegible on 55" TVs from a normal living room sitting distance is "accepted" (stop with your demands, kiddo)- I would like to know why...
No 12 Button controller defaults, because people want to sell 5 USD Snes Controller ripoffs from china in their on page stores to "help the community"? Because you have to cater to the "build my own cabinet" market, that throws in the additional trackball once in a while? Because you just hate a UI that makes more sense, than hiding scripts that should be default toggles in (literally) the sevenths sub menu under "tools"?
Because you want Retropie, at heart, still only ever to be usable with a keyboard, a mouse and maybe a SNES controller attached?
I'm turning off all the snark, if this has the potential to become a discussion about UI defaults, and why you are sticking to them. I also am very willing to just listen to arguments, if there are any. I'm willing to learn.
But I dont accept the usual - "we dont like them ideas in here, boy - go look at them forks" attitude thats just there to prolong egos.
Also - as far as the "demands" approach is concerned, I use it to put some weight behind my statements, to get people to actually look at the arguments.
Whats the most likely use case here? A young tween/thirtysomething, picking up a 35USD Pie and having a PS3 controller lying around, or ordered from ebay.
He/She will be playing in the living room, on a TV - only being familiar with game UIs from the past decade and an iPhone UI.
Why dont cater to that audience, at least a little - with some, even optional, UI defaults that make some sense.
Also UI, is not something - an unattached person will "fix for you" doing individual pull requests. At least not very likely. Its a pretty integral part of the whole thing. (Hard to change. People dont like changes made there, because they like whats familiar - (and thats true for me as well.. ))
-
@notimp
the UIs are how they are because it's much easier to make these 'DOS' style interfaces than the literally 1000s of hours it would take to make and maintain some kind of elaborate UI that does everything we need.so it's obvious and expected that a project with 0 full-time programmers on it (and a handful of people who chose to spend a portion of their free time on it) has plenty of room for improvement, but it's similarly obvious that demanding such features will be met with "ok, you do it". what else do you expect to happen?
you may see a lot of failings in retropie as it is, but the current volunteers are barely keeping up with the maintenance of it as it is. there's a whole host of fundamental work to be done before we even get to 'let's spend years building a unified UI' stage.
the fact that you are even able to complain about 'quality of life' stuff is a veiled compliment to the vast efforts of retropie's developers, as the whole thing at least hangs together for you to get that far. you're welcome...
First - make the Emulation Station Menu "endless" (i.e. pressing up on the first item moves you down to the bottom one), second - make "shutdown" the last option in the menu , NOT "quite to command line". Because - guess who uses the quit to command line option in the main menu in the grand scheme of things - NO ONE. (I quess, people that cant press F4 on a Keyboard they are about to use, for the command line anyway... (dont get rid of it, move it to a less prominent place).
these are good suggestions and easy to implement. i highlight them as they are buried in your misplaced rant.
-
RetroPie is not Emulationstation and Recalbox is not a fork of RetroPie. RetroPie-Setup is just a collection of shell scripts for Raspbian (and Debian based distributions). Shell scripts are perfectly suited for a CLI. Emulationstation was maintained by Aloshi in the past. Development stopped and there was little interest to maintain 3rd party software for a long time. If you are a C++ coder you can contribute any change you wish. You can also express a wish. But don't demand anything. Why should someone spend free time for features which are only important for you?
Recalbox on the other hand is a complete buildroot linux distribution with customized Emulationstation. It should provide a more out of the box experience. So Realbox should be the right choice for you.
-
@notimp not adding a lot to what others already said, but there's a very simple and easy reason as to why the controller default is not the 12 button controller.
It's simply because the majority of the consoles being emulated did not have such a controller. The fact that you may use such a controller (I do it as well) does not make it the default. In fact, most systems that run on the pi except for the psx, N64 and Dreamcast have a maximum of... 6 buttons, unless I'm missing something obvious.
And yes, a lot of people run this with controllers that are similar to the original ones, or on arcade cabinets. But once again, EmulationStation is not RetroPie.
The fact that this may be recommended as a fork to people - regardless of whether this may be a problem to you for whatever reason - just speaks volumes about what it has achieved, in spite of what it hasn't. The fact that other forks are recommended is also great - I have no desire for a single platform future as people's needs are different.
If you do want to help and have a productive conversation, please leave the attitude at the door.
If you just want to come here and release some frustration about how RetroPie isn't what you wanted it to be, and you still can't believe why people are recommending it, then I'm sorry but I don't think you'll get a lot of traction. In fact, maybe use that as an opportunity to consider that different people have different needs, tastes, levels of tolerance to things that may be missing, and above all gratitude for what they're getting rather than a sense of entitlement for what they're not, which is really what ends up coming across in your opinions. And that nobody's view of the world, in isolation, is the right one.
I don't think anyone here would object if most things you say were implemented, but you seem to misunderstand what it is that people behind the project do, how much time and dedication it takes, and that if more people would be willing to help, more could be achieved.
Also, for my own learning, I'd like to know what RetroPie forks you refer to. I'm not aware of there being any, though I'm not well versed there.
I know of Lakka and Recalbox as alternative projects, but they are not forks - each of them is a solid standalone project in their own right, with different goals.
Was it any of these you were referring to? If not, please do share. Thank you.
Have a good weekend.
Edit: and just for credit where credit is due, "This includes hacks like "map leftstick to digipad inputs on non analog stick game plattforms" which is something I'm sure more beginners would like to use - but good luck finding that piece of code in seventh nested submenu." is certainly a good point. Thanks for raising it.
-
The extent to which some people criticize something that is given to them absolutely free of charge never fails to astound.
Here you have very skilled people donating free time and resources to contribute to a project that anyone can obtain, modify and submit contributions to - and the first thing that comes to your mind is "I'm going to register for the forum and write a post that shits all over their efforts and i'll title it 'fresh impressions'!
-
Thank you for getting that out, Lord knows I couldn't...
-
@notimp said in Fresh impressions from someone that used several Emulation frontends over the years.:
Whats the most likely use case here? A young tween/thirtysomething, picking up a 35USD Pie and having a PS3 controller lying around, or ordered from ebay.
He/She will be playing in the living room, on a TV - only being familiar with game UIs from the past decade and an iPhone UI.
Why dont cater to that audience, at least a little - with some, even optional, UI defaults that make some sense.
I am actually really glad RetroPie doesn’t cater to a particular audience and has an open, DIY attitude when it comes to solving one’s own design challenges and ideas. That is the spirit of the Raspberry Pi anyway. I am NOT using it with controllers lying around or bought on ebay. I am NOT using it in the living room on a TV. I am not trying to cater to game UIs from the past decade. My project is an arcade system, complete with actual arcade controls and designed to run games that are 30 years old! For me, RetroPie is the best option, and I recognize there are opportunities for improvement, but I also understand the effort it takes and I can contribute my own time and experience where I am able. It’s a community, not a commercial product, and one that I have been proud to be a part of.
-
I find retro pi extremely friendly to use.
A few small niggles here and there but honestly the work done over the years is really good.
There are tons of other emulators on other systems that are pure brutes to get working never mind configure.
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.