Thanks for this info. It is sad but it means that I have to find different solution for my case.
Konrad

@mitu Good point. I did visit that page, but obviously did not look good enough. :-)

@moltke44 said in Rom folder vanished after renaming with "." at beginning ... can't locate, rename, or delete.:

/home/pi/RetroPie/roms/snes$ rename ".Super Nintendo Entertainment System" "SNES"
syntax error at (user-supplied code), near "."

You said mv also didn't work. Which syntax did you use? I'm on my Kubuntu Linux at the moment. There, this works:

mv ".Super Nintendo Entertainment System" "SNES"

By the way, please mark commands and their output with a codeblock (three backticks before and after the text).

@steve-bamford yes, sorry my response was a bit quick! I must have skimmed over your question. It's good to see others using xroar. I use it to play the 5 games I had on the Tandy 30-odd years ago.

@stevepax Hi, I have the same setup as you so I am hoping I can help.

There are two keys that I know of in MAME that could be doing what you suggest, "F10" which toggles throttle on and off, and "insert" which throttles when it is held down. As mitu suggests try pressing tab to get into MAME menu and check the Input (General) and see what the throttle key is assigned to.

Setting up the controls for Street Fighter 2 and other similar six buttons games took a little trial on error (as least it did for me!). If it helps I have my buttons set up like this:

Player one

Top row from left to right
LP - lctrl (P1 button 2)
MP - lalt (P1 button 3)
HP - space (P1 button 5)

Bottom row from left to right

LK - lshift (P1 button 1)
MK - z (P1 button 4)
HK - x (P1 button 6)

I set the keys up from within MAME using Input (this game).

Hope that helps

@hobwell are you sure its not a bootleg controller?

@shizzmoney

Well this has solved my problem too, so thanks.
The indicated retroarch.cfg file was changed somehow to system_directory = "default", which breaks this emulator.

I find it amazing, that such changes are made in the core with no regard whatsoever to impacts to all retroarch ecosystem...

@pumpkinrat Not sure about settings in the standalone PCSX, but couldn't you change the output res of that pluggin to 1024x768 (seeing as you had it set to 1360x768 anyways) or a res that has something resembling a 4:3 ratio? I set most of my cores to run at 640x480, as that's technically higher than the original res in most cases anyways. Other benefit to the lower res means less stress on the pi, meaning potentially less input lag.

@dematica
Ok so any one having the same problem
It’s only on RetroPie witch is a shame cause it’s just what I wanted to use . It apears that on Recalbox the joysticks work just fine .
Still open to help if any one can point me in the right direction
Found my joystick I’d
Unplug
LSUSB
Plug back in
LSUSB
You can see the id

@nicky_s14 Check if you have a snapshot.png in the /home/pi folder. It's not the folder where raspi2png is located, is the folder where the command was executed.

@brenthunter2005 said in MAME - USB Mouse works fine, but Aimtrak gun does not:

everything is upside down (when I move the gun down, the cursor on the screen goes up!).

Maybe that it is because you hold your gun sideways, gangsta style! ;-)

@jont Your problem lies with the 3rd Party image. It's impossible to know how it's configured. It maybe for a specific display, it's likely to be highly customized in some unknown way, it could just be incorrectly set up. That's why the good folks on here cannot support these images because it's a waste of energy as nobody knows what the software is. Add to that the fact they are likely to be shipped with roms and the fact that people are paying for these! It's a big breach of the rules as shown here. See point 5. So as advised above, a fresh install will allow a full troubleshoot as we all have the same image on our sd cards.

@mitu Thank you, I'll do that.

@vretro

I had the same problem and found a solution: the Remote Pi app!

It works like a virtual keyboard and mouse in one. Now you can type all keys and F1 etc. without mapping. And the mouse function is good too for Amiga use.

https://remotepi.io

And this app I use to check memory and shutt down the Raspberry Pi:

Command Pi

Hope this helps!

At last, i managed to get it working!
I had to use Code functionallity of the Linux Joystic Mapper as well as Device settings in order to map the analog axis to Steering Wheel. another problem was to get the Hat functions of the USB pad to be accepted by the Linux Mapper diriver. In the Linux Joystic Mapper code examples, one can read out how transform Hat-functinaillty to digital inputs. Also, the PSX emulator expects axis inputs between -32767 to 32767.

