The information is this thread is obsolete. You no longer require libdxtn, it's apparently unmaintained. Instead, simply run the driconf GUI from the mesa dev tools and on the "Image Quality" tab activate "Enable S3TC texture compression even if software support is not available".
The information is this thread is obsolete. You no longer require libdxtn, it's apparently unmaintained. Instead, simply run the driconf GUI from the mesa dev tools and on the "Image Quality" tab activate "Enable S3TC texture compression even if software support is not available".
No, the OP tells you to install libdxtn first. This is no longer necessary unless you really want to "compress textures" on-the-fly. Since most distributions run a mile from this library and even the maintainer claims it's unmaintained it's all a recipe for breaking your mesa library.
Aside from that the link in the OP is a 404 anyway. Hopefully people will read as far as the update above before ramdomly trawling the net to find something they don't even need.
Those instructions are obsolete and refer to libdxtn which is no longer needed. You only need to install mesa-dev, run driconf and enable s3tc compression support in the options.
I would like to report the game mostly works on git kernel/ddx/drm/mesa r600g driver on "ATI RV730XT [Radeon HD 4670]" (ChipID = 0x9490) hardware.
I have about 25fps in 1920x1200.
This driver recently got s3tc capabilities through libdxtn.
Sometimes my commander spawns maimed though, and sometimes units disappear, or the world looks lightblue. I haven't been able to locate the problem thats causing this, or game settings that influence it.
Joined: 15 May 2007, 11:33 Location: Suomi/Finland
Hello! I have radeon HD 4500 video (ID 1002:9555). How I got it working:
Build a magic library # layman -a stormfront # emerge dev-libs/libtxc_dxtn
Build a gallium-enabled mesa # USE=gallium emerge mesa
Have fun.
PS: No need to enable S3TC in driconf, it is on by default in gallium. PPS: It seems that disappearing units have something to do with transformations, since they do not really disappear, their coordinates are just malformed.
If the glxinfo output contains 'GL_EXT_texture_compression_s3tc', good, otherwise you need to install libtxc_dxtn. The necessary code to go into ~/.drirc for force-enabling this stuff is something like this:
Joined: 28 Jul 2008, 05:51 Location: Australia I've spent quite a lot of time on this recently.
Firstly, I can confirm Spring runs with low graphics settings on ATI 1950xt with 3.0.4 kernel using the OSS driver and KMS enabled.
There are some caveats:
You must set LoadingMT=0 in your spring settings or Spring will crash/freeze on load with kernel errors related to "GEM lookup" and "CS parser" written to dmesg. You should use HardwareCursor=1 or your mouse may lag or cause a crash You should install libdxtn so S3TC/DDS textures work as expected. I have seen occasional glitches when zooming particular maps (Supreme Battlefield is one example). I suspect related to the presence of water or my choice of water rendering settings.
If it runs on the 1950xt (which is about 8 years old) it should run on any HD* card with higher settings.
I also run Spring on a HD6870 with the closed-source driver and haven't experienced any issues. I did try to switch to the OSS driver but at the time I didn't know about the LoadingMT setting so it was crashing on load.
On a more general note I have never had issues with any software or game except Spring. System stability is good, blender works, webGL works, compiz works on both drivers and cards. Framerates on the HD6870 are more than adequate at 2560x1600 when playing games like Shogun TW2 under Windows or Civ5 under Wine.
In short, my experience with ATI on linux and windows has been excellent with the exception of Spring under the OSS driver. In Springs' case the main issue is that no Spring devs and very few players use the ATI OSS driver. Issues go unnoticed and are difficult to fix. Things should improve as the OSS driver stabilises (there have been massive changes in the kernel graphics system since 2.6).
Of course you don't have to use the OSS driver and probably should use fglrx if you're running a HD* card. I only switched because:
I like experimenting with the bleeding edge I hate proprietary drivers in linux fglrx only supports HD* and higher.
Here's the Final Guide with the hoops I had to jump through to get it to work on my Intel HD Graphics (on a Toshiba Satellite R630-155). Not sure how much is necessary, but this made it better for me. It will still have glitches under some conditions, so don't expect any miracles, especially on big games.
First, I highly recommend updating the Mesa driver to >=8.0.4, or waiting until Ubuntu 12.10 is released. You should install the newest driver. I tried playing without it, and I couldn't. If you don't do it, the rest of this guide will delay your doom from ~5 minutes to ~10 minutes of game.
freelikegnu wrote:
Download and extract the latest version. you will also need two packages (and their dependencies):
i've already installed an ubuntu 12.10 and i'm using the ati-opensource drivers. it seems to work pretty well, the remaining errors are caused by faulty widgets (for example viewtopic.php?f=44&p=530188#p530188 ) and an engine bug is already fixed in the development version of spring.
i can't say anything about stability because i didn't use it a long time. imo linux 3.5 seems to be the first version which could work without big issues. (at least the ati drivers).
Users browsing this forum: No registered users and 1 guest
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum