Originally posted by Hamish Wilson
View Post
Announcement
Collapse
No announcement yet.
Will Mesa/Gallium3D Work With The Open-Source Doom 3?
Collapse
X
-
Originally posted by bug77 View Posthttp://www.xbitlabs.com/articles/gra...s_3.html#sect0
Not jaw-dropping by today's standards, but you can see some bump mapping missing. I imagine that's easier to see on enemies then walls. Also check out the framerates on those video cards.
Comment
-
Originally posted by Reloaded211 View PostFrom my experience, Doom 3 in Wine runs much better than the native version (getting around 40 fps on Radeon HD 4550), probably because Wine does some optimizations while native binary is unoptimized and pretty much old now. In fact, I never really got the sound working right when running Doom 3 natively on Linux, the sound just disappears after some time. Never saw that happening in Doom 3 in Wine.
Originally posted by Reloaded211 View PostBy the way, framerates tend to be up to around 30% higher when running the game in single-user mode using xgame script, probably because there's no DE overhead that way.
Originally posted by Reloaded211 View PostHell, tried running Doom 3 using Mesa 7.8 some year and a half ago. Completely unplayable, unlike now. Things are roling really fast lately here.
With the release of Fedora 13 everything did work, except for the shadowing, which has been working fine since Fedora 15 and the switch to Gallium 3D. Ever since then it has just been more and more optimizations. Lets hope we see some more soon.
Comment
-
@Qaridarium
thats complete bullshit. wine matches opengl 1:1 and does not transform opengl 2 to 3. but the sound system is really outdated in the old doom3 native binary, should be much better when the source code can be fixed. maybe even a recompile against new libs is enough. i also did crossplattform tests some years ago and i remember that you have got verify aa/af settings ingame via screenshots against the win version. i did several speed tests and linux was often a tiny bit faster because parts of those where not active. you should be sure that you compare the same visuals not something you can benchmark but is rendered differently.
Comment
-
Doom3 can not detect the true amount of video ram when running with the open source drivers. So it defaults to 64mb or so and therefore chooses low quality rendering. You have to force the vram amount in the config to get high or ultra quality.
Low quality rendering is not caused by the free drivers but by a game bug. Quake4 with the default config has the same problem, but is fixable the same way.
Click to enlarge
Comment
-
Originally posted by Lynxeye View PostDoom3 can not detect the true amount of video ram when running with the open source drivers. So it defaults to 64mb or so and therefore chooses low quality rendering. You have to force the vram amount in the config to get high or ultra quality.Michael Larabel
https://www.michaellarabel.com/
Comment
-
Originally posted by Qaridariumthis is a know openGL2.1 catalyst bug wine runs faster because wine translate it into openGL3.x
most people are bitten by this bug if they try to play HON.
Originally posted by Kano View Post@Qaridarium
wine matches opengl 1:1 and does not transform opengl 2 to 3
Comment
Comment