Jump to content
IGNORED

RetroBat (Windows 11 EmulationStation Frontend) using .rpk format (MAME64 or Libretro/MAME)


Recommended Posts

 

RetroBat (Windows 11 Emulation Station Frontend) using .rpk format (MAME64 or Libretro/MAME)

 

Why?

* With Batocera I need to reboot my PC go to the BIOS to switch each time between Batocera and Windows (and for laptops, I need to reconfigure the BIOS to disable secure boot)

   I like Batocera, which is a Linux based Emulation Station) running from a USB drive  (it can be installed dedicated on a PC), but I am using this device with Windows and other purposes (e.g. watch TV channels)

   https://forums.atariage.com/topic/335490-batocera-emulation-system-and-ti-994a

 

* RetroBat solves that issue as it runs on Windows 11 (64 Bit), but for the TI-99/4A it relies on the .zip file structure for roms.

   It has the same Emulation Station interface, but I did not want to redo all the work done for the Batocera configuration

 

* It is very straight forward to install and to customize it

 

  The only issues I currently have

   1.  Bezel backdrop does not work (works with Libretro/MAME, not with MAME64 starting from RetroBat, but from command prompt mame it shows the Bezel)

   2.  When using Libretro/MAME it sometimes start the TI-99/4A, sometimes not (very similar issue as in Batocera setup).   MAME64 (v253) is stable in startup

   3.  USB-DB9 Joystick works in MAME64,  but a PS4 controller does not work  (but PS4 controller works with Libretro/MAME)

   4.  Hotkey using a keyboard does not work.   (now using ALT TAB to exit), but the PS4 controller works with SHARE + OPTION buttons as hotkeys to exit)

 

 

  • Like 3

 

Detailed instructions how to install RetroBat for a TI-99/4A system on Windows 11 (64-bit).

 

TI99-Retrobat-Setup.zip

  

  (the directory you can copy it over the installed directories it will overwrite / merge into those directories)

 

  for /roms/ti99, with preview of images, videos (see the Batocera thread https://forums.atariage.com/topic/335490-batocera-emulation-system-and-ti-994a)

 

 

This video is Batocera based, but RetroBat has the same Emulation Station interface:

 

Edited by globeron
  • Like 2
  • Thanks 1

Item 1 (Bezel of TI99) and 3 (PS4 controller) seems to be resolved magically on my other PC which I normally use.  For item 2 i use now Mame64.

 

Only item 4 left. Hotkey on the keyboard with TI99 (other emulators Shift + Esc works).

But I am using the PS4 controller hockey (PS + OPTIONS). 

 

 

Also updated with another TI-Logo (file called mess.png)  for the system (C:\RetroBat\emulationstation\.emulationstation\themes\es-theme-carbon\art\logos)

 

TI99-Retrobat-Setup.zip

 

Edited by globeron
  • Like 1
  • 3 weeks later...

 

Update:

 

TI99-Retrobat-Setup-v2.zip

 

in the logo's directory either delete "mess.svg"  (or overwrite it with a Ti-logo mess.svg) otherwise the MESS logo remains.

 

Re issue 4 fix  * added the /Retrobat/bios/mame/ini/mame.ini file  (UI_Active    1),  so that the ESC (Keyboard) works to exit back to Retrobat

                     (or create a mame.ini file  using  mame  -createconfig and copy that into the directory above)

 

Re issue 2 - use MAME64 it is more stable and starts the emulator (Libretro does not start the emulator)

 

 

Items to sort out:

Re issue 3 - when using a USB-Controller everything works and sometimes the Bluetooth connected PS4-type controller also works normally.

                  (I have not figured out yet when the PS4 controller works and when not).

 

Issue 1:

 

 The only issues I currently have

   1.  Bezel backdrop does not work (works with Libretro/MAME, not with MAME64 starting from RetroBat, but from command prompt mame it shows the Bezel)

   2.  Fixed (use MAME64) - When using Libretro/MAME it sometimes start the TI-99/4A, sometimes not (very similar issue as in Batocera setup).   MAME64 (v253) is stable in startup

   3.  USB-DB9 Joystick works in MAME64,  but a PS4 controller does not work  (but PS4 controller works with Libretro/MAME)

   4.  (Fixed, UI Active  1 in mame.ini)  - Hotkey using a keyboard does not work.   (now using ALT TAB to exit), but the PS4 controller works with SHARE + OPTION buttons as hotkeys to exit)

 

 

 

  • Like 2
On 6/10/2023 at 8:59 AM, globeron said:

 

Why?

* With Batocera I need to reboot my PC go to the BIOS to switch each time between Batocera and Windows (and for laptops, I need to reconfigure the BIOS to disable secure boot)

 

 

 

 

