• Star Wars themed Arcade Cabinet

    Projects and Themes
    4
    3 Votes
    4 Posts
    875 Views
    P

    @windg & @mitu you spotted it. It's the image on the front door.
    I was mounting the vinyl with the door on my workbench and did not realize that it was 180 degrees rotated. Bummer!
    Moving the hinges to the other side is unfortunately not easy for several reasons, so I have decided to order another printed piece of vinyl and cover it again.
    Waiting to be delivered ...

  • 0 Votes
    2 Posts
    543 Views
    windgW

    I have read that ps1 mini is using the pcsx-rearmed emulator.
    This emulator had the issue with this game you describe but it get fixed see: https://github.com/libretro/pcsx_rearmed/issues/560. Maybe the version that the system is using is older. I don't know if you can the update the emulator

    You can try to change the Dynamic recompiler to interpreter (slower), if you have this option.

  • 0 Votes
    15 Posts
    1k Views
    D

    I banged my head over this for some time before coming up with a solution.

    The problem is that when you hit that power button, an interrupt is sent to the login daemon, telling it to shutdown the system. You can't interrupt that in any way, or replace it with a different operation as far as I can see.

    You can create a service with killall -s SIGTERM retroarch in its shutdown operation - but by then it's too late. Systemctl has already killed all user processes - including retroarch.

    So what I had to do was actually run retroarch as a service itself. That was systemctl left it for its own shutdown procedure. I'm fairly new services, so I don't claim this is the perfect solution but it works for me.

    This is based on "retropie" on a Raspberry Pi. If you're running some other Linux system it may or may not be helpful.

    First, we need to prevent retroarch from starting in the normal way. I edited /opt/retropie/configs/all/autostart.sh, commenting out the existing lines and adding in a call to the shell bash:

    bash #/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ mame-libretro ~/RetroPie/roms/mame-libretro/robotron.zip #emulationstation #auto

    Next I created a new service by adding a file /etc/systemd/system/killmame.service containing

    [Unit] Description=A service start and stop MAME cleanly After=console-setup network-online.target multi-user.target [Service] User=pi ExecStart=/home/pi/bin/start.sh ExecStop=/home/pi/bin/killmame.sh Type=simple StandardInput=tty-force TTYVHangup=yes TTYPath=/dev/tty20 TTYReset=yes SendSIGKILL=no KillMode=none [Install] WantedBy=multi-user.target

    Notes:

    You'll need to create that as root (eg. sudo nano killmame.service) killmame is a bad name for the service. It started off only intending to kill it, but morphed into a complete service - retroarch.service might be a better name All the tty stuff is needed or retroarch won't run The two scripts in ExecStart and ExecStop need to be created in the next step

    Now we create a directory /home/pi/bin and create the two scripts in the (can do this as the pi user):

    start.sh:

    #!/bin/bash cd /home/pi export TERM=linux export USER=pi chvt 20 /opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ mame-libretro ~/RetroPie/roms/mame-libretro/robotron.zip & bash

    The command starting /opt/retropie is what I previously had in my autostart.sh. Obviously it's specific to my game, you will need to change it to whatever you had in your autostart.sh file.

    You MUST have the & character at the end, putting the command into background. Otherwise systemctl will kill it in the early steps of shutdown. I'm not sure why.

    killmame.sh:

    #!/bin/bash # echo checking for mame running ... > /home/pi/bin/killmame.log # ps -deafww | grep libretro | grep robotron >> /home/pi/bin/killmame.log killall -s SIGTERM retroarch echo shutting down MAME at `date` >> /home/pi/bin/killmame.log

    The commented-out lines 'echo' and 'ps' were for debugging - to see if my game was actually running when it came to being shut down.

    Finally we need to register and enable our new service:

    sudo systemctl daemon-reload sudo systemctl start killmame sudo systemctl enable killmame

    All those should complete without output. If the 'start' fails, you'll need to figure out why before continuing.

    If they all work, you can reboot. Your machine should first drop into a shell prompt, but then very soon after retroarch should take over. Hitting the kill switch should now shutdown retroarch cleanly, saving high scores.

    The only glitch I've found is that if you use <ESCAPE> to exit retroarch, you'll find lots of key presses on the shell window from your game controls. Usually they're harmless but it's just possible you might accidently issue some fatal commands. Probably removing the invocation of bash from autostart.sh woud solve that, but you might then not be able to get back into a shell after exiting with escape. I generally log in remotely using ssh, so that wouldn't worry me.

    I hope this helps someone as I spent hours trawling for a solution without finding one. It was only while explaining to my wife why it was impossible, that it occurred to me to actually run retroarch as a service itself.

    If someone is able to tidy this up into a cleaner solution I'd be very grateful.

  • 0 Votes
    2 Posts
    366 Views
    J

    I've managed to get somewhere with this. I was looking at the rom history on another website and it seems the dip switch function is broken in the driver. The workaround is to make the changes in service mode. I have tried this and can verify that it works. Changing them from the mame menu would be better, but as its usually only a one-off change, I'll live with it.

  • 0 Votes
    1 Posts
    566 Views
    No one has replied
  • 0 Votes
    11 Posts
    1k Views
    J

    @mitu I've got it working now, I had a typo in my file, I had missed out the / before dev/input/. Schoolboy error but sorted now. Many thanks for the pointers and your help. Working between my PC and the cabinet is quite tricky. I'll need to get SSH sorted out so I can do the edits from the PC direct.

  • 17 Votes
    52 Posts
    13k Views
    S

    sorry.I wasn't asking for the game roms,just the already to go set up really,I can add the roms myself

    thankyou

  • 0 Votes
    1 Posts
    166 Views
    No one has replied
  • Retropie R2D2

    Projects and Themes
    5
    4 Votes
    5 Posts
    1k Views
    simpleethatS

    @IanDaemon 1. I wanted them to match (couldn't find square HMDI readily)
    2. The places I put them are actually round details. Apparently the paint I was using didn't particularly like rubbery material
    see original

  • 0 Votes
    3 Posts
    585 Views
    A

    Thanks!

  • 0 Votes
    2 Posts
    664 Views
    edmaul69E

    @funkybunch if you can actually use it, it would be axis 4 +/- for left and right and axis 5 +/- for up and down.

  • 0 Votes
    65 Posts
    15k Views
    quicksilverQ

    @snowpile
    Sorry for the late replay. Create a file in your /roms/pc/ folder called Tie Fighter.conf copy and paste the contents below into that file and use it to launch your game. If you have any issues let me know.

    # This is the configuration file for DOSBox SVN. (Please use the latest version of DOSBox) # Lines starting with a # are comment lines and are ignored by DOSBox. # They are used to (briefly) document the effect of each option. [sdl] # fullscreen: Start dosbox directly in fullscreen. (Press ALT-Enter to go back) # fulldouble: Use double buffering in fullscreen. It can reduce screen flickering, but it can also result in a slow DOSBox. # fullresolution: What resolution to use for fullscreen: original, desktop or a fixed size (e.g. 1024x768). # Using your monitor's native resolution with aspect=true might give the best results. # If you end up with small window on a large screen, try an output different from surface.On Windows 10 with display scaling (Scale and layout) set to a value above 100%, it is recommended # to use a lower full/windowresolution, in order to avoid window size problems. # windowresolution: Scale the window to this size IF the output device supports hardware scaling. # (output=surface does not!) # output: What video system to use for output. # Possible values: surface, overlay. # autolock: Mouse will automatically lock, if you click on the screen. (Press CTRL-F10 to unlock) # sensitivity: Mouse sensitivity. The optional second parameter specifies vertical sensitivity (e.g. 100,-50). # waitonerror: Wait before closing the console if dosbox has an error. # priority: Priority levels for dosbox. Second entry behind the comma is for when dosbox is not focused/minimized. # pause is only valid for the second entry. # Possible values: lowest, lower, normal, higher, highest, pause. # mapperfile: File used to load/save the key/event mappings from. Resetmapper only works with the default value. # usescancodes: Avoid usage of symkeys, might not work on all operating systems. fullscreen = true fulldouble = false fullresolution = desktop windowresolution = original output = overlay autolock = true sensitivity = 100 waitonerror = true priority = higher,normal mapperfile = mapper-SVN.map usescancodes = false [dosbox] # language: Select another language file. # machine: The type of machine DOSBox tries to emulate. # Possible values: hercules, cga, tandy, pcjr, ega, vgaonly, svga_s3, svga_et3000, svga_et4000, svga_paradise, vesa_nolfb, vesa_oldvbe. # captures: Directory where things like wave, midi, screenshot get captured. # memsize: Amount of memory DOSBox has in megabytes. # This value is best left at its default to avoid problems with some games, # though few games might require a higher value. # There is generally no speed advantage when raising this value. language = machine = svga_s3 captures = capture memsize = 16 [render] # frameskip: How many frames DOSBox skips before drawing one. # aspect: Do aspect correction, if your output method doesn't support scaling this can slow things down! # scaler: Scaler used to enlarge/enhance low resolution modes. If 'forced' is appended, # then the scaler will be used even if the result might not be desired. # To fit a scaler in the resolution used at full screen may require a border or side bars, # to fill the screen entirely, depending on your hardware, a different scaler/fullresolution might work. # Possible values: none, normal2x, normal3x, advmame2x, advmame3x, advinterp2x, advinterp3x, hq2x, hq3x, 2xsai, super2xsai, supereagle, tv2x, tv3x, rgb2x, rgb3x, scan2x, scan3x. frameskip = 0 aspect = false scaler = none [cpu] # core: CPU Core used in emulation. auto will switch to dynamic if available and # appropriate. # Possible values: auto, dynamic, normal, simple. # cputype: CPU Type used in emulation. auto is the fastest choice. # Possible values: auto, 386, 386_slow, 486_slow, pentium_slow, 386_prefetch. # cycles: Amount of instructions DOSBox tries to emulate each millisecond. # Setting this value too high results in sound dropouts and lags. # Cycles can be set in 3 ways: # 'auto' tries to guess what a game needs. # It usually works, but can fail for certain games. # 'fixed #number' will set a fixed amount of cycles. This is what you usually # need if 'auto' fails (Example: fixed 4000). # 'max' will allocate as much cycles as your computer is able to # handle. # Possible values: auto, fixed, max. # cycleup: Amount of cycles to decrease/increase with keycombos.(CTRL-F11/CTRL-F12) # cycledown: Setting it lower than 100 will be a percentage. core = dynamic cputype = auto cycles = max cycleup = 10 cycledown = 20 [mixer] # nosound: Enable silent mode, sound is still emulated though. # rate: Mixer sample rate, setting any device's rate higher than this will probably lower their sound quality. # Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716. # blocksize: Mixer block size, larger blocks might help sound stuttering but sound will also be more lagged. # Possible values: 1024, 2048, 4096, 8192, 512, 256. # prebuffer: How many milliseconds of data to keep on top of the blocksize. nosound = false rate = 44100 blocksize = 1024 prebuffer = 25 [midi] # mpu401: Type of MPU-401 to emulate. # Possible values: intelligent, uart, none. # mididevice: Device that will receive the MIDI data from MPU-401. # Possible values: default, win32, alsa, oss, coreaudio, coremidi, none. # midiconfig: Special configuration options for the device driver. This is usually the id or part of the name of the device you want to use (find the id/name with mixer/listmidi). # Or in the case of coreaudio, you can specify a soundfont here. # When using a Roland MT-32 rev. 0 as midi output device, some games may require a delay in order to prevent 'buffer overflow' issues. # In that case, add 'delaysysex', for example: midiconfig=2 delaysysex # See the README/Manual for more details. mpu401 = intelligent mididevice = alsa midiconfig = 128:0 [sblaster] # sbtype: Type of Soundblaster to emulate. gb is Gameblaster. # Possible values: sb1, sb2, sbpro1, sbpro2, sb16, gb, none. # sbbase: The IO address of the soundblaster. # Possible values: 220, 240, 260, 280, 2a0, 2c0, 2e0, 300. # irq: The IRQ number of the soundblaster. # Possible values: 7, 5, 3, 9, 10, 11, 12. # dma: The DMA number of the soundblaster. # Possible values: 1, 5, 0, 3, 6, 7. # hdma: The High DMA number of the soundblaster. # Possible values: 1, 5, 0, 3, 6, 7. # sbmixer: Allow the soundblaster mixer to modify the DOSBox mixer. # oplmode: Type of OPL emulation. On 'auto' the mode is determined by sblaster type. All OPL modes are Adlib-compatible, except for 'cms'. # Possible values: auto, cms, opl2, dualopl2, opl3, opl3gold, none. # oplemu: Provider for the OPL emulation. compat might provide better quality (see oplrate as well). # Possible values: default, compat, fast, mame. # oplrate: Sample rate of OPL music emulation. Use 49716 for highest quality (set the mixer rate accordingly). # Possible values: 44100, 49716, 48000, 32000, 22050, 16000, 11025, 8000. sbtype = sb16 sbbase = 220 irq = 7 dma = 1 hdma = 5 sbmixer = true oplmode = auto oplemu = default oplrate = 44100 [gus] # gus: Enable the Gravis Ultrasound emulation. # gusrate: Sample rate of Ultrasound emulation. # Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716. # gusbase: The IO base address of the Gravis Ultrasound. # Possible values: 240, 220, 260, 280, 2a0, 2c0, 2e0, 300. # gusirq: The IRQ number of the Gravis Ultrasound. # Possible values: 5, 3, 7, 9, 10, 11, 12. # gusdma: The DMA channel of the Gravis Ultrasound. # Possible values: 3, 0, 1, 5, 6, 7. # ultradir: Path to Ultrasound directory. In this directory # there should be a MIDI directory that contains # the patch files for GUS playback. Patch sets used # with Timidity should work fine. gus = false gusrate = 44100 gusbase = 240 gusirq = 5 gusdma = 3 ultradir = C:\ULTRASND [speaker] # pcspeaker: Enable PC-Speaker emulation. # pcrate: Sample rate of the PC-Speaker sound generation. # Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716. # tandy: Enable Tandy Sound System emulation. For 'auto', emulation is present only if machine is set to 'tandy'. # Possible values: auto, on, off. # tandyrate: Sample rate of the Tandy 3-Voice generation. # Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716. # disney: Enable Disney Sound Source emulation. (Covox Voice Master and Speech Thing compatible). pcspeaker = true pcrate = 44100 tandy = auto tandyrate = 44100 disney = true [joystick] # joysticktype: Type of joystick to emulate: auto (default), none, # 2axis (supports two joysticks), # 4axis (supports one joystick, first joystick used), # 4axis_2 (supports one joystick, second joystick used), # fcs (Thrustmaster), ch (CH Flightstick). # none disables joystick emulation. # auto chooses emulation depending on real joystick(s). # (Remember to reset dosbox's mapperfile if you saved it earlier) # Possible values: auto, 2axis, 4axis, 4axis_2, fcs, ch, none. # timed: enable timed intervals for axis. Experiment with this option, if your joystick drifts (away). # autofire: continuously fires as long as you keep the button pressed. # swap34: swap the 3rd and the 4th axis. Can be useful for certain joysticks. # buttonwrap: enable button wrapping at the number of emulated buttons. # circularinput: enable translation of circular input to square output. # Try enabling this if your left analog stick can only move in a circle. # deadzone: the percentage of motion to ignore. 100 turns the stick into a digital one. joysticktype = 2axis timed = false autofire = false swap34 = false buttonwrap = false circularinput = false deadzone = 10 [serial] # serial1: set type of device connected to com port. # Can be disabled, dummy, modem, nullmodem, directserial. # Additional parameters must be in the same line in the form of # parameter:value. Parameter for all types is irq (optional). # for directserial: realport (required), rxdelay (optional). # (realport:COM1 realport:ttyS0). # for modem: listenport (optional). # for nullmodem: server, rxdelay, txdelay, telnet, usedtr, # transparent, port, inhsocket (all optional). # Example: serial1=modem listenport:5000 # Possible values: dummy, disabled, modem, nullmodem, directserial. # serial2: see serial1 # Possible values: dummy, disabled, modem, nullmodem, directserial. # serial3: see serial1 # Possible values: dummy, disabled, modem, nullmodem, directserial. # serial4: see serial1 # Possible values: dummy, disabled, modem, nullmodem, directserial. serial1 = dummy serial2 = dummy serial3 = disabled serial4 = disabled [dos] # xms: Enable XMS support. # ems: Enable EMS support. The default (=true) provides the best # compatibility but certain applications may run better with # other choices, or require EMS support to be disabled (=false) # to work at all. # Possible values: true, emsboard, emm386, false. # umb: Enable UMB support. # keyboardlayout: Language code of the keyboard layout (or none). xms = true ems = true umb = true keyboardlayout = auto [ipx] # ipx: Enable ipx over UDP/IP emulation. ipx = false [autoexec] # Lines in this section will be run at startup. # You can put your MOUNT lines here. MOUNT c "/home/pi/RetroPie/roms/pc/Star Wars - Tie Fighter (1994)/" C: TIE.EXE exit
  • RetroPie R2D2

    Projects and Themes
    13
    4 Votes
    13 Posts
    4k Views
    W

    @edmaul69 Exceptional tips! Thank you. Yeah, I'm not a master of the dremel, as you can see. It was a learning process. And, you're right, there's loads more I want to do with this thing!

  • How to replicate setup

    Help and Support
    4
    0 Votes
    4 Posts
    2k Views
    cortex91C

    @matalog Alright, I think i can give it a go at the weekend.
    I'll post my testings in here and let you know if it works.

  • 0 Votes
    13 Posts
    4k Views
    I

    @mediamogul

    Have at it. I stole the heart of it from Heath Ledger's Joker.

  • 0 Votes
    23 Posts
    22k Views
    edmaul69E

    @akafox it sucks it isn't playable on the pi since it isnt dos or windows 3.1. Lots of dos star wars games though. I bought all of them on disc and floppy except the original star wars which was on a 5.25" floppy. I would download the unreleased super star wars as well for dos.