PS3 RetroArch 1.7.1 Extended Version

STLcardsWS do not be nervous like this :p , it will fix itself.


Fix_It_Felix_Jr_pic_jpeg.jpg

Nervous? LOL No try and advise for best of the community. Not some noob on this project...

If i see something that is not best for a user then i say something (that simple). I seriously doubt there is many that have the experience as i do with this project in regards to knowing all the ins and out of the various cores. knowing the bottlenecks of various core and just the history of the project.. Many of these cores are not "NEW" to me on the PS3. many of these i tested back in the 0.9.7 - v1.0.0.2 releases and know there is some serious issues (some the PS3 will never overcome). doobz and myself were able to get alot of cores working. Some of them eventually became official cores later on and some did not, pete_uk as well did some work in getting the POC working.

I worked with many who did work on the retroarch projects and test builds over the years, I was using RetroArch PS3 before it was even released (back then called SSNES later changed to RetroArch since it was like the "SNES" name to much in the title). I know alot about the project

If bringing up concerns and valid issues is being "nervous" then well that is quite humorous.. My only goal is getting the best release possible up and reasons i am not afraid to make my concerns known if i feel they need to be made. I don't make the comments to take away from what these guys have done and do in this scene, both are great devs and people. However i want to offer some perspective on various things and things I am sure they may not of even considered.

I guess i just should shut up and not offer what i know or concern i feel are valid.? I do not think that is wise.
 
Last edited:
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)

Good, if you want to get some progress then you need to test something new. ;)

As I said before, they were labelled like working cores since I read OK on the table of the cores on the private area and I thought they were good ones. Tbh i've been surprised that they didn't work. O_o

Then I have had a doubt, am I wrong? I just reviewed the old thread and I noticed that OK was only intended for compilation purposes. The thread is 6 months old, not just 2 days old, so I couldn't remember it anymore. In fact on the same thread I (me, myself) tested some cores and though they compiled i reported them like on the table here below.

As you can see, I made confusion because I read bad or too fastly the old thread, so it's a fault of mine.

Please don't tell me that the scene deserves stable releases, because it's the reason for which I started to do these unofficial releases some years ago, you should rememeber it. :)

I had no reason to release it without alpha or beta label since I already used those labels in past. I simply thought that OK meant that the cores worked, I just read bad. My mistake. I always try to do everything such stable as possible, it's for this reason that I removed other 6 cores before than releasing (3do, crocods, desmume, etc). I tested them in the previous six days, they gave black screen and then I removed them. I just put into these 4 cores (puae,atari,dosbox,mednafensnes) only because i thought they were okay.

Probably I have had too hurry, I could take another week to test everything with more quite and then to do the release.

Now stop debating with the administrator of my favourite psx site. :P
I follow you since 2010 when the scene started and you wrote in another forums while i was active only on italian forums but i read you every day. :)

Let me see if I'm able to do a more appropriated release. Not too bad this one though, you didn't get freeze loading cores but loading roms that's a bit different.

Anyway https://translate.google.com/transl...o-retroarch-1-7-1-extended-version/&sandbox=1
So somebody, in other places, warned users about possible freezes with this release.

