• Doom 3 Bfg Vs Original
• Doom 3 Vs Doom 3 Bfg

Doom 3: BFG Edition is a re-release of Doom 3 released on October 16, 2012 in North America, October 18, 2012, in Australia and October 19, 2012 in Europe for Microsoft Windows, PlayStation 3, and Xbox 360.The BFG Edition features enhanced graphics, better audio (with more horror effects), a checkpoint save system, and support for 3D displays and HMDs.

Doom 3: BFG Edition is best described as the net result of John Carmack and id Software taking on an HD remastering project, because this new release is effectively a 720p console revamp of a 2004 PC game originally designed with a 640x480 resolution in mind. While some might argue that the PC version is somewhat superfluous when stacked up against eight years' worth of community-driven mods, on console the BFG Edition makes a lot more sense and in the hands of Carmack and company, the result is a game that's a cut above the typical HD remaster.

For a start, some thought has been given to the way in which Doom 3 will be played on console. An aesthetic originally designed around a desktop environment with the screen directly in front of the player has been tuned to better suit a living room environment. The lighting has been revamped, making the BFG Edition brighter and easier to track with the display at range, field of view has been tweaked with 16:9 screens in mind, while certain elements of the artwork have been embellished to reduce some of the more glaring, lower-quality texture work.

In the PC version, the changes are a mixed bag, but on console, the choices seem fitting. Thankfully the craze for simple PC ports masquerading as 'HD remasters' appears to be over, but it's gratifying that in bringing Doom 3 to console, id has put the work in here. In Carmack's own words, the firm knew that farming out the game to a sub-contractor would result in sub-optimal results, so it carried out the conversion itself and the results are generally impressive - especially when it comes to frame-rate, where Doom 3: BFG Edition targets a 60 frames per second update.

We'll roll out the cross-platform comparison vids, but perhaps the most telling - and relevant - head-to-head is the 2004 original vs. BFG Edition PC video we ran yesterday, illustrating the work id carried out in turning a specific kind of computer experience into a big, brash, console blaster.

There are few surprises on the console front. By and large, both Xbox 360 and PlayStation 3 operate at native 720p, with no anti-aliasing applied. There's a large degree of contrast between many of the visual components, leading to obvious edges and plenty of jaggies. On top of that, anisotropic filtering does appear to be engaged, but at a relatively low level so there's obvious shimmering on ground textures. However, all of these compromises are in place to serve the frame-rate target, and to that end, the drawbacks are worthwhile, because the 60Hz experience transforms the game. At its best, particularly in the highly enjoyable Lost Mission bonus campaign, Doom 3 still manages to provide an enjoyable slice of classic id gunplay and frame-rate is a crucial element in this - nothing can beat the low-latency response and the super-smooth, arcade-style refresh that's synonymous with 60FPS gameplay.

'id Software's take on HD remastering doesn't make a whole lot of sense on PC - this is designed with console in mind and from a tech perspective, it's an impressive achievement in many ways.'

Alternative versions of this video are available:

While the console versions provide an almost identical picture, there are some bonus goodies on the PC version to enjoy over and above support for higher resolutions. First up, anti-aliasing - up to 4x multi-sampling - can be employed to smooth off the edges which tidies up the image no end (although the original 2004 game supported up to 16x on our PC). Secondly, a new motion blur effect - sneaked in by John Carmack himself just before the game shipped - is one of the finest implementations we've seen. Both camera and object-based, cranking it up to the full 32x sampling produces some truly excellent results.

On console, id has had to make some compromises in order to achieve that 60Hz target. Indeed, they're the same cutbacks employed in Rage, which ran at the same frame-rate. To maintain that silky-smooth update, every single frame needs to be generated in under 16.67ms, but the reality is that there are so many variables in rendering any given scene that sometimes the engine inevitably runs over budget. When this happens, the framebuffer is flipped as the screen is refreshing, resulting in torn frames.

At this point, id's internal auto-balancing code kicks in at full effect. According to Carmack, Doom 3 is a game with multiple light passes that hammers the GPU far more than Rage ever did, but regardless, the same dynamic performance optimisations are carried out here - screen resolution lowers on the fly in order to reduce GPU load until rendering times slip back beneath the 16.67ms threshold. At that point, full 720p resolution is restored.

