Language Selection

English French German Italian Portuguese Spanish

Doom 3 1.3.1302 Linux Performance

Filed under
Gaming

A few days ago, a new point release for Doom 3 was released along with an SDK (Software Development Kit) update. Among other things, there are some substantial improvements in the Linux update, mainly with PunkBuster, EAX support, the installer, and variety of other fixes. Overall, Timothee Besset (Doom 3 Linux port maintainer) has done a great job with this new patch, however, are there any performance benefits or losses from this latest patch? The id Software Doom 3 1.3.1302 patch performance is the focus of this article.

One of the un-documented adjustments in the standard change log is the adoption of a new installer. We feel the 1.3.1302 installer is MUCH improved over the 1.1.1282 and 1.1.1286 versions.

As Timothee Besset, the Doom 3 Linux port maintainer, was facing some troubles with using SSE2 code in the initial Doom 3 Linux release, we were expecting to see some performance benefits when we had upgraded to this new release (1.3.1302). Unfortunately, this wasn't exactly the case. Once we had upgraded, there was roughly a 4-10 FPS drop in the average frame-rate in all of the different benchmarks we ran. The results however were much closer as the image quality on the 1.3.1302 version was increased. Even with the decrease in performance, and we hope this is only a temporary situation until the next patch is released, the substantial changes made in Doom 3 v1.3 can significantly enhance the game-play thus it's recommended to make the Doom 3 upgrade.

Full Review with benchmarks and graphs.

More in Tux Machines

Exclusive: Elephone P1000, Snapdragon 801, 2K and CyanogenMod!

Elephone, most known for their every expanding range of Mediatek phones and as being one of the first manufacturers in China to offer an Android 4.4 Kitkat update, are preparing a 2014 Flagship killer of their own. The Elephone P1000 will be the most exciting Elephone smartphone to date with features we have not seen from the company so far. The P1000 will boast a 2.5Ghz Snapdragon 801 processor, Adreno 330 GPU, 3GB RAM and 32GB of on board memory. This compared to their current phones is an amazing achievement! Read more

Ken Starks to Keynote At Ohio LinuxFest

As most FOSS Force readers probably already know, Ken’s articles here and on his own Blog of Helios are only a small part of what he does. He’s one of those too rare people who works to make a difference in this world and he does so by leveraging the power of Linux and free and open source software for the greater good. As the founder of the Reglue project (originally called Helios), he’s responsible for putting refurbished computers in the hands of financially challenged students in and around the Austin, Texas area where he resides. Over the years there have been thousands of these students and many of them, given Reglue computers while in middle or high school, have gone on to not only earn undergraduate degrees, but to attend graduate school as well — often studying computer science. Read more

Mesa 10.3 release candidate 1

Mesa 10.3 release candidate 1 is now available for testing. The current plan is to have an additional release candidate each Friday until the eventual 10.3 release, (Ian can follow up to state what the planned date is for that). The tag in the git repository for Mesa 10.3-rc1 is 'mesa-10.3-rc1'. I have also pushed a tag '10.3-branchpoint' to mark the point where master and 10.3 diverge. This should make git-describe a bit more useful. As a reminder, with the 10.3 branch now created, patches nominated with: CC: will now be candidates only for the new 10.3 branch. To nominate patches for the older 10.2 branch as well, please use: CC: "10.2 10.3" The expectation is that the 10.2 branch will remain alive with bi-weekly releases until after 10.3.1 release. Mesa 10.3 release candidate 1 is available for download from ftp://freedesktop.org/pub/mesa/10.3 Read more

Canonical Joined The Khronos Group To Help Mir/Wayland Drivers

Canonical's specific involvement with the Khronos Group isn't listed and we haven't seen Canonical names closely associated with any major specs out of the different working groups to date. However, Oliver Ries, the Head of Engineering Product Strategy at Canonical, wrote into Phoronix that they joined the group for pushing their display server agenda with trying to work towards an underlying driver standard for Mir/Wayland. Oli noted in his email, "Canonical has joined Khronos in order to help establish the necessary driver standard that is required for Mir (and Wayland) to succeed. We have specifically contributed to the current standard proposal/draft." Read more