Posts made by 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.

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.

Hi,

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.

Issue resolved. It seems a video configuration issue in recalbox.conf after upgrading. Details here.

Everything sorted out. You can mark this thread as resolved.

Thanks @azvarel . The video mode conf works! If you want to modify manually:

Connect to your Recalbox via SSH:

ssh root@recalbox

Edit file recalbox.conf:

mount -o remount,rw /
vi recalbox.conf

replace:

global.videomode=CEA 4 HDMI

with:

global.videomode=default

Exit saving (:wq! ENTER)
Restart Recalbox:

shutdown -r now

For me, this is an issue during upgrade. It seems the upgrade process doesn´t take into account if you are using an external hard-drive for the game library, updating the files in the SD card but not in the external drive.

Please, review carefully for the next launch (4.1)

The 32X issue is solved by using a new romset. but playing 32X games I'm experiencing the same issue reported with NES: when trying to play for the second time you can´t see anything in the screen while you can hear the game in the background. I'm thinking to rollback to 4.0.0 version. This new stable version isn´t it.

@jsianes the 32X issue resolved using a different romset. Incompatibility of my previous romset with new 32X emu?

Trying another romset, it works. But 'faulty' rooms worked great with 4.0.0 version. So, this should be any kind of incompatibility with the last emu version.

Edit: The blackscreen issue is reproducible also playing 32X games. Just try to play two times Virtua Racing Deluxe. The first time works and the second doesn't.

Reporting same issue here using 'stable' version 4.0.1. I can play one NES game and get black screen with sound in the background trying the second one. Additionally, I can´t play any 32X game. Did you really test this version before launching? Doesn't look like an stable version for me.

Puede alguien probar alguna rom de 32X? A mi se me queda pantalla en negro.

I'm experiencing same issue with Recalbox 4.0.1.

@Substring frozen in black screen and if you press hotkey and start back to ES.

I had similar issue and I did a full re-install of Recalbox. I have all my games and configuration in an external WD Element HD connected to the RPI3 via USB. The good thing of this you don't need to mess about moving games and conf to the SD. All the configuration is inside the external HD. So, when reinstalling, you don't need to worry about the SD. Just reinstall and select the external HD as your preferred storage and all your roms and configuration will be there.

I upgraded yesterday my Recalbox RPI3 set to latest stable version. Now, 32X emulator doesn´t work. Black screen when trying to launch any game (some of them already tested and working with previous version).

Detail:

• Recalbox version: 4.0.1
• Emulator/Core: Default (trying using LIBRETRO/PICODRIVE with same results)
• Kernel version: Linux RECALBOX 4.1.19-v7 #1 SMP Wed Jan 25 14:52:49 UTC 2017 armv7l GNU/Linux

A mi me paso lo mismo ayer. Se quedo actualizando por 1 hora y luego fallo la actualizacion. Imagino que le salto a mucha gente a la vez la actualizacion y los servidores no daban ancho de banda para todos.

Al final tuve que sacar la SD y actualizar a mano bajando la version 4.0.1 desde la web. Asi funciono a la primera.