VOGONS


First post, by garrynichol

User metadata
Rank Newbie
Rank
Newbie

I'm running acad 10 dos in dosbox and everything is fine except for the mouse is sluggish sort of like the cursor is on the end of a long thin rubber stick. It overshoots the intended cursor position making it difficult to pick entities. Anyone that can help?

I have the settings in dosbox.conf as follows:

fullscreen=true
fulldouble=true
fullresolution=1920x1080
windowresolution=original
output=overlay
autolock=true
sensitivity=125
waitonerror=true
priority=highest,normal
mapperfile=mapper-0.74.map
usescancodes=true

language=
machine=svga_S3
captures=capture
memsize=16

serial1=directserial realport:com1
serial2=disabled
serial3=disabled
serial4=disabled

Reply 1 of 16, by ripsaw8080

User metadata
Rank DOSBox Author
Rank
DOSBox Author

A serial mouse going through DOSBox's serial port emulation is known to have noticeable latency, but you only need to do that if the game/application only supports a serial mouse and not a ps/2 style mouse, or if you want to have two mice (one ps/2, one serial) for some reason.

Reply 2 of 16, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Known to have noticeable latency? Really?

1+1=10

Reply 3 of 16, by ripsaw8080

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Tass Times in Tonetown not running correctly
Read robertmo's last comment.

Known to those that have tried hooking up a serial mouse and using it. Perhaps not known to others. 😉

Reply 4 of 16, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

In Settlers its barely noticable and does not shoot over, even with an USB converter. Keep in mind that the serial mouse protocol takes ~22 milliseconds for one update while PS/2 etc. are faster. DOSBox adds up to 1ms to the delay, unless the cycles are set wrong or some scheduling bug is being hit.

1+1=10

Reply 5 of 16, by ripsaw8080

User metadata
Rank DOSBox Author
Rank
DOSBox Author

I've read that serial mice are 40hz, so 25ms per report, but maybe there's overhead or something. I haven't tried the serial mouse extensively, but in Windows 1.x with its bus/serial mouse driver, and in Tass Times, the delay is far more exaggerated than you describe.

Reply 6 of 16, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Were you using a real serial port or USB?

1+1=10

Reply 7 of 16, by ripsaw8080

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Real serial. My Intel motherboard has one serial and one parallel port: COM1 and LPT1. As robertmo pointed out in that other thread, I plugged the mouse in after WinXP had started up to avoid it being detected.

Reply 8 of 16, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Ah, with a real serial port I get the delay. Turn off FIFO buffers on the host (device manager) and restart the computer. Helped me.

With FIFO on the serial interface waits a certain amount of time after receiving data before triggering an interrupt. It hopes the buffer gets filled up a bit more. The mouse however sends only 3 bytes in a row which is not enough to reach the limit.

If you don't want to plug off the mouse every time:
Plug it in, switch your computer on, let it install.
Then deactivate (not uninstall) it in the device manager.

1+1=10

Reply 9 of 16, by garrynichol

User metadata
Rank Newbie
Rank
Newbie

I'm using a gyration mouse with a usb connection. Autocad 10 has two choices for mice: mouse systems 3 button/ms or logitech 3 button.
I'm using the mouse systems driver in autocad. The delay is worse when I don't use the direct serial setting in dosbox conf.

Reply 10 of 16, by Qbix

User metadata
Rank DOSBox Author
Rank
DOSBox Author

read what hal wrote and use that.

Water flows down the stream
How to ask questions the smart way!

Reply 11 of 16, by garrynichol

User metadata
Rank Newbie
Rank
Newbie

I tried what hal said and it doesn't improve the mouse response

Reply 12 of 16, by eL_PuSHeR

User metadata
Rank l33t++
Rank
l33t++

[Thread moved to DOSBox Games/Apps. Section]

Reply 13 of 16, by garrynichol

User metadata
Rank Newbie
Rank
Newbie

Just running NortonCommander in Dosbox still gives me inaccurate mouse response so I don't think this has anything to do with the autocad drivers.

Reply 14 of 16, by garrynichol

User metadata
Rank Newbie
Rank
Newbie

I tried disabling the windows mouse and connecting a serial mouse to com1 with the serial mouse driver in autoexec.bat in dosbox.conf. It works but even a little worse than the windows mouse. I'm still using serial1 as directserial in doscox.conf. Should that be set to dummy or something else?

Reply 15 of 16, by garrynichol

User metadata
Rank Newbie
Rank
Newbie

I tried setting dosbox.conf to serial1=dummy with the windows mouse disabled but the mouse still is slack in dosbox. If I move the mouse up and down about once a second the cursor is actually down when my mouse is up and vice versa.

Reply 16 of 16, by garrynichol

User metadata
Rank Newbie
Rank
Newbie

Finally got the mouse working great!
I changed the fullscreen parameter to false istead of true
I changed the windowresolution param from original to 1350x1080
(I'm using a 1920x1080 screen)
The mouse is perfect now, accurate and everything.

SO THERE IT IS : FULLSCREEN=TRUE SCREWS UP THE MOUSE