Mouse pointer issues

[Intuition]

No matter which direction I move my mouse in the pointer moves in a diagonal line towards the bottom right corner of the window until it vanishes off screen, even when in the Early Start Menu. The pointer doesn't respond to RAmiga+cursor keys either.

I've tried the mousehack option in the config file, i've also tried multiple different mice.

What I have noticed is that if the UAE window doesn't have focus then the Amiga pointer moves in the same direction as the X11 pointer. As soon as I click in the UAE window the X11 pointer disappears as expected but the Amiga pointer now only moves in the same diagonal direction again.

I'm running dual monitors with the NVidia 319 drivers on Kubuntu 13.04 with the fengestad/devel PPA, though the same problem occurs using the version in the stable PPA.

Can anyone shed any light on why this happens? I'm stuck with using WinUAE under WINE until I can solve this problem.

Thanks.

[TCD]

Sounds a bit like the mouse is configured as a joystick... is the mode in FS-UAE (F12) for the first port set to 'Mouse'?

[Intuition]

Originally Posted by TheCyberDruid

Sounds a bit like the mouse is configured as a joystick... is the mode in FS-UAE (F12) for the first port set to 'Mouse'?

Hi CyberDruid,

Yes it's set as '[M] Mouse'.

I tried switching it to joystick mode and then back again to see if that would help but it still behaves the same.

If I set it to '[M] Keyboard' this allows RAmiga+cursor keys to move the pointer so that's one step closer.

[Intuition]

I changed my xorg.conf from having a separate xserver for each screen to now use Twinview and now the Amiga mouse pointer actually moves in the direction I move the mouse, only to jump back to the point it started at.

I had to set mouse_speed = 200 as it only moved about 2cm in any direction without it.

I've attached my xorg.conf and another logfile incase anyone can spot an obvious error on my part.

[Intuition]

Hmmm.... If I keep the middle mouse button held down whilst I move the mouse, the Amiga pointer moves correctly.

It's not an ideal solution but it works for now.

I'm really baffled as to why this is happening but I shall persevere until it's solved!

[Intuition]

I've just discovered that holding down any of the mouse buttons whilst moving it makes it move in the correct direction.

This is the weirdest problem I have ever come across and I'm still no closer to discovering the cause....

[jbl007]

Your xorg.conf looks very oldschoolish. Input related configuration is not needed anymore, autodetection works much better in most cases.
Install xserver-xorg-input-evdev, remove the "InputDevice" sections and the 2 InputDevice lines from section "ServerLayout".
Perhaps this fixes your problems.

[Intuition]

Originally Posted by jbl007

Your xorg.conf looks very oldschoolish. Input related configuration is not needed anymore, autodetection works much better in most cases.

heheh It was autogenerated by 'nvidia-xconfig', I should email them and tell them to update their tools.

Install xserver-xorg-input-evdev, remove the "InputDevice" sections and the 2 InputDevice lines from section "ServerLayout".
Perhaps this fixes your problems.

I've done this and restarted X but I still get the same problem. Whenever FS-UAE has focus the mouse just moves in the direction I point it but then it "bounces" back towards the place it started from.

Thanks for trying to help though, much appreciated.

[Intuition]

I can't find any explanation for why this is happening, it's driving me crazy now!

I guess I must be the only one having this problem too?

[FrodeSolheim]

Originally Posted by Intuition

I guess I must be the only one having this problem too?

I have certainly never seen it, nor heard of any other users with the issue.

I can probably make a logging function for the next development release, so you/we can see the mouse events FS-UAE gets from SDL - printed to stdout and log file.

[Intuition]

Originally Posted by FrodeSolheim

I have certainly never seen it, nor heard of any other users with the issue.

I can probably make a logging function for the next development release, so you/we can see the mouse events FS-UAE gets from SDL - printed to stdout and log file.

That would be great, thanks.

It doesn't seem to be window manager specific either as it happens in KDE and Window Maker.

I'll try using the Nouveau driver rather than the binary Nvidia one tomorrow in case it's a driver issue.

[Intuition]

I've "fixed" it for now by adding automatic_input_grab = 0 to the config file.

The FS-UAE window accepts mouse click events as normal and the pointer moves in the direction it's supposed to move but i can see both the Amiga pointer and the Linux pointer.

[Intuition]

*bump*

I'm still getting this problem with the latest update from the Ubuntu repo.

Any chance of that version with more verbose debug output?

Thank you for your hard work btw, this is the best UAE for *nix platforms by far!

Thanks!

[FrodeSolheim]

I've just implemented some extra logging, so this will be available in the next development version.

Then, by setting the environment variable FS_DEBUG_INPUT=1, and starting fs-uae from a terminal with --stdout, you'll get output like this:

