PS3 RetroArch CE (Unofficial - Community Edition) Beta 4

[Lambada]

Hey @JediKnight007 do you know which core runs System32 Arcade? (Golden Axe 2: Death Adder)
I'm recreating my playlists all over again because I uninstalled Retroarch 1.7.6 and I'm going to start using the CE edition.
And which runs Neogeo MVS (console mode) roms?

 

[JediKnight007]

Hey @JediKnight007 do you know which core runs System32 Arcade? (Golden Axe 2: Death Adder)
I'm recreating my playlists all over again because I uninstalled Retroarch 1.7.6 and I'm going to start using the CE edition.
And which runs Neogeo MVS (console mode) roms?

MAME 125 runs System32, but it's very choppy. FB Neo might also run it (haven't been playing with RetroArch for awhile), but it will also probably be choppy. FB Neo will play Neo Geo fine, I believe there is an option in the UniBios that allows console mode.

 

[Lambada]

The second problem looks like a "hacky patch" (not used by official retroarch), it affects the ozone interface (in XMB interface is not visible because there is not a "navigation bar" at bottom)

As you can see the icon names inside the ozone theme are correct, and the image represented by them is correct too, are 4 small circles that represents the 4 buttons that needs to be pressed with the right thumb finger
Im mentioning this because at some point i was wondering if the problem was related with the icons (someone renamed or swapped the PNG files), but nop, the ozone icons are fine

But... the way how ozone is displaying the button info is wrong (so there is some problem somewhere else), i mean... in the default installation of retroarch PS3, if we press "cross" button in the dualshock retroarch takes it as an "OK"... and circle button as "Back", but what can be seen in the screen is the opposite

Also, there is an option that seems to be related:
[Setings]->[Input]->[Menu Controls]->[Menu Swap OK and Cancel Butons]

By default that option is [OFF]... if you change it to [ON] the buttons swaps (but the information text in main menu of ozone swaps too, and becomes incorrect again). Try it, is bewitched

I been taking a look at how the buttons are mapped in other controller profiles related with the PS3 and i dont see anything strange in them, this is why i think this is some kind of "hacky patch" that was applyed specifically to the retroarch PS3 port in the source code... and this is why i was not having success when i was trying to replace the .cfg file (because the button mapping is hardcoded ?)

Some of this config files could be interesting
https://github.com/libretro/retroarch-joypad-autoconfig
This one specifically, it seems to have the button mapped exactly like in the USRDIR\autoconfig\SixAxis Controller.cfg included in all the "Retroarch Community Edition" versions published so far
https://github.com/libretro/retroarch-joypad-autoconfig/blob/master/hid/Sony_PLAYSTATION(R)3_Controller.cfg





Edit:
I said this looks like a problem because i guess this option should be enabled by default, the description says:
[Setings]->[Input]->[Menu Controls]->[Menu Swap OK and Cancel Butons]


If at some point someone implements the required functions to get this info from xRegistry.sys (this way we know the user preferences in this mattter) we can change it automatically at the first boot...
But in the meantime, the way how is working the actual retroarch PS3 is placing us in the "western" boat, right ?
In a default installation of the "retroarch community edition" we have the cross button mapped to "OK" and circle to "Back" so yeah... whoever decided that gave a preference to the western button mapping, so the default state of this option should be [ON]

It looks like there is a bug in the update information about the cores. If I go to Core Downloader, select to update a core manually, wait until it completes the update, then try to download the same core; for some cores it says that the latest version is already installed, but for others the core is downloaded again.

These icons are swapped. Also at certain distance from the screen they look like d-pad icons.
View attachment 32976

You are right @sandungas and @aldostools , in the Ozone Theme the navigation tips at the bottom are wrong. The OK and Cancel buttons are swapped no matter if you change the settings at "Input/Menu Controls/Menu Swap OK and Cancel Buttons". If you enable it, the buttons change and the icons also change.
The problem are not the PNG files, are just that the icons below are not linking to the correct PNG.

