![\"gokotta_bocetos_v01\"](\"http:\/\/ludumdare.com\/compo\/wp-content\/uploads\/2016\/01\/gokotta_bocetos_v01.jpg\")
<\/a>![\"gokotta_bocetos_v02\"](\"http:\/\/ludumdare.com\/compo\/wp-content\/uploads\/2016\/01\/gokotta_bocetos_v02.jpg\")
<\/a>![\"gokotta_bocetos_v03\"](\"http:\/\/ludumdare.com\/compo\/wp-content\/uploads\/2016\/01\/gokotta_bocetos_v03.jpg\")
<\/a>![\"gokotta_ref_01\"](\"http:\/\/ludumdare.com\/compo\/wp-content\/uploads\/2016\/01\/gokotta_ref_01.jpg\")
<\/a><\/p>\nOnce we had the main ideas and sketches clear, we did a layout, so that the \u201ccoders\u201d could have something to work in as soon as posible, and the \u201cartists\u201d could finish modelling.<\/p>\n
While the layout was being done, we started with the PJ. It was important thtat this one was the first \u201cfinal model\u201d to be done, so that the animator could start rigging, while the rest kept on modelling props and scenario.<\/p>\n Lightmapping and Ambient Occlusion textures done, as well, and then, to UE4!!<\/p>\n Once modelling was finished, we did the UVs and then gave them to the RIG department.<\/p>\n Rigging and Skinning finished, so our animator could start as soon as possible.<\/p>\n Meanwhile, all objects were modelled and UVs were done, so that UE4 lightmapping worked perfectly and optimized for HML5.<\/p>\n When every UVs was ready, we started rendering all lightmaps and shadows. Then, we treated them in Photoshop and passed each texture to each material.<\/p>\n We wanted some variety in the suitcases, so we did 3 different textures. It\u2019s a pity, but we couldn\u2019t use them in the end Once every model and map was done, we put toghether everything in UE4, replacing the initial layout.<\/p>\n In order to optimize and make it work smooth in HTML5, every light was \u201cCooked\u201d and the used the least amount of opacities we could. We also used simple materials, as well. Almost all lighting work is pre-rendered.<\/p>\n To achieve the \u2018growing\u2019 effect, we used morphers, so that we can make it \u201cgrow\u201d as he swallowed.<\/p>\n \u00a0<\/p>\n Meanwhile\u2026 in the \u201ccoding\u201d department\u2026<\/strong><\/p>\n After the \u201cinitial joke\u201d (two simultaneous themes), we took a while to think how we could structure this game, and more important. What did we need?<\/p>\n We decided to use \u201cBlueprints\u201d, because in this game we didn\u2019t need extremely complex coding, and results with these are just great, they\u2019re easy to do and intuitive. This is a very basic scheme. Each scanner \u201creads\u201d an internal value the suitcases going through have. A boleean (Radiactive? True: scanners change material to \u201cGreen\u201d, False: Leave the suitcase alone!)<\/p>\n Each scanner have three colliders. \u201cIn\u201d, changing the suitcase material in case Plutonium is \u201ctrue\u201d. \u201cOut\u201d turns the material back to normal in case it changed previously (and the player couldn\u2019t grab the suitcase on time), and \u201cfeeding tube\u201d collider, which \u201cgathers\u201d every suitcase the player decide to pick.<\/p>\n There is also a \u201cBoxTraceForObjects\u201d collider that \u201csucks\u201d every suitcase inside it when the player push the button.<\/p>\n Each suitcase is a \u201cdummie blueprint\u201d, containing only a boolean value, mesh with its materials, a thruster, activated only when \u201csucked\u201d, and some internal values, as speed and direction.<\/p>\n<\/a><\/p>\n<\/a><\/a><\/a><\/a><\/p>\n<\/a><\/p>\n<\/a><\/a><\/p>\n<\/a><\/a><\/p>\n<\/a><\/p>\n<\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/a><\/a><\/a><\/p>\n<\/a><\/a><\/p>\n\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n