#DUKE NUKEM FOREVER DEVELOPMENT TIME DRIVERS#

#DUKE NUKEM FOREVER DEVELOPMENT TIME DRIVERS#

Nvidia didn’t include any SLI profile for this game in their latest drivers and due to that, only one of our cores was being used.

This clearly shows optimization issues that can only be overcome by your PC’s raw power. We should also note that there were some scenes where our Q9650 wasn’t stressed and our GPU was not used to its fullest. Still, this dualcore system managed to maintain 60fps with maxed out settings at 1080p. When we tried to simulate a dualcore system, we witnessed a small performance hit. Our first core was used to its fullest, and the remaining cores were used around 30-50%. Truth be told, there are some gains (4-5fps) but as we can see, Duke Nukem Forever didn’t take full advantage of our Q9650. During its development peak, the best PC CPUs available were dualcores, so it’s only natural to see minimal gains when using a quadcore. However, we have to keep in mind that the game was in development for a very long time. Since the game was developed primarily for the PC, we’d expect it to take full advantage of our hardware. We’ve also used the latest WHQL drivers and Windows 7 64Bit. As always, we used an overclocked Q9650 (4.2Ghz) with 4GB DDR2 and an Nvidia GTX295 GPU. With Piranha Games’ help, the company polished, ported the PC version to consoles and added the multiplayer mode.

Gearbox Software then stepped in and acquired the game’s rights.

After its closure, Triptych Games decided to continue the game’s development and due to their hard work, the PC version of DNF was almost finished. 3D Realms developed the PC version with an enhanced Unreal engine and was shut down, about two years ago. For those that don’t, here is how the story goes more or less. Most of you pretty much know what happened with Duke Nukem Forever so we won’t discuss extensively its development cycle.

Duke nukem forever development time