@Crystal could you take a look when you have time? It should be easy to fix.

 

[sandungas]

@Crystal could you take a look when you have time? It should be easy to fix.

Initially i also thought that it could be easy to fix but now im not so sure because there is another "hack" indirectly related with this. The gamepad profiles (files named sixaxis.cfg etc...) are also "hardcoded" in the retroarch PS3 port.
With this i mean... if you try to load a different gamepad.cfg (or you try to create your own customized) you are going to realize that are completly ignored
I realized about this missing feature when i was trying to figure what was happing with the incorrect mapping of the button images in the ozone main menu... but also because i dont like the message "sixaxis controller detected" that appears everytime we boot retroarch (because my controller is a dualshock3 not a sisaxix)

In my oppinion the best description is "PlayStation 3 Controller" because is more generic
As far i remember there is a gamepad.cfg in the official retroarch repository that shows that name (well, they have a lot, i was lurking them for curiosity sake and to try to understand how are mapped the buttons)

Edit:
I dont remember well the details of all this... but if someone is interested scroll back in the thread, probably i wrote an small wall of text trying to explain it

 

[Shadow Moses]

I may have come across a bug. I deleted some games from a playlist I created on the online playlist editor. The next time i tried to run RetroArchCE it would take me back to XMB. the only way I found to resolve it was to delete the playlist. Deleting games from playlists seems to be broken.

 

[Lambada]

Demons of Asteborg (new indie game release) rom for Mega Drive isn't working on Retroarch with Genesis Plus GX. It gives black screen and freezes PS3.
Probably the CE core needs to be updated. It works on latest Retroarch for Windows x64.

 

[Neoguto]

Hi there!!
I'm a newbie on PS3 and have been installed the Retroarch CE on my son's PS3, but I wanna know, were can I download the cores to that version!!

Thanks!!

 

[Geese howard]

Hi there!!
I'm a newbie on PS3 and have been installed the Retroarch CE on my son's PS3, but I wanna know, were can I download the cores to that version!!

Thanks!!

https://xbins.org/libretro/nightly/playstation/ps3/latest/cex-ps3/

 

[Neoguto]

https://xbins.org/libretro/nightly/playstation/ps3/latest/cex-ps3/

Thx!!

 

[Neoguto]

So, there's any Sega Saturn working on retroarch?

 

[JediKnight007]

So, there's any Sega Saturn working on retroarch?

Not on PS3.

 

[aldostools]

So, there's any Sega Saturn working on retroarch?

There is a very early, and somewhat laggy version of Sega Emulator for PS3 released in 2010. No further development is known for PS3.
https://store.brewology.com/ahomebrew.php?brewid=3

It is a standalone emulator, not part of retroarch.

 

[Neoguto]

There is a very early, and somewhat laggy version of Sega Emulator for PS3 released in 2010. No further development is known for PS3.
https://store.brewology.com/ahomebrew.php?brewid=3

It is a standalone emulator, not part of retroarch.

They could port the Yaba Sanshiro core to PS3 Retroarch, that core works fine and fast even on smartphones.

 

[JediKnight007]

Demons of Asteborg (new indie game release) rom for Mega Drive isn't working on Retroarch with Genesis Plus GX. It gives black screen and freezes PS3.
Probably the CE core needs to be updated. It works on latest Retroarch for Windows x64.

Picodrive plays it, but SRAM, save states, and rewind don't work.

There is a very early, and somewhat laggy version of Sega Emulator for PS3 released in 2010. No further development is known for PS3.
https://store.brewology.com/ahomebrew.php?brewid=3

It is a standalone emulator, not part of retroarch.

The last build of the standalone PS3 Mednafen port also has a laggy Yabause module.

 

[Lambada]

Picodrive plays it, but SRAM, save states, and rewind don't work.

Really? No SRAM? Dammit.
I have a Mega Drive with Everdrive X7 and the game doesn't work with SRAM too. I wanted to play in PS3 Retroarch just because of the possibility of using SRAM or Savestates. Otherwise I would have to play on my PC, I was trying to avoid that =P

 

[Lambada]

Added some shaders to my collection. Managed to split crt-hyllian in a multipass way, making it at least twice faster! Then using it I could make some new presets (crt-super-xbr, cboard-bl0-smartblur-crt). Added phosphor mask too.

Here's a link to ps3-shaders updated totday:
https://anonymousfiles.io/4KtMOTFj/

What's new:

- crt-hyllian-multipass (much faster!)
- crt-super-xbr (runs fullspeed even on snes 1.60)
- cboard-bl0-smartblur-crt (included inside special-presets. It's very good with SMW and SM-All Stars!)

Where can we download your optimized shaders? The links are broken.
Are they already included in Retroarch CE pkg or are they available inside Retroarch "Online Updater / Update CG Shaders"?

 

[Lambada]

Initially i also thought that it could be easy to fix but now im not so sure because there is another "hack" indirectly related with this. The gamepad profiles (files named sixaxis.cfg etc...) are also "hardcoded" in the retroarch PS3 port.
With this i mean... if you try to load a different gamepad.cfg (or you try to create your own customized) you are going to realize that are completly ignored
I realized about this missing feature when i was trying to figure what was happing with the incorrect mapping of the button images in the ozone main menu... but also because i dont like the message "sixaxis controller detected" that appears everytime we boot retroarch (because my controller is a dualshock3 not a sisaxix)

In my oppinion the best description is "PlayStation 3 Controller" because is more generic
As far i remember there is a gamepad.cfg in the official retroarch repository that shows that name (well, they have a lot, i was lurking them for curiosity sake and to try to understand how are mapped the buttons)

Edit:
I dont remember well the details of all this... but if someone is interested scroll back in the thread, probably i wrote an small wall of text trying to explain it

@aldostools , @sandungas and @Crystal I fixed the swapped buttons! I found the error.

The original code of SixAxis Controller.cfg is:

input_driver = "ps3"
input_device = "SixAxis Controller"
input_b_btn = "0"
input_y_btn = "1"
input_select_btn = "2"
input_start_btn = "3"
input_up_btn = "4"
input_down_btn = "5"
input_left_btn = "6"
input_right_btn = "7"
input_a_btn = "8"
input_x_btn = "9"
input_l_btn = "10"
input_r_btn = "11"
input_l2_btn = "12"
input_r2_btn = "13"
input_l3_btn = "14"
input_r3_btn = "15"
input_l_x_plus_axis = "+0"
input_l_x_minus_axis = "-0"
input_l_y_plus_axis = "+1"
input_l_y_minus_axis = "-1"
input_r_x_plus_axis = "+2"
input_r_x_minus_axis = "-2"
input_r_y_plus_axis = "+3"
input_r_y_minus_axis = "-3"

input_b_btn_label = "Cross"
input_y_btn_label = "Square"
input_select_btn_label = "Select"
input_start_btn_label = "Start"
input_up_btn_label = "D-Pad Up"
input_down_btn_label = "D-Pad Down"
input_left_btn_label = "D-Pad Left"
input_right_btn_label = "D-Pad Right"
input_a_btn_label = "Circle"
input_x_btn_label = "Triangle"
input_l_btn_label = "L1"
input_r_btn_label = "R1"
input_l2_axis_label = "L2"
input_r2_axis_label = "R2"
input_l3_btn_label = "L3"
input_r3_btn_label = "R3"
input_l_x_plus_axis_label = "Left Analog Right"
input_l_x_minus_axis_label = "Left Analog Left"
input_l_y_plus_axis_label = "Left Analog Down"
input_l_y_minus_axis_label = "Left Analog Up"
input_r_x_plus_axis_label = "Right Analog Right"
input_r_x_minus_axis_label = "Right Analog Left"
input_r_y_plus_axis_label = "Right Analog Down"
input_r_y_minus_axis_label = "Right Analog Up"
input_menu_toggle_btn_label = "PS"

*The fixed SixAxis Controller.cfg is:

input_driver = "ps3"
input_device = "SixAxis Controller"
input_b_btn = "8"
input_y_btn = "1"
input_select_btn = "2"
input_start_btn = "3"
input_up_btn = "4"
input_down_btn = "5"
input_left_btn = "6"
input_right_btn = "7"
input_a_btn = "0"
input_x_btn = "9"
input_l_btn = "10"
input_r_btn = "11"
input_l2_btn = "12"
input_r2_btn = "13"
input_l3_btn = "14"
input_r3_btn = "15"
input_l_x_plus_axis = "+0"
input_l_x_minus_axis = "-0"
input_l_y_plus_axis = "+1"
input_l_y_minus_axis = "-1"
input_r_x_plus_axis = "+2"
input_r_x_minus_axis = "-2"
input_r_y_plus_axis = "+3"
input_r_y_minus_axis = "-3"
input_b_btn_label = "Cross"
input_y_btn_label = "Square"
input_select_btn_label = "Select"
input_start_btn_label = "Start"
input_up_btn_label = "D-Pad Up"
input_down_btn_label = "D-Pad Down"
input_left_btn_label = "D-Pad Left"
input_right_btn_label = "D-Pad Right"
input_a_btn_label = "Circle"
input_x_btn_label = "Triangle"
input_l_btn_label = "L1"
input_r_btn_label = "R1"
input_l2_btn_label = "L2"
input_r2_btn_label = "R2"
input_l3_btn_label = "L3"
input_r3_btn_label = "R3"
input_l_x_plus_axis_label = "Left Analog Right"
input_l_x_minus_axis_label = "Left Analog Left"
input_l_y_plus_axis_label = "Left Analog Down"
input_l_y_minus_axis_label = "Left Analog Up"
input_r_x_plus_axis_label = "Right Analog Right"
input_r_x_minus_axis_label = "Right Analog Left"
input_r_y_plus_axis_label = "Right Analog Down"
input_r_y_minus_axis_label = "Right Analog Up"
input_menu_toggle_btn_label = "PS"

Fixing the swapped buttons
The problem were these lines:
input_b_btn = "0"
input_y_btn = "1"
input_a_btn = "8"
input_x_btn = "9"


They should be:
input_b_btn = "8"
input_y_btn = "1"
input_a_btn = "0"
input_x_btn = "9"


Fixing the wrong button labels

The default lines below:
input_l2_axis_label = "L2"
input_r2_axis_label = "R2"


They should be:
input_l2_btn_label = "L2"
input_r2_btn_label = "R2"

If not the L2/R2 label won't be recognized and won't appear. They will appear as buttons 12 and 13 in the Retroarch UI.

To discover that I started to remap all buttons of Port 1 Controls manually (Settings > Input > Port 1 Controls).
At every button that I pressed it assigned a number (before they were all called as Auto:NameOfPS3button).
And then I compared the default values of the SixAxis Controller.cfg with the new ones from the same Port 1 Controls screen that I was configuring my buttons.
So If the default controls in the CFG were right, all the buttons that I pressed and were shown in the screen would still have the same values. They would match... but they didn't.

After it was set, when I pressed CIRCLE the button would CONFIRM just like the Japanese systems. And CROSS would CANCEL.
If you check the CFG label and compare with the ICONS, it wall makes sense.

Now, go to Settings > Input > Menu Controls and look for that option:
Menu Swap OK and Cancel Buttons. <OFF>
Swap buttons for OK/Cancel. Disabled is the Japanese button orientation, enabled is the western orientation.

OFF is the default in PS3 build. If you change to ON, the western orientation will be enabled and the CROSS will CONFIRM and CIRCLE will CANCEL.

Now it's time to in the next release use the fixed CFG version as the default one. And I suggest to leave the SWAP OK AND CANCEL BUTTONS <ON> so it would be in the western mode.

So the problem were not the images of the button files, it was the autoconfig CFG that had the wrong button numbers assigned. We were all wrong, LOL.

PS: Curious fact, the autoconfig PS3 Controller (hid) file from PC version uses the same button numbers as the Fixed one from the PS3 Console version.

EDIT: Updated the post with a fix for another bug, related to button labels, that I found in the SixAxis Controller.cfg.[/COLOR]

 

[sandungas]

@Lambada im reviewing my reports here because i wrote about this problem some months ago and there are some details i forgot that are making me doubt about what you wrote

The most important detail is that i was modifying the file USRDIR\autoconfig\SixAxis Controller.cfg and retroarch was ignoring my changes
It was ignoring the field named "input_device" (containing the name that appears in a floating notification everytime we boot retroarch)... a few posts after my report @Crystal confirmed that this text is actually hardcoded

As far i remember, it was ignoring also the desriptions at bottom highlighted in yellow in this screenshot

And as far i remember... i also was "swapping" the buttons to fix the incorrect icons displayed in ozone theme... and was ignored too
I also tryed to rename the file SixAxis Controller.cfg to PlayStation 3.cfg just to see if retroarch was able to load a file with a different name... and at some point i was so desperate that i deleted the .cfg file and retroarch was booting normally
So... at that point i thought the retroarch PS3 port have that controller settings fully hardcoded and is ignoring the .cfg file entirelly
So... i went to the source code and dedicated some time to try to "search" for that controller hardcoded settings but i could not find anything :/

----------------------
In your post you are suggesting the solution is to modify the file SixAxis Controller.cfg but as far i understood it doesnt matters what we do with that file because retroarch is ignoring it

 

[Lambada]

@Lambada im reviewing my reports here because i wrote about this problem some months ago and there are some details i forgot that are making me doubt about what you wrote

The most important detail is that i was modifying the file USRDIR\autoconfig\SixAxis Controller.cfg and retroarch was ignoring my changes
It was ignoring the field named "input_device" (containing the name that appears in a floating notification everytime we boot retroarch)... a few posts after my report @Crystal confirmed that this text is actually hardcoded

As far i remember, it was ignoring also the desriptions at bottom highlighted in yellow in this screenshot


And as far i remember... i also was "swapping" the buttons to fix the incorrect icons displayed in ozone theme... and was ignored too
I also tryed to rename the file SixAxis Controller.cfg to PlayStation 3.cfg just to see if retroarch was able to load a file with a different name... and at some point i was so desperate that i deleted the .cfg file and retroarch was booting normally
So... at that point i thought the retroarch PS3 port have that controller settings fully hardcoded and is ignoring the .cfg file entirelly
So... i went to the source code and dedicated some time to try to "search" for that controller hardcoded settings but i could not find anything :/

----------------------
In your post you are suggesting the solution is to modify the file SixAxis Controller.cfg but as far i understood it doesnt matters what we do with that file because retroarch is ignoring it

How it was done

Hmmm... the thing I did was that I remapped the buttons and I checked button numbers from the default sixaxis controller.cfg with the numbers displayed when I was remapping. The buttons that were correct matched, the others that I highlighted didn't.

The "input_device =" if you change in CFG it won't work, I also tried.

All my tests I did in RPCS3 emulator until now, because I thought it was more convenient to test and edit files if I needed.
Anyway, because you told me that editing SixAxis Controller.cfg didn't work with you... I tested this:

1. Launched my PS3's Retroarch to check how my buttons were, they were default without the fix and then I quit.
   
2. Deleted my SixAxis Controller.cfg from my PS3.
   
3. Got my working SixAxis Controller.cfg from my RPCS3's Retroarch and uploaded the file in my PS3 through FTP.

So now I booted again my PS3's Retroarch (which is the Crystal's version too) and voiolá, the buttons were fixed but as Japanese orientation and it corresponds with the images in the bottom. I just need to go Settings > Input > Menu Controls > Menu Swap OK and Cancel Buttons and set it to ON as in my last post and the orientation will be western.

