1 |
Hi all. |
2 |
|
3 |
I've got an amd64 install of gentoo, and I'm using the nvidia drivers package |
4 |
version x11-drivers/nvidia-drivers-100.14.19 compiled with gcc 4.2.0 and |
5 |
kernel 2.6.22-gentoo-r8. This is with a PNY 8600GT 256MB card (PCI-E 16x) |
6 |
(540MHz core, the overclocking doesn't seem to work as advertiosed with |
7 |
nvidia... The card just refuses to overclock... i.e. ignores any attempt). |
8 |
|
9 |
I have a small openGL program that takes 32 png's, loads them as textures and |
10 |
displays them on the screen, while performing FSAA at mode 7 (16x), set by |
11 |
using the __GL_FSAA_MODE=7 env variable. |
12 |
|
13 |
I have two screens... One 1280x1024 and one 1680x1050. Both at 60Hz, and i'm |
14 |
using TwinView. |
15 |
|
16 |
Starting my app at a window size of 1000x900 is fine. App runs with almost 0% |
17 |
CPU (AMD X2 4800+), and at 50FPS (The display is drawn ising glTimerFunc at |
18 |
20ms intervals). All fine and dandy. |
19 |
|
20 |
But if I maximise the window to the full 1280x1024 resolution on the small |
21 |
monitor or 1680x1050 resolution on the big monitor, suddenly the application |
22 |
starts using 100% CPU. The CPU increase seems to happen when either the width |
23 |
or height goes above a certain value (Different for X & Y). |
24 |
|
25 |
Anyone else seen this? Disabling FSAA means I don't hit the problem, but then |
26 |
the display just doesn't look nice & smooth any more... Having fewer objects |
27 |
on the screen seems to make a difference too... There's no errors anywhere... |
28 |
|
29 |
I've tried installing the nvidia performance stuff (v2.1) but it doesn't |
30 |
compile OOTB. So that'll take some more investigation, but maybe someone else |
31 |
has been something? I wasn't aware that the nvidia drivers had a limit on |
32 |
either the resolution or number of textures that could be FSAA'ed in |
33 |
hardware.. Does it? |
34 |
|
35 |
TIA |
36 |
Hamish. |
37 |
|
38 |
|
39 |
-- |
40 |
gentoo-amd64@g.o mailing list |