RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    Star Wars Dedicated Cab - Speed and sound problems

    Scheduled Pinned Locked Moved Help and Support
    mameslowsoundstarwars
    11 Posts 3 Posters 918 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • dankcushionsD
      dankcushions Global Moderator @nicosuave
      last edited by

      please provide a verbose log as per https://retropie.org.uk/forum/topic/3/read-this-first

      N 1 Reply Last reply Reply Quote 0
      • N
        nicosuave @dankcushions
        last edited by

        @dankcushions

        Hi I'm trying to figure out how to turn on verbose logging for Advanced Mame. This doesn't an option available when I open the rom via the emulation station.

        N 1 Reply Last reply Reply Quote 0
        • N
          nicosuave @nicosuave
          last edited by

          @nicosuave

          Sorry, I think I have it now:

          Verbose logging on, and I've chucked it up on pastebin.

          Pastebin

          dankcushionsD 1 Reply Last reply Reply Quote 0
          • dankcushionsD
            dankcushions Global Moderator @nicosuave
            last edited by

            @nicosuave i have no experience with advmame - this may be the usual performance for it on this game. have you tried the recommended arcade emulators? https://retropie.org.uk/docs/Arcade/#step-1-choose-your-arcade-emulators

            N 1 Reply Last reply Reply Quote 0
            • N
              nicosuave @dankcushions
              last edited by

              @dankcushions

              Yes, but unfortunately, the other emulators introduce a dead zone issue which is persistent with the flight yoke adapter. There are some earlier threads where folks reported getting this going, so I assume it's a settings issue I can address.

              @james-milroy , @wstanek , and @caver01 all had comments which pointed to changing the advmame.rc file, but I haven't been able to find effective snips of this file just yet.

              I'll try to PM them directly and see if they'd be able to help out.

              1 Reply Last reply Reply Quote 0
              • N
                nicosuave
                last edited by

                And just to add detail.

                Using lr-2003-plus, the audio and performance are clear and fast. However, the deadzone manifests and I can't figure out how to remove it.

                Using advmame, the deadzone is gone, but the performance is slow and the audio is slow/garbled.

                Using lr-mame2016, the deadzone is back, and the audio is good, performance is fast, but the video is fuzzy. Looks like the width of the vectors is off.

                Looks like lr-2003-plus is the closest yet, if I could just get it to listen my settings for the mapped controller. Here's how I have it setup right now:

                pi@retropie:/dev/input $ cat /proc/bus/input/devices
I: Bus=0003 Vendor=0483 Product=572b Version=0111
N: Name="Alan-1 USB Flight Yoke Adapter"
P: Phys=usb-0000:01:00.0-1.3/input0
S: Sysfs=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.0/0003:0483:572B.0004/input/input5
U: Uniq=0000
H: Handlers=event4 js0
B: PROP=0
B: EV=1b
B: KEY=f 0 0 0 0 0 0 0 0 0
B: ABS=3
B: MSC=10

I: Bus=0003 Vendor=6708 Product=2666 Version=0100
N: Name="2603666 CONTROLLER"
P: Phys=usb-0000:01:00.0-1.4/input0
S: Sysfs=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:6708:2666.0005/input/input6
U: Uniq=
H: Handlers=event5 js1
B: PROP=0
B: EV=1b
B: KEY=fff 0 0 0 0 0 0 0 0 0
B: ABS=30027
B: MSC=10

I: Bus=0003 Vendor=046d Product=4051 Version=0111
N: Name="Logitech M510"
P: Phys=usb-0000:01:00.0-1.1/input2:1
S: Sysfs=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1:1.2/0003:046D:C52B.0003/0003:046D:4051.0006/input/input31
U: Uniq=4051-c2-d7-06-4d
H: Handlers=mouse0 event0
B: PROP=0
B: EV=17
B: KEY=ffff0000 0 0 0 0 0 0 0 0
B: REL=1943
B: MSC=10

I: Bus=0003 Vendor=046d Product=4004 Version=0111
N: Name="Logitech K360"
P: Phys=usb-0000:01:00.0-1.1/input2:2
S: Sysfs=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1:1.2/0003:046D:C52B.0003/0003:046D:4004.0007/input/input32
U: Uniq=4004-78-a4-fd-87
H: Handlers=sysrq kbd leds event1
B: PROP=0
B: EV=12001f
B: KEY=3f 301ff 0 0 0 0 483ffff 17aff32d bfd44446 0 0 1 130ff3 8b17c007 ffff7bfa d941dfff ffbeffdf ffefffff ffffffff fffffffe
B: REL=1040
B: ABS=1 0
B: MSC=10
B: LED=1f

