Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: Doom 3: possible?

  1. #1

    Default Doom 3: possible?

    I'm running the latest ati open source driver directly from the git server. Mesa 7.3 and libdrm 2.4.5 are there. DRI and opengl acceleration are working pretty good. But...doom 3 starts correctly but the combat scene is almost black. I can see my weapon, some lights and sound is pretty good but something is still missing. Are we still far or some parameter is missing from my xorg.conf? (which is pretty basic)
    Thanks

  2. #2
    Join Date
    May 2007
    Posts
    352

    Default

    I've played doom3 with the ARB render path on an x850, nearly all the way through. In ~/.doom3/base/DoomConfig.cfg make sure you have r_renderer set to "arb".

  3. #3

    Default

    Quote Originally Posted by adamk View Post
    I've played doom3 with the ARB render path on an x850, nearly all the way through. In ~/.doom3/base/DoomConfig.cfg make sure you have r_renderer set to "arb".
    Now it works thank you. Do you know if there are some optimization to make the game work smoothier? I have an ati mobility x1600 and using the proprietary drivers things are better (no suprises).

  4. #4
    Join Date
    May 2007
    Posts
    352

    Default

    I'm not aware of any real optimizations. For doom3 to really perform well, you need support for decompressing s3tc textures ( http://homepage.hispeed.ch/rscheideg...3tc_index.html ). Unfortunately that library has severe issues with multitexturing on the r300 mesa drivers, leading to flickering and flashing textures.

    In addition, I understand that a memory manager will really help to accelerate certain features needed for the arb2 render path.

    Adam

  5. #5

    Default

    Quote Originally Posted by piccolotux View Post
    Now it works thank you. Do you know if there are some optimization to make the game work smoothier? I have an ati mobility x1600 and using the proprietary drivers things are better (no suprises).
    You could try the new radeon-rewrite branch:
    http://cgit.freedesktop.org/mesa/mes...radeon-rewrite

  6. #6
    Join Date
    Jul 2007
    Posts
    402

    Default

    The r500 driver still is not performance optimized, but that's being worked on now. In the next year, the speed ought to improve dramatically with updates.

  7. #7

    Default

    Thanks for all your answers.

    You could try the new radeon-rewrite branch:
    http://cgit.freedesktop.org/mesa/mes...radeon-rewrite
    Thanks for this suggestion too. But I guess I have to compile mesa from git. Am I wrong?

  8. #8
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,284

    Default

    I think you would probably want to compile the whole driver stack from git. AFAIK the radeon-rewrite branch includes support for the current drm and X drivers but most of the focus is on getting Mesa ready to work with KMS, GEM and DRI2 -- the holy grail

  9. #9

    Default

    Quote Originally Posted by bridgman View Post
    I think you would probably want to compile the whole driver stack from git. AFAIK the radeon-rewrite branch includes support for the current drm and X drivers but most of the focus is on getting Mesa ready to work with KMS, GEM and DRI2 -- the holy grail
    So...from what I understand I should have to compile mesa, libdrm and X from git...

  10. #10
    Join Date
    Jul 2007
    Posts
    402

    Default

    You may not need to compile X from git (as long as you have 1.6, you should be OK), but the rest probably do need it. (DRM for GEM, mesa for the rewritten 3d, and the X Driver for DRI2 and such goodies.) I haven't had time to try this yet myself (No one appears to have a an Arch PKGBUILD so I'll have to make my own sometime) so let me know if it helps!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •