Every time I play dreamcast, displays the setting screen time/date
-
@Folly said in Every time I play dreamcast, displays the setting screen time/date:
@caver01 said in Every time I play dreamcast, displays the setting screen time/date:
@Folly said in Every time I play dreamcast, displays the setting screen time/date:
make a file in '/home/pi/.reicast/mappings' called controller_Your Gamepad.cfg and paste the text in this file.
now enjoy !
Ok, so I am trying to follow the instructions above. I use an IPAC-4 keyboard interface controller.
I ran ./reicast-joyconfig and selected it, went through the mapping process, received my configuration text. Created a file in the mappings folder called "Ultimarc I-PAC Arcade Control Interface .cfg" because that's what the config program output: mapping_name = Ultimarc I-PAC Arcade Control Interface .
So, I have this config file in the mappings folder. How do I tell reicast how to use that config file? When I launch the emulator, I get to the date screen, and I can't do anything! The clouds are animating, and it's just waiting for my input, but none of the keys I setup are doing anything. I need to login remotely and restart the pi.I must be missing a step. Right?
Hi caver01,
I think you forgot to put 'controller' in file name.
Your file has to be called :
'controller_Ultimarc I-PAC Arcade Control Interface .cfg'
When you start it will automatically find your controller.Bummer. So, I tried adding the word controller_ to my mapping file as suggested, but it didn't matter. 3.6 came with reicast and a mappings folder that already had several in there like controller_gcwz.cfg, controller_pandora.cfg, and so now I have mine, but it doesn't work. I still get into the date screen and I can't do anything with my controls. Is it perhaps waiting for input from an analog stick? All I can really map to keyboard is the d-pad and buttons. Ideas?
-
im having a similar issue with reicast where it keeps assigning my nes adapter to the first and second player instead of my 8Bitdo bluetooth controllers. is there anyway in the controller configs to force controller priority?
-
@caver01 said in Every time I play dreamcast, displays the setting screen time/date:
@Folly said in Every time I play dreamcast, displays the setting screen time/date:
@caver01 said in Every time I play dreamcast, displays the setting screen time/date:
@Folly said in Every time I play dreamcast, displays the setting screen time/date:
make a file in '/home/pi/.reicast/mappings' called controller_Your Gamepad.cfg and paste the text in this file.
now enjoy !
Ok, so I am trying to follow the instructions above. I use an IPAC-4 keyboard interface controller.
I ran ./reicast-joyconfig and selected it, went through the mapping process, received my configuration text. Created a file in the mappings folder called "Ultimarc I-PAC Arcade Control Interface .cfg" because that's what the config program output: mapping_name = Ultimarc I-PAC Arcade Control Interface .
So, I have this config file in the mappings folder. How do I tell reicast how to use that config file? When I launch the emulator, I get to the date screen, and I can't do anything! The clouds are animating, and it's just waiting for my input, but none of the keys I setup are doing anything. I need to login remotely and restart the pi.I must be missing a step. Right?
Hi caver01,
I think you forgot to put 'controller' in file name.
Your file has to be called :
'controller_Ultimarc I-PAC Arcade Control Interface .cfg'
When you start it will automatically find your controller.Bummer. So, I tried adding the word controller_ to my mapping file as suggested, but it didn't matter. 3.6 came with reicast and a mappings folder that already had several in there like controller_gcwz.cfg, controller_pandora.cfg, and so now I have mine, but it doesn't work. I still get into the date screen and I can't do anything with my controls. Is it perhaps waiting for input from an analog stick? All I can really map to keyboard is the d-pad and buttons. Ideas?
Check your filename again :
'controller_Ultimarc I-PAC Arcade Control Interface .cfg' (no space in front of .cfg(so there was a second fault))
it has to be :'controller_Ultimarc I-PAC Arcade Control Interface.cfg'Hope it helps.
-
@JoargTheBard said in Every time I play dreamcast, displays the setting screen time/date:
im having a similar issue with reicast where it keeps assigning my nes adapter to the first and second player instead of my 8Bitdo bluetooth controllers. is there anyway in the controller configs to force controller priority?
Don't know exactly how this works, but i think you can edit this in '/home/pi/.reicast/emu.cfg
-
@lcsjuniorsi said in Every time I play dreamcast, displays the setting screen time/date:
@Folly Hi, tomorrow I will do the tests suggested. Anyway, I decided to buy an RTC module.
Nice to hear you want to try this with an RTC module.
Should be nice if that's the solution.
Like to hear your results. -
@Folly said in Every time I play dreamcast, displays the setting screen time/date:
Check your filename again :
'controller_Ultimarc I-PAC Arcade Control Interface .cfg' (no space in front of .cfg(so there was a second fault))
it has to be :'controller_Ultimarc I-PAC Arcade Control Interface.cfg'Hope it helps.
No, that was just a transcription error on my part. There is no space at the end of the filename before the .cfg. The file is named exactly as you have it written here. It still doesn't work. It just completely ignores the keyboard.
-
@caver01 said in Every time I play dreamcast, displays the setting screen time/date:
@Folly said in Every time I play dreamcast, displays the setting screen time/date:
Check your filename again :
'controller_Ultimarc I-PAC Arcade Control Interface .cfg' (no space in front of .cfg(so there was a second fault))
it has to be :'controller_Ultimarc I-PAC Arcade Control Interface.cfg'Hope it helps.
No, that was just a transcription error on my part. There is no space at the end of the filename before the .cfg. The file is named exactly as you have it written here. It still doesn't work. It just completely ignores the keyboard.
Sorry,
Can't help you with this for the moment. -
@Folly When my pi boots, it assigns my adapter controllers to js0 and js1, so when my bluetooth controllers connect, they get indexed as js2 and js3. i need to get my bluetooth controllers to take those slots when they connect, but i cant figure that out. it would solve a lot of controller issues im having with the stuff that doesnt use retroarch controls. Reicast kept overwriting my emu.cfg file with the raphnet adater settings when it booted, so i had to comment out the autoconfig command in the reicast.sh script so it would go with the default one that has the NES30 Pro controls.
-
Is it possible that autoconfig is also preventing my keyboard controller from working? It would be nice to understand exactly what is happening. I feel unable to troubleshoot because I don't understand what it is doing.
-
heres what i was told that fixed my issue:
@Hyell said in Dreamcast Controls Issues:
Hello,
When you start reicast, you launch a script :
/opt/retropie/emulators/reicast/bin/reicast.shIn this script, you got a function : mapInput(). It's editing emu.cfg
I think you can comment a line to disable mapInput() (near the end of file):
getAutoConf reicast_input || mapInput
just add "#" like this :
# getAutoConf reicast_input || mapInputOr change this line (begining of the file):
local conf="$configdir/dreamcast/emu.cfg"
to
local conf="$configdir/dreamcast/emu.cfg.autoConf"i then set set the right controllers and automap files in the emu.cfg, and everything worked. hope this helps!
I think it will work :
-
@JoargTheBard Thanks for pointing me in the (possibly) right direction! I will dig in and see what I can do.
-
@JoargTheBard said in Every time I play dreamcast, displays the setting screen time/date:
i then set set the right controllers and automap files in the emu.cfg, and everything worked. hope this helps!
Do you mean that you transcribed the results of the reicast-joyconfig directly into the emu.cfg? That seems easy enough.
-
the controller config part of my emu.cfg looks like this
[input]
evdev_device_id_1 = 2
evdev_device_id_2 = 3
evdev_device_id_3 = -1
evdev_device_id_4 = -1
evdev_mapping_1 = /opt/retropie/configs/dreamcast/mappings/controller_8BitdoNES30Pro.cfg
evdev_mapping_2 = /opt/retropie/configs/dreamcast/mappings/controller_8BitdoNES30Pro.cfg
joystick_device_id = -1 -
@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. -
@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
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.