Why did John Carmack leave id Software last November? The statements issued at the time suggested that Carmack simply wanted to concentrate on his new role as CTO of virtual reality firm Oculus. But the truth, as it turns out, is a little more complicated than that.
According to a USA Today story spotted by The Verge, Carmack wanted ZeniMax, id Software's parent firm, to partner with Oculus so that Wolfenstein: The New Order and Doom 4 would support Oculus' VR headset. ZeniMax, however, wasn't interested. From the USA Today piece:
[If the deal had gone through,] Carmack would not have left id in November and would have continued working at both companies. "I would have been content probably staying there working with the people and technology that I know and the work we were doing," he says.
"But they couldn't come together on that which made me really sad. It was just unfortunate," Carmack says. "When it became clear that I wasn't going to have the opportunity to do any work on VR while at id software, I decided to not renew my contract."
As we reported last year, Carmack hoped to remain close to id as a "technical advisor"—but according to him, "it just didn't work out." In the same tweet, Carmack added, "Probably for the best, as the divided focus was challenging."
|1. Hdfisise - $600||2. Ryszard - $503||3. punkUser - $502|
|4. the - $306||5. SomeOtherGeek - $300||6. Ryu Connor - $250|
|7. doubtful500 - $200||8. Anonymous Gerbil - $150||9. webkido13 - $135|
|10. cygnus1 - $126|
|The TR Podcast 175: the Zen of chipmaking and ARM's Cortex-A72 revealed||4|
|Elon Musk lays out vision for a battery-powered future||103|
|Inside ARM's Cortex-A72 microarchitecture||34|
|Asus' 144Hz MG279Q monitor may top out at 90Hz with FreeSync||56|
|Deal of the week: A Bay Trail netbook for $161, free case fans, and more||18|
|DirectX 12 Multiadapter shares work between discrete, integrated GPUs||96|
|Gigabyte's 9-series motherboards are Broadwell-ready||45|
|The TR Podcast will be live on Twitch shortly!||3|
|AMD delays FreeSync support for multi-GPU systems||40|