DEX357
Member
yes, I confirm, it's laggingBeetle SNES 25 fps (not really playable)
yes, I confirm, it's laggingBeetle SNES 25 fps (not really playable)
did you try to boot a game , That is the question, not if it loads a core into retroarch.
Yes you have to connect the mouse, but if you load the alpha and set the parameters and press ok then it will hang, it does not support pad. Also atari - st/ste/tt/falcon (Hatari) does not support pad. but after plugging the mouse, it reacts poorly to clicks with mega delays, and the cursor flies like crazy. And after turning on OK, ps3 also freez.I load "Shadow of the beast III" rom and this show up:
View attachment 11239
I can't move the pointer or do anything with this menu. But i can go back to Retroarch or XMB menu. So i don't know it's kind of freeze or just needs mouse & keyboard to run the game.
Yes you have to connect the mouse, but if you load the alpha and set the parameters and press ok then it will hang, it does not support pad. Also atari - st/ste/tt/falcon (Hatari) does not support pad. but after plugging the mouse, it reacts poorly to clicks with mega delays, and the cursor flies like crazy. And after turning on OK, ps3 also freez.
Yes.CFW only, right?
So, these Cores are freeze PS3 during load core or load ROMs :
- P-UAE
- VICE C64
- DOSBox
And these are load with lag and low fps:
- Atari Jaguar
- Hatari
- Beetle SNES
- P-UAE
- VICE C64
- DOSBox
These cores work well as separate homebrews and there is no problem with them just went wrong to add them to RA.
Beetle SNES this core I see for the first time and weakly does not need to be added when it is optimal the same with Jaguar was once but my request was removed, because why a core that can not be used at most it would be necessary to refine the emulation and it will take time. Hatari I saw as only homebrew for 3.55 I did not see the + version, so on 4.81 / 82 it does not install on but probably on old cfw it worked well.
Nope i can't install it on 4.81, it say error code at installation. Exactly the same as the standard version of dosbox without modifying files on 4.xxThe 3.55 one, should work on 4.xx CFW,. just needs to be resigned.
Not included,- VICE C64
l.
Nope i can't install it on 4.81, it say error code at installation. Exactly the same as the standard version of dosbox without modifying files on 4.xx
Some quick test and also some of the reported comments
(Testing not complete and anyone that can report on a core please do so.)
- NON Working / Issues
- Official Cores (appeared in previous official releases)
- Clone / Duplicate
Yeah, you're right. As you should know, I like homebrews such stable as possible, in fact my previous releases were stable and well working since I tested a lot of cores with several roms for each one of them.One of the main missing things for the retroarch ps3 port are the testers.Some of these cores not sure why are added, (was it beneficial to add some of these? )As its just going to add confusion on a release that has been buggy for sometime in many releases (RetroArch PS3). I think the goal should to make the most stable release as possible. So that would be using only cores that are actually playable.
Was beetle SNES really needed to added when its 1/3 of the needed speed and there is already 3 working SNES cores included. Don't understand why some of these are added. I do like seeing the PoC stuff but not when its not needed or in a build that is just going to add more confusion to user's especially new user's and if its not explained there are bugs or problems with XX core and XX core that's a problem as well.
Love the work guys and love everything you do @Ezio and @Zar but i still think there is issues we could be avoiding to make this a great release for the PS3. if something is going to aggravate a user's and not work why add it? ...
For me hard to report something i know will have alot of issues. Can't really say checkout this new RetroArch build with 44 cores when i know in back of my mind there is 10 or so that you could drop (and should drop) because they either do not run / duplicates or perform at such a low speed they are not worth loading the core. None of that info is in the release notes or anything so people and as news sites post this that info will not carry over and you have alot of post saying this does not work and this is not working. Don't try this release i could not get this and that to work.. ect.. When it could of been a release with NO problems on the included cores.
RetroArch needs a stable build with all working cores. (that has been missing for almost 2 years now if not longer)
- The official ones when stable are missing all the cores.
- The unofficial one when stable are providing the missing cores and also many non-working/slow emu's
I would like to thank the guys tested cores here and reported feedbacks, they are really useful, unfortunately testers for ps3 retroarch are rare goods.
Various people offered to test in this forum just the other day prior to release .
this was not presented as a testing build. it was presented as moreless a stable release with now 44 cores included. (that were tested) That is what other places are going to report as that is the message that was being relayed
Just so many incomplete / non functional RetroArch PS3 builds out there already. The scene deserves a stable release and if testing is the purpose here , its needs to be labeled as such. because otherwise you start to see exactly what was detailed appear in the news at places
example
https://translate.google.com/transl...retroarch-1-7-1-extended-version/&prev=search
(which i think is going to just setup a user for some disappointing experiences and frustrations)
I know the intentions are GOOD, and i think the release is great but i think it could of been handled a bit differently to avoid some confusion.