I'll try RetroBat, however it's possible to install Windows 11 without TPM 2.0 and Secure Boot creating a bootable USB stick (try Rufus 4.1). ;-) 

 

  • Like 1
Just now, tmop69 said:

 

I'll try RetroBat, however it's possible to install Windows 11 without TPM 2.0 and Secure Boot creating a bootable USB stick (try Rufus 4.1). ;-) 

 

Also, try Tiny11.

https://archive.org/details/tiny-11-NTDEV

  • Like 3
  • 2 weeks later...

 

Fixed item 1 - Bezel backdrop 

TI-99/4A Bezel.

 

files are in this zip:

TI99-Retrobat-Setup-v3.zip

 

 

 

For the Bezels, this is the directory that worked for me (using a TI-99/4A and using MAME)
C:\RetroBat\saves\mame\artwork
put here genhorizontal.zip
and horizont.ini in C:\Retrobat\bios\mame\ini

horizont.ini:
#
# CORE ARTWORK OPTIONS
#
fallback_artwork genhorizontal

# Uncomment next line to use this for all games
override_artwork genhorizont


These posts helped:
https://mrdo.mameworld.info/mame_artwork_generic.php (e.g. download genhorizont.zip)
https://forums.launchbox-app.com/topic/54304-default-mame-bezels/

 

 

  • Like 2

 

(Not working via Retrobat yet to start MAME,  not sure if both Retrobat/Emulstation and MAME can use the Bluetooth PS4 Controllers, but all other systems work fine).

 

When using MAME directly it works partially.

 

3.  USB-DB9 Joystick works in MAME64,  but a PS4 controller does not work 

 

 

(Via UI Mode,  press TAB):

* Bluetooth PS4 controller gets detected in MAME under Joystick (number 1 means Joystick 1,  if you have more you see Joystick 2)

* Often I see all 0  under Device ID

* Then I turn off the Bluetooth controller and turned it on, then all is working  (you see these values)

   (this works directly with MAME, but with Retrobat,  it remains all 0 and turn on/off the PS4 controller sometimes shows -65536, etc. but does not work)

 

964284189_SCR563.thumb.jpg.7578af2ebe4e1fd51481d7cbf299fcf4.jpg

837159530_SCR558.thumb.jpg.cc5b03f24439c1517758424dfb16fb14.jpg

1519813751_SCR561.thumb.jpg.d4fb828e6649b649ebe75658b7b391b8.jpg

 

 

 

 

 

 

 

 

 

7 hours ago, gferluga said:

I follow the instructions but when I select a cart in Mame I get a message that required rom is missing or incorrect.

Please advise...

Thanks in advance.

 

 

My guess is that the 

 

C:\RetroBat\roms\ti99  directory  is empty ?  (no .rpk)

 

(see ti99 directory here):

https://ftp.whtech.com/Cartridges/Batocera/Batocera-ti99v2.zip

 

 

 

 

4 hours ago, mizapf said:

Please tell us the precise error message; this will likely give the answer.

 

For the Wireless Controllers issue - there is no error message 

