10-05-2018, 10:37 PM
How Serious Sam set itself apart in the era of Duke Nukem and Quake
<div style="margin: 5px 5% 10px 5%;"><img src="http://www.sickgaming.net/blog/wp-content/uploads/2018/10/how-serious-sam-set-itself-apart-in-the-era-of-duke-nukem-and-quake.jpg" width="200" height="200" title="" alt="" /></div><div><blockquote><p><strong><em>“</em>To gain what we want to achieve in the game, that’s huge environments and a huge number of enemies, we had to deliver something that wasn’t actually seen anywhere.“</strong></p></blockquote>
<p><em>-Croteam CTO Davor Hunski explores </em>Serious Sam’<em>s need for </em><em>large</em><em> environmental scope.</em></p>
<p>In an interview for <a href="https://arstechnica.com/gaming/2018/10/war-stories-serious-sam-almost-didnt-happen-until-crates-saved-the-day/">Ars Technica’s War Stories series</a>, Croteam’s chief creative officer Davor Hunski tells the story of how Serious Sam’s hand-made engine came to be and how a vertical slice demo ultimately saved the game.</p>
<p>Hunski explains how the early Serious Sam development team set their sights on a first-person shooter game and, lacking the funds to use a big-name engine, set out to create their own 2D Wolfenstein-like engine.</p>
<p>However, as technology continued to evolve throughout the project’s development, games like Duke Nukem and Quake came out and offered features that made the team’s 2D engine something that was no longer viable.</p>
<p>Instead, Hunski explains that they aimed to stand out from the crowd by creating an engine that could handle 10 times the on-screen enemies and projectiles that other games of the time featured. </p>
<p>“So, we invented this caching ahead system, where one projectile or moving object would actually cache [maybe] three or four seconds ahead, everything that it could collide and until nothing changed during those three, four seconds, it wouldn’t have to test again against an environment for collision,” says Hunski.</p>
<p>“To speed up the collision, we were not able to use real geometry of cubes for collision. But we approximated them with several spheres,” he explains. “On the one side, it sped up immensely our collision tests, because actually a test with a cube is a really, really easy one. And the second gain that we got is that we could have multidirectional gravities so characters would be able to walk on ceilings, inside the spheres, so we had several types of gravity and we actually put that into the game as secret places locations, and that was really, really awesome.”</p>
<p>Hunksi’s full explanation of that early engine tech and how a lone positive review of a vertical slice demo can be found in the <a href="https://www.youtube.com/watch?v=kXh1JJ_Jtew">full video</a> just above.</p>
</div>
<div style="margin: 5px 5% 10px 5%;"><img src="http://www.sickgaming.net/blog/wp-content/uploads/2018/10/how-serious-sam-set-itself-apart-in-the-era-of-duke-nukem-and-quake.jpg" width="200" height="200" title="" alt="" /></div><div><blockquote><p><strong><em>“</em>To gain what we want to achieve in the game, that’s huge environments and a huge number of enemies, we had to deliver something that wasn’t actually seen anywhere.“</strong></p></blockquote>
<p><em>-Croteam CTO Davor Hunski explores </em>Serious Sam’<em>s need for </em><em>large</em><em> environmental scope.</em></p>
<p>In an interview for <a href="https://arstechnica.com/gaming/2018/10/war-stories-serious-sam-almost-didnt-happen-until-crates-saved-the-day/">Ars Technica’s War Stories series</a>, Croteam’s chief creative officer Davor Hunski tells the story of how Serious Sam’s hand-made engine came to be and how a vertical slice demo ultimately saved the game.</p>
<p>Hunski explains how the early Serious Sam development team set their sights on a first-person shooter game and, lacking the funds to use a big-name engine, set out to create their own 2D Wolfenstein-like engine.</p>
<p>However, as technology continued to evolve throughout the project’s development, games like Duke Nukem and Quake came out and offered features that made the team’s 2D engine something that was no longer viable.</p>
<p>Instead, Hunski explains that they aimed to stand out from the crowd by creating an engine that could handle 10 times the on-screen enemies and projectiles that other games of the time featured. </p>
<p>“So, we invented this caching ahead system, where one projectile or moving object would actually cache [maybe] three or four seconds ahead, everything that it could collide and until nothing changed during those three, four seconds, it wouldn’t have to test again against an environment for collision,” says Hunski.</p>
<p>“To speed up the collision, we were not able to use real geometry of cubes for collision. But we approximated them with several spheres,” he explains. “On the one side, it sped up immensely our collision tests, because actually a test with a cube is a really, really easy one. And the second gain that we got is that we could have multidirectional gravities so characters would be able to walk on ceilings, inside the spheres, so we had several types of gravity and we actually put that into the game as secret places locations, and that was really, really awesome.”</p>
<p>Hunksi’s full explanation of that early engine tech and how a lone positive review of a vertical slice demo can be found in the <a href="https://www.youtube.com/watch?v=kXh1JJ_Jtew">full video</a> just above.</p>
</div>