I: Bus=0003 Vendor=046d Product=4057 Version=0111
N: Name="Logitech B330/M330/M331"
P: Phys=usb-0000:01:00.0-1.1/input2:3
S: Sysfs=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1:1.2/0003:046D:C52B.0003/0003:046D:4057.0008/input/input33
U: Uniq=4057-9c-a1-cd-77
H: Handlers=mouse1 event2
B: PROP=0
B: EV=17
B: KEY=ffff0000 0 0 0 0 0 0 0 0
B: REL=1943
B: MSC=10

I: Bus=0003 Vendor=046d Product=4004 Version=0111
N: Name="Logitech K360"
P: Phys=usb-0000:01:00.0-1.1/input2:4
S: Sysfs=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1:1.2/0003:046D:C52B.0003/0003:046D:4004.0009/input/input34
U: Uniq=4004-54-4a-51-92
H: Handlers=sysrq kbd leds event3
B: PROP=0
B: EV=12001f
B: KEY=3f 301ff 0 0 0 0 483ffff 17aff32d bfd44446 0 0 1 130ff3 8b17c007 ffff7bfa d941dfff ffbeffdf ffefffff ffffffff fffffffe
B: REL=1040
B: ABS=1 0
B: MSC=10
B: LED=1f

I: Bus=0003 Vendor=046d Product=4057 Version=0111
N: Name="Logitech B330/M330/M331"
P: Phys=usb-0000:01:00.0-1.1/input2:5
S: Sysfs=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1:1.2/0003:046D:C52B.0003/0003:046D:4057.000A/input/input35
U: Uniq=4057-d6-cb-07-53
H: Handlers=mouse2 event6
B: PROP=0
B: EV=17
B: KEY=ffff0000 0 0 0 0 0 0 0 0
B: REL=1943
B: MSC=10

                I ran Evdev for event 4:

                pi@retropie:/dev/input $ evdev-joystick --s /dev/input/event4
Supported Absolute axes:
  Absolute axis 0x00 (0) (X Axis) (value: 1277, min: 0, max: 4095, flatness: 0 (=0.00%), fuzz: 0)
  Absolute axis 0x01 (1) (Y Axis) (value: 2504, min: 0, max: 4095, flatness: 0 (=0.00%), fuzz: 0)

                And everything looks cool. Running jstest shows me incremental axis values as I turn the yoke. Doesn't automatically swing to the extremes, so no deadzone at that level, I don't think.

                dankcushionsD 1 Reply Last reply Reply Quote 0
                • dankcushionsD
                  dankcushions Global Moderator @nicosuave
                  last edited by

                  @nicosuave i believe you may be able to adjust some analog options in lr-mame2003-plus via the MAME menu. @mahoneyt944 may know more <3

                  M 1 Reply Last reply Reply Quote 0
                  • M
                    mahoneyt944 @dankcushions
                    last edited by mahoneyt944

                    There's a analog deadzone core option.

                    Retroarch quick menu-> options-> analog deadzone -> value

                    Make sure the game is mapped to use analog and not the dpad in the mame menu.

                    Mame menu-> Input this game-> AD Stick X / Y.

                    N 1 Reply Last reply Reply Quote 1
                    • N
                      nicosuave @mahoneyt944
                      last edited by

                      @mahoneyt944

                      Hello! Apologies for how long it took me to get back.

                      I've verified the first thing you suggested, quick menu, options, analog deadzone is set to 0.

                      Next, I went to input this game, and AD Stick X and Y. I'm not sure if this is significant, but the AD Stick X and Y are mapped to both RP2 HAT Up, Down, Left, and Right. But also the Axis 1, 0, X and Y.

                      [img]https://i.imgur.com/QbjstQk.jpg[/img]

                      I have a gamepad plugged in to port 1, and the alan-1 plugged into port 2. Both are recognized, but removing the gamepad, resetting to default and going back through things unless anyone has any other ideas.

                      1 Reply Last reply Reply Quote 0
                      • N
                        nicosuave
                        last edited by

                        And that did it.

                        After my last reply, I removed the gamepad physically, and put the alan-1 flight yoke adapter in position one of the RPI.

                        Then, I deleted the Mame-2003-plus config files at \home\pi\RetroPie\roms\arcade\mame2003-plus\cfg

                        I went into Retroarch config from Retropie and went to bind inputs for port 1. I changed it from Gamepad to Gamepad with Analog, set it to left analog, then mapped only the analog and four buttons.

                        Next, started up Star Wars, and mapped input for this game to the Analog X/Y and buttons.

                        Deadzone gone!

                        Settings and everything held after reboot.

                        Thanks for all the help!

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post

                        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.