[4.1-Unstable] Bug reports

[Substring]

@Эдвис-Фатходинов are you using custom config files for retroarch ?

[Edvis]

@Substring did not understand you.
retroarch Did not change anything. Everything was fine on v 4.0.0
, Then I updated it to 4.0.2 and immediately to 4.1

[Raphael Bueno Hatencia]

It´s normal to have all folders ROMs with disk size bigger than the actual size? See example pic.

[Substring]

@Эдвис-Фатходинов there was an update of retroarch on 4.1, hence the problem. We solved it by manually forcing the video font path in the retroarch config file.

[Substring]

@Raphael-Bueno-Hatencia This is not the place to discuss about what space files are, and what space they really take (see what a FAT cluster is, or what an inode is)

[azvarel]

@Substring

I do not know if this was mentioned before, because I was not following version 4.1, but I had to update to perform some tests with the rpi3 bluetooth, come on.

1. controller snes30 8bitdo firmware 2.70
I can pair but if it hangs up for lack of use or if you turn off rpi3 the pairing is lost

2. wiimote without wiimotion (first model)
It is paired, however when setting the UP, LEFT buttons with you, but when I set the RIGHT, DOWN buttons, it changes the LEFT mapping.

3. Dualshock 3
It is paired, however the LEDs keep blinking forever, it does not position which controller it is (I do not know if there has to be an xbox360 controller), even if it is disabled in the settings it persists.

4. PSP and DC games
I remember someone put some spreadsheets to report which games are 100% working, which ones need overclocking, which ones do not work.
@paradadf can you help me?

5. Overclocking
When testing the game Outrun Coast 2 Coast of the PSP, I saw that it gives a lot of choking and the gameplay is very much to be desired, when leaving the game it gave black screen, it stopped the recalbox, I made the overclock in the extreme way and simply the recalbox broken, did not initialize more.

[azvarel]

@Эдвис-Фатходинов said in [4.1-Unstable] Bug reports:

Hello, when using the hotkey, the bottom of the screen shows no letters, but squares, how to fix it? So it became after the system update v.4.1

This happened to me and I did the direct installation by downloading the files from https://archive.recalbox.com/updates/v1.0/unstable/ and I am using the English language.

[paradadf]

@azvarel the compatibility lists are on the "IMPORTANT - README FIRST" section.

[Substring]

@azvarel said in [4.1-Unstable] Bug reports:

@Substring

I do not know if this was mentioned before, because I was not following version 4.1, but I had to update to perform some tests with the rpi3 bluetooth, come on.

1. controller snes30 8bitdo firmware 2.70
I can pair but if it hangs up for lack of use or if you turn off rpi3 the pairing is lost