CoresBuildableWorking
4doYes
81YesYes
2048YesYes
atari800YesBlack screen
basilisk2Yes
bluemsxYes
bsnes_cplusplus98Yes
cap32YesBlack screen/freeze
crocodsYesBlack screen/freeze
desmumeYes
dosboxYesBoot at the main menu, it could work.
emuxYes
fbalphaYesYes
fbalpha2012YesYes
fbalpha2012_cps1Yes
fbalpha2012_cps2Yes
fbalpha2012_cps3Yes
fbalpha2012_neogeoYes
fceumm YesYes
fmsxYes
fuseYesBlack screen
gambatteYes
genesis_plus_gxYesYes
gmeYes
gpspYesWhite screen
gwYesYes
handyYesYes
hatariYesBlack screen
lutroYesYes
mame2000YesYes
mame2003YesYes
mednafen_gbaYes
mednafen_lynxYesYes
mednafen_ngpYesYes
mednafen_pce_fastYesYes
mednafen_pcfxYesYes
mednafen_psxYesNo
mednafen_snesYesYes, low fps and bad audio
mednafen_supergrafxYesYes
mednafen_vbYesYes
mednafen_wswanYesYes
meteorYes
mgbaYesYes, it finally works
nekop2Yes
nestopiaYesYes
nxengineYesYes
o2emYesIt should work, keyboard required
pcsx_rearmedYesNo
picodriveYes
pocketcdgYes
pokeminiYes
prboomYesYes
prosystemYesYes
puaeYesBoot at the main menu, it could work.
px68kYesYes
quicknesYesYes
remotejoyYes
scummvmYes
snes9xYes
snes9x2002Yes
snes9x2005Yes
snes9x2010YesYes
stellaYes
tgbdualYesWhite screen
tyrquakeYesYes
uzemYes
vba_nextYesYes
vbamYes
vecxYesYes
vice_x64Yes
vice_x128Yes
vice_xplus4Yes
vice_xvicYes
virtualjaguarYesYes, low fps and bad audio
xrickYes
yabauseYes
3dengineGL
blastemDYN
bnesC11
bsnes_accuracyC11
bsnes_balancedC11
bsnes_performanceC11
bsnes_mercury_accuracyC11
bsnes_mercury_balancedC11
bsnes_mercury_performanceC11
chaigameC14
citraGL
craftGL
dinothawrC11
dolphinC11+GL
easyrpgC11
ffmpegGL
fsuaeC11
mame??
mame2014 C11
mame2016C11
mednafen_saturnC11
melondsC11
mrboommrboom.c is too big, 19 Mo...
mupen64plusC11+DYN
openlaraC11
parallel_n64opengl+DYN
pcemDYN
pcsx1pcsx_rearmed
ppssppDYN+GL+C11
psp1ppsspp
redreamC11+DYN+GL
reicastC11+DYN+GL
rustationRust
sameboyC11
stonesoupC11
tempGBANot ported, it's only for PSP
video_processormissing libv4l2
 
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


Libretro Cores

  • 81_libretro_ps3
  • 2048_libretro_ps3
  • atari800_libretro_ps3
  • bluemsx_libretro_ps3
  • dosbox_libretro_ps3 (Black screen)
  • fbalpha_libretro_ps3
  • fbalpha2012_libretro_ps3
  • fceumm_libretro_ps3
  • fmsx_libretro_ps3
  • freeintv_libretro_ps3 (bios required)
  • gambatte_libretro_ps3
  • genesis_plus_gx_libretro_ps3
  • gw_libretro_ps3
  • handy_libretro_ps3
  • hatari_libretro_ps3
  • lutro_libretro_ps3
  • mame2000_libretro_ps3
  • mame2003_libretro_ps3 (for best results use MAME 0.78 romset, Note: A lower version Romset are better then using a higher., but 0.78 is best to use)
  • mednafen_lynx_libretro_ps3
  • mednafen_ngp_libretro_ps3 (have not tested but is an official core, this core has been broke in the past)
  • mednafen_pce_fast_libretro_ps3
  • mednafen_pcfx_libretro_ps3
  • mednafen_snes_libretro_ps3 (Unplayable 20-25 FPS)
  • mednafen_supergrafx_libretro_ps3 - Clone of Mednafen_PCE-Fast (plays both SuperGrafx and Turbo Grafx)
  • mednafen_vb_libretro_ps3
  • mednafen_wswan_libretro_ps3
  • mgba_libretro_ps3
  • nestopia_libretro_ps3
  • nxengine_libretro_ps3
  • o2em_libretro_ps3
  • pokemini_libretro_ps3
  • prboom_libretro_ps3
  • prosystem_libretro_ps3
  • puae_libretro_ps3 (Black Screen)
  • quicknes_libretro_ps3
  • snes9x_libretro_ps3
  • snes9x2005_libretro_ps3
  • snes9x2010_libretro_ps3
  • stella_libretro_ps3
  • tyrquake_libretro_ps3
  • vba_next_libretro_ps3
  • vecx_libretro_ps3
  • virtualjaguar_libretro_ps3 (unplayable 20-25 FPS)

Please can anybody test bluemsx and fmsx? Thanks

snes9x2010 works fine, snes9x2005 works at half of the full speed
fbalpha2012 and mgba work
mednafen_pcfx works but with poor performance as in the previous releases.
2048 works
81 works but it's not compatible with all the roms.
Handy and mednafen lynx work and are alternatives since some roms work with one and not with the other one and viceversa.
 
I just want to say another THANK to @Zar and @Ezio for their hard work on RA PS3.

