I’ve been trying to get the Amiga P-UAE core running, but one big problem I’ve been having is using the mouse to get around P-UAE’s menu. The mouse speed is too fast and twitchy to be used normally. I have to make tiny movements with the mouse to even properly control the mouse pointer, and even then it’s still difficult to use. I tried lowering the DPI of my physical mouse to 100, and that didn’t even do anything. How do I adjust the mouse speed when running GUI cores like P-UAE and Hatari so that it isn’t too fast or twitchy to use?
I have the same issue on Linux and Android – do you know if this is a recent bug or has the core always behaved this way? Strangely / thankfully it’s not the mouse emulation itself that’s at fault, i.e. I can play Lemmings and such as normal.
One workaround is to create UAE configuration files for your disks i.e. you don’t have to use the GUI at all. For example:
kickstart_rom_file=/storage/emulators/Amiga/kick.rom
chipmem_size=1
bogomem_size=2
use_gui=no
nr_floppies=2
cpu_type=68000
cpu_speed=real
cpu_compatible=true
ntsc=false
chipset=ocs
immediate_blits=false
gfx_linemode=double
gfx_framerate=1
sound_output=normal
sound_frequency=44100
sound_channels=mixed
sound_interpol=none
show_leds=true
floppy_speed=100
gfx_center_vertical=smart
gfx_center_horizontal=smart
gfx_color_mode=16
floppy0=/storage/emulators/Amiga/Rick Dangerous.adf
Taken from https://github.com/libretro/libretro-uae/blob/master/RickDangerous.uae.
Thanks for this reply. I get the same problem. Where do we need to put this file ? In the “Configfiles” directory of lakka ? What the name should be ?
Hi ! Using Lakka, I put kick.rom in /storage/system ; .adf and .uae files in /storage/roms/Amiga. Then in retroarch I choose “load content & autodetect core” and choose the .uae file. It does work !
I have one problem though : I need the UAE core to output at 320x240 or 320x256 in order to properly apply the pixel shaders (I use a combination of xbr level 2 scaled 3 times and crt-lottes, which looks AMAZING). However, even when using the gfx_width and gfx_height / gfx_lores options (and also gfx_linemode = none), it doesn’t work properly, and looks as if the pixel shaders was applied to a higher resolution picture. [EDIT : indeed the core internal resolution remains at 640x400 ; how to override this ?]
Here is my .uae file :
kickstart_rom_file=/storage/system/kick13.rom chipmem_size=1 bogomem_size=2 use_gui=no nr_floppies=2 cpu_type=68000 cpu_speed=real cpu_compatible=true ntsc=false chipset=ocs immediate_blits=false gfx_linemode=none gfx_framerate=1 gfx_width=320 gfx_height=240 sound_output=normal sound_frequency=44100 sound_channels=mixed sound_interpol=none show_leds=true floppy_speed=100 gfx_center_vertical=smart gfx_center_horizontal=smart gfx_color_mode=16 floppy0=/storage/roms/Amiga/Superfrog-1.adf
Actually, in the core options, there is an “internal resolution” setting. Its lowest possible value is 640x400 apparently. Is it possible to work around it ?
The kind of work around I found ATM is to set the gfx_lowres mode, and reduce the “scale” value of the shader. However the picture takes a fraction of the screen so that’s not very satisfying 
[QUOTE=bidinou;52042]Hi ! Using Lakka, I put kick.rom in /storage/system ; .adf and .uae files in /storage/roms/Amiga. Then in retroarch I choose “load content & autodetect core” and choose the .uae file. It does work !
I have one problem though : I need the UAE core to output at 320x240 or 320x256 in order to properly apply the pixel shaders (I use a combination of xbr level 2 scaled 3 times and crt-lottes, which looks AMAZING). However, even when using the gfx_width and gfx_height / gfx_lores options (and also gfx_linemode = none), it doesn’t work properly, and looks as if the pixel shaders was applied to a higher resolution picture. [EDIT : indeed the core internal resolution remains at 640x400 ; how to override this ?]
Here is my .uae file :[/QUOTE]
Question, when you say storage/roms/Amiga/Superfrog-1.adf, is “storage” basically the same as the C:, or is it the Retroarch folder? I am having trouble setting up my uae file…