Every time I play dreamcast, displays the setting screen time/date
-
@JoargTheBard said in Every time I play dreamcast, displays the setting screen time/date:
evdev_mapping_1 = /opt/retropie/configs/dreamcast/mappings/controller_8BitdoNES30Pro.cfg
evdev_mapping_2 = /opt/retropie/configs/dreamcast/mappings/controller_8BitdoNES30Pro.cfgWow. I can't believe it. I made it work. I took the spaces out of my mapping file and replaced them with underscores, then commented out the automap line in the .sh file as you instructed. Then I updated my emu.cfg adding this:
[input] evdev_device_id_1 = 4 evdev_device_id_2 = 5 evdev_device_id_3 = -1 evdev_device_id_4 = -1 evdev_mapping_1 = /opt/retropie/configs/dreamcast/mappings/controller_Ultimarc_I-PAC_Arcade_Control_Interface.cfg evdev_mapping_2 = /opt/retropie/configs/dreamcast/mappings/controller_Ultimarc_I-PAC_Arcade_Control_Interface.cfg joystick_device_id = -1
and it actually works. Crazy taxi has a few audio problems on the P3, but it actually worked. Thanks for your help!
-
I'd like to see this thread back on topic, because I'm definitely interested in seeing the date/time display removed/fixed. It seems @lcsjuniorsi tried using the RTC module with no luck, but thanks to him for giving it a try. Anyone else have any ideas?
-
@cafarellidigital Agreed. Sorry for the diversion into controls mapping.
Now that I can get past the date screen, I too would like to see this overcome.
Is ANYONE using a Raspberry Pi able to get around the date picker? It appears for me every single time I launch something.
-
@lcsjuniorsi said in Every time I play dreamcast, displays the setting screen time/date:
@Folly Hi
I changed the <command> in es_systems.cfg for dreamcast, but it did not work.
I tried with an RTC module and also had no success:
https://learn.adafruit.com/adding-a-real-time-clock-to-raspberry-pi/overviewHowever, I found the performance of the best game to call for ...reicast %ROM%.
In a few days I come back to do more tests and study reicast.Too bad it did not work.
Can you try booting reicast directly from X in terminal ?
Set the time 5 minutes before the clock in X.
Exit and boot reicast again directly from X in terminal.
Does the time and date stick without re-entering ? -
@Folly Hi,
I formatted the SD and added only the bios and a game, did the proceedings:
- Deleted all of the vmu_save _ *.bin files and re-created.
- Changed 5 minutes before and test.
- I left zeroed datetime 01/01/1998 00:00 and test.
- Changed the runcommand to call reicast directly.
- Changed 5 minutes before and test.
- I left zeroed datetime 01/01/1998 00:00 and test.
- I changed the timezone with rasp-config.
- Changed 5 minutes before and test.
- I left zeroed datetime 01/01/1998 00:00 and test.
- I returned the runcommand configuration.
- Added the RTC module and made the following procedures:
- I checked with the RTC commands:
- hwclock -r
- timedatectl
- Changed 5 minutes before and test.
- I left zeroed datetime 01/01/1998 0:00 and test.
- I found that the Dreamcast.RTC parameter store 20 years later.
- I left datetime xx/xx/ 1996 xx: xx and test.
- I made a brief analysis of the source code reicast.
Still, nothing to solve.
I had no time to check the output as you suggested, however, it seems that this is a known bug:
-
@lcsjuniorsi said in Every time I play dreamcast, displays the setting screen time/date:
@Folly Hi,
@
I formatted the SD and added only the bios and a game, did the proceedings:- Deleted all of the vmu_save _ *.bin files and re-created.
- Changed 5 minutes before and test.
- I left zeroed datetime 01/01/1998 00:00 and test.
- Changed the runcommand to call reicast directly.
- Changed 5 minutes before and test.
- I left zeroed datetime 01/01/1998 00:00 and test.
- I changed the timezone with rasp-config.
- Changed 5 minutes before and test.
- I left zeroed datetime 01/01/1998 00:00 and test.
- I returned the runcommand configuration.
- Added the RTC module and made the following procedures:
- I checked with the RTC commands:
- hwclock -r
- timedatectl
- Changed 5 minutes before and test.
- I left zeroed datetime 01/01/1998 0:00 and test.
- I found that the Dreamcast.RTC parameter store 20 years later.
- I left datetime xx/xx/ 1996 xx: xx and test.
- I made a brief analysis of the source code reicast.
Still, nothing to solve.
I had no time to check the output as you suggested, however, it seems that this is a known bug:
Hi,
Did not have the possibility to reply in the last couple of days.
But, thank you for trying all that what you described.Seems we'll have to wait to get it fixed somehowe.
- list item
-
just found a solution for the time/date setting bug.
- Install dreamcast emulator "NullDC"
- start dreamcast without a game and you are in the bios
- make your settings (date,time,language) and exit the bios
- NullDC just craete a new file in the /data directory : dc_nvmem.bin
- rename dc_nvmem.bin to dc_flash.bin and copy the file to your raspberry pi /bios folder, overwrite existing file
- start reicast with a game and have fun without the date/time setting screen
-
@misslehead3 i havent tried modified runcommand but in normal setting a rtc does not fix it. I just verified that my rtc is fully working and still no dice.
-
@ango this did not work for me. Not sure if it is because i have a realtime clock or not
-
@ango can you share your dc_nvmem.bin file?
-
I did what ango said and it worked for me. Here is my dc_flash.bin file.
-
Replacing the dc_flash.bin didnt work for me.
Solution:
Setting the clock (and btw recreating the broken VMUs for saving games) is working by using the Systemmanager entry in the ES Dreamcast Menu. If the entry is missing, execute the following command and restart ES:
ln -sv fileThatDoesNotExist ~/RetroPie/roms/dreamcast/systemManager.cdi -
@Sinatra Thanks! Could this ship with RetroPie without any issues?
-
@danyo Huh, replacing the dc_flash worked for me at first but then stopped working.
I've tried resetting the VMUs multiple times to no avail unfortunately.
-
@goigle said in Every time I play dreamcast, displays the setting screen time/date:
@danyo Huh, replacing the dc_flash worked for me at first but then stopped working.
I've tried resetting the VMUs multiple times to no avail unfortunately.
Ditto,
Using the posted dc_flash filed worked for a couple of weeks, but stopped last night. I tried replacing the file, and resetting the VMU, and still get the request to set the date/time. -
@TyphonInc Mine setup also stopped working after weeks without problems.... :( replaced dc_flash, creating new VMU's... nothing worked...
-
It stopped working for me too.
The reason for this bug is that (currently) the linux client does not exit cleanly and just halts execution. This means that it does not call the routines to save the NVRAM which results in no date and time being saved.
https://github.com/reicast/reicast-emulator/issues/863There is already a pull-request with the fix submitted:
https://github.com/reicast/reicast-emulator/pull/917
But there is no new version of reicast available.Temporary fix:
I found a reicast branch that contains all fixes for this problem and should be upto date with the current reicast master:
https://github.com/7oxicshadow/reicast-emulatorIs somebody able to build it and can provide the fixed emulator for us?
-
I couldn't get it to work using the new methods here. It seems as if (at least for me; RPi 3 w/ Retropie 4.2) reicast will only play nice with dc_flash.bin with MD5 checksum 74e3f69c2bb92bc1fc5d9a53dcf6ffe2.
Granted, I can still save new games and load my saves.....so this issue of having to set the date/time each time is more cosmetic and slightly annoying rather than an impediment on actual gameplay and data loading.
I agree with danyo than the software just needs to be updated to fix this issue on the majority of builds, IMO.
-
@danyo said in Every time I play dreamcast, displays the setting screen time/date:
It stopped working for me too.
The reason for this bug is that (currently) the linux client does not exit cleanly and just halts execution. This means that it does not call the routines to save the NVRAM which results in no date and time being saved.
https://github.com/reicast/reicast-emulator/issues/863There is already a pull-request with the fix submitted:
https://github.com/reicast/reicast-emulator/pull/917
But there is no new version of reicast available.Temporary fix:
I found a reicast branch that contains all fixes for this problem and should be upto date with the current reicast master:
https://github.com/7oxicshadow/reicast-emulatorIs somebody able to build it and can provide the fixed emulator for us?
I hope this gets merged in soon. :)
-
I have updated my branch to hopefully fix the "date/time" problem when using RetroPie.
Some Background:
My initial fix for this issue was tested on both a linux desktop machine and a Raspberry PI and both worked as expected. I had never tried it with a front end launcher before as I always use them standalone.
When I read that people were still having problems using my branch on RetroPie I ran some tests and confirmed that it did not work??? This didn't make sense as I could run it standalone and it worked fine?
After digging around in the launch script used by RetroPie it was apparent that they make use of the command line switch "-config" which allows you to configure most of the options in the emu.cfg at launch.
It appears that using "-config" forces Reicast to use a "virtual" configuration and as such discards everything in the emu.cfg file. This means that the dreamcast.RTC value was also being discarded and a default value being used resulting in the Dreamcast bios displaying the date/time screen.
I have done some quick tests using my latest branch on RetroPie and the issue seems resolved.
If any Devs are reading this and want to try it, it is important that you modify the makefile in /shell/linux to enable NO_VIRTUAL_CFG. This will allow the -config command line to modify the emu.cfg fle rather than a virtual ram copy.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.