Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 02-21-08, 11:10 AM   #1
JaXXoN
Registered User
 
Join Date: Jul 2005
Location: Munich
Posts: 910
Default Mouse pointer gets stuck in UT2004 with 169.0x

Hi!

I'm having a triple head setup where the left and middle displays
are connected to a video card (forming "Screen0" using twinview)
and the right display is connected to a second video card ("Screen1"
as "monoview"). The two screens / three displays are bound together
with Xinerama.

Now the problem is that since 169.07 the mouse pointer can
easily "get stuck" in UT2004 with this setup: when being at the main
menu, moving the mouse from the left to the right, it can easily
happen that the pointer can't be moved any further to the right,
getting stuck a random location. When moving the mouse back to
the left and then to the right again, there is a good chance that
the pointer temporarily "recovers" and you can reach the right edge,
again (or get stuck somewhere else).
In-game, this means that you can't move further to the right,
which is very annoying as you can imagine. The problem doesn't
exist for up/down movements.

I played around with the xorg configuration and figured out
that the problem goes away when twinview is configured for
the middle and the right display. However, i would prevere
using the left and the middle display for twinview, since
these two displays are my primary displays during desktop
operations, avoiding the annoying re-draw events when
moving windows across displays. In other words: the
display connection setup that works for UT2004 is not
convenient for desktop work.

Please find attached a number of working and broken xorg.conf
files. Seems like the twinview orientations doesn't have
any effect:

Code:
  Videocard 2:0:0             Videocard 1:0:0
  Screen1:Twinview   LeftOf   Screen0:Monoview   broken
  Screen1:Monoview   RightOf  Screen0:Twinview   broken
  Screen1:Monoview   LeftOf   Screen0:Twinview   working
  Screen1:Twinview   RightOf  Screen0:Monoview   working
