Jump to content
LaunchBox Community Forums

5thWolf

Members
  • Posts

    272
  • Joined

  • Last visited

Posts posted by 5thWolf

  1. So I ran into an odd issue. Was mapping everything since I got the forced order figured out. Every game was fine until I hit polposition 2. Its is mapping the #1 controller as #6!!! But when you go in-game nothing works because it's mapping as #6. I tried deleting the polpos2 settings file, but nothing.
    Any one have any ideas? This is super strange. Not sure if there are other games but its consistent to that game. This did not happen till I implemented the controller file. But why all games are good but one is off?

  2. 2 minutes ago, faeran said:

    Yes, but you would have to create a custom theme and add the code for the video into it.

    Would that be as easy as copying this theme and adding the new lines in?
    Also, how do I activate the 3D box on the right like other people did? Mine doesn't have it.

  3. So I have the Ultimarc lightguns "ATRAK Device #1 & 2" and they work great! However in MAME I noticed they are by default assigned as "Joystick":

    image.thumb.png.197797244ab5ed609c4f0ac4eccad6e1.png

    So my question is, is there a benefit to get MAME to set them "Lightgun" or "Mouse" instead of "Joystick"?
    Though they seem fine, just want to know if MAME handles them differently if they set as any of the other types.

  4. Ok so it definitely was something on the ID, most likely a mistake since the wheel shows up 2 times in USB Device Manager. Maybe I chose the wrong one or something. But..... I did test the copy past from MAME and it worked perfectly!!! It looks like this:

    <?xml version="1.0"?>
    <mameconfig version="10">
       <system name="default">
          <input>
             <mapdevice device="Logitech G HUB G29 Driving Force Racing Wheel USB product_c24f046d-0000-0000-0000-504944564944 instance_2c2c8660-f0d1-11ed-8013-444553540000" controller="JOYCODE_1" />
          </input>
       </system>
    </mameconfig>

    This makes it a million times easier then looking for IDs anywhere else or in Windows!!!!! THANK YOU BOTH!!!!!!!!!!!!!!!!!

  5. So I copy/pasted your code and no more crash!! However It didn't seem to change the controller assignment. Going to double check the IDs and report back. Will also try the copy ID through MAME to see if it works.

    image.thumb.png.a791b7fc49604e48bd5386c9f37f4763.png

  6. Here is the message I get:

     

    E:\ARCADES\Arcade\Emulation\MAME>mame -v
    Attempting load of mame.ini
    Parsing mame.ini
    Attempting load of mame.ini
    Parsing mame.ini
    Loading translation file language\English\strings.mo
    Reading translation file: 1 strings, original table at word offset 7, translated table at word offset 9
    Loaded 0 translated string from file
    Starting plugin data...
    Starting plugin hiscore...
    Attempting load of mame.ini
    Parsing mame.ini
    Attempting load of mame.ini
    Parsing mame.ini
    Attempting load of source\empty.ini
    Attempting load of ___empty.ini
    Video: Monitor 65592 = "\\.\DISPLAY1" (primary)
    Video: Monitor 131073 = "\\.\DISPLAY2"
    Direct3D: Using Direct3D 9
    Physical width 3840, height 2160
    Direct3D: Initialize
    Direct3D: Configuring adapter #0 = NVIDIA GeForce GTX 1080
    Direct3D: YUV format = RGB
    Direct3D: Max texture size = 16384x16384
    Direct3D: Device created at 3840x2160
    Direct3D: Initialize HLSL
    DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
    Input: Adding keyboard #1: HID Keyboard Device (device id: \\?\HID#VID_046D&PID_C232#2&1a87f3a8&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
    Input: Adding keyboard #2: HID Keyboard Device (device id: \\?\HID#VID_0C45&PID_7603&MI_00#a&289f0fff&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
    Input: Adding keyboard #3: HID Keyboard Device (device id: \\?\HID#VID_0C45&PID_7603&MI_01&Col05#a&346236&0&0004#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
    Input: Adding keyboard #4: HID Keyboard Device (device id: \\?\HID#VID_AA55&PID_0101&MI_00#8&514d615&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
    Input: Adding keyboard #5: HID Keyboard Device (device id: \\?\HID#VID_0C45&PID_7603&MI_01&Col06#a&346236&0&0005#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
    Input: Adding keyboard #6: HID Keyboard Device (device id: \\?\HID#VID_093A&PID_2533&MI_01&Col02#a&688dfd6&0&0001#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
    Input: Adding keyboard #7: HID Keyboard Device (device id: \\?\HID#VID_0C45&PID_7603&MI_01&Col04#a&346236&0&0003#{884b96c3-56ef-11d1-bc8c-00a0c91405dd})
    Input: Adding mouse #1: HID-compliant mouse (device id: \\?\HID#VID_1241&PID_1111#7&389a3010&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
    Input: Adding mouse #2: HID-compliant mouse (device id: \\?\HID#VID_093A&PID_2533&MI_00#a&3376a5d7&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
    Input: Adding mouse #3: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1601&MI_02#8&253a70e3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
    Input: Adding mouse #4: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1602&MI_02#8&389ab7f3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
    Input: Adding lightgun #1: HID-compliant mouse (device id: \\?\HID#VID_1241&PID_1111#7&389a3010&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
    Input: Adding lightgun #2: HID-compliant mouse (device id: \\?\HID#VID_093A&PID_2533&MI_00#a&3376a5d7&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
    Input: Adding lightgun #3: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1601&MI_02#8&253a70e3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
    Input: Adding lightgun #4: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1602&MI_02#8&389ab7f3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd})
    Input: Adding joystick #1: GC101 Controller 1.03 (device id: GC101 Controller 1.03 product_565620bc-0000-0000-0000-504944564944 instance_e0d1ac80-f162-11ed-8001-444553540000)
    DirectInput: Device type=0x15 subtype=0x02 HID=yes
    DirectInput: Unable to get properties for joystick GC101 Controller 1.03 axis 3.
    DirectInput: Unable to get properties for joystick GC101 Controller 1.03 axis 4.
    Input: Adding joystick #2: GC101 Controller 1.03 (device id: GC101 Controller 1.03 product_565620bc-0000-0000-0000-504944564944 instance_e0d1ac80-f162-11ed-8002-444553540000)
    DirectInput: Device type=0x15 subtype=0x02 HID=yes
    DirectInput: Unable to get properties for joystick GC101 Controller 1.03 axis 3.
    DirectInput: Unable to get properties for joystick GC101 Controller 1.03 axis 4.
    Input: Adding joystick #3: ATRAK Device #1 (device id: ATRAK Device #1 product_1601d209-0000-0000-0000-504944564944 instance_2c2bc310-f0d1-11ed-8009-444553540000)
    DirectInput: Device type=0x14 subtype=0x01 HID=yes
    Input: Adding joystick #4: T.Flight Hotas X (device id: T.Flight Hotas X product_b108044f-0000-0000-0000-504944564944 instance_ddf5b380-f8a6-11ed-8001-444553540000)
    DirectInput: Device type=0x14 subtype=0x01 HID=yes
    DirectInput: Unable to get properties for joystick T.Flight Hotas X axis 3.
    DirectInput: Unable to get properties for joystick T.Flight Hotas X axis 4.
    Input: Adding joystick #5: ATRAK Device #2 (device id: ATRAK Device #2 product_1602d209-0000-0000-0000-504944564944 instance_2c2c1130-f0d1-11ed-800c-444553540000)
    DirectInput: Device type=0x14 subtype=0x01 HID=yes
    Input: Adding joystick #6: Logitech G HUB G29 Driving Force Racing Wheel USB (device id: Logitech G HUB G29 Driving Force Racing Wheel USB product_c24f046d-0000-0000-0000-504944564944 instance_2c2c8660-f0d1-11ed-8013-444553540000)
    DirectInput: Device type=0x16 subtype=0x03 HID=yes
    DirectInput: Unable to get properties for joystick Logitech G HUB G29 Driving Force Racing Wheel USB axis 2.
    DirectInput: Unable to get properties for joystick Logitech G HUB G29 Driving Force Racing Wheel USB axis 3.
    DirectInput: Unable to get properties for joystick Logitech G HUB G29 Driving Force Racing Wheel USB axis 4.
    Optional memory region ':screen' not found
    Starting No Driver Loaded ':'
      (missing dependencies; rescheduling)
    Starting Video Screen ':screen'
    Starting No Driver Loaded ':'
    Checking for icons in directory icons
    No candidate icons found for machines
    Attempting to parse: controls.cfg
    Error parsing XML configuration file controls.cfg
    Fatal error: Could not load controller configuration file controls.cfg

  7. It seems to find it, it just says it cant load it

    When i first tried the cfg i didn't put it in the right folder and it just out right crashed. When i moved it to ctrlr is just said can't load it.

    Mine is just a windows error popup box from mame, will send a pic tomorrow when i can, doesn't look like your pic though just that single line i quoted before. I double checked spelling and file location you have it correct. And mame ini points to ctrlr.

  8. oooooo I missed the &amp;
    But shouldn't copying what mame gives you into clipboard work? if it does it will make it a million times easier to handle the IDs. it says it in the site:

    However, every config file  in the folder and the example on MAME site doesn't have that xml version. Does it need it??
    Regardless I did try your code with and without the xml version and still got the error. 😔

    image.thumb.png.d5681334c6164a8eec839fd427477f1a.png

×
×
  • Create New...