| View previous topic :: View next topic |
| Author |
Message |
bassman_fr
Apprentice
Joined: 30 Mar 2004
Posts: 201
Location: France Lyon
|
 Posted: Fri Sep 10, 2004 4:36 pm Post subject: [NVIDIA]Score minable à glxgears |
 |
|
Bonjour à tous,
j'ai un score minable avec une nvidia Geforce FX 5700 alors ca me met un peu les b...
voici :
| Code: |
6901 frames in 5.0 seconds = 1380.200 FPS
6660 frames in 5.0 seconds = 1332.000 FPS
6772 frames in 5.0 seconds = 1354.400 FPS
6762 frames in 5.0 seconds = 1352.400 FPS
6757 frames in 5.0 seconds = 1351.400 FPS
6763 frames in 5.0 seconds = 1352.600 FPS
6971 frames in 5.0 seconds = 1394.200 FPS
6734 frames in 5.0 seconds = 1346.800 FPS
|
voilà mon xorg.conf :
| Code: |
Section "Module"
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
# This loads the Type1 and FreeType font modules
Load "type1"
Load "freetype"
# This loads the GLX module
Load "glx" # libglx.a
#Load "dri" # libdri.a
EndSection
# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
RgbPath "/usr/X11R6/lib/X11/rgb"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
#
FontPath "/usr/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
# The module search path. The default path is shown here.
# ModulePath "/usr/X11R6/lib/modules"
EndSection
# **********************************************************************
# Server flags section.
# **********************************************************************
Section "ServerFlags"
# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
# Option "NoTrapSignals"
# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# Option "DontZap"
# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
# Option "Dont Zoom"
# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.
# Option "DisableVidModeExtension"
# Uncomment this to enable the use of a non-local xvidtune client.
# Option "AllowNonLocalXvidtune"
# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.
# Option "DisableModInDev"
# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
# Option "AllowNonLocalModInDev"
EndSection
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
Section "InputDevice"
Identifier "Keyboard1"
Driver "Keyboard"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for XFree86
# Option "XkbRules" "xfree86"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "fr"
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/psaux"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Option "Protocol" "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
EndSection
# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the XF86Config man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
Section "Monitor"
Identifier "Monitor0"
HorizSync 30 - 96
VertRefresh 50 - 160
Option "DPMS"
# === mode lines based on GTF ===
# VGA @ 100Hz
# Modeline "640x480@100" 43.163 640 680 744 848 480 481 484 509 +hsync +vsync
# SVGA @ 100Hz
# Modeline "800x600@100" 68.179 800 848 936 1072 600 601 604 636 +hsync +vsync
# XVGA @ 100Hz
# Modeline "1024x768@100" 113.309 1024 1096 1208 1392 768 769 772 814 +hsync +vsync
# 1152x864 @ 60Hz
# Modeline "1152x864@60" 81.642 1152 1216 1336 1520 864 865 868 895 +hsync +vsync
# 1152x864 @ 85Hz
# Modeline "1152x864@85" 119.651 1152 1224 1352 1552 864 865 868 907 +hsync +vsync
# 1152x864 @ 100Hz
# Modeline "1152x864@100" 143.472 1152 1232 1360 1568 864 865 868 915 +hsync +vsync
# 1280x960 @ 75Hz
# Modeline "1280x960@75" 129.859 1280 1368 1504 1728 960 961 964 1002 +hsync +vsync
# 1280x960 @ 100Hz
# Modeline "1280x960@100" 178.992 1280 1376 1520 1760 960 961 964 1017 +hsync +vsync
# SXGA @ 100Hz
# Modeline "1280x1024@100" 190.960 1280 1376 1520 1760 1024 1025 1028 1085 +hsync +vsync
# SPEA GDM-1950 (60Hz,64kHz,110MHz,-,-): 1280x1024 @ V-freq: 60.00 Hz, H-freq: 63.73 KHz
# Modeline "GDM-1950" 109.62 1280 1336 1472 1720 1024 1024 1026 1062 -hsync -vsync
# 1600x1000 @ 60Hz
# Modeline "1600x1000" 133.142 1600 1704 1872 2144 1000 1001 1004 1035 +hsync +vsync
# 1600x1000 @ 75Hz
# Modeline "1600x1000" 169.128 1600 1704 1880 2160 1000 1001 1004 1044 +hsync +vsync
# 1600x1000 @ 85Hz
# Modeline "1600x1000" 194.202 1600 1712 1888 2176 1000 1001 1004 1050 +hsync +vsync
# 1600x1000 @ 100Hz
# Modeline "1600x1000" 232.133 1600 1720 1896 2192 1000 1001 1004 1059 +hsync +vsync
# 1600x1024 @ 60Hz
# Modeline "1600x1024" 136.385 1600 1704 1872 2144 1024 1027 1030 1060 +hsync +vsync
# 1600x1024 @ 75Hz
# Modeline "1600x1024" 174.416 1600 1712 1888 2176 1024 1025 1028 1069 +hsync +vsync
# 1600x1024 @ 76Hz
# Modeline "1600x1024" 170.450 1600 1632 1792 2096 1024 1027 1030 1070 +hsync +vsync
# 1600x1024 @ 85Hz
# Modeline "1600x1024" 198.832 1600 1712 1888 2176 1024 1027 1030 1075 +hsync +vsync
# 1920x1080 @ 60Hz
# Modeline "1920x1080" 172.798 1920 2040 2248 2576 1080 1081 1084 1118 -hsync -vsync
# 1920x1080 @ 75Hz
# Modeline "1920x1080" 211.436 1920 2056 2264 2608 1080 1081 1084 1126 +hsync +vsync
# 1920x1200 @ 60Hz
# Modeline "1920x1200" 193.156 1920 2048 2256 2592 1200 1201 1203 1242 +hsync +vsync
# 1920x1200 @ 75Hz
# Modeline "1920x1200" 246.590 1920 2064 2272 2624 1200 1201 1203 1253 +hsync +vsync
# 2048x1536 @ 60
# Modeline "2048x1536" 266.952 2048 2200 2424 2800 1536 1537 1540 1589 +hsync +vsync
# 2048x1536 @ 60
# Modeline "2048x1536" 266.952 2048 2200 2424 2800 1536 1537 1540 1589 +hsync +vsync
# 1400x1050 @ 60Hz M9 Laptop mode
# ModeLine "1400x1050" 122.000 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync
# 1920x2400 @ 25Hz for IBM T221, VS VP2290 and compatible display devices
# Modeline "1920x2400@25" 124.620 1920 1928 1980 2048 2400 2401 2403 2434 +hsync +vsync
# 1920x2400 @ 30Hz for IBM T221, VS VP2290 and compatible display devices
# Modeline "1920x2400@30" 149.250 1920 1928 1982 2044 2400 2402 2404 2434 +hsync +vsync
EndSection
Section "Monitor"
Identifier "Monitor1"
HorizSync 31.5 - 37.9
VertRefresh 50 - 70
Option "DPMS"
# === mode lines based on GTF ===
# VGA @ 100Hz
# Modeline "640x480@100" 43.163 640 680 744 848 480 481 484 509 +hsync +vsync
# SVGA @ 100Hz
# Modeline "800x600@100" 68.179 800 848 936 1072 600 601 604 636 +hsync +vsync
# XVGA @ 100Hz
# Modeline "1024x768@100" 113.309 1024 1096 1208 1392 768 769 772 814 +hsync +vsync
# 1152x864 @ 60Hz
# Modeline "1152x864@60" 81.642 1152 1216 1336 1520 864 865 868 895 +hsync +vsync
# 1152x864 @ 85Hz
# Modeline "1152x864@85" 119.651 1152 1224 1352 1552 864 865 868 907 +hsync +vsync
# 1152x864 @ 100Hz
# Modeline "1152x864@100" 143.472 1152 1232 1360 1568 864 865 868 915 +hsync +vsync
# 1280x960 @ 75Hz
# Modeline "1280x960@75" 129.859 1280 1368 1504 1728 960 961 964 1002 +hsync +vsync
# 1280x960 @ 100Hz
# Modeline "1280x960@100" 178.992 1280 1376 1520 1760 960 961 964 1017 +hsync +vsync
# SXGA @ 100Hz
# Modeline "1280x1024@100" 190.960 1280 1376 1520 1760 1024 1025 1028 1085 +hsync +vsync
# SPEA GDM-1950 (60Hz,64kHz,110MHz,-,-): 1280x1024 @ V-freq: 60.00 Hz, H-freq: 63.73 KHz
# Modeline "GDM-1950" 109.62 1280 1336 1472 1720 1024 1024 1026 1062 -hsync -vsync
# 1600x1000 @ 60Hz
# Modeline "1600x1000" 133.142 1600 1704 1872 2144 1000 1001 1004 1035 +hsync +vsync
# 1600x1000 @ 75Hz
# Modeline "1600x1000" 169.128 1600 1704 1880 2160 1000 1001 1004 1044 +hsync +vsync
# 1600x1000 @ 85Hz
# Modeline "1600x1000" 194.202 1600 1712 1888 2176 1000 1001 1004 1050 +hsync +vsync
# 1600x1000 @ 100Hz
# Modeline "1600x1000" 232.133 1600 1720 1896 2192 1000 1001 1004 1059 +hsync +vsync
# 1600x1024 @ 60Hz
# Modeline "1600x1024" 136.385 1600 1704 1872 2144 1024 1027 1030 1060 +hsync +vsync
# 1600x1024 @ 75Hz
# Modeline "1600x1024" 174.416 1600 1712 1888 2176 1024 1025 1028 1069 +hsync +vsync
# 1600x1024 @ 76Hz
# Modeline "1600x1024" 170.450 1600 1632 1792 2096 1024 1027 1030 1070 +hsync +vsync
# 1600x1024 @ 85Hz
# Modeline "1600x1024" 198.832 1600 1712 1888 2176 1024 1027 1030 1075 +hsync +vsync
# 1920x1080 @ 60Hz
# Modeline "1920x1080" 172.798 1920 2040 2248 2576 1080 1081 1084 1118 -hsync -vsync
# 1920x1080 @ 75Hz
# Modeline "1920x1080" 211.436 1920 2056 2264 2608 1080 1081 1084 1126 +hsync +vsync
# 1920x1200 @ 60Hz
# Modeline "1920x1200" 193.156 1920 2048 2256 2592 1200 1201 1203 1242 +hsync +vsync
# 1920x1200 @ 75Hz
# Modeline "1920x1200" 246.590 1920 2064 2272 2624 1200 1201 1203 1253 +hsync +vsync
# 2048x1536 @ 60
# Modeline "2048x1536" 266.952 2048 2200 2424 2800 1536 1537 1540 1589 +hsync +vsync
# 2048x1536 @ 60
# Modeline "2048x1536" 266.952 2048 2200 2424 2800 1536 1537 1540 1589 +hsync +vsync
# 1400x1050 @ 60Hz M9 Laptop mode
# ModeLine "1400x1050" 122.000 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync
# 1920x2400 @ 25Hz for IBM T221, VS VP2290 and compatible display devices
# Modeline "1920x2400@25" 124.620 1920 1928 1980 2048 2400 2401 2403 2434 +hsync +vsync
# 1920x2400 @ 30Hz for IBM T221, VS VP2290 and compatible display devices
# Modeline "1920x2400@30" 149.250 1920 1928 1982 2044 2400 2402 2404 2434 +hsync +vsync
EndSection
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
# Standard VGA Device:
Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# installed.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
EndSection
# === ATI device section ===
Section "Device"
Identifier "nvidia Geforce 5700"
Driver "nvidia"
EndSection
# **********************************************************************
# Screen sections
# **********************************************************************
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen0"
Device "nvidia Geforce 5700"
Monitor "Monitor0"
DefaultDepth 24
Option "backingstore"
Subsection "Display"
Depth 24
Modes "1280x1024"
ViewPort 0 0 # initial origin if mode is smaller than desktop
Virtual 1280 1024
EndSubsection
EndSection
# **********************************************************************
# ServerLayout sections.
# **********************************************************************
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
Section "ServerLayout"
# The Identifier line must be present
Identifier "Server Layout"
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.
Screen "Screen0"
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
|
si qqun a une suggestion pour améliorer ca je suis preneur |
|
| Back to top |
|
 |