Screen0 is always defined for the videocard on PCI bus 1:0:0.
Screen1 as always defined for the videocard on PCI bus 2:0:0.
(Switching screens - assigning 1:0:0 to Screen1 and 2:0:0 to
Screen0 - doesn't make the mouse hanging problem going away)
I also tried evdev instead of the standard X mouse driver,
but it didn't made any difference. Also disabling off composite
or ARGB GLX visuals doesn't has any effect on the problem.

BTW.: in order to get the mouse pointer visible at all, i
needed to replace

Code:
  Load "extmod"
by

Code:
  SubSection   "extmod"
       Option  "omit xfree86-dga"
  EndSubSection
Any feedback is highly appreciated!

regards

Bernhard
Attached Files
File Type: zip xorg-ut2k4.zip (11.8 KB, 121 views)
File Type: zip nvidia-bug-report.log.zip (37.7 KB, 103 views)
JaXXoN is offline   Reply With Quote
Old 02-23-08, 07:44 AM   #2
JaXXoN
Registered User
 
Join Date: Jul 2005
Location: Munich
Posts: 910
Default Re: Mouse pointer gets stuck in UT2004 with 169.0x

Just to keep you in the loop: the "pointer stuck" problem also goes away
when defining three screens (two for the first card and one for the second
card). This imposes some small overhead - twinview would certainly be
better, but the 8800GTs have enough performance to drive the separate
screens at 50+ FPS. Means: the triple screen solution is currently good
enough for me.

I have attached my xorg.conf for reference.

regards

Bernhard
Attached Files
File Type: zip xorg.conf-ut2k4.zip (972 Bytes, 126 views)
JaXXoN is offline   Reply With Quote
Old 02-26-08, 07:30 PM   #3
JaXXoN
Registered User
 
Join Date: Jul 2005
Location: Munich
Posts: 910
Default Re: Mouse pointer gets stuck in UT2004 with 169.0x

Hi!

Just to let you know, the problem persists with 169.12!

BTW.: In the mean time, i tried out some more complex UT2K4 ONS maps
and have the impression that my new 8800GTs are slower than my
old 7800GTX cards. This might be related by the overhead imposed
by using three screens rather then having just two (where one screen
handles two displays using twinview).I will take myself time to run some
benchmarks to get better numbers ...

regards

Bernhard
JaXXoN is offline   Reply With Quote
Old 02-28-08, 06:52 AM   #4
JaXXoN
Registered User
 
Join Date: Jul 2005
Location: Munich
Posts: 910
Default Re: Mouse pointer gets stuck in UT2004 with 169.0x

Hi!

Here are the Benchmark results:

Code:
Card	Driver	Mode			Resolution	FPS
7800GTX	9746	twinview+monoview	3840x1024	49.5
8800GTX	9746	twinview+monoview	3840x1024	49.9
8800GT	169.12	twinview+monoview	3840x1024	48.5
8800GT	169.12	triplescreen		3840x1024	44.1
8800GT	169.12	twinview+monoview	4800x1200	48.8
8800GT	169.12	triplescreen		4800x1200	44.6
Note 1:
This benchmark has been used:
http://www.linux-magazin.de/static/l...tbench-0.4.tgz
You also need "UMark-ONS.demo4" from here:
http://ut2k3botbench.sourceforge.net/addons.php

Note 2: FSAA and ANISO disabled

Note 3: The tests with the 7800GTX and 8800GTX cards have been
performed about a year ago with an older driver version.

Note 4:
twinview+monoview means
* screen0 is a twinview setup with two LCDs on the first card
* screen1 handles the third LCD through the second card
triplescreen means
* screen 0+1 are handling the two LCDs on the frist card (separate X-screens)
* screen 2 handles the third LCD through the second card


As already guessed, a three screen setup (tripleview) imposeses
some performance penalty. Interesstingly, the card type or the
resolution have no impact. Means: for UT2004, my CPU (AMD Athlon
X2 4400+) is the limiting factor.

So, although triplescreen is slower than twinview+monoview (because
of the overhead caused by handling three screen rather than two screen),
the performance penality (annoying stuttering) should not have been as big
as i experienced during network multiplay - maybe i just had a worse
network connection during that test.

Anyway, it would be realy helpful if somebody could confirm (or deny)
that (s)he has the same issue (as posted in top) with twinview+monoview.

regards

Bernhard
JaXXoN is offline   Reply With Quote
Old 03-12-08, 09:55 AM   #5
JaXXoN
Registered User
 
Join Date: Jul 2005
Location: Munich
Posts: 910
Default Re: Mouse pointer gets stuck in UT2004 with 169.0x

Just to let you know, the problem still persists with 171.06.

regards

Bernhard
JaXXoN is offline   Reply With Quote
Old 03-25-08, 07:19 PM   #6
JaXXoN
Registered User
 
Join Date: Jul 2005
Location: Munich
Posts: 910
Default Re: Mouse pointer gets stuck in UT2004 with 169.0x

Hi!

Some more news: i upgraded my hardware to a C2D E8400 and the
software to Fedora 8 but the problem even got worse:

After upgrading the hardware but using my old Fedora Core 6 installation,
the mouse pointer now even gets stuck when moving up/down with the
the triple-screen setup (which used to work). Updating to Fedora 8
didn't helped.

For reference, please check the nvidia-bug-report.log

regards

Bernhard
Attached Files
File Type: zip nvidia-bug-report.log.zip (32.8 KB, 98 views)
JaXXoN is offline   Reply With Quote
Old 03-27-08, 09:52 PM   #7
JaXXoN
Registered User
 
Join Date: Jul 2005
Location: Munich
Posts: 910
Default Re: Mouse pointer gets stuck in UT2004 with 169.0x

Here's an update:

Somehow the settings in UT2004.ini changed to no-mouse grab and windowed mode
which for sure imposes the problem that you can't move any further after a while.
After reverting back to mouse grab full screen mode, UT2004 works again as desired,
at least with the triple-screen setup as mentioned earlier. When using twinview for
two of the screens, then the problem shows up again.

BTW.: i created a small program that reads out the pointer x and y values and prints
it to the current console. Using this utility i figured out how UT2004 handles mouse input:

Let's assume the screen is 1600 x 1200, then UT2004 will initially set the pointer
to (800, 600). Then, when moving to the left, the x value will decrease. When it
reaches 0, then then the pointer is reset to 800. When moving to the right, then the
x value increases and is reset to 800 once it reaches 1599. Please note that
the real pointer is not visible and UT2004 maintains its own software pointer.
So the x/y value reported for the real (but invisible pointer) do not reflect the
values of the software pointer (which can have wired effects if something goes
wrong).

So far so good. now the problem is that with a 4800x1200 twinview+xinerama setup
UT2K4 shows the following effect: the pointer is reset to 2400 (as expected) and
when moving to the right, then the x value increases (as expected). When the
x value hits 4799, then the value is reset to 2400 as expected, but then the value
suddenly changes to 1599 and the visible mouse pointer makes a sudden jump to
the left. Further moving the mouse to the right keeps the x value at 1599.
When now moving to the left (but not down to 0), then right again, the pointer
gets again stuck at 1599. When then moving to the left to 0, then the system again
wraps around to 2400 and it is now possible again to increase the x-value to 4799
(where it again reverts to 2400, then 1599).

This effect doesn't show up when three screens are defined.

I'm real wondering how the nvidia driver could have an influence on how
the mouse pointer works?! (100.14.23 worked fine)

regards

Bernhard
Attached Files
File Type: zip mousetrack.zip (1.0 KB, 113 views)
File Type: zip nvidia-bug-report.log.zip (32.8 KB, 100 views)
JaXXoN is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


Similar Threads
Thread Thread Starter Forum Replies Last Post
Doh, M$ Optical Intellimouse Explorer not good for games Creole General Hardware 18 09-28-02 09:55 PM

All times are GMT -5. The time now is 01:09 AM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.