So my guess is only the input device name can't be changed and you can't add another cfg there, only SixAxis Controller.cfg will load.

Some other tests

1. Another thing, I checked the the Port 1 controls in my PS3, they were all fine (Circle and Cross matching with PS3 Dualshock) but the label said it was "Auto" because technically I didn't change the buttons through Retroarch in my PS3 (I did in RPCS3) so It judges as if they were always fixed. This is not a problem, anyway. If you try to set to return the CFG to default, it remains the same because it thinks it's the default.
   
2. I quit PS3's Retroarch and deleted the working cfg with fixed buttons (through FTP), and now I booted it up again. The buttons were again incorrect (like expected). So the DEFAULT SixAxis Controller.cfg with wrong button is in fact HARDCODED. But it doesn't mean you can't fix it. It means if you delete your SixAxis Controller.cfg, you will miss the correct button layout and it will be back with wrong buttons problem.

So in part I'm right. The user can fix it, but @Crystal should fix in the future and put it hardcoded as the new default one.

Test yourself the cfg file below.

EDIT: One more thing, I found another bug in the SixAxis Controller.cfg. The new CFG was reuploaded as an attachment.

The default lines below:
input_l2_axis_label = "L2"
input_r2_axis_label = "R2"

They should be:
input_l2_btn_label = "L2"
input_r2_btn_label = "R2"

