[4.1-Unstable] Bug reports
-
@azvarel Should know what's inside to be sure
-
bluetooth.tar\var\lib\bluetooth
file settings
\8C:CD:E8:BF:3A:DA
file info
\cache
file 8C:CD:E8:BF:3A:DA -
I ran more tests with version 4.1
-
HDD loading is much faster
-
WiiU PRO controller works perfectly.
-
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)
-
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)
-
When entering the emulator the icons of the retroarch options are appearing a black square.
-
-
@azvarel run
tar -tvf ~/bluetooth/bluetooth.tar
the output will be much clearer for me/ Please -
@azvarel said in [4.1-Unstable] Bug reports:
I ran more tests with version 4.1
- HDD loading is much faster
Unexpected nehaviour, nothing's been done on that side
- WiiU PRO controller works perfectly.
Great !
- 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 ...
- 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 ?
- 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 ?
-
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.
-
@azvarel why the heck do you bother with noobs ? Either make a recalbox integrated update, or just burn a .img
-
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
withglobal.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
-
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 changedglobal.videomode=CEA 4 HDMI
withglobal.videomode=default
and yet the error still persists.Solved!
1. Controller SNES30
The problem of not handling the 8bitdo snes30 pairing still persists! -
@azvarel your tar should contain a folder which name is the mac address of your SNES30 right under var/lib/bluetooth/B8:27:EB:7A:6C:7C/
But that's not the case ... wtf ... it is supposed to save the folder when pairing succeeded, and when recalbox is shutting down
where is you /recalbox/share located ? SD ? USB ? LAN ?
-
@Substring said in [4.1-Unstable] Bug reports:
where is you /recalbox/share located ? SD ? USB ? LAN ?
USB
-
1. Timezone
Problem at timezone, by default comes Europe/France when changing by America/Noronha by the Manager or by the ownrecalbox.conf
the schedule in the emulators continue Europe/France2. Why are emulators in alphabetical order, not by system order?
Why did version 4.1 not continue the same way as version 4.0? Would not it be interesting to implement this in Manager for the user to arrange the order they want?Ex.
Nintendo - Super Nintendo - Nintendo 64 - GameBoy - GameBoy Advance
And not like this:
GameBoy - GameBoy Advance - Nintendo - Nintendo 64 - Super Nintendo
Should I open issue in github?
-
Dreamcast
I tested Marvel vs Capcom 2 game in .cdi file game opens, good gameplay, but no sound, just like Ikaruga in .gdi file, is also without sound.
That's right?
-
Dreamcast emulator can not see the advanced settings to see the core, when entering the game does not have the option to enter the emulator
PSP the games that work are mini games like Zuma, Tetris, games like Burnout Legends, Ultimate Ghosts'n Ghoulsts, God of War has precarious gameplay
-
stop emulation station via web 2.0 not working?
-
- emulators are in alphabetical order following the same order as in the roms folder. That's because the es_systems.cfg is now automatically generated depending on the arch it's built.
- timzone : this issue was once reported in 4.0. But errr ... no one ever complained about that
- dreamcast sound etc ... : most probably a dump problem, my ikaruga does have sound, music etc ... but most of times inputs die after the first ingame movie (not the launch of the spaceship, the one after a few monster waves)
- i don't understand anything to what you say regarding andvanced settings to the core. Reicast is a standalone, not a libretro core
- as i said PSP emulation can be erratic. For example soul calibur broken destiny runs rather fine with almost 60fps all the time once the emulator tweaked.
-
@Raphael-Bueno-Hatencia the last time I tried it it was working
-
@Substring said in [4.1-Unstable] Bug reports:
- emulators are in alphabetical order following the same order as in the roms folder. That's because the es_systems.cfg is now automatically generated depending on the arch it's built.
I'll issue issue on github about this.
- timzone : this issue was once reported in 4.0. But errr ... no one ever complained about that
I will have to create another issue (now timezone works perfectly on kodi)
- dreamcast sound etc ... : most probably a dump problem, my ikaruga does have sound, music etc ... but most of times inputs die after the first ingame movie (not the launch of the spaceship, the one after a few monster waves)
my problem is that in the boot of the dreamcast no longer has audio, and look I did everything to test...
- i don't understand anything to what you say regarding andvanced settings to the core. Reicast is a standalone, not a libretro core
I know it is not libretro but there is no advanced settings access? Even if it's standalone?
- as i said PSP emulation can be erratic. For example soul calibur broken destiny runs rather fine with almost 60fps all the time once the emulator tweaked.
For now I gave up this emulator in rpi3 so I realized only 5 or 6 games will work fine. (I can only help with which games work on the compatibility list)
-
@azvarel no need to fill an issue for the order of systems, I don't think we will change that. Because if we do change it, then we lose 50% of the interest of having it generated automatically.
For dreamcast : reicast is a very basic emulator, can't expect much from it except the config files which are very poor
-
@Substring
I am not taking the merit of your work, it is very gratifying to talk and help with you on the one hand in improving the system...I thought of the following way: this option to be automatic or not, to be modified via Manager, where the automatic form was disabled, the field where you would leave it in your order would appear. (I know it seems to be a trivial thing, but of paramount importance to anyone doing implementations / adaptations on consoles, eg I own a SNES so I'd like the order to be ... NES / SNES / N64 ... where the SNES would be main using that option to start it at the boot of the recalbox)
It's just a line of code ~ hahahahahaha
jokes aside, I hope you have understood the idea.
Back to dreamcast
Certain in not being able to wait much in this emulator,
But because some people work sound and others do not?
Is this what I do not understand, and why do I soon have no sound at all?