axis vendor=0x00ff product=0x0000 src=0 target=joyaxis deadzone=10 axis=0 #Left analog Y-axis (Dwn>0<Up) axis vendor=0x00ff product=0x0000 src=1 target=joyaxis min=0 max=255 axis=1 #Right Analog X-axis (R>0<L) axis vendor=0x00ff product=0x0000 src=2 target=joyaxis axis=2 #Right Analog Y-axis (Dwn>0<Up) axis vendor=0x00ff product=0x0000 src=3 target=joyaxis axis=3 #L2/R2 Analog axis (L2>0<R2) #axis vendor=0x00ff product=0x0000 src=4 target=joyaxis axis=4 #Cross button button vendor=0x00ff product=0x0000 src=0 target=joybtn button=0 #Circle button button vendor=0x00ff product=0x0000 src=1 target=joybtn button=1 #Triangle button button vendor=0x00ff product=0x0000 src=3 target=joybtn button=3 #Square button button vendor=0x00ff product=0x0000 src=2 target=joybtn button=2 #L-Button button vendor=0x00ff product=0x0000 src=4 target=joybtn button=4 #R-Button button vendor=0x00ff product=0x0000 src=5 target=joybtn button=5 #L2-Button (Axis 4) button vendor=0x00ff product=0x0000 src=6 target=joybtn button=6 #R2 Button (Axis4) button vendor=0x00ff product=0x0000 src=7 target=joybtn button=7 #Select Button button vendor=0x00ff product=0x0000 src=8 target=joybtn button=8 #Start Button button vendor=0x00ff product=0x0000 src=9 target=joybtn button=9 #Up Button button vendor=0x00ff product=0x0000 src=10 target=joybtn button=10 #Down Button button vendor=0x00ff product=0x0000 src=11 target=joybtn button=11 #Left Button button vendor=0x00ff product=0x0000 src=12 target=joybtn button=12 #Right Button button vendor=0x00ff product=0x0000 src=13 target=joybtn button=13 #Left analog Button button vendor=0x00ff product=0x0000 src=14 target=joybtn button=14 #Right Analog Button button vendor=0x00ff product=0x0000 src=15 target=joybtn button=15 #L3-Button #button vendor=0x00ff product=0x0000 src=16 target=joybtn button=16 #R3 Button #button vendor=0x00ff product=0x0000 src=17 target=joybtn button=17 #Extra buttons button vendor=0x00ff product=0x0000 src=18 target=joybtn button=18 button vendor=0x00ff product=0x0000 src=19 target=joybtn button=19 button vendor=0x00ff product=0x0000 src=20 target=joybtn button=20 button vendor=0x00ff product=0x0000 src=21 target=joybtn button=21 #assign a joystick number fo script purposes script vendor=0x045e product=0x001a device=1 #"Microsoft SideWinder" script vendor=0x081f product=0xe401 device=0 #"USB gamepadad" #script vendor=0x00ff product=0x0000 device=2 #Joypad 0" #script vendor=0x06f8 product=0xa300 device=4 # Guillermo DualShock code "Cargame.code" ``` Cargamecode ``` var val; #get a positive value for acceleration # >128 indicates acceleration #js1 is Racing wheel val=js1.a[1]/2+128; #produce a brake value # <128 indicates brakes # we need to reverse the sense of the axis val-=js1.a[2]/2; a[3]=val; #note that accelerating and braking at # the same time results in no action # but cannot be resolved here #USB Button #USB Gamepad Left-Button b[10]=(js0.a[0]<128); #USB Gamepad Right-Button b[11]=(js0.a[0]>128); #USB Gamepad Up-Button b[8]=(js0.a[1]<128); #USB Gamepad Down-Button b[9]=(js0.a[1]>128); #USB Gamepad A-Button b[1]=(js0.b[0]); #USB Gamepad B-Button b[0]=(js0.b[1]); #USB Gamepad X-Button b[3]=(js0.b[2]); #USB Gamepad Y-Button b[2]=(js0.b[3]); #USB Gamepad L-Button b[4]=(js0.b[4]); #USB Gamepad R-Button b[5]=(js0.b[5]); #USB Gamepad Select-Button b[6]=(js0.b[8]); #USB Gamepad Start-Button b[7]=(js0.b[9]); #MS Sidewinder Racing Wheel #SteeringWheel axis a[0]=(js1.a[0]); #Break pedal a[1]=(js1.a[1]); #Gas Pedal a[2]=(js1.a[2]); #MS Sidewinder A-Button b[12]=(js1.b[0]); #MS Sidewinder B-Button b[13]=(js1.b[1]); #MS Sidewinder C-Button b[14]=(js1.b[2]); #MS Sidewinder X-Button b[15]=(js1.b[3]); #MS Sidewinder Y-Button b[16]=(js1.b[4]); #MS Sidewinder Z-Button b[17]=(js1.b[5]); #MS Sidewinder L-Button b[18]=(js1.b[6]); #MS Sidewinder R-Button b[19]=(js1.b[7]); ```

Ok... I think I know what's happening, and If I'm correct I'm a completly dumbass xD
It seems that key taps are recognized and considered even in loading screen. With gamepad in hand (xbox 360), I usually tap A button repeatedly (an impatient one here...). It happens that the first emu in menu is the amiga one, and the first entry in Amiga's rooms is UAE4ALL, so, that's it. It's my "A" taps in loading screen that launch uae4all when screen becomes operative.
Yep... totally dumbass xD

Anyway, if I'm not a dumbass after all and the issue happens again (without "A" tapping :-P ) I'll let you know.
Thanks and regards!

Can please anybody share his/her experience?