id On RAGE "Cluster!@#$" and Lead Platforms [Oct 07, 2011, 9:33 pm ET] – Share – Viewing Comments
Kotaku asks the musical question "Why Was The PC Launch of Rage Such A "Cluster!@#$"?," getting answers from id on the topic, who express frustration with problems that were largely caused by driver issues. Along the way they also address how the game being designed for consoles holds back the PC edition. "You can choose to design a game around the specs of a high-end PC and make console versions that fail to hit the design point, or design around the specs of the consoles and have a high-end PC provide incremental quality improvements," John Carmack tells them. "We chose the latter." He also bluntly addresses why this makes sense for id (emphasis Kotaku's):
"We do not see the PC as the leading platform for games," Carmack added. "That statement will enrage some people, but it is hard to characterize it otherwise; both console versions will have larger audiences than the PC version. A high end PC is nearly 10 times as powerful as a console, and we could unquestionably provide a better experience if we chose that as our design point and we were able to expend the same amount of resources on it. Nowadays most of the quality of a game comes from the development effort put into it, not the technology it runs on. A game built with a tenth the resources on a platform 10 times as powerful would be an inferior product in almost all cases."
Had they contacted NVIDIA and ATI 6 months ago, I wonder if these problems would be here now.
Knowing how closely Carmack has worked with GPU vendors in years past, I would be extremely surprised if either nVidia or ATI had not been informed several months prior about driver issues affecting Rage. My guess is that nVidia and ATI had plenty of advance but were slow to deliver fixes, and id was forced to decide whether Rage should be released on schedule - hoping that driver updates would be available by launch date.
All of the above is pure speculation, but I know Carmack has mentioned working closely with both vendors in the past to address driver issues.
Date
Subject
Author
Copyright © 1996-2022 Stephen Heaslip. All rights reserved.
All trademarks are properties of their respective owners.
Privacy Policy. Manage Cookie Settings.
News CGI copyright © 1999-2022 James "furn" Furness & Blue's News. All rights reserved.
Chatbear v1.5.0/blue++: Page generated 24 September 2022, 22:16.