Week 40:<\/strong><\/p>\n\n\n\n Last week I completed\na scene that can be used as an environment for the interaction we will have to\nimplement. This week I made a simple UI menu for the Unity Application:<\/p>\n\n\n\n\n https:\/\/i.gyazo.com\/54fdb30a54109ff212006bf0180fb23f.mp4<\/a><\/p>\n\n\n\n The menu has 3 options: \u201cPlay\u201d, \u201cInformation\u201d and \u201cQuit\u201d. Where the\n\u201cPlay\u201d button will take the player into the scene I did last week. The\n\u201cInformation\u201d button will display some simple information. Lastly, the \u201cQuit\u201d\nbutton will simply quit the application. Even though the menu doesn\u2019t have that\nmuch features as of yet, one could always add these in the future if needed.<\/p>\n\n\n\n For next week, I will start the development of an interaction that can\nbe implemented into the scene. Possibly also do some research on some of the\nissues I found in the previous weeks. All while waiting on the gloves to be\ncompleted, so that I can start with the interface between Arduino and Unity;\nSomething I already tinkered with in week 38.<\/p>\n\n\n\n Week 39:<\/strong><\/p>\n\n\n\n After\nhaving connected the Arduino and Unity application together in week 38. I figured I could start on the creation of a scene (terrain, models,\nobjects, etc.) within Unity. In this case, removing the scene I did in week 37 so that I could start on something\nfresh. Where I decided to use free low poly packs from the Unity store, combining this<\/a> and this<\/a> pack. Which ultimately gave the terrain a decent look: <\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n This scene will be able to serve as the environment for\nwhere we can implement the interaction. E.g. by having the interaction in the\nmiddle (where the pink cube is located). Furthermore, I will also add a soundtrack to this scene. Something\nthat can be looped in the background. <\/p>\n\n\n\n In addition to this, I have started the development of an UI menu that can be implemented into the Unity application as a main menu. <\/p>\n\n\n\n Petter<\/strong>:<\/strong> <\/p>\n\n\n\n Previously I was using mostly Unitys predefined components to create the physics and movements of the cube. Now this works all right, but because we are using a virtual interface, our control of the cube, or the lack off, makes it very difficult to make the cube return to a cube after turning. <\/p>\n\n\n\n We could introduce stabilization of the xyz axises if the cubes are not aligned to 0, 90, 180 and so on, but this returns us to the previous problem, calibration, even if this does work, it would not be optimal, sometimes you want to hold the cube 45 degrees in the air to see three sides right? There are of course ways to achieve this as well, but what I\u2019m learning as I\u2019m trying out different solutions is that all these problems are caused because I jumped straight into full fledged joint based physics, which as I\u2019m also learning seems to create more problems than it\u2019s worth right now. So, I went back to the basics to ensure our cube functions like it should, coding it from the ground up. It\u2019s going well but there are many options to consider. <\/p>\n\n\n\n![\"\"](\"http:\/\/dronesonen.usn.no\/wp-content\/uploads\/2019\/10\/Example-daniel-1024x549.png\")
![\"\"](\"http:\/\/dronesonen.usn.no\/wp-content\/uploads\/2019\/10\/Example-daniel2-1024x620.jpg\")
![\"\"](\"http:\/\/dronesonen.usn.no\/wp-content\/uploads\/2019\/10\/Uml-william-1024x720.png\")
<\/figure>\n","protected":false},"excerpt":{"rendered":"