I know there is a few bug and problem with 1.7.1 Extended (and everyone knows it's usual and it will be fixed) but the important thing is;
This 1.7.1E is a way better than official RA created by Libretto in Retroarch Site. Official 1.7.1 just includes 21 cores and so many great cores like MAME & PCE are removing from their build. But this build from @Ezio includes more than 40 full working cores with updated cores. I really appreciat for everyone who contributed to create this great build. (: (:
 

They did because @thehero_ (is a good guy and reported) and he is a member here as well and I am sure read through comments and then even tested himself. Not all sites do that......

Good, if you want to get some progress then you need to test something new. ;)

I did and seen the same issues i have seen in the past on some of these cores . That why i knew before even launching there would be issues. Then i launched and my suspicions were confirmed..

Please don't tell me that the scene deserves stable releases, because it's the reason for which I started to do these unofficial releases some years ago, you should rememeber it. :)

If you feel the same why should i not say it? I know your wanting to do alot of good here and i believe you are and have done so much good already, (THANK YOU!!!!!) No doubt you want this to be as polished as possible. I do as well, so that why i like to see it handled a bit differently so that we do not add more confusion on a port that badly needs to be stable and we only get to being stable by using cores that actually work well. (many new ps3 user;s and i doubt anyone is going back to use the older more polished release) (like i suggested in the past an add-on package for these PoC cores is a much better approach and in itself educate the user better without even having to explain it or rely on others to explain it. when you see "RetroArch PoC Cores Addon.pkg" its kind of self explanatory. Also more user's are wanting a build that just has the working cores/play full speed then the PoC testing builds.

My goal is the same as yours, we are just seeing a different path for it.
Now stop debating with the administrator of my favourite psx site. :P
I follow you since 2010 when the scene started and you wrote in another forums while i was active only on italian forums but i read you every day. :)

Let me see if I'm able to do a more appropriated release. Not too bad this one though, you didn't get freeze loading cores but loading roms that's a bit different

I been around a long time, and i know how news and word flows. So that goes into my thinking as well

No this release was not bad whatsoever, what was bad was just some of the dialog missing (which adds to the confusion). user's are going to have issues with some cores .

I am more then happy to help in anyway i can.
I would also like to get alot operation details going for the PS3 as well. (something that has always been missing) Bios requirements and all.
 
Last edited:
Hey ezio, you could give me a file witch Polish translation, in December, I corrected the translation but some things have happened and as I see it, some of my improvements are not quite successful. And at the next edition, I would like to improve it.
 
Hey ezio, you could give me a file witch Polish translation, in December, I corrected the translation but some things have happened and as I see it, some of my improvements are not quite successful. And at the next edition, I would like to improve it.
What do you want to know?
 
I don't test fMSX yet.

but when i trying to load Donkey Kong (1982).col with bluemsx, it just freeze my PS3 with black screen

Are you using 'Databases' and 'Machines' folders? Read here http://docs.libretro.com/library/bluemsx/

I do not want to know anything :P I want to improve the translation I did for 1.7.0 :p
Ah okay. :)
Then just do it and i'll update the frontend to latest source once I understood which cores remove to do the build more stable.
 
but when i trying to load Donkey Kong (1982).col with bluemsx, it just freeze my PS3 with black screen
I confirm I checked this Donkey Kong (1982).col and other roms with the same ps3 freez effect.
Ah okay. :)
Then just do it and i'll update the frontend to latest source once I understood which cores remove to do the build more stable.
And you would have a .h file somewhere because the one I uploaded for liberto disappeared from the server?
 
Did you use bios?
Need a bios? Where to put it in what catalog? First time I see that in RA you have to install bios :/
FMSX too black screen but without freez it is possible to return to the fast menu.
 
Last edited:
I confirm I checked this Donkey Kong (1982).col and other roms with the same ps3 freez effect.

And you would have a .h file somewhere because the one I uploaded for liberto disappeared from the server?
Yes, i have it. I saw you fill a pull request on december for polish update but you used the c files instead than the necessary header file. Then Twinaphex fixed it himself.
You need to modify this one https://www.sendspace.com/file/s884c7
 
Try Bios^ then :)
(if the notes say a bios is required and you do not have it and not booting a game i think the issue might be obvious or at least the next option to try)
 
But, where can i find BIOs and what can i must do with them @Ezio ??

We don't advise on how to obtain copyrighted files..

.Some core need them in the same folder as the game your botting, where other cores rely on them in the "system" folder of RA. but most will always work with it in the game folder. every core can be different.
 
Back
Top