Similar to Rage, it's the Xbox 360 that commands the advantage here, an aspect hinted at by Carmack himself. Dynamic resolution scaling is employed less often and there are fewer torn frames, giving the 360 game a more polished appearance in many scenes. The question is to what extent the performance auto-balancer is successful: 60 frames per second gameplay is the premium in this game and dropping frames not only impacts the look of the game, but more importantly the feel of it too.

Doom 3: BFG Edition - performance analysis

Eight years on, you may think that running a 2004 vintage PC game at 60Hz on a PlayStation 3 or Xbox 360 would be a piece of cake, but Doom 3: BFG Edition demonstrates fairly well that it is indeed more challenging than you might think. It's worth remembering that the original game was something of a performance hog in its day - it could run reasonably enough on a GeForce 6600 GT, but you'd be hard-pressed to get 60FPS on a 6800 Ultra at a decent resolution, and as far as ultra level settings go (which required a gargantuan - for the time - 500MB of texture memory), you could forget it.

Carmack on Doom 3: BFG Edition

At QuakeCon 2012, John Carmack took to the stage to deliver his traditional keynote - a vast 216-minute presentation delivered without notes, where one of the smartest, most talented developers in the games business simply speaks his mind about id software's current projects.

Here's what Carmack had to say about Doom 3: BFG Edition in particular:

'We decided with the way our internal resources were sitting at the time that we really should do this ourselves because we should be the best people to do it and we knew that if we put it out to another company we'd wind up with a 30 frames per second game, because if we look at the history of consoles, we had Quake 4 - which was a Tech4-based engine and it really struggled to hold 30 frames per second on the 360.

'But we know a whole lot more about the platforms now, we got all the experience we got now going through Rage and we figured - well, this should be a slam dunk - and before I started the project I had some vague thought that maybe I'll be able to do the full 60 frames per second stereoscopic, but it turned out it's only just barely possible to get to 60 frames per second at all on the consoles.

'You wouldn't think it but Doom 3 is actually a lot more aggressive in terms of GPU utilisation than Rage is. Rage pretty much manages to do everything in one pass, or one pre-pass and one regular pass, while Doom 3 adds it all up per light on there. Most of the Doom 3 levels are considerably more taxing on the systems than Rage is and we winded up even taxing out the PC in some cases. If you wind up running multi-mon, 2.5K resolution on there you can suck up pretty much all the power that any GPU combination will throw at you, which probably means that in some ways it's probably not as good of a use of the power as what we're doing now, but it does have all the trade-offs.

'And looking back at the game... it's interesting when I go back a long ways back to earlier games, like when I look back at the original Doom or Quake running in the original modes... like 'my god, these bathroom tile-size pixels' and 320x240 resolution and this looks... horrible! Doom 3 - especially when you run it in higher resolutions - still looks pretty good - when we showed it at E3 we had several people comment that. We're not pretending it's a triple-A top of the line title ready to go head-to-head with the very latest releases but one step down, the old game still shows pretty well there. And if you do run it on PC at a much higher resolution or even on the console, where the game was designed for 640x480 pretty much and when you wind up running it at 720p or 1080p with anti-aliasing and then in stereo, it adds quite a bit to it - so I'm pretty pleased with how all that turned out.'

Doom 3 Bfg Vs Original

It's also worth bearing in mind that the core rendering hardware within the current-gen consoles is only a year or two more modern than the original game itself, suggesting that a simple PC port probably wouldn't be good enough - exactly as John Carmack suggests in his 2012 QuakeCon keynote. In fact, we can ascertain that for sure by looking at Quake 4 - an Xbox 360 launch game running on the same idTech 4 engine. It's safe to say that the general performance level is immensely variable at best, very disappointing at worst.

Clearly, Doom 3: BFG Edition is an enormous improvement. For the most part, both console versions do indeed run at the prescribed 60 frames per second, with all the bonuses in smooth gameplay and low-latency controller response that this tends to bring with it. However, while the performance auto-balancer tends to produce exactly the kind of results you'd want on Xbox 360, there are many isolated areas where the PS3 suffers in comparison, with screen-tear, judder and frame-rate drops manifesting more prominently. This wouldn't be a problem if it were limited just to the engine-driven cut-scenes, but unfortunately the most noticeable examples of this are during gameplay.

Xbox 360 isn't perfect but it acquits itself fairly well while PS3 clearly struggles in certain areas, the silky smooth feel of the combat compromised when the engine is under load. For those with stereo 3D displays, the importance of frame-rate to the feel of the gameplay is easily demonstrated - switch to the HDMI 1.4 modes supported on both Xbox 360 and PlayStation 3 and frame-rate is cut down to 30FPS. While the 3D effect is reasonably effective, the introduction of judder and the dulled precision in the control systems makes it a bit of a disappointment. It's safe to say that if 3D is your bag, the PC version is by far and away the best bet - and it's pretty decent in 2D too.

While it's safe to say that we're not fully convinced by the BFG Edition on PC in terms of the basic proposition, performance shouldn't be an issue on any modern computer - not only is eight-year-old code being run on modern hardware, but we're also seeing the benefits of multi-core aware optimisation developed for idTech 5 being redeployed on the older game. The £300 Digital Foundry PC runs the game beautifully at either of our test resolutions (HD ready 1366x768 or full HD 1920x1080) with additional rendering features in play (MSAA and motion blur) and we still got a lovely 60FPS presentation with just minor frame-rate drops (exaggerated somewhat in the tests owing to our strict adherence to v-sync).

As an aside, we thought it would be fun to check out the on-disc versions of Doom 1 and its successor. The Xbox 360 versions are basically the exact same code previously released onto Xbox Live Arcade, while the PS3 games are all-new products - interesting in that id says that it essentially injected the old code into its established idTech 5 underpinnings and went from there. The key difference here is that the Xbox 360 ports are carried out by an external developer, whereas PS3 benefits from the attention of the original developer, and that does seem to make a difference.

Aside from differences in menu systems and presentation, the games look like a close match, though the id-created PS3 versions command a couple of advantages. Firstly, joypad rumble is implemented on the Sony platform, but not on the Xbox 360. Secondly, there's a question of gameplay. As you can see from the screenshots below, Doom and Doom 2 both top out with a 35FPS frame-rate - quite why, we don't know but it's the same on PC, for those interested, the difference being that v-sync is not natively supported as it is on console. Performing a simple 'spin around on the spot' test reveals that the 360 versions of these titles appear to have more visible judder and while we've not carried out any input lag tests, the PS3 game simply seems to feel more responsive generally.

On top of this, there's a bizarre issue where installing the BFG Edition onto the Xbox 360 hard drive actively disables Doom and Doom 2 when run from the game's initial menu - according to Bethesda, they need to be run from the 'My Games' area of the 360's dashboard.

Doom 3: BFG Edition - the Digital Foundry verdict

'It's id's dogged, admirable insistence on 60 frames per second gameplay that elevates the experience and makes it so much more worthwhile - and that's where we find our point of differentiation between the two console releases.'

Doom 3 Vs Doom 3 Bfg

It's a strange state of affairs where the version that is demonstrably the best of the three is also the most difficult to recommend, but that's exactly the situation we find ourselves in with Doom 3: BFG Edition. PC has additional rendering features over console, it has improved stereo 3D support and is the first title to support next-gen VR via the Oculus Rift. However, the changes don't best suit the platform, there are launch day bugs in need of patching, and the lack of mod support (which may be addressed now that Carmack has confirmed that the BFG Edition will be open sourced) is a disappointment.

Clearly, this is a product aimed at introducing Doom 3 to a new console audience, and in this respect the BFG Edition is a much more appealing proposition: the changes to the artwork and lighting make a lot more sense when viewed on an HDTV and the joypad implementation works well, producing gameplay that often echoes Rage in terms of pacing and response. Other changes to the gameplay are a mixed bag though: the lack of checkpoints is a real pain, but the controversial switch to allow the player to carry both flashlight and gun simultaneously works well - though it is a bit strange that the light doesn't produce any shadows.

However, it's id's dogged, admirable insistence on 60 frames per second gameplay that elevates the experience and makes it so much more worthwhile - and that's where we find our point of differentiation between the two console releases. While image quality is mostly identical between the two platforms, it's the Xbox 360 that more closely adheres to the target frame-rate, and thus becomes the most logical choice for those lucky enough to own both current-gen consoles.

Credits and distribution permission

• Other user's assetsAll the assets in this file belong to the author, or are from free-to-use modder's resources
• Upload permissionYou can upload this file to other sites but you must credit me as the creator of the file
• Modification permissionYou must get permission from me before you are allowed to modify my files to improve it
• Conversion permissionYou are not allowed to convert this file to work on other games under any circumstances
• Asset use permissionYou are allowed to use the assets in this file without permission as long as you credit me
• Asset use permission in mods/files that are being soldYou are not allowed to use assets from this file in any mods/files that are being sold, for money, on Steam Workshop or other platforms
• Asset use permission in mods/files that earn donation pointsYou must get permission to earn Donation Points for your mods if they use my assets

Author notes

This author has not provided any additional notes regarding file permissions

File credits

This author has not credited anyone else in this file

Donation Points system

This mod is not opted-in to receive Donation Points

• Version 1.1.12.13

  • _______________________________________
  • 1 June 2019 - Classic RBDOOM-3-BFG 1.1.12.13
  • _______________________________
  • WARNING: The game dll support is nearly complete but
  • there are still bugs while using them.
  • [classicdoom]
  • - crosshair hit frame will last for 2/3 of a second
  • - Improved episodic handling in EXPINFO/MAPINFO
  • - EXINFO improvements and bugfixes
  • - Added 'interpic' and 'endmode' in EXINFO's episode definition
  • - Fixed memory leaks with non-midi music
  • - Added loading lumps directly to physical memory
  • [DOOM3BFG]
  • - Added support for 4 controllers on windows and sdl 2.0
  • - Extended audio file maximum size when decoding

• Version 1.1.12.12

  • WARNING: The game dll support is nearly complete but
  • there are still bugs while using them.
  • [classicdoom]
  • - Added Crosshair with hit detection on Classic Doom
  • - Stabilize Z-memory
  • [DOOM3BFG]
  • - Moved Controller layout option to the controls settings
  • - Fix issue with player model field of view (I hope)
  • - Slight rework of soft shadow LOD CVar
  • - Fixed Compiler issues with gcc 8

• Version 1.1.12.11

  • _______________________________________
  • 14 April 2019 - Classic RBDOOM-3-BFG 1.1.12.11
  • _______________________________
  • WARNING: The game dll support is nearly complete but
  • there are still bugs while using them.
  • [classicdoom]
  • - Added option to enable music Reverb
  • - ActMap can now execute console commands
  • - idmus can now run from the console
  • [DOOM3BFG]
  • - game.dll will now be able to get as import
  • classic Doom globals object
  • (also updated the game api version from 9 to 10)
  • - Added support for Visual Studio 2019

• Version 1.1.12.10

  • _______________________________________
  • 30 March 2019 - Classic RBDOOM-3-BFG 1.1.12.10
  • _______________________________
  • WARNING: The game dll support is nearly complete but
  • there are still bugs while using them.
  • [classicdoom]
  • - Added jumping and a new map script ActMap
  • - Further fixes and improvements for EXPINFO/MAPINFO
  • - Spelling fix for one of the Master Levels ending
  • - Added new command line '-exportMaster' which
  • 'extract' the MASTERLEVELS.wad in order
  • to be use in other ports (mostly ZDoom and derivates)
  • - Improved OpenAL's 3D Audio
  • [DOOM3BFG]
  • - Updated game.dll cmake script and linux and
  • vs2017 cmake scripts will
  • return a log file with the cmake's output

• Version 1.1.12.9

  • [classicdoom]
  • - Fixed loading animated Flats from custom wads
  • - Further fixes and improvments for EXPINFO/MAPINFO
  • - When in 2d perspective the player will flip when moving backwards
  • [DOOM3BFG]
  • - Updated Open Platform
  • - When in 2d perspective the player will flip when moving backwards
  • - Added support for non-ASCII characters in filepaths on windows
  • - Linux makefile will create an executable instead of a shared library

• Version 1.1.12.8.5

  • WARNING: The game dll support is nearly complete but
  • there are still bugs while using them.
  • [classicdoom]
  • - All games will pause if the open platform overlay is open
  • - Fixed a bug where weapons are incorrectly shown in status bar after loading a save file
  • - Added new CVar 'cl_pitch' that allow you to change standard sound pitch
  • [DOOM3BFG]
  • - Updated Open Platform
  • - All games will pause if the open platform overlay is open
  • - Added achievement progress notification
  • - PDA will not be triggered if the player press shift+tab

• Version 1.1.12.8

  • _______________________________________
  • 09 February 2019 - Classic RBDOOM-3-BFG 1.1.12.8
  • _______________________________
  • WARNING: The game dll support is nearly complete but
  • there are still bugs while using them.
  • [classicdoom]
  • - Minus-Plus buttons will show/hide the status bar
  • - Fixed a small bug when showing the weapon in use on status bar with the super shotgun
  • [DOOM3BFG]
  • - Added support for Open Platform*
  • - Allow controller sticks to be remapped for 2d perspective oriented controls
  • [Launcher]
  • - Added linux compatibility (requires Mono runtime)
  • *Open Platform Project : https://github.com/MadDeCoDeR/Open_Platform

• Version 1.1.12.5

  • _______________________________________
  • 27 January 2019 - Classic RBDOOM-3-BFG 1.1.12.5
  • _______________________________
  • WARNING: The game dll support is nearly complete but
  • there are still bugs while using them.
  • [classicdoom]
  • - Added ThirdPerson view
  • - Show which weapon slot is in use on Status Bar
  • - Added MAPINFO support for DOOM I
  • [DOOM3BFG]
  • - Fixed GOG Language Bug

• Version 1.1.12.3

  • _______________________________________
  • 12 January 2019 - Classic RBDOOM-3-BFG 1.1.12.3
  • _______________________________
  • WARNING: The game dll support is nearly complete but
  • there are still bugs while using them.
  • [classicdoom]
  • - Added Freelook
  • - Added Option to disable Ramdomized pitches on Doom sfx's
  • [DOOM3BFG]
  • - Fixed Linux Support (again)
  • - Add support for game dll on Linux
  • - Further improvments on game dll

• Version 1.1.12

  • _______________________________________
  • 27 December 2018 - Classic RBDOOM-3-BFG 1.1.12
  • _______________________________
  • WARNING: While using dll don't try to use PDA videos or PDA inventory and don't try to do
  • multiple load games in a single playthrou.The game dll support is nearly complete but
  • there are still bugs while using them.
  • [classicdoom]
  • - Optimized DeHeckeD Text editor
  • - Doom sfx will use the file's sample rate instead of the default (11025 MHz)
  • [DOOM3BFG]
  • - Added Support for game dll files on both 32 and 64-bit executables

• Version 1.1.10.10

  • _______________________________________
    17 September 2018 - Classic RBDOOM-3-BFG 1.1.10.10
    _______________________________
    [classicdoom]
    - Reorganized graphical options
    - Added Option to toggle Always Run
    - Bugfixes and Optimizations
    - Fixed Doom 2 Map 15's inaccessible secret
    - Added Map exclusive fixes to EXPINFO
    [DOOM3BFG]
    - Fixed a double flashlight model bug when using the original flashlight
    - reduced bluish tint for FilmicPostProcess (special thanks to TheVoodoo)

• Version 1.1.10.9

  • _______________________________________
    07 September 2018 - Classic RBDOOM-3-BFG 1.1.10.9
    _______________________________
    [classicdoom]
    - Added the PWADs on the source code files
    - Added option to change the lighting (Real Light)
    - Added JPEG support for Doom graphics (Doom GFX)
    - Added the missing Palette colors for image conversions
    [DOOM3BFG]
    - Fixed compilation issues with newer versions of Visual Studio 2017
    - Improved linux cmake scripts

• Version 1.1.10.5

  • _______________________________________
    03 July 2018 - Classic RBDOOM-3-BFG 1.1.10.5
    _______________________________
    [classicdoom]
    - Added PNG support for doom graphics (doom Gfx)
    - Improved the stability of Classic Doom's z-memory (I hope)
    - Optimize and improve the mod exclusivity system
    [DOOM3BFG]
    - Fixed controller vibration system for SDL*
    *it should work with any compatible controller, for example a PS3 Controller

• Version 1.1.10

  • ______________________________________
    31 May 2018 - Classic RBDOOM-3-BFG 1.1.10
    _______________________________
    [classicdoom]
    - Restored Linux support
    - Fixes and improvments for aspect ratio correction
    - Removed slime trails (by using MBF's source code)
    - Fixed an issue with backpack obtained from cheats
    - Added support for sprites inside compress files (.pk3,.zip)
    [DOOM3BFG]
    - Restored Linux support
    - Updated OpenAL library and added support for ogg,flac,mp3 and bink audio formats(On all 3 games)