Desintegr
l33t
Joined: 25 Mar 2004
Posts: 863
Location: France - Orléans
|
| Posted: Fri Sep 10, 2004 5:46 pm Post subject: |
|
|
| Tu as essayé dans un jeu comme Enemy Territory ou America's Army ? |
|
| Back to top |
|
|
bassman_fr
Apprentice
Joined: 30 Mar 2004
Posts: 201
Location: France Lyon
|
| Posted: Fri Sep 10, 2004 5:53 pm Post subject: |
|
|
| non cependant quand je vois que les scores a glxgears pour des configs infèrieures sont les doubles des miens ... je me dis qu'il y a un problème ! |
|
| Back to top |
|
|
zarasoustra17
Guru
Joined: 01 Jul 2003
Posts: 382
Location: Marseille France
|
| Posted: Fri Sep 10, 2004 6:27 pm Post subject: |
|
|
| Personnellement, je suis passé de 1900 à 1250 sur une gf400mx en passant aux nouveaux drivers nvidia 61.11 et à xorg 6.799... , cela dit je n'ai pas constaté de ralentissements dans les jeux et Doom3 est fluide en 1024x768 en qualité moyenne, ce qui est inespéré avec cette config, donc je reste très circonspect sur les benchs type glxgears... |
|
| Back to top |
|
|
bosozoku
Advocate
Joined: 11 Jan 2004
Posts: 2431
Location: Roazhon
|
| Posted: Fri Sep 10, 2004 7:15 pm Post subject: |
|
|
Si tu veux un bon benchmark, utilise quake3 ! Glxgears sert juste à vérifier que tu as la 3D, pas à véérifier les capacités de ta cartes.
_________________
Stationlinux.org - Wiki Fvwm FR - Config Fvwm |
|
| Back to top |
|
|
rom
Apprentice
Joined: 21 Oct 2003
Posts: 246
Location: paris
|
| Posted: Fri Sep 10, 2004 7:49 pm Post subject: |
|
|
| zarasoustra, ça marche avec une gf400Mx doom3 ? |
|
| Back to top |
|
|
zarasoustra17
Guru
Joined: 01 Jul 2003
Posts: 382
Location: Marseille France
|
| Posted: Fri Sep 10, 2004 8:03 pm Post subject: |
|
|
| rom wrote: | | zarasoustra, ça marche avec une gf400Mx doom3 ? |
Heu, c'est une Gf4mx440 en fait, celle qui est intégrée aux CM nforce2, j'ai oublié quelques 4....
Sinon, ça marche avec Doom3  |
|
| Back to top |
|
|
nuts
Veteran
Joined: 10 Jan 2004
Posts: 1630
|
| Posted: Fri Sep 10, 2004 8:45 pm Post subject: |
|
|
si ca marche avec doom3 j attends de voir ma geforce 3  |
|
| Back to top |
|
|
Pachacamac
Veteran
Joined: 22 Nov 2003
Posts: 1264
Location: Paris - France
|
| Posted: Fri Sep 10, 2004 9:02 pm Post subject: |
|
|
Holà peut-être que je vais pouvoir tenter ce jeu finallement  Tu l'as sous windows ou avec cedega ?
Peux tu me dire si ta config est proche de la mienne : amd 1600+ avec 756mo de ram et une geforce4mx440. J'espère que ca suffira... |
|
| Back to top |
|
|
nuts
Veteran
Joined: 10 Jan 2004
Posts: 1630
|
| Posted: Fri Sep 10, 2004 9:20 pm Post subject: |
|
|
petitun j ai pas encore doom3 car j attends ne serait ce que la demo en natif sous linux. cadega, j ai pas tester, si on peut me le filer pkoi pas je testerai bien.
petideu, ma config: nforce2, 512DDR, xp2200+, geforce3 ti 200. ton cpu a toi me parait juste enfin faudra voir |
|
| Back to top |
|
|
sireyessire
Advocate
Joined: 20 Mar 2003
Posts: 2991
Location: back in Paris, France
|
| Posted: Fri Sep 10, 2004 9:20 pm Post subject: |
|
|
@bassman_fr: oui c'est pas terrible, avec ma FX5200 sur un laptop j'ai 1.5 fois plus et des nvidia=1.0.6111
_________________
I never think of the future. It comes soon enough.
Albert Einstein
Try simpler first
Shockley |
|
| Back to top |
|
|
moon69
Guru
Joined: 30 Aug 2003
Posts: 444
|
| Posted: Fri Sep 10, 2004 10:36 pm Post subject: |
|
|
moi avec une fx5200 cpu=athlon 2200xp et 512 mo de ram j'obtient:
9650 frames in 5.0 seconds = 1930.000 FPS
8343 frames in 5.0 seconds = 1668.600 FPS
3793 frames in 5.0 seconds = 758.600 FPS
6425 frames in 5.0 seconds = 1285.000 FPS
5328 frames in 5.0 seconds = 1065.600 FPS |
|
| Back to top |
|
|
zarasoustra17
Guru
Joined: 01 Jul 2003
Posts: 382
Location: Marseille France
|
| Posted: Fri Sep 10, 2004 11:28 pm Post subject: |
|
|
Ma config:
Athlon 2500+
Cm nforce2 GT( gforce4mx440 intégré)
512 Mo de RAM (dont 64 partagés)
Doom3 tourne avec cedega en 800x600 qualité Maxi ou 1024x768 qualité moyenne et c'est stable !!!(2h00 de jeu sans le moindre plantage...)
pour cedega: emerge cedega. |
|
| Back to top |
|
|
dioxmat
Bodhisattva
Joined: 04 May 2002
Posts: 709
Location: /home/mat
|
| Posted: Sat Sep 11, 2004 1:11 am Post subject: |
|
|
glxgears n'est pas un bench. Il dépend de ta résolution, de ce que fait ta machine a ce moment la, de ta profondeur d'écran... et n'a jamais eu vocation de bench.
Tu veux tester ta carte ? Lance un jeu. |
|
| Back to top |
|
|
bultom
n00b
Joined: 07 Sep 2004
Posts: 11
|
| Posted: Sat Sep 11, 2004 7:08 am Post subject: |
|
|
Par contre je vois que ton Xorg.conf est un ancien fichier de conf d'ati donc je serais toi je repartirai d'un fichier de conf tout propre 
enfin cque j'en dis =) |
|
| Back to top |
|
|
nuts
Veteran
Joined: 10 Jan 2004
Posts: 1630
|
| Posted: Sat Sep 11, 2004 7:08 am Post subject: |
|
|
| glxgears fais du 2130 en moyenne chez moi par dessus un kde en 1280x1024 24bits |
|
| Back to top |
|
|
rom
Apprentice
Joined: 21 Oct 2003
Posts: 246
Location: paris
|
| Posted: Sat Sep 11, 2004 11:59 am Post subject: |
|
|
| Alors ça change quoi le 4 de MX 440 ? IL y a les implémetations t et l dessus ? Parce que moi avec ma gf 440 mx je n'a déja pas pu faire marcher la démo de Deus ex 2 et je crois bien que doom 3 utilise le même type d'éclairage. Bon sinon ça vaut le coup doom 3 ? Ce que j'ai lu à son propos ne m'a pas semblé très convaicant (couloir, méchant, baston, couloir ...). |
|
| Back to top |
|
|
zarasoustra17
Guru
Joined: 01 Jul 2003
Posts: 382
Location: Marseille France
|
| Posted: Sat Sep 11, 2004 12:59 pm Post subject: |
|
|
La GF4MX440 et GF440MX sont les mêmes cartes , je pense:
| Code: | | VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX - nForce GPU] (rev a3) |
Sinon Doom3, c'est à peu près le même scénario que Half-Life(une expérience qui tourne mal...), mais l'ambiance est vraiment flippante, ce jeu ne necessite pas d'avoir beaucoup de neurones pour s'en sortir, mais question Adrénaline, il vaut son pesant d'or...L'environnement sonore et graphique valent 99% de l'intérêt du jeu, on se croirait à mi-chemin entre Ghost of Mars et Alien(les films) tant pour le réalisme que pour le suspense, sinon le but du jeu c'est tuer les méchants... |
|
| Back to top |
|
|
nuts
Veteran
Joined: 10 Jan 2004
Posts: 1630
|
| Posted: Sat Sep 11, 2004 1:23 pm Post subject: |
|
|
| rom wrote: | | Alors ça change quoi le 4 de MX 440 ? IL y a les implémetations t et l dessus ? Parce que moi avec ma gf 440 mx je n'a déja pas pu faire marcher la démo de Deus ex 2 et je crois bien que doom 3 utilise le même type d'éclairage. Bon sinon ça vaut le coup doom 3 ? Ce que j'ai lu à son propos ne m'a pas semblé très convaicant (couloir, méchant, baston, couloir ...). |
la difference entre entre les differente geforce 4mx sont les frequence gpu et ram.
deus ex2 n'a rien a voir avec doom3, deja c'est pas du tout le meme moteur.
doom3 niveau ambiance il deboite |
|
| Back to top |
|
|
Pachacamac
Veteran
Joined: 22 Nov 2003
Posts: 1264
Location: Paris - France
|
| Posted: Sat Sep 11, 2004 2:51 pm Post subject: |
|
|
ouaip doom3 est fillpant, je l'ai essayé chez un pote ca déchire.
je ne pense pas avoir le même rendu puisqu'il a un amd 3200+ ; 1Go de ram et une ati 9800pro mais bon je ne suis pas très exigeant au niveau des graphismes tant que c'est fluide.
ce week end ou plutot lundi - mardi - mercredi ? on fait une lan alors je pense que je le mettrai sur mon ordi pour voir ce que ça donne. C'est bête que la démo n'existe pas. |
|
| Back to top |
|
|
shmal
Tux's lil' helper
Joined: 07 Aug 2004
Posts: 143
Location: France, 91
|
| Posted: Sat Sep 11, 2004 3:08 pm Post subject: |
|
|
Mon xorg.conf si ça peut aider :
| Code: | Section "ServerLayout"
Identifier "Simple Layout"
Screen 0 "Screen 1" 0 0
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
Section "Files"
RgbPath "/usr/X11R6/lib/X11/rgb"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/Speedo/"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/CID/"
FontPath "/usr/share/fonts/75dpi/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/local/"
EndSection
Section "ServerFlags"
Option "DPMS" "off"
Option "BlankTime" "0"
Option "StandbyTime" "0"
Option "OffTime" "0"
EndSection
Section "Module"
Load "glx"
Load "dbe"
SubSection "extmod"
Option "omit xfree86-dga"
EndSubSection
Load "type1"
Load "speedo"
Load "freetype"
EndSection
Section "InputDevice"
Identifier "Keyboard1"
Driver "Keyboard"
Option "AutoRepeat" "500 30"
Option "XkbRules" "xorg"
Option "XkbModel" "microsoftprooem"
Option "XkbLayout" "fr"
EndSection
Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ImPS/2"
Option "Device" "/dev/mouse"
Option "Buttons" "5"
Option "ZAxisMapping" "4 5"
EndSection
Section "Monitor"
Identifier "My Monitor"
HorizSync 31.5 - 80.5
VertRefresh 60.0 - 75.0
Option "DPMS" "off"
EndSection
Section "Device"
Identifier "Standard VGA"
Driver "vga"
VendorName "Unknown"
BoardName "Unknown"
EndSection
Section "Device"
Identifier "NVIDIA FX 5900 XT"
Driver "nvidia"
Option "NvAGP" "2"
Option "HWCursor" "true"
Option "CursorShadow" "true"
Option "CursorShadowAlpha" "75"
Option "CursorShadowXOffset" "8"
Option "CursorShadowYOffset" "4"
Option "RenderAccel" "true"
EndSection
Section "Screen"
Identifier "Screen 1"
Device "My Video Card"
Monitor "My Monitor"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 8
Modes "1280x1024" "1024x768" "800x600"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1280x1024" "1024x768" "800x600"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x1024" "1024x768" "800x600"
EndSubSection
EndSection
Section "DRI"
Group 0
EndSection |
|
|
| Back to top |
|
|
nuts
Veteran
Joined: 10 Jan 2004
Posts: 1630
|
| Posted: Sat Sep 11, 2004 3:40 pm Post subject: |
|
|
| c est quoi le nvAGP=2 ? |
|
| Back to top |
|
|
bosozoku
Advocate
Joined: 11 Jan 2004
Posts: 2431
Location: Roazhon
|
| Posted: Sat Sep 11, 2004 4:03 pm Post subject: |
|
|
C'est pour dire d'utiliser l'agp de la carte je crois.
nvAGP=1, c'est agpgart il me semble...
_________________
Stationlinux.org - Wiki Fvwm FR - Config Fvwm |
|
| Back to top |
|
|
nuts
Veteran
Joined: 10 Jan 2004
Posts: 1630
|
| Posted: Sat Sep 11, 2004 4:33 pm Post subject: |
|
|
| j y pige rien a ca, moi j ai pas mis de nvagp et ca fonctionne bien |
|
| Back to top |
|
|
moon69
Guru
Joined: 30 Aug 2003
Posts: 444
|
| Posted: Sat Sep 11, 2004 4:54 pm Post subject: |
|
|
normal, il faut mettre juste quand tu as compiler dans le kernel agppart
sinon pas la peine |
|
| Back to top |
|
|
|
French