(I can see them being connected as 1 and 2, but no input, unless I turn them on/off sometimes it works in MAME,  I guess a bluetooth / Windows issue and if 2 programs use the controllers (retrobat/emulstation and mame)

I am using MAME 256  (but tried earlier versions as well)

 

 

When using USB (for Joystick controllers) it works fine (as long they are assigned wireless port 1 and 2 of course,  means to turn of all other controllers as they dynamically might take port 1 and 2)

(it can be configured statically to use port 1 and 2 for the specific controllers I saw)

 

 

 

 

  • Like 1

And your console ROMs? (ti99_4a.zip)

 

(Note: The RPKs may be put wherever you want; they need not be put in a preset path, since you have to provide the full path name anyway. Only the *.zip files must be put into the rompath.)

I could reproduce this error message when I removed the ti99_4a.zip file, so it seems that your installation does not find the file in the dedicated path. If you have a mame.ini, what does your rompath setting say? (for me, 11th line from the top)

 

I usually run MAME from a command line, not by clicking the mame executable, so your situation may vary from mine.

 

  • Like 1

Reinstalled from scratch, but no success. Same errors.

 

From command line I get:

 

C:\RetroBat\emulators\mame>mame ti99_4a
994a_rom_hb.u610 NOT FOUND (tried in ti99_4a)
994a_rom_lb.u611 NOT FOUND (tried in ti99_4a)
994a_grom0.u500 NOT FOUND (tried in ti99_4a)
994a_grom1.u501 NOT FOUND (tried in ti99_4a)
994a_grom2.u502 NOT FOUND (tried in ti99_4a)
Fatal error: Required files are missing, the machine cannot be run.

C:\RetroBat\emulators\mame>

 

Try mame ti99_4a -rompath c:\retrobat\bios

 

and maybe check that ti99_4a.zip contains the files as listed above - just to make sure you did not use an outdated rom package.

  • Like 1
6 hours ago, gferluga said:

It's working. I have had to copy the mame.ini file into C:\RetroBat\emulators\mame

 

glad to hear it works!

 

I thought when starting MAME from Retrobat it uses the mame.ini from this directory - C:\RetroBat\bios\mame\ini   (I will add it to this in the TI-99.zip file)

and starting mame directly it uses C:\RetroBat\emulators\mame

 

(and similar with the bezel artwork it uses another directory from the saves\mame\artwork directory vs  \emulators\mame\artwork

 

 

 

 

 

 

  • 5 months later...

 

Retrobat/MAME64  (.rpk format, with preview pictures and videos). 

 

TI-99/4A - now 337 titles are working: 

image.thumb.jpeg.e711137976d4c72f00da6c6d872f3538.jpeg  image.thumb.png.70a10efa057f48028161bf2cd6881230.png

 

 

 

 

NOTE:

Note - F18A related games DO NOT work on the Retrobat/MAME64 install (as it emulates a normal TI-99/4A)

 

F18A programs these you can try out online at js99er.net

(enable F18A in the Option menu) .cc @Asmusr

image.png.30f0e086a5c24b2805d86a8ef48c16ce.png

image.thumb.png.d32d027e68094ff42e2112b8fa19bd3b.png

  • Like 2

Troubleshooting why PS4 wireless controllers do not work when started via Retrobat in the MAME64 emulator.

 

USB wired controllers all work fine in Retrobat and opening MAME64 with TI-99/4A emulator (they do not have this issue),

but the bluetooth PS4 wireless controllers is having issues (combination of Retrobat + Windows+ MAME64 ?)

Sometimes after turning off the PS4 controller (with the P button on the controller - hold for 10 seconds and then turning on might work once in a while). 

 

In Retrobat in the  C:\RetroBat\emulationstation\emulatorLauncher.log

 

2024-01-13 18:21:46.866 [INFO]      --------------------------------------------------------------
2024-01-13 18:21:46.875 [INFO]      [Startup] "C:\RetroBat\emulationstation\emulatorLauncher.exe"  -p1index 0 -p1guid 030000004c050000cc09000000006800 -p1path "\\?\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&0002054c_pid&09cc#9&31f89a67&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" -p1name "PS4 Controller" -p1nbbuttons 16 -p1nbhats 0 -p1nbaxes 6  -system ti99 -emulator mame64 -core mame64 -gameinfo "C:\Users\globe\AppData\Local\Temp\emulationstation.tmp\game.xml" -rom "C:\RetroBat\roms\ti99\MarioBrosE.rpk"
2024-01-13 18:21:46.934 [INFO]      [Game] MarioBros
2024-01-13 18:21:47.020 [INFO]      [Generator] Using Mame64Generator
2024-01-13 18:21:47.083 [INFO]      [PadToKey] Loaded C:\RetroBat\emulationstation\.emulationstation\es_padtokey.cfg
2024-01-13 18:21:47.086 [INFO]      [Running] C:\RetroBat\emulators\mame\mame.exe ti99_4a -skip_gameinfo -rompath C:\RetroBat\bios;C:\RetroBat\roms\ti99 -cfg_directory C:\RetroBat\bios\mame\cfg -inipath C:\RetroBat\bios\mame\ini -hashpath C:\RetroBat\bios\mame\hash -artpath C:\RetroBat\saves\mame\artwork -snapshot_directory C:\RetroBat\screenshots -ioport peb -ioport:peb:slot2 32kmem -ioport:peb:slot3 speech -cart C:\RetroBat\roms\ti99\MarioBrosE.rpk -state_directory C:\RetroBat\saves\mame\states -ctrlrpath C:\RetroBat\saves\mame\ctrlr -nofilter -verbose -throttle -sound dsound -video d3d -resolution auto -aspect auto -waitvsync -dial_device joystick -trackball_device joystick -paddle_device joystick -positional_device joystick -mouse_device joystick -joystickprovider dinput
2024-01-13 18:21:47.175 [INFO]      [PadToKey] Add joystick PS4 Controller - Device:0, Player:1, Path:\\?\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&0002054c_pid&09cc#9&31f89a67&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
2024-01-13 18:22:22.230 [INFO]      PS4 Controller - Device:0, Player:1, Path:\\?\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&0002054c_pid&09cc#9&31f89a67&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
2024-01-13 18:22:29.029 [INFO]      [PadToKey] Add joystick PS4 Controller - Device:0, Player:1, Path:\\?\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&0002054c_pid&09cc#9&31f89a67&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
2024-01-13 18:22:29.034 [INFO]      [PadToKey] Add joystick PS4 Controller - Device:0, Player:1, Path:\\?\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&0002054c_pid&09cc#9&31f89a67&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
2024-01-13 18:25:27.744 [INFO]      PS4 Controller - Device:0, Player:1, Path:\\?\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&0002054c_pid&09cc#9&31f89a67&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
2024-01-13 18:25:27.748 [INFO]      PS4 Controller - Device:0, Player:1, Path:\\?\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&0002054c_pid&09cc#9&31f89a67&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
2024-01-13 18:25:29.438 [INFO]      [PadToKey] Add joystick PS4 Controller - Device:0, Player:1, Path:\\?\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&0002054c_pid&09cc#9&31f89a67&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
2024-01-13 18:25:29.443 [INFO]      [PadToKey] Add joystick PS4 Controller - Device:0, Player:1, Path:\\?\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&0002054c_pid&09cc#9&31f89a67&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
2024-01-13 18:25:58.868 [INFO]      PS4 Controller - Device:0, Player:1, Path:\\?\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&0002054c_pid&09cc#9&31f89a67&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
2024-01-13 18:25:58.872 [INFO]      PS4 Controller - Device:0, Player:1, Path:\\?\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&0002054c_pid&09cc#9&31f89a67&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
2024-01-13 18:26:01.502 [INFO]      [PadToKey] Add joystick PS4 Controller - Device:0, Player:1, Path:\\?\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&0002054c_pid&09cc#9&31f89a67&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
2024-01-13 18:28:26.857 [INFO]      PS4 Controller - Device:0, Player:1, Path:\\?\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&0002054c_pid&09cc#9&31f89a67&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
 

 

then copied this command line (and added -ui_active,   or use mame.ini in the \bios\mame\ini\mame.ini file (to set ui_active  1)

 

 

 

See video part 1 (seems to work):

PS4 controller paired with Windows and turned on (connected), then start MAME64 and exit, start-again, exit, etc. it seems to work properly.

(sometimes the PS4 controller is seen in MAME64, but does not react to buttons, then turn it off (P button on the controller hold for 10 sec.) 

and turn it on again, then suddenly it might work (verify it with the menu (via TAB button), to see if the wireless device/joystick receives input signals.

 

via Command line:

C:\RetroBat\emulationstation>

 

C:\RetroBat\emulators\mame\mame.exe ti99_4a -skip_gameinfo -rompath C:\RetroBat\bios;C:\RetroBat\roms\ti99 -cfg_directory C:\RetroBat\bios\mame\cfg -inipath C:\RetroBat\bios\mame\ini -hashpath C:\RetroBat\bios\mame\hash -artpath C:\RetroBat\saves\mame\artwork -snapshot_directory C:\RetroBat\screenshots -ioport peb -ioport:peb:slot2 32kmem -ioport:peb:slot3 speech -cart C:\RetroBat\roms\ti99\MarioBrosE.rpk -state_directory C:\RetroBat\saves\mame\states -ctrlrpath C:\RetroBat\saves\mame\ctrlr -nofilter -verbose -throttle -sound dsound -video d3d -resolution auto -aspect auto -waitvsync -dial_device joystick -trackball_device joystick -paddle_device joystick -positional_device joystick -mouse_device joystick -joystickprovider dinput -ui_active

 

 

 

 

 

See video part 2 (does not work):

PS4 controller paired with Windows and turned on (connected), then start Retrobat.

 

You can start it directly  C:\Retrobat\retrobat.exe

 

but using this batch file (as in Retrobat forum there are other emulators that might lock the controller as well),

but so far all my other emulators work fine, except the Retrobat MAME64 combination. 

 

Weird enough the escape (hotkey) by pressing Select + Start works in the emulator to go back to Retrobat (or maybe Retrobat is still managing the PS4 Controller)

 

 

Retrobatstart.bat

@echo off
taskkill /f /im explorer.exe
retrobat.exe
set "emulatorProcess=emulationstation.exe"
:CHECK_PROCESS
tasklist /fi "imagename eq %emulatorProcess%" | findstr /i /c:"%emulatorProcess%" > nul
if %errorlevel% equ 0 (
    timeout /nobreak /t 5 > nul
    goto :CHECK_PROCESS
)
start explorer.exe
exit /b 0
 

 

MAME64 and exit, start-again, exit, etc. it seems to work properly.

(sometimes the PS4 controller is seen in MAME64, but it does not react to buttons, then turn it off (P button on the controller hold for 10 sec.) 

and turn it on again, then suddenly it might work (verify it with the menu (via TAB button), to see if the wireless device/joystick receives input signals.

 

In the video the PS4 controller works fine Retrobat, but not when starting MAME64.   (but other emulators work fine via Retrobat with the PS4 wireless controller)

 

 

  • Like 1

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...