Recent Posts

Pages: [1] 2 3 ... 10
1
Themes / Re: Classic Anime & Tokusatsu (C.A.T.) JukeBox v2 update 22
« Last post by kent79 on Yesterday at 07:02:13 PM »
Update to v2 update 22

- fixed sound effect while navgiating items
2
Themes / Re: How to add curvature and scanlines to the snapshots?
« Last post by Elaphe666 on Yesterday at 07:28:18 AM »
Thank you, but I finally converted all my snaps using actions and automation with Photoshop.

3
General / Re: I can't play on DuckStation and PCSX2 through Attract Mode
« Last post by skellington on November 30, 2024, 07:28:55 PM »
I have faced a similar issue it used to work but then the error posted started to pop up. I tried to change the slashes but still doesnt work I'll try to reinstall or try a different emulator
4
Scripting / Reduce scroll speed in History plugin?
« Last post by Elaphe666 on November 30, 2024, 02:40:41 PM »
Is is posible? How?
5
Themes / Re: Hyperspin Theme Mode [Released]
« Last post by jakabasej8 on November 28, 2024, 05:59:10 AM »
hi I would like the letters to be displayed longer, https://www.plastikatrcek.si/prodajni-program/plasticne-cevi-2/ example I would like it to be displayed for about 2 or 3 seconds, how can I get this. kuhinja po meri

Hi! To display the letters for a longer duration
6
General / Know selected game?
« Last post by Elaphe666 on November 25, 2024, 01:09:12 AM »
Is there any temporal file where the currect selected game is temporaly stored or any other way to know the selected game? I would need to read that information from an Autohotkey script. Thank you.
8
Emulators / Re: ENVIRONMENT VARIABLES NOT WORKING
« Last post by davismark on November 21, 2024, 06:40:05 PM »
Could you please provide examples of where %USERPROFILE% and other environment variables are effective? I'm using it in RetroArch's appendconfig, but it doesn't seem to work, and the log file isn't showing the expected results.
9
AttractMode with debug log when work (Only USB Qanba Arcade Joystick Q1):
Code: [Select]
...
Joysticks after mapping:
ID: 0 => Joy0(Qanba Arcade Joystick Q1)
ID: 1 => Joy7(No Joystick)
ID: 2 => Joy7(No Joystick)
ID: 3 => Joy7(No Joystick)
ID: 4 => Joy7(No Joystick)
...

AttractMode with debug log when don't work (bluetooth and USB joy), after pairing bluetooth joystick:
Code: [Select]
...
Failed to get vendor ID of joystick /dev/input/js1
Failed to get product ID of joystick /dev/input/js1
Joysticks after mapping:
ID: 0 => Joy0(Qanba Arcade Joystick Q1)
ID: 1 => Joy1(8Bitdo NES30 Arcade)
ID: 2 => Joy7(No Joystick)
ID: 3 => Joy7(No Joystick)
ID: 4 => Joy7(No Joystick)
...

When pairing bluetooth joystick missed the "vendor ID" and "product ID"
Code: [Select]
# udevadm info --query=all --name=/dev/input/js1
P: /devices/pci0000:00/0000:00:1e.0/dw-apb-uart.0/dw-apb-uart.0:0/dw-apb-uart.0:0.0/serial0/serial0-0/bluetooth/hci0/hci0:11/0005:2DC8:1081.000A/input/input24/js1
M: js1
R: 1
U: input
D: c 13:1
N: input/js1
L: 0
E: DEVPATH=/devices/pci0000:00/0000:00:1e.0/dw-apb-uart.0/dw-apb-uart.0:0/dw-apb-uart.0:0.0/serial0/serial0-0/bluetooth/hci0/hci0:11/0005:2DC8:1081.000A/input/input24/js1
E: DEVNAME=/dev/input/js1
E: MAJOR=13
E: MINOR=1
E: SUBSYSTEM=input
E: USEC_INITIALIZED=139116391
E: ID_INPUT=1
E: ID_INPUT_JOYSTICK=1
E: ID_BUS=bluetooth
E: ID_PATH=pci-0000:00:1e.0-platform-dw-apb-uart.0
E: ID_PATH_TAG=pci-0000_00_1e_0-platform-dw-apb-uart_0
E: ID_FOR_SEAT=input-pci-0000_00_1e_0-platform-dw-apb-uart_0
E: TAGS=:seat:uaccess:
E: CURRENT_TAGS=:seat:uaccess:
but with command "udevadm info -a --name=/dev/input/js1" I can saw at parent device the infos.
Code: [Select]
  looking at parent device '/devices/pci0000:00/0000:00:1e.0/dw-apb-uart.0/dw-apb-uart.0:0/dw-apb-uart.0:0.0/serial0/serial0-0/bluetooth/hci0/hci0:11/0005:2DC8:1081.000A/input/input24':
    KERNELS=="input24"
    SUBSYSTEMS=="input"
    DRIVERS==""
    ATTRS{capabilities/abs}=="30627"
    ATTRS{capabilities/ev}=="1b"
    ATTRS{capabilities/ff}=="0"
    ATTRS{capabilities/key}=="ffff000000000000 0 0 0 0"
    ATTRS{capabilities/led}=="0"
    ATTRS{capabilities/msc}=="10"
    ATTRS{capabilities/rel}=="0"
    ATTRS{capabilities/snd}=="0"
    ATTRS{capabilities/sw}=="0"
    ATTRS{id/bustype}=="0005"
    ATTRS{id/product}=="1081"
    ATTRS{id/vendor}=="2dc8"
    ATTRS{id/version}=="0100"
    ATTRS{inhibited}=="0"
    ATTRS{name}=="8Bitdo NES30 Arcade"
    ATTRS{phys}=="a4:83:e7:11:06:2b"
    ATTRS{power/async}=="disabled"
    ATTRS{power/control}=="auto"
    ATTRS{power/runtime_active_kids}=="0"
    ATTRS{power/runtime_active_time}=="0"
    ATTRS{power/runtime_enabled}=="disabled"
    ATTRS{power/runtime_status}=="unsupported"
    ATTRS{power/runtime_suspended_time}=="0"
    ATTRS{power/runtime_usage}=="0"
    ATTRS{properties}=="0"
    ATTRS{uniq}=="e4:17:d8:eb:08:79"
10
General / Linux - USB Keyboard or other USB device don't work when paring bluetooth joy
« Last post by mjnman on November 18, 2024, 01:57:23 PM »
When paring bluetooth 8bitdo N30 the keyboard commands or different USB joystick commands doesn't work in the AttractMode menu. So, if I send a command via bluetooth joystick 8bitdo N30 (command: prev_game, next_game or anything definited) the keyboard commands start to working.
If I start AttractMode binary without bluetooth joystick paring the keyboard commands or USB joystick work correcly.
How I can debug this issue?
I'm using debian bookworm with kernel 6.8.5 on X86 with AttractMode 2.7.0.
In attachment the "attract.cfg".
Pages: [1] 2 3 ... 10