That's rather surprising. But I don't believe it. You should turn the pad on AFTER recalbox starts loading ES, not before (yeah, that's a change since 4.0)

2. wiimote without wiimotion (first model)
It is paired, however when setting the UP, LEFT buttons with you, but when I set the RIGHT, DOWN buttons, it changes the LEFT mapping.

Ain't the wiimote already configured ? If you're familiar with es config files, what if you manually edit the file to set the right values ?

3. Dualshock 3
It is paired, however the LEDs keep blinking forever, it does not position which controller it is (I do not know if there has to be an xbox360 controller), even if it is disabled in the settings it persists.

I don't have such behaviour. A few people reported it. I just own some shanwans, no genuine, and the led does work.

4. PSP and DC games
I remember someone put some spreadsheets to report which games are 100% working, which ones need overclocking, which ones do not work.
@paradadf can you help me?

5. Overclocking
When testing the game Outrun Coast 2 Coast of the PSP, I saw that it gives a lot of choking and the gameplay is very much to be desired, when leaving the game it gave black screen, it stopped the recalbox, I made the overclock in the extreme way and simply the recalbox broken, did not initialize more.

That's why there is a warning about overclocking. Extrem voids your warranty. You should know that the PSP emulation is a succession of ups & downs : some games do very nicely work, some can be tweaked, some are just unplayable (give a try to ultimate ghouls'n'ghosts or tekken 6 ...)

[azvarel]

@Substring said in [4.1-Unstable] Bug reports:

That's rather surprising. But I don't believe it. You should turn the pad on AFTER recalbox starts loading ES, not before (yeah, that's a change since 4.0)

I don't have such behaviour. A few people reported it. I just own some shanwans, no genuine, and the led does work.

I'm going to film the process that I do to pair the 8bitdo controller and turn off the recalbox and when it pairs again it gets lost, I take advantage and I also do the dualshock 3 for you to see.

@paradadf
I will give an updated there in the psp spreadsheet has many games that "fart" in rpi3

[Substring]

@azvarel Yesterday i talked with someone on IRC whose BT data was not saved, which is very surprising as no one reported that after more than a month of unstable. Can you check if you have an archive in ~/bluetooth/ ?

regarding PPSSPP : there are SO MANY possible tweaks inside the emulator that you should really experiment with them and report best settings.

for example : multithread is not activated by default, whereas it gives a major speed boost (but the team says it's still experimental and can lead to bugs)

[azvarel]

@Substring has a bluetooth.tar file

[Substring]

@azvarel Should know what's inside to be sure

[azvarel]

@Substring

bluetooth.tar\var\lib\bluetooth
file settings
\8C:CD:E8:BF:3A:DA
file info
\cache
file 8C:CD:E8:BF:3A:DA

[azvarel]

I ran more tests with version 4.1

1. HDD loading is much faster

2. WiiU PRO controller works perfectly.

3. games that use the emulator picodrive (mastersystem / megadrive / gamegear) is not opening zip files (all my romset is .zip and it worked in version 4.0.2)

4. When leaving any game, do not return to the emulationstation screen, it is on the black screen that has the recalbox logo underneath and freezes, I have to turn off rpi3 (this was not happening in version 4.0.2)

5. When entering the emulator the icons of the retroarch options are appearing a black square.

[Substring]

@azvarel run tar -tvf ~/bluetooth/bluetooth.tar the output will be much clearer for me/ Please

[Substring]

@azvarel said in [4.1-Unstable] Bug reports:

I ran more tests with version 4.1

1. HDD loading is much faster

Unexpected nehaviour, nothing's been done on that side

2. WiiU PRO controller works perfectly.

Great !

3. games that use the emulator picodrive (mastersystem / megadrive / gamegear) is not opening zip files (all my romset is .zip and it worked in version 4.0.2)

I'm surprised ...

4. When leaving any game, do not return to the emulationstation screen, it is on the black screen that has the recalbox logo underneath and freezes, I have to turn off rpi3 (this was not happening in version 4.0.2)

any game with any emulator ? I don't have such behaviour. Are you running an upgrade from 4.0.2 or a 4.1 .img ?

5. When entering the emulator the icons of the retroarch options are appearing a black square.

You're in the xmb menu, not the rgui. You should download assets from the UI. But you're not supposed to have xmb, but rgui. Are you running the latest unstable without custom configs ?

[azvarel]

@Substring

Continuing the tests,
For some reason of initialization, something was missing, the megadrive / mastersystem / gamegear games came back to work, this after having restarted the recalbox several times.

The freeze on leaving the game still remains

I downloaded the latest stable version of github and downloaded the root and boot files at https://archive.recalbox.com/updates/v1.0/unstable/ and replace them

I will do the installation unstable by downloading directly through the recalbox and post the results.

[Substring]

@azvarel why the heck do you bother with noobs ? Either make a recalbox integrated update, or just burn a .img

[azvarel]

@Substring

D**n! I downloaded version 4.0.1, updated to version 4.0.2, modified recalbox.conf to download version 4.1 unstable, and the error of the black screen when leaving the game persists.

I changed global.videomode=CEA 4 HDMI with global.videomode=default and yet the error still persists.

@Substring said in [4.1-Unstable] Bug reports:

@azvarel run tar -tvf ~/bluetooth/bluetooth.tar the output will be much clearer for me/ Please

/recalbox/share/system$ tar -tvf ~/bluetooth/bluetooth.tar
drwxr-xr-x 0/0         0 1980-01-01 01:00:09 var/lib/bluetooth/
drwx------ 0/0         0 1980-01-01 01:00:16 var/lib/bluetooth/B8:27:EB:7A:6C:7C/
-rw------- 0/0        28 1980-01-01 01:00:16 var/lib/bluetooth/B8:27:EB:7A:6C:7C/settings