Official recalbox 4.0.0 beta thread
-
u coup pourquoi ne pas l'avoir mis/laissé aussi directement dans le répertoire accessible en écriture le fichier es_systems.cfg ? Il sert quand même énormément pour plein de confs customs et est référencé partout dans la doc...
-
On est sur la béta 1 et il y a quand même beaucoup de changements versus la 3.3 (d'ou le passage en 4.0 ^^). Donc il va falloir quelques temps pour que tout retourne au petits oignon mais on reste très loin des premières beta de la 3.3. On a quelque chose qui fonctionne très bien même sur une beta1 :D.
-
@Voljega Perfect, i'm gonna try to make it work by hand. I never scrape the Fba/Mame games anyway, but it's good to know that. Thank you. @Subs After some testing, looks like the only system (at the moment) who can't read the old version savegames is GBA. I tried with some ps1 and n64 games and it works just well. I wanna try the rest of the systems soon. If i start a new game in a GBA game it saves without problems, but i don't wanna lose my previously save gamedatas. I tried saving ingame and then overwrite the file, without success. And i haven't find yet the way to make to work again the PcengineCD games, i don't know what to do. I tried with other syscard3.pce file, tried changing the cores... it just simply keeps throw me back to ES.
-
@Dragda, in recalbox 4.0.0, on rpi2, we switched the gba default core. Before the core was gpsp and now, we are now using mgba. So your savestate problem may come from this. You can switch your gba core using the advanced, game option in ES. We also moved the save folder. Saves files are no more all in /saves folder, but splitted in subfolder for each system. /saves/snes etc.... About your PC engine CD problem, did you add the bios file of this system ?
-
@voljega : concernant le
es_system.cfg, ce fichier doit être absolument réécrit lors des mises à jour de recalbox, sinon pas d'accès aux nouveaux systèmes qui seront ajoutés lors des futures mises à jour. Or actuellement la partition/recalbox/share/qui est accessible en écriture n'est pas touchée lors des updates. Les fichier dans /recalbox/share_init/ eux le sont. Du coup le fichieres_system.cfgest uniquement présent dans/recalbox/share_init/afin qu'il soit réécrit. Après je ne vois pas trop le soucis, dans les précédentes versions, tu pouvais modifier ce fichier à ta guise, mais ce dernier se trouvait réinitialisé lors d'une update du système. Tes modifications étaient alors à refaire post update. Actuellement tu as toujours accès à ce fichier que tu peux modifier à ta guise et ce dernier sera toujours réinitialisé après une update du système. Les seules chose qui changent, sont son emplacement (un peu déroutant au début, mais vous vous y ferez vite) et le fait que le système soit en read only, nécessitant de taper une commande pour monter la partition en RW avant de faire la modif :mount -o remount, rw /Il faut bien voir le passage en RO comme une évolution majeure dans la stabilité future du système. Ce n'est pas pour vous empêcher de modifier le système, vous embêter ou quoique ce soit d'autre. Mais réellement pour éviter de niquer les systèmes au moindre soucis. -
@rockaddicted Yeah, as you can see in my comments about the new savedata folders, i have keep that in consideration already. I found the problem! Looks like now, the .sav file is been storage in the same folder as the rom, but for some reason the .state file is storage in the new savefile folder. I changed the core to gpsp, overwrite the .sav in "/recalbox/share/roms/gba", and now i can load my old save (phew). It has to be fixed in the second beta. About the PcEngineCD, yup, i have put the bios in. In fact, i was using a lot this system in previous betas (DraculaX, Gate of thunder, Mad Stalker, etc) without problems. I tried to do testings changing the core, but nope, it refuses to work. Normal pcengine games work fine as always.
-
@roxkaddicted je critique pas le passage en ro qui va clairement dans le bon sens. C'est juste que pour des gens qui ne connaissent pas grand chose à l'informatique, la manipulation de certains fichiers devient du coup extrèmement compliquée... La partition se remet toute seule en RO au reboot au moins ou il faut faire l'opération inverse ? <p style="text-align: center;">en fait l'idéal dans l'avenir serait peu-être de masquer toutes ces opérations et l'accès aux trois principaux fichiers de conf (conf.txt, recabox.conf, es_systems.cfg) derrière recalbox-manager qui se chargerait tout seul de modifier les droits des partitions et les fichiers ? a minimiserait les erreurs et les connaissances à acquérir</p>
-
@voljega et oui on a bien conscience que le passage en RO va "bloquer" certaines personnes ayant leurs habitudes sous la 3.3.0. Mais on part du principe que 95% des gens utilisant recalbox n'ont pas vraiment besoin de faire des modifs en SSH pour utiliser, configurer le système. Donc que ça passera de façon transparente pour beaucoup. Pour les autres il faudra qu'ils modifient leurs habitudes, et prennent le réflexe de passer en RW avant d'éditer des fichiers. Après bientôt il y aura les tutos, et wikis qui vont bien aller pour accompagner et guider tout le monde. Donc pareil ça se devrait également bien se passer. Pour répondre à ta question, oui le passage en RO au reboot est automatique. Sinon bien entendu rien n'est figé et il n'est pas impossible qu'à l'avenir, dans les prochaines versions, des solutions soient trouvées pour faciliter les choses (faire des diff entre les fichiers de conf présents dans
/recalbox/share/et/recalbox/share_init/pour les mises à jours, intégration de plus de fichiers de conf au recalbox-manager, etc...). Mais chaque choses en son temps
-
Hey peoples, firstable, thx to make dream become true. The child inside me bless you. Well, i've a few questions about the new recalboxOS. It's about screen compatibility. For some reason, there's some screen (hdmi) who need drivers to work. Is it possible now to install external driver on the recalBox ? I bought last week ago, a 7inch LCD screen on amazon, a waveshare screen. It work in HDMI with my computer or my PS3, but he doesn't work on my Pi2. I read on their wiki that i need to install some drivers. How could do that ?
-
@dragda
Looks like now, the .sav file is been storage in the same folder as the rom, but for some reason the .state file is storage in the new savefile folder
Weird save + savestates files must be in the same folder
/recalbox/share/saves/system_nameIt has to be fixed in the second beta.
If you are talking about rolling back to gpsp core by default, nope sorry we'll keep mgba as default core. But you are now able to define your prefered core very easily, so it is not a big deal. About your problem with pcengine cd games, I'll take a look this evening. I didn't test it... But we didn't update this core between 3.3.0 beta 17 et 4.0.0, So I don't really understand the problem without practice my own tests
-
@Yeton, Hello, hummm for a specific hardware support, you should open an issue on recalbox's github. Describe the situation, and give more informations as possible (screen ref, link to the driver, etc...)
-
@rockaddicted Looks like we don't understand each other XD. The default core saves where it should, but the gpsp core saves in the same folder of the rom. I was not talking about changing the default core, as you say, i can change the core easily. I was thinking in fix the location to save in "/saves/gba" as well with the gpsp core. If you can test my PcEngineCD problem i would really appreciate that ^^. (English is not my native language, so sorry if i not express myself properly. It would be a lot worse if i try to do it in french :P)
-
@Dragda haha no problem english is not my native language too, and I didn't really listen during school ... so ...
So in recalbox 4.0.0, when you save a game using the default core (mgba) files are created in /recalbox/share/saves/gba, BUT when you do the same thing once forced gpsp as gba core, the save files are created in/recalbox/share/roms/gba/? -
@rockaddicted That's it.
-
@Dragda, fine I'll look these points, I'll do my feedback here
-
Hello! Thanks for the new version but I have a few problems. Since I updated I can't copy the roms directly to the sd card on linux. It says I don't have permitions to write in this folder. I tried by network and Windows doesn't detect my recalbox and with linux, I can see on the begining but after copy a few megas it dissappear and I can't copy anything else for a while. Anyone with a solution? Thanks!
-
Salut et merçi pour la maj ! Juste une question on peut mettre a jour directement a patir de la beta 17 ou on est obligé de refaire un instal ?
-
Install obligatoire
-
Hi, Thanks for the new version. I've updated and here are a few problems:
- Turned ON the WIFI connection and the system freezes. Using Edimax EW-7811Un Wireless N Nano USB 150Mbps.
- Swicht to another language and when the system restart It's freezes on the loading screen.
- I'm a Mac user and I can’t copy the roms directly to the sd, "share" partition is not mounted when I put my sd card on my computer. On v3.3.0-beta17 this works fine.
Thanks!
-
@Marcos Clatablera
- Turned ON the WIFI connection and the system freezes. Using Edimax EW-7811Un Wireless N Nano USB 150Mbps.
Hi :D. For me, i have no problemes with the wifi but you have a long waiting time of "freezes" juste after turned ON Wifi. Time for the recalbox to join your wifi... I made the test with an other dongle but i can try with my edimax next time
- Swicht to another language and when the system restart It’s freezes on the loading screen.
Can you give us the language you want use. maybe they have a problem with this language.
- I’m a Mac user and I can’t copy the roms directly to the sd, « share » partition is not mounted when I put my sd card on my computer. On v3.3.0-beta17 this works fine.
That strange... I can make a test in my mac after...
do you have try to access to your recalbox with a ping ? https://github.com/recalbox/recalbox-os/wiki/Identify-your-recalbox's-IP-on-your-network-(EN)#with-apple-osx Or try connect with winscp ? https://github.com/recalbox/recalbox-os/wiki/Network-access-with-WinSCP-(EN)