SDL mouse event x   31 y:   36 xrel:   -2 yrel:   -3
SDL mouse event x:   29 y:   35 xrel:   -2 yrel:   -1
SDL mouse event x:   28 y:   34 xrel:   -1 yrel:   -1
SDL mouse event x:   28 y:   33 xrel:    0 yrel:   -1
SDL mouse event x:   27 y:   32 xrel:   -1 yrel:   -1
SDL mouse event x:   26 y:   32 xrel:   -1 yrel:    0

[wawa]

now, after years í have a similar issue. probably dur to running fs-uae under virtual machine (vmware player) and this on almost all of my multiple installations of different flavours of debian. only on one debian 7 it seems to be working fine.

in general, the mouse pointer is uncontrollable, and just after it initially appears in left upper corner after just any mouse action it slides away from the screen and diaapears or is making wild jumps all around the place.

how to debug and correct this? i need fs-uae for debugging of aros68k (which is what im running in this case, might that be an issue?) winuae is just too slow under wine.

here is my config so far:

# FS-UAE configuration saved by FS-UAE Launcher
# Last saved: 2016-01-09 13:38:59

[fs-uae]
# amiga_model = A600
amiga_model = A4000/040
# bsdsocket_library = 1
# chip_memory = 2048
# fast_memory = 4096
# fast_memory = 16384
hard_drive_0 = /home/wawa/aros-68k-464/bin/amiga-m68k/AROS
kickstart_ext_file = /home/wawa/aros-68k-464/bin/amiga-m68k/AROS/boot/amiga/aros-ext.bin
kickstart_file = /home/wawa/aros-68k-464/bin/amiga-m68k/AROS/boot/amiga/aros-rom.bin
# kickstart_file = /home/wawa/Dokumente/FS-UAE/Kickstarts/kick.rom
uaegfx_card = 1
zorro_iii_memory = 65536
# graphics_card = picasso-iv-z3
# graphics_card_rom = /home/wawa/Dokumente/FS-UAE/Kickstarts/PIV_FLAS.BIN
joystick_port_2_mode = nothing
joystick_port_1 = nothing
#console_debugger = 1
# serial_port = /dev/pts/3
serial_port = tcp://0.0.0.1:1234
# serial_port = /dev/ttyS0
# serial_port = /tmp/vser
mouse_speed = 10
# accuracy = 1

heres the short boot log it presents:

AL lib: (WW) FreeDevice: (0xdec69e0) Deleting 96 Buffer(s)
wawa@wawa-virtual-machine:~$ fs-uae
FS-UAE 2.8.3 (Built for Linux x86)
Copyright 1995-2002 Bernd Schmidt, 1999-2015 Toni Wilen,
2003-2007 Richard Drummond, 2006-2011 Mustafa 'GnoStiC' Tufan,
2011-2015 Frode Solheim, and contributors.

This is free software; see the file COPYING for copying conditions. There
is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE. See the README for more copyright info, and the source code for
a full list of contributors

UAE: Initializing core derived from WinUAE 3220
LOG: /home/wawa/Documents/FS-UAE/Cache/Logs/fs-uae.log.txt
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
AL lib: (WW) ALCjackBackendFactory_init: jack_client_open() failed, 0x11
AL lib: (WW) alc_initconfig: Failed to initialize backend "jack"
UAE: KS ROM 4f508fe3 (524288 bytes)
UAE: KS ROM d0373f8f (524288 bytes)
 -- stub -- my_resolvesoftlink 
res_initcode context = (nil)


picasso96_alloc2


monitor: 0
setting gwwpagesize to something...

i will also need some help in setting up remote serial or tcp connection to it from m68k-aros-gdb, so far i tried via tcp and various ports according to what i have read but no success..

[jbl007]

Originally Posted by wawa

joystick_port_2_mode = nothing

You should remove this option or set it to "mouse".

[Team_Hoi]

Hi,

I've just got FS-UAE running with a HD file containing DPaint IV. It's pure magic having a working DPaint on my screen again. It must have been almost 20 years ago or so since I last worked with DPaint.

There's only one issue I can't seem to resolve. I'm working with a Wacom Cintiq tablet, and FS-UAE uses only a small portion of the Cintiq screen to drive the Amiga mouse pointer. This results in the pointer accelerating past the position of my Wacom pen. I've switched the Amiga Mouse in the FS-UAE Launcher to a Cintiq entry in the drop-down menu, but then the pointer doesn't move at all.

Searching for a solution I stumbled across a discussion here mentioning a mouse hack mode you can set in the configuration. How do I realize that? Or is there maybe a better solution?

Many thanks in advance.

[Team_Hoi]

Ah, entering "mouse_integration = 1" in the FS-UAE Launcher's Custom Configuration window solved the issue!

[Team_Hoi]

I've just discovered a new issue. One of the Wacom pen buttons serves as my right mouse button, but the right-click menus in DPaint only open for a short moment, then disappear again, no matter if I hold down the right mousebutton.

This only occurs when I switch to MacOS full screen mode though. Does anyone recognize this issue?

Thanks,

Metin

I've got the same problem of the mouse pointer jumping back towards the original location. Intuition or wawa, did either of you ever find a solution?