Black Triangles

> It wasn’t just that we’d managed to get a triangle onto the screen. That could be done in about a day. It was the journey the triangle had taken to get up on the screen. If anyone wants to experience something like that today, just follow an introductory tutorial on Vulkan programming. Vulkan is a programming model that gives so much low-level control directly to programmers. As a result, this "Hello Triangle" example became (in)famous for its need to…

>It had passed through our new modeling tools, through two different intermediate converter programs, had been loaded up as a complete database, and been rendered through a fairly complex scene hierarchy, fully textured and lit (though there were no lights, so the triangle came out looking black). The black triangle demonstrated that the foundation was finally complete the core of a fairly complex system was completed, and we were now ready to put it to work doing cool stuff. Wow…

This is a fascinating article, and it's been submitted and discussed many times in the past. Of course, all those discussions are now closed, so if there's anything new to say, this will be the place. Here are some of the previous submissions: Black Triangles 131 points 9 months ago 28 comments (http://rampantgames.com/blog/?p=7745) Black Triangles 2 points 10 months ago 0 comments (http://rampantgames.com/blog/?p=7745#) Black Triangles 3 points 10 months ago 0 comments (http://rampantgames.com/blog/?p=7745) The…

I like this story because a lot of times when you're doing something correctly, there are "black triangles" in the beginning. People tend to want to skip the "black triangles" by using frameworks and other things that give the appearance of quick progress, but I've found they often create long-term slowdowns.