Doom 3 is ugly? (linux, 6800GT)


Recommended Posts

Hello.

I am currently running gentoo with the lastest nvidia drivers from ~x86 portage, and something seems very wrong with Doom3.

I am running at high detail, 2x antialiasing on a Geforce 6800GT.

On Windows:

http://www.raptorized.com/public_files/d3_.../shot00001.jpeg

http://www.raptorized.com/public_files/d3_.../shot00002.jpeg

On Linux:

http://www.raptorized.com/public_files/d3_.../shot00001.jpeg

http://www.raptorized.com/public_files/d3_.../shot00002.jpeg

Bumpmapping seems downsampled to around 64.

it is most noticeable in the second screenshot. If that can be of any use I use Twinview with Xinerama extensions.

Some info:

supernaut@ewigkeit supernaut $ glxinfo | grep "direct" | awk '{ print $3 }'
Yes
supernaut@ewigkeit supernaut $

ewigkeit root # cat /proc/mtrr
reg00: base=0x00000000 (   0MB), size= 512MB: write-back, count=1
reg01: base=0xc0000000 (3072MB), size= 256MB: write-combining, count=1
reg02: base=0xd0000000 (3328MB), size= 256MB: write-combining, count=1
ewigkeit root #

ewigkeit root # X -version

X Window System Version 6.8.0
Release Date: 8 September 2004
X Protocol Version 11, Revision 0, Release 6.8
Build Operating System: Linux 2.6.9-gentoo-r9ewigkeit i686 [ELF]
Current Operating System: Linux ewigkeit 2.6.9-gentoo-r9ewigkeit #8 Mon Dec 6 21:30:47 EST 2004 i686
Build Date: 04 December 2004
        Before reporting problems, check http://wiki.X.Org
        to make sure that you have the latest version.
Module Loader present
ewigkeit root #

ewigkeit root # lsmod
Module                  Size  Used by
ohci_hcd               18308  0
snd_pcm_oss            48296  0
snd_mixer_oss          17536  1 snd_pcm_oss
snd_seq_oss            31552  0
snd_seq_midi_event      6144  1 snd_seq_oss
snd_seq                49232  4 snd_seq_oss,snd_seq_midi_event
forcedeth              14656  0
snd_intel8x0           28840  2
snd_mpu401_uart         6080  1 snd_intel8x0
snd_rawmidi            20068  1 snd_mpu401_uart
snd_seq_device          6344  3 snd_seq_oss,snd_seq,snd_rawmidi
nvidia               3462492  12
ewigkeit root #

Any ideas what might be causing this? Quake3 seems to run fine :)

Link to comment
https://www.neowin.net/forum/topic/256662-doom-3-is-ugly-linux-6800gt/
Share on other sites

Well it would be extremely hard to have doom 3 set up "incorrectly."

And as for glxinfo, you can see up there that DRI _is_ enabled:

supernaut@ewigkeit supernaut $ glxinfo | grep "direct" | awk '{ print $3 }'
Yes
supernaut@ewigkeit supernaut $

if you really need the full glxinfo output I can post that but you know...

WELL I officially fixed it.

I disable texture downsampling and other things, and noticed there was a setting named image_ignorehigh "1". i turned it off, and everything is back to normal. Performance is even better than windows apparently...

There most definitively is a bug with quality detection...

WELL I officially fixed it.

I disable texture downsampling and other things, and noticed there was a setting named image_ignorehigh "1". i turned it off, and everything is back to normal. Performance is even better than windows apparently...

There most definitively is a bug with quality detection...

585096462[/snapback]

So, you fixed it by....

making changes to the doom config file?

Alister

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • These features described above are good, but far from what developers will like the most. The main feature that developers will care and love the most it's called "Bring Your Own Models". It gives us the ability to connect to LOCAL AI models running on Ollama. The feature it's located on GitHub Copilot tab -> On the model picker where you can select "manage models" instead of paid models and then it will show you the "Bring your own models" window where you can now select Ollama and the endpoint of your local server. So if you have a beefy spec machine you can now use your own model 100% local inside Visual Studio 2026 18.7.0
    • Microsoft Teams is getting a controversial location tracking feature that users may hate by Usama Jawad Image generated with Microsoft Copilot Earlier this year, Microsoft planned to roll out a controversial location tracking feature in Teams, but following customer feedback, it decided to delay its release. The bad news is that the company has decided to launch it later this year, but it's based on roughly the same design that was shared earlier, which means that many users still have good reason to worry. Basically, Microsoft Places and Teams have received workplace check-ins via Wi-Fi. The idea is that if an employee arrives at the office and connects to their enterprise network, their profile status indicator will show them as being present in the office. For example, if you arrive at work, open Teams on your PC, and connect to the "Studio B" company Wi-Fi network, your Teams profile will indicate that you are present in "Studio B", as shown below: Microsoft says that this feature is basically a replacement for physical workplace check-in peripherals, it reduces the need to manually update your status, and it also enables co-workers to know that you're at work so that they can coordinate in-person meetings with you. IT admins can enable this workplace check-in capability at a tenant level, and users have the ability to control whether they want to enable it or not. Of course, all of that sounds great on paper, but naturally, many Teams customers may still have concerns, as they did before. This is because it enables your reporting manager and other members of the organization to track if you are at the office, when you arrive at the office, and where you are right now. This could be problematic for people who work in what they consider to be flexible work environments or hybrid setups, and this kind of location tracking could be considered an invasion of privacy. Microsoft has tried to alleviate some of these concerns by letting users know that they can manually set their location easily, which essentially overrides workplace check-in if they feel uncomfortable with it. However, that doesn't really solve the problem because your organization could enforce a workplace policy that mandates that this feature remains enabled. The Redmond tech giant has also assured users that this capability does not store historical data and is only a real-time indicator of location. Finally, it only generates a signal when you connect to a corporate network, which means that if you are working from home and connect your PC to your personal Wi-Fi, it won't broadcast your location to your employer; you will simply be shown as "Remote". Microsoft has encouraged IT admins to prepare for this change and begin informing users so they know what to expect once it begins rolling out later this year.
    • Wow, Microsoft IS cooking lately... This only shows that they COULD improve, they just chose not to for whatever reasons. That obsession with AI was destroying them from the inside out.
  • Recent Achievements

    • Very Popular
      AndrewSteel earned a badge
      Very Popular
    • Veteran
      Taliseian went up a rank
      Veteran
    • One Month Later
      Clizby earned a badge
      One Month Later
    • One Month Later
      Timaximus earned a badge
      One Month Later
    • Week One Done
      Timaximus earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      512
    2. 2
      +Edouard
      162
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      Steven P.
      82
    5. 5
      ATLien_0
      80
  • Tell a friend

    Love Neowin? Tell a friend!