VOGONS

Common searches


mouse is jumpy

Topic actions

First post, by sehh

User metadata
Rank Newbie
Rank
Newbie

I'm running dosbox 0.65 under Windoze Server 2003 64bit and its working great.

Unfortunately i can't use the mouse. While i can see the pointer and move it around, its jumpy, thus impossible to use.

For example, when its in the upper left corner and i move my hand downwards,
by just a little bit, the pointer moves to the bottom corner.

Its as if the "sensitivity" is maxed out or some other compatibility problem.

I am not having this issue with any other application or game.

Any help would be appriciated.

--
sehh

Reply 1 of 23, by sehh

User metadata
Rank Newbie
Rank
Newbie

One last thing i forgot to mention:

I changed "sensitivity=100" from dosbox.conf to different values but that didn't help.

For example, i lowered it to "10", as a result the mouse would still jump from one end of the screen to the other, but now it would do it in slow motion. The mouse would behave as if in "dream state" 😀

Its probably a problem in the way dosbox reads my mouse movement.... (at this point i can hear all the dosbox developers rushing to say that dosbox has no problems and that its my fault) 😀 🤣

--
sehh

Reply 7 of 23, by sehh

User metadata
Rank Newbie
Rank
Newbie

hmm i copied the SDL dll files from dosbox to another game, and it still worked. Which suggests the problem isn't there.

BUT

i did find another game (SDL based, again) but which DOES have the same mouse problems as dosbox (https://sourceforge.net/project/showfiles.php?group_id=66561)

any suggestions please?

--
sehh

Reply 8 of 23, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

As they're using the relative mouse motion fields as well, i guess
the SDL_MouseMotionEvent->xrel and ->yrel is messed up on your system.
You can try to output the fields of the motion-variable in
HandleMouseMotion() of sdlmain.cpp

Reply 10 of 23, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

> i guess the issue is with SDL?

Well i don't know, but i assume it is as two different programs are affected.
You could test that by modifying the sources, maybe somebody else with
the same system could do that as well.

Reply 14 of 23, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Do regular 32bit x86 compiles work? Maybe i can send you
a build that displays some information about the mouse
SDL events.
Guess that the SDL people would be interested in knowing
about it if there's really a bug.

Reply 16 of 23, by sehh

User metadata
Rank Newbie
Rank
Newbie

this is while i'm in windowed mode:

mouse motion: xrel 1, yrel 2, posx 283, posy 138
mouse motion: xrel 0, yrel 1, posx 283, posy 139
mouse motion: xrel 1, yrel 2, posx 284, posy 141
mouse motion: xrel 0, yrel 1, posx 284, posy 142
mouse motion: xrel 1, yrel 1, posx 285, posy 143
mouse motion: xrel 1, yrel 1, posx 286, posy 144
mouse motion: xrel 1, yrel 1, posx 287, posy 145
mouse motion: xrel 1, yrel 1, posx 288, posy 146
mouse motion: xrel 1, yrel 1, posx 289, posy 147
mouse motion: xrel 1, yrel 0, posx 290, posy 147
mouse motion: xrel 1, yrel 0, posx 291, posy 147
mouse motion: xrel 1, yrel 0, posx 292, posy 147
mouse motion: xrel 1, yrel -1, posx 293, posy 146
mouse motion: xrel 1, yrel 0, posx 294, posy 146
mouse motion: xrel 1, yrel -1, posx 295, posy 145
mouse motion: xrel 1, yrel 0, posx 296, posy 145
mouse motion: xrel 0, yrel -1, posx 296, posy 144

this is while i'm in fullscreen mode:

mouse motion: xrel 0, yrel 385, posx 0, posy 1023
mouse motion: xrel 205, yrel 1793, posx 205, posy 1023
mouse motion: xrel 102, yrel 257, posx 307, posy 1023
mouse motion: xrel 1025, yrel 1537, posx 1279, posy 1023
mouse motion: xrel 820, yrel 769, posx 1279, posy 1023
mouse motion: xrel 1230, yrel 512, posx 1279, posy 1023
mouse motion: xrel 1230, yrel 256, posx 1279, posy 1023
mouse motion: xrel 1639, yrel 0, posx 1279, posy 1023
mouse motion: xrel 1435, yrel -512, posx 1279, posy 511
mouse motion: xrel 1845, yrel -769, posx 1279, posy 0
mouse motion: xrel 1639, yrel -1025, posx 1279, posy 0
mouse motion: xrel 1230, yrel -1025, posx 1279, posy 0
mouse motion: xrel 1025, yrel -1281, posx 1279, posy 0
mouse motion: xrel 820, yrel -1025, posx 1279, posy 0
mouse motion: xrel 614, yrel -1281, posx 1279, posy 0
mouse motion: xrel 52, yrel -320, posx 1279, posy 0
mouse motion: xrel 51, yrel -257, posx 1279, posy 0

(the above debug output is based on the exe you compiled for me)

anything else i can do to help truck this bug to its source?

--
sehh

Reply 17 of 23, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

All mouse information seems to be wrong (at least odd) when in fullscreen.

Maybe try to change the sdl video driver:
set SDL_VIDEODRIVER=windib
set SDL_VIDEODRIVER=directx

Or add the SDL_VIDEODRIVER=windib/directx to the environment variables
(if that's available for your OS).

The directx interface is the default, unless it can't set the video mode
for some odd reason.

Reply 18 of 23, by sehh

User metadata
Rank Newbie
Rank
Newbie

below is the result from running with non-default video driver: set SDL_VIDEODRIVER=windib

fullscreen returns the following (again, mouse is jumpy):

mouse motion: xrel 68, yrel -481, posx 1279, posy 0
mouse motion: xrel -12, yrel -497, posx 1267, posy 0
mouse motion: xrel -88, yrel -497, posx 1179, posy 0
mouse motion: xrel -180, yrel -493, posx 999, posy 0
mouse motion: xrel -256, yrel -473, posx 743, posy 0
mouse motion: xrel -328, yrel -449, posx 415, posy 0
mouse motion: xrel -400, yrel -417, posx 15, posy 0
mouse motion: xrel -464, yrel -377, posx 0, posy 0
mouse motion: xrel -516, yrel -337, posx 0, posy 0
mouse motion: xrel -576, yrel -273, posx 0, posy 0
mouse motion: xrel -612, yrel -217, posx 0, posy 0
mouse motion: xrel -640, yrel -153, posx 0, posy 0
mouse motion: xrel -640, yrel -93, posx 0, posy 0
mouse motion: xrel -640, yrel -33, posx 0, posy 0
mouse motion: xrel -640, yrel 23, posx 0, posy 23
mouse motion: xrel -632, yrel 83, posx 0, posy 106
mouse motion: xrel -616, yrel 135, posx 0, posy 241
mouse motion: xrel -588, yrel 191, posx 0, posy 432
mouse motion: xrel -556, yrel 251, posx 0, posy 683
mouse motion: xrel -516, yrel 307, posx 0, posy 990
mouse motion: xrel -480, yrel 359, posx 0, posy 1023
mouse motion: xrel -436, yrel 403, posx 0, posy 1023
mouse motion: xrel -384, yrel 447, posx 0, posy 1023
mouse motion: xrel -340, yrel 475, posx 0, posy 1023
mouse motion: xrel -288, yrel 499, posx 0, posy 1023
mouse motion: xrel -240, yrel 511, posx 0, posy 1023
mouse motion: xrel -184, yrel 511, posx 0, posy 1023
mouse motion: xrel -128, yrel 511, posx 0, posy 1023
mouse motion: xrel -76, yrel 511, posx 0, posy 1023
mouse motion: xrel -16, yrel 511, posx 0, posy 1023

--
sehh

Reply 19 of 23, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Please try it with =directx as well (as in some cases dosbox will fall back
to windib by default).
Do the output= settings make any difference? Or changing fullresolution=
to various values?