Is anyone uses an ATI Videocard under Linux ?

[MAXDDARK]

This game rocks !
But the property Linux ATI drivers suck big time on several games while on other 3d games they work great.
I wonder if anyone experiencing the same issue as me and unable to play this game without crashes with full graphics and forced to use the safe mode to play ?

Is anyone tried the FREE/Open ATI drivers ? how does it work out in general and in this game specific ?

I am using ATI 9800 Pro Radeon.

[arlick]

i have ati radeon x700 se.

i have to use the opetion forze mode to play, without it i cant.
this is because the game need opengl version 2.1 to use some graphics options, but by now the ati drivers only have 2.0.6 opengl version.

[MAXDDARK]

do you use the property drivers ? (I assume yes).
and did anyone try the open drivers ?

[arlick]

do you use the property drivers ? (I assume yes).
and did anyone try the open drivers ?

yes sorry :P, i use the property drivers.

what open drivers are u talking? mesa?

[MAXDDARK]

To be honest I never tried (or I don't remember trying) the open drivers but I think it's Mesa or fglrx.

I yeah I see my Video card is too new to be supported under the open drivers
http://wiki.cchtml.com/index.php/Open_source_drivers

[arlick]

To be honest I never tried (or I don't remember trying) the open drivers but I think it's Mesa or fglrx.

fglrx are the propietary.

i tried with it (mesa) i dont know how to have 3d with it >.<

[MAXDDARK]

follow the guide : http://wiki.cchtml.com/index.php/Open_source_drivers
IF your videocard is supported.
WOW, mesa is supporting the long waited OpenGL 2.1 !
http://mesa3d.org/

[arlick]

follow the guide : http://wiki.cchtml.com/index.php/Open_source_drivers
IF your videocard is supported.
WOW, mesa is supporting the long waited OpenGL 2.1 !
http://mesa3d.org/

yes, but without direct rendering ;)

[arlick]

in the spanish forum we are trying to run it

http://www.regnumonline.com.ar/forum/showthread.php?t=8060

[MAXDDARK]

IF I knew Spanish...;)
what does it mean without "direct rendering" ?
how does it influence the gameplay graphics ?

[arlick]

IF I knew Spanish...;)
what does it mean without "direct rendering" ?
how does it influence the gameplay graphics ?

hehehe well...

without direct rendering... u dont have 3d graphics, no regnum, no beryl, no 3d games...

but with mesa u have opengl 2.1.

maeby we are doing some wrong, but we dont know what.

to compile the 2.1 version download mesa and compile with this command (in mesa files path)

make linux

to have direct rendereing type:

make linux-dri

or to build to your architecture:

make linux-dri-x86 or linux-dri-x64-86 or linux-dri-ppc...

[MAXDDARK]

is there a prepered .deb file for it WITH direct rendering and OpenGL 2.1, Mesa 7.0.1 version ?

[arlick]

is there a prepered .deb file for it WITH direct rendering and OpenGL 2.1, Mesa 7.0.1 version ?

i dont know but... i dont think so.
i didt find that for .rpm or .deb

[MAXDDARK]

if you have ubuntu you can try this guide : http://ubuntuforums.org/showthread.php?t=487735&highlight=mesa

it is a bit outdated, but if you can make it - tell me how ;)

[arlick]

if you have ubuntu you can try this guide : http://ubuntuforums.org/showthread.php?t=487735&highlight=mesa

it is a bit outdated, but if you can make it - tell me how ;)

we did that ;)

is a little more complicated than this.

here my glxinfo with mesa drivers:


name of display: :0.0
display: :0 screen: 0
direct rendering: No
server glx vendor string: Brian Paul
server glx version string: 1.4 Mesa 7.0
server glx extensions:
GLX_MESA_copy_sub_buffer, GLX_MESA_pixmap_colormap,
GLX_MESA_release_buffers, GLX_ARB_get_proc_address, GLX_EXT_visual_info,
GLX_EXT_visual_rating, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer
client glx vendor string: Brian Paul
client glx version string: 1.4 Mesa 7.0
client glx extensions:
GLX_MESA_copy_sub_buffer, GLX_MESA_pixmap_colormap,
GLX_MESA_release_buffers, GLX_ARB_get_proc_address, GLX_EXT_visual_info,
GLX_EXT_visual_rating, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer
GLX version: 1.4
GLX extensions:
GLX_MESA_copy_sub_buffer, GLX_MESA_pixmap_colormap,
GLX_MESA_release_buffers, GLX_ARB_get_proc_address, GLX_EXT_visual_info,
GLX_EXT_visual_rating, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer
OpenGL vendor string: Brian Paul
OpenGL renderer string: Mesa X11
OpenGL version string: 2.1 Mesa 7.0
[...]


but u see, i dont have 3d graphics (direct rendering)

[arlick]

try this guide

http://dri.freedesktop.org/wiki/Building

i dont have a debian based system installed now

[MAXDDARK]

So, does Rengum work with Mesa ?

[arlick]

So, does Rengum work with Mesa ?

not by now.

by now i dont have 3d graphics with mesa.

maybe i dont configure it well, im trying it now

[Myxir]

You can have DRI with mesa if I got this article right.
http://www.mesa3d.org/install.html
I'm just following this How-To. I'll report my results.
Got an error.... I'll spend some time on it now.

[leptom]

Can you paste your xorg.conf??

You're using mesa 3d but don't have direct rendering I thought it's for your xorg config.

Regards

[arlick]

here is my xorg.conf using mesa drivers:



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 font modules
# Load "type1"
Load "freetype"
# Load "xtt"

# This loads the GLX module
Load "glx"
# This loads the DRI module
Load "dri"

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/share/X11/rgb.txt"

FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/OTF"
FontPath "/usr/share/fonts/Type1"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/75dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/local/"
FontPath "/usr/lib/X11/fonts/misc/"
FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/lib/X11/fonts/Speedo/"
FontPath "/usr/lib/X11/fonts/Type1/"
FontPath "/usr/lib/X11/fonts/TTF/"
FontPath "/usr/lib/X11/fonts/OTF/"
FontPath "/usr/lib/X11/fonts/cyrillic/"
FontPath "/usr/lib/X11/fonts/75dpi/"
FontPath "/usr/lib/X11/fonts/100dpi/"

# The module search path. The default path is shown here.

# ModulePath "/usr/lib/dri"

EndSection


# ************************************************** ********************
# Input devices
# ************************************************** ********************

# ************************************************** ********************
# Core keyboard's InputDevice section
# ************************************************** ********************

Section "InputDevice"

Identifier "Keyboard1"
Driver "kbd"

# 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"


# These are the default XKB settings for Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""

# Option "XkbDisable"

Option "XkbRules" "xorg"
Option "XkbModel" "pc101"
Option "XkbLayout" "es"

EndSection


# ************************************************** ********************
# Core Pointer's InputDevice section
# ************************************************** ********************

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2" # IntelliMouse PS/2
Option "Device" "/dev/input/mice"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

# Option "Protocol" "Xqueue"

# Mouse-speed setting for PS/2 mouse.

# Option "Resolution" "256"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

# Option "BaudRate" "9600"
# Option "SampleRate" "150"

# Mouse wheel mapping. Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7. Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.

Option "ZAxisMapping" "4 5 6 7"

# Emulate3Buttons is an option for 2-button 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 xorg.conf 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 "My Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

HorizSync 31.5-79.0

# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

VertRefresh 50-70

Option "DPMS" "true"


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
# intalled.

# BusID "PCI:0:10:0"

# VideoRam 256

# Clocks 25.2 28.3

EndSection

# Device configured by xorgconfig:

Section "Device"
Identifier "** ATI Radeon (generic) [radeon]"
Driver "radeon"
VideoRam 262144
# Insert Clocks lines here if appropriate
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 "Screen 1"
Device "** ATI Radeon (generic) [radeon]"
Monitor "My Monitor"
DefaultDepth 24

Subsection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
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 "Simple 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. In this example, screen 2 is located to the
# right of screen 1.

Screen "Screen 1"

# 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

Section "DRI"
Group "video"
Mode 0666
EndSection

[leptom]

The difference between my xorg.conf and yours:

My device section have: option "DRI" "true"
My DRI section have not group defined

Try it!

[arlick]

The difference between my xorg.conf and yours:

My device section have: option "DRI" "true"
My DRI section have not group defined

Try it!

it dont work :crying1: :crying1:

direct rendering no

[MAXDDARK]

several days ago I've looked in the wiki for ATI video cards and apparently NONE of the ATI cards supports OpenGL 2.1
OpenGL 2.0 is the limit for them, and the new cards support Directx10.
only the newer Nvidia cards support OpenGL 2.1

so even if we do manage to make the mesa drivers to work, the hardware won't support OpenGL2.1

we are officially screwed !

[surak]

Regnum is fine with OpenGL 2.0

[MAXDDARK]

Regnum is fine with OpenGL 2.0

yes it is.
But I recall you saying that in order to see all the Directx features with OpenGL in this game, we must have OpenGL 2.1

so what are we missing ?

[surak]

That was a misunderstanding. OpenGL 2.0 has all the capabilities needed to show the game at full detail.

[Smiley2k7]

I've got Raedeon 1300/1550 but not under Linux :P but under DirectX

[arlick]

That was a misunderstanding. OpenGL 2.0 has all the capabilities needed to show the game at full detail.

my problem is if i wanna play i need active "force secutiry mode", without it i always crash before start the game.

my opengl version with propietary drivers are: 2.0.66...

[surak]

That's because ATI propietary drivers crashes compiling shaders. I'm considering to disable shader support for ATI under linux (until drivers are fixed)

[Angelwinged_Devil]

That's because ATI propietary drivers crashes compiling shaders. I'm considering to disable shader support for ATI under linux (until drivers are fixed)
is there a fullbright command?

[Holokauston]

Yeah would be great if we could, love the game and would like top play it more like it is intended to look =)

EDIT:
Ohh see you made the change, THX! looks great and works like a charm :)

[LudvigCro]

This game rocks !
But the property Linux ATI drivers suck big time on several games while on other 3d games they work great.
I wonder if anyone experiencing the same issue as me and unable to play this game without crashes with full graphics and forced to use the safe mode to play ?

Is anyone tried the FREE/Open ATI drivers ? how does it work out in general and in this game specific ?

I am using ATI 9800 Pro Radeon.

I am using a RV250 Radeon 9000 card. It s about 4 years old and not supported by ATI anymore.

With the free Xorg drivers 'radeon' or 'ati' the client didnt start, it gave the message 'graphic driver too old...'

I just tried the newest original driver 'fglrx' from ATI that supports my hardware. It is the legacy version 8.28. With this one installed, the game is workin just great!

Im happy now, hope you get it too.

[hong_kong_man]

LudvigCro - Problem being, installing the proprietary drivers officially screws your system if you want to uninstall them. You can't uninstall them without making something not work. :fury:

Also, they are propietary. Bad. Bad. Using them supports ATI's non-free driver crap.

Oh well... :rale:

[Anpu]

Try Mesa 7.0.1 and use driconf to enable s3tc compression. it works for "older" not supported cards, at least for 9250, 9200 etc

[Belaf]

Great! This worked for me. Fedora FC8 with radeon drivers and a radeon 9000 pro card.

Thanks a lot.