Linked by Thom Holwerda on Mon 10th Sep 2007 20:24 UTC, submitted by hechacker1
Permalink for comment 270062
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
More News »
Sponsored Links



Member since:
2005-07-06
Trying to figure out what goes wrong and where between your rendering code and the end result on the screen can be quite difficult at times.
For instance it's not unheard of for a machine to BSOD randomly with some development versions of games, just because of a specific usage pattern of the 3d api that expose a latent bug in the driver - and you have no easy way of figuring it out since the drivers are essentially a black box.
I know that some kind of catastrophic event will have to happen for the gaming industry to start doing any significant amount of linux development, but things like this can help turn it into a more comfortable platform to develop games for than windows.
Edited 2007-09-10 22:41