@rgbfr

What do you think the problem is?

It could be the ROM, it could be the ROMSET/file format, it could be the videomode....
Check these possibilities.

https://wiki.recalbox.com/en/tutorials/games/generalities/isos-and-roms/romsets-for-recalbox https://wiki.recalbox.com/en/tutorials/video/display-configuration/complete-video-configuration-guide https://forum.recalbox.com/topic/25635/recalbox-8-0-dreamcast-problème-chd-v5

@zing Merci pour ta réponse.

Malheureusement, j'ai trouvé les mêmes éléments que toi, ej'ai déjà testé ces propositions, et il me semble que dans ces discussions le souci n'est pas résolu et les forumeurs parlent d'un autre émulateur.

Depuis, j'ai tenté de désactiver (prudemment) quelques options de flycast via retroarch (fog effect, mipmapping, gd-rom fast-loading), et même essayé une troisième rom en chd mais le bug persiste. 😞

Et effectivement, n'étant pas du genre à faire les MAJ day one, et constatant d'une part que la 7.2.2 fonctionnait idéalement sur mes différents systèmes et au vu des soucis remontés sur la version 8 avec les pi3b+, j'avoue que j'ai préféré ne pas upgrader pour l'instant (j'ai vu passer l'annonce de la 8.1 que je tenterais sans doute mais sûrement en laissant passer plusieurs semaines en cas de correctifs).

@scavy Certains le sont maintenant....mais ils rament bien comme il faut ( Tomb raider chronicles )

@barbudreadmon D'accord je comprends mieux. Vivement le Gpi Case 3 avec stick intégré alors ! 😛

@pier65 bon j'ai réinstallé recalbox et cette fois ma manette est reconnue à chaque démarrage. Je me doutais qu'il y avait un gros problème quand, après avoir demandé plusieurs fois d'oublier les périphériques bluetooth, la manette était toujours dans la liste des manettes 😕

Bon, pour le moment la recalbox semble bien fonctionner avec ma pi4 maintenant.

Encore merci !

@fredcsn

vi que não consta a correção do issue que abri no Gitlab...

Sim, o seu issue continua em aberto, isso indica que infelizmente ainda não foi resolvido.

vc acha que nas próximas atualizações eles irão corrigir esse bug

Preciso deixar claro que não sou um desenvolvedor, sou apenas um moderador, então infelizmente não posso te dar uma certeza.
Eu acredito que o bug será resolvido na próxima versão sim, mas a versão 8.0.1 já estava "encaminhada" há certo tempo, e os desenvolvedores estão focando seus esforços na resolução do problema de tela preta, estão entrando em contato direto com a fundação Raspberry pois é um bug que surgiu após a fundação atualizar o firmware dos RPi, a versão 8.0.2 inclusive foi lançada logo em seguida pois a solução sugerida pela fundação não resolveu para todos e acabou afetando outras pessoas, então tiveram que reverter...

Isso tudo acaba atrasando a equipe, então fica difícil dar alguma previsão precisa.

It is not so much Windows CE the concern, but to manage the Memory Management Unit within the processor SH4 of the console which is necessary (used also by Win CE). This can be done on a PC but not on Pi because it requires too much resources.

https://discord.com/channels/438014472049917953/439141063425392640/927635792199843890

SUJET DEPLACE A LA SECTION CORRECTE.

@JoCo

https://forum.recalbox.com/topic/25592/pas-de-son-dans-les-emulateurs https://wiki.recalbox.com/fr/tutorials/audio/fix-emulationstation-sound-issues

J'ai regardé les logfiles, en particulier es_log.txt, voici ce que j'y ai trouvé :

[1980/01/01 02:01:51.227] (INFO ) : [Run] Command: python /usr/bin/emulatorlauncher.pyc -p1index 0 -p1guid 030000005e040000ea02000001030000 -p1name "Xbox One S Controller" -p1nbaxes 4 -p1nbhats 1 -p1nbbuttons 13 -p1devicepath /dev/input/event0 -system dreamcast -rom /recalbox/share/roms/dreamcast/Capcom\ vs.\ SNK.chd -emulator libretro -core flycast -ratio auto [1980/01/01 02:01:51.228] (INFO ) : [Pad2Keyboard] No pad2keyb configuration. [1980/01/01 02:01:51.228] (INFO ) : [MQTT] Publishing to tcp://127.0.0.1:1883 from recalbox-emulationstation OK! [1980/01/01 02:01:51.228] (INFO ) : [Hardware] Start in-game Hardware processes [1980/01/01 02:01:53.601] (INFO ) : [Hardware] Stop in-game Hardware processes [1980/01/01 02:01:53.602] (WARN!) : [Run] Non-Zero exit code 250 !

Je pensais que le nom de ma ROM était mal "traduit" dans le script : les espaces deviennent des anti-slash+espace... Mais en regardant un peu plus, cela semble être le case pour d'autres systèmes et les ROMs associées.

Du coup, le seul indice est le code de sortie 250. Je n'arrive pas à trouver à quoi cela correspond pour libretro et/ou flycast.

@ssssq

when I was on HDMI it was running p e r f e c t.
after perfect crt setup

First: It would save time if you had said this information from the beginning, please specify as much information as possible so that someone can help you correctly.

So the problem is probably the fact that you configure it in CRT, possibly you need to change the Dreamcast videomode, and once again I would point out that Dreamcast/N64/PSP are emulators that have these emulation difficulties.

Let's go to some questions:

Do you have your BIOS perfectly recognized in the built-in BIOS checker (green thumbs)? Have you already tested it with the two emulators: Flycast and Reicast? You can test the same game with an iso redump as mentioned in the documentation?

In addition, there is the question of the videomode I mentioned, the information appears in the recalbox.conf file:

## Dreamcast emulator ## Like N64, such a CPU intensive emulator needs a small resolution ## Consider DMT 4 HDMI (640*480) or DMT 9 HDMI (800*600). If you have a black screen on dreamcast, try DMT 9 HDMI here ;dreamcast.videomode=DMT 4 HDMI

The official Flycast documentation specifies some resolutions:
https://docs.libretro.com/library/flycast/#core-options

Reicast's official documentation specifies some possible video configurations:
https://reicast.com/guide/

Maybe this will help:
https://forum.recalbox.com/topic/23950/7-2-mode-non-optimum/10