[4.1-Unstable] Bug reports

[kelv]

Hello Everybody. I burned a new image a week and a half ago using the root file and the boot files in RP3 and unstable 4.1. My question is: before with previous untable builds every 2 days there were an update available however so far I didn't received any new updates. Is it expected? THX

[Substring]

@kelv are we allowed to spend our free time on something​ else than recalbox ?

[kelv]

@Substring jeje, so I guess is expected. I don't as at the beginning every two days we have updates. I wanted only to check . Pls, No hard feelings

[lackyluuk]

@substring not sure if this is 4.1 related: I have added two psx roms (.bin extension, it worked before updating to 4.1) but the system does not show up in ES. I updated the gamelist, did a reboot etc. I cannot even access the psx folder from the Web Manager (it is loading 100 of years and nothing happens). Any idea about this?

[paradadf]

@lackyluuk bin extension for psx games have been deleted from recognized ones. You need to launch ghe game with its cue file. You can easily create them if you miss them. Google for tutorials
https://forum.recalbox.com/topic/4501/remove-bin-extention-for-psx

[lackyluuk]

@paradadf doh'..I should habe known this -.- thanks mate.
Maybe the _readme can be updated accordingly.

[paradadf]

@lackyluuk it has
https://github.com/recalbox/recalbox-buildroot/pull/669/commits/c84ed0a2a44e12920ed1a47623d167e3f2f3341a

[lackyluuk]

@paradadf lol, forget everything I said today

[toniosj]

With the last version of 4.1, my roms patched of SNES dont working now. I have a rom patched of Zelda Link to the Past (spanish traduction), that it was working very well in recalbox 4.0.

Whats happening?

[qwesup]

Regarding the issue with the retroarch squares for HUD messages, I have removed ~/configs/retroarch/retroarchcustom.cfg , yet the problem continues. What is the value that changed in this file so I can add it manually?
I am on the 3/5 build of 4.1 unstable, which was upgraded from 4.0.2.

EDIT:
Was able to figure this out by comparing to a fresh build. In the retroarchcustom.cfg file, change :
video_font_path = ""
to:
video_font_path = /recalbox/share_init/system/.emulationstation/themes/recalbox/data/ubuntu_condensed.ttf

[Substring]

@qwesup dunno if you updated to the latest unstable, but i think this was solved and available for users. I added an automatc umdate of this parameter when updating

[Substring]

@toniosj cores have been updated, but i doubt such a feature was lost. I guess you're talking about an ips patch ?

[toniosj]

@Substring Yes, IPS patch.

[Raphael Bueno Hatencia]

Not sure if is a bug, but no matter what slot you are saving when using save state, the text always show that you saved on slot 0, even when you are on slot 1,2, or 3 or soo on.

But everything saved correctly, just display incorrect.

[toniosj]

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

@toniosj cores have been updated, but i doubt such a feature was lost. I guess you're talking about an ips patch ?

Have you try if the problem exists?

[jsianes]

This afternoon I detected an issue using unstable 4.1 version. The message when writing and reading save-states always said the slot was #0 despite the slot you are really using. The save/load state seems to work correctly it seems an issue with the displayed message when reading/writing. I noticed playing Final Fight CD from MegaCD, but I think the issue is reproducible using any libretro core. Please, take a look.

[Substring]

@jsianes that's a retroarch bug, would probably require a b*mp of retroarch. No idea if this will happen in 4.1

[Raphael Bueno Hatencia]

I managed to get wifi working again. No recalbox problem, it was my SSID hidden. Recalbox can't connect to hidden wifi? That would be nice.

[Edvis]

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

[jsianes]

@Эдвис-Фатходинов make sure you are using the latest unstable version. That happened to me first time I moved from 4.0 stable to unstable. Right after the first update, it came another a couple of days after that fixed that issue.