If not the L2/R2 label won't be recognized and won't appear. They will appear as buttons 12 and 13 in the Retroarch UI.

 

[sandungas]

Initially i was also trying to use the setting "Port 1 controls" to try to find what was happening, also to try to see if it could be used as a temporal fix (in the meantime someone finds the problem in the source code) but i realized it was confusing me even more because is like a remap on top of another remap (for the option that does the swap in beteen X and O)... on top of a bug
It was too much confusing
What i was doing later was to delete all the retroarch config files to "reset" it entirelly to the default settings (as far i remember retroarch generates its own config files automatically at the next boot)... and even i was uninstalling retroarch and installing it again (the 500mb of #beta3) just to be sure i was starting my experiments from defaults

Im not sure if you fixed it in your setup just by using only the file "SixAxis Controller.cfg" or you have some more settings modifyed, i guess your file needs to be checked in a fresh retroarch install for confirmation
Anyway... the research we did was a bit a wayaround, is handy but this needs to be reviewed by someone used to the source code that could deduce where is the problem

[*]I quit PS3's Retroarch and deleted the working cfg with fixed buttons (through FTP), and now I booted it up again. The buttons were again incorrect (like expected). So the DEFAULT SixAxis Controller.cfg with wrong button is in fact HARDCODED

Thanks for confirming this, when i was writing my previous post i was not completly sure if i remember it well, but yeah... i guess when i realized about that is when i thrown the towell
At the next day i was taking a look at the source code, i was not able to find it (but obviouslly i missed it, is there hidden somewhere, lol)... and decided to report it here with the hope someone else finds it

*Another reason why i thrown the towell at that point is because i was also working in photoshop to replace some icons with the retroarch logo (and there are many)
One of the things we was changing in the "RetroarchCE edition" was the ICON0.PNG (with a new design of the "space invader" guy)... and i wanted to replace all the other apparences of it
Nothing personal against the official retroarch logo, i hope nobody involved in the project gets angry... is just i like the original pixelated "invader" by TAITO a lot
I been reviewing that images yesterday, are around 20 or 25 icons... i will upload them later