<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Aaron Meehan on Medium]]></title>
        <description><![CDATA[Stories by Aaron Meehan on Medium]]></description>
        <link>https://medium.com/@aaronmkainos?source=rss-2a66cd6c63ba------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*kAQLDHHUhRSQfnWAL_BUBQ.png</url>
            <title>Stories by Aaron Meehan on Medium</title>
            <link>https://medium.com/@aaronmkainos?source=rss-2a66cd6c63ba------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 01:03:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@aaronmkainos/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Making GearVR Development Less Painful With Vive]]></title>
            <link>https://medium.com/@aaronmkainos/making-gearvr-development-less-painful-with-vive-de3028d1b895?source=rss-2a66cd6c63ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/de3028d1b895</guid>
            <category><![CDATA[unity]]></category>
            <category><![CDATA[htc-vive]]></category>
            <category><![CDATA[samsung-gear-vr]]></category>
            <category><![CDATA[vr]]></category>
            <category><![CDATA[virtual-reality]]></category>
            <dc:creator><![CDATA[Aaron Meehan]]></dc:creator>
            <pubDate>Tue, 25 Jul 2017 09:29:48 GMT</pubDate>
            <atom:updated>2017-07-25T09:29:48.165Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>This is blog was originally written in late 2016 but was never published — much has changed since then (we’ve been doing no GearVR development since) but I believe the content is still relevant and useful so I thought I’d publish it now and maybe it’ll help you out! The code is available <a href="https://github.com/KainosSoftwareLtd/ViveForGearVR">here</a>.</blockquote><h3>Making GearVR Development Less Painful With Vive</h3><p>In the Applied Innovation team at <a href="https://www.kainos.com/">Kainos</a> we’re always looking for promising new tech to experiment with — things that other companies perhaps aren’t looking at or aren’t taking seriously. For a while now one of our main focus points has been non-games VR — it’s got amazing possibilities and it’s still early days. We’re still in the ‘wild west’ era of VR development; there are lots of <a href="https://en.wikipedia.org/wiki/Virtual_Boy">mistakes</a> to learn from and <a href="http://www.wareable.com/ar/magic-leap-need-to-know-release-date-price-specs-features">exciting projects</a> being worked on and we don’t really know the best ways to approach many <a href="http://www.middlevr.com/resources/the-challenges-of-creating-a-vr-application/">development challenges</a> yet.</p><p>We’ve been experimenting quite a bit with the GearVR recently. Mobile VR solves a lot of issues that we have with using something like a Vive or Rift as a demoing platform; it’s light, easy to transport and doesn’t require a powerful PC. It’s inferior in many ways of course, one of the most notable being a lack of positional tracking; but that doesn’t matter when the alternative is carrying a desktop or chunky laptop around with you, not to mention the other kit needed for the desktop headsets as well.</p><p>Development for the GearVR is pretty straightforward if you’re familiar with Unity, however you’ll quickly run into a problem — testing changes inside the headset is a massive pain. Building and deploying to the Android device can take up to a few minutes and you then have to insert it into the GearVR which can be awkward (you get good at it quickly, but it’s still an additional step and I’ve sent my phone flying plenty of times). You can use developer mode for some things of course; but with VR I find you need to actually put the headset on to get a feel for most changes.</p><p>To me, this stood in stark contrast to developing for the HTC Vive, trying out changes for the Vive is just a matter of hitting the run button in Unity and sticking the headset to your face; it’s very quick and doesn’t interrupt your development at all. Another great aspect of Vive development is that you can move things around and tweak properties and settings while the application is running in Unity. This is really nice for VR where the user experience can be completely ruined if something doesn’t feel right — you can check lots of different positioning combinations and other variables while the app is in play, then save the best values and apply them. Being able to do this sort of thing reduces development time considerably and it’s something that you cannot do with the GearVR. But wouldn’t it be nice if you could?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/0*mt2KprSU8dHtfiyX." /></figure><p>We found, as it turns out, that you can; and it’s not all that difficult to do! When we were thinking about using the Vive for GearVR development, we came up with a few things we would need to do first;</p><ol><li>Restrict the Vive movement to GearVRs tracking capabilities.</li><li>Come up with a way to quickly switch out Vive specific GameObjects for GearVR specific GameObjects.</li><li>Emulate the GearVR input via the Vive controller.</li></ol><p>Quickly switching platform specific GameObjects was easy to do, it’s just a matter of importing them all into Unity as normal then enabling the ones you need and disabling the ones you don’t — we made a script for this.</p><p>The Vive of course has full freedom of movement — it can track you as you move around a room, whereas the GearVR only tracks rotation in place, so we needed to restrict it. We did this with some simple maths — just displacing the Vive camera so that the player is always in the same position. Finally we used Microsoft’s <a href="https://msdn.microsoft.com/en-us/library/windows/desktop/ms645533(v=vs.85).aspx">mouse input</a> functions (through <a href="https://inputsimulator.codeplex.com/">this library</a>) to simulate mouse presses as well as the mouse position when using the trigger and touchpad on the Vive controller, this was convenient because the GearVR touchpad is mapped directly to normal mouse left clicks and movement so we could just code all our inputs with the mouse as normal, no messing around with different inputs for the Vive.</p><p>If you think this sounds useful, the code we used is available on our <a href="https://github.com/KainosSoftwareLtd/ViveForGearVR">Github</a> - but you’ll need a few things set up first. If you’re not already developing for GearVR in Unity, I highly recommend following the <a href="https://developer3.oculus.com/documentation/mobilesdk/latest/concepts/mobile-game-engine/#mobile-unity">setup guide on oculus.com</a>, make sure you have the Android and Java SDK installed and located in Unity preferences. If you follow the setup guide you’ll end up with an OVR folder in your Unity assets folder, that’s all you need for the GearVR side of things but you’ll also need to get the <a href="https://www.assetstore.unity3d.com/en/#!/content/32647">SteamVR plugin</a> from the Unity store. I’m not going to write an entire tutorial on Vive and GearVR development, but you do need to know the basics of both (and Unity obviously) so I recommend a read through the <a href="https://developer3.oculus.com/documentation/mobilesdk/latest/">Oculus documentation</a>. The SteamVR <a href="https://developer.valvesoftware.com/wiki/SteamVR">documentation</a> isn’t great but it’s fairly easy to figure out the basics from looking at the prefabs and scripts included in the SteamVR plugin.</p><p>Now you have the API’s set up, you can download the Unity assets for the Vive to GearVR project (via <a href="https://github.com/KainosSoftwareLtd/ViveForGearVR">Github</a>). Unzip the folder and copy everything into the assets folder of your Unity project. In the prefabs folder you’ll see an object called <em>‘HMDPositionAndPlatformSwitch’</em>, this is used to position the GearVR and Vive player cameras, and acts as a reference point to keep the Vive restricted to this position. It also contains the script to switch between the Vive and GearVR modes. Place this wherever you want in the scene.</p><p>You’ll want to have player objects for the GearVR and Vive as well, the SteamVR CameraRig prefab is perfect for use as a player object, for the GearVR you can simply use a plain old Unity camera — you could use the <em>‘OVRPlayerController’</em> prefab found in the OVR folder however remember that it has a collider attached by default which may cause issues (personally I found it was interfering with walls in a small scene, since I didn’t need the collider or any of the other functionality of the <em>‘OVRPlayerController’</em> I just used a basic camera instead).</p><p>Next, drag the <em>‘HMDPositionAndPlatformSwitch’</em> prefab into the scene. You’ll notice two arrays in the script attached to the <em>‘HMDPositionAndPlatformSwitch’</em> prefab, these are fairly self explanatory — just drag any Vive specific objects into the ‘<em>Htc Vive Objects</em>’ array and drag any GearVR specific objects into the ‘<em>Gear Vr Objects</em>’ array; makes sense, right? For Vive this will include the ‘<em>[SteamVR]</em>’ object and your Vive player object whereas I only have my player camera for the GearVR. Now you can switch the relevant objects on and off using the <em>‘Platform’</em> drop down in the <em>‘HMDPositionAndPlatformSwitch’</em> object, remember to switch this to Vive when running in Unity and GearVR when building for GearVR.</p><p>Now we’re almost done; just drag the <em>‘ViveMovementRestrictor’</em> script onto your Vive player object and drag the Camera object for your player onto the Player Camera slot in the ‘<em>Vive Movement Restrictor</em>’ script (this is Camera (eye) in the Vive CameraRig prefab if you’re using that for your Vive camera). Now drag the <em>‘HMDPositionAndPlatformSwitch’</em> object into the ‘<em>Camera Position Obj</em>’ field in ‘<em>Vive Movement Restrictor</em>’ script. This script does what it says on the tin — it prevents the Vive from moving, only allowing rotation similar to the GearVR.</p><p>Finally attach the <em>‘ViveToGearVRInputs’</em> script on the player object for the Vive and attach both Vive controllers to it. The ViveToGearVR inputs script uses the Vive controllers’ trigger to emulate a mouse click (left mouse button or mouse 0 in Unity) and the touchpad to control the position of the mouse. Note that when running the game in a window in Unity the mouse position tracking will be off, you can use the fullscreen option for better mouse tracking with the touchpad. You may also want to pay attention to where your mouse cursor is; if you click the play button in Unity and then click the trigger on the Vive controller (without moving the cursor) it’s going to stop the application…seems obvious but it might confuse you the first few times!</p><p>Developing apps and experiences for VR right now is an interesting challenge, and it’s one that requires a lot of trial and error before you start to get things right. It can be a pain to go through this process when developing for the GearVR with it’s build time and time spent trying to get your phone into the HMD, but hopefully our attempt at using the Vive as a quick testing platform will be helpful to those of you lucky enough to have a Vive available. Thanks for reading and if you have any questions don’t hesitate to drop us an email at <a href="/service/mailto:rnd.developer@kainos.com">rnd.developer@kainos.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de3028d1b895" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Highlights from VR World Congress]]></title>
            <link>https://medium.com/@aaronmkainos/highlights-from-vr-world-congress-b109acc6e6b2?source=rss-2a66cd6c63ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/b109acc6e6b2</guid>
            <category><![CDATA[virtual-reality]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[htc-vive]]></category>
            <category><![CDATA[vr]]></category>
            <category><![CDATA[oculus-rift]]></category>
            <dc:creator><![CDATA[Aaron Meehan]]></dc:creator>
            <pubDate>Wed, 03 May 2017 12:29:22 GMT</pubDate>
            <atom:updated>2017-05-03T12:34:06.337Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LVervjmy005yosHo2ARXJw.jpeg" /></figure><p>A couple of weeks ago I attended VR World Congress in Bristol, it was a great event with lots of interesting speakers and exhibitors, so I thought I’d put together a (hopefully) short blog on my favourite points over the three days of the event. There were over a hundred speakers at VRWC this year, so rather than mention them all I’m just going to go over a few of the points that were most interesting or insightful to me. These are in no particular order, but I feel like they’re all relevant — so let’s get to it!</p><p>There were lots of interesting talks on the first day but I thought the VR market review (2016–17) by Carl Hibbert was pretty insightful. It may not have been particularly surprising (for the most part), but it’s always useful to better know the area in which you’re working — in numbers rather than just feeling.</p><p>The talk made concrete a few assumptions that I had taken for granted, for example; that games dominate current VR spending (at $35m), and that 360 video content was far behind ($&lt;5m, including ads). Carl suggested that video needs better platforms especially when it comes to monetising as features are really lacking. He made it clear that he felt that video would catch up to games over the next few years if these improvements were made; I’m sceptical (although that scepticism is strongly influenced by my own preference for ‘full 3D’ VR content) but it will be an interesting space to watch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iZJjuGwwm_9ILxhflHilbA.png" /><figcaption>We need to push our way up the slope of enlightenment!</figcaption></figure><p>It’s hard to see sometimes when you’re working on VR projects and talking to people in VR, but it’s also always good to be reminded that VR is only just getting its legs and it’s still not quite a sure thing. Games are probably the biggest consumer market for VR and yet VR still accounts for less than one percent of games spending. Of course I don’t want to be all doom and gloom, VR is growing fast; it’s just not invincible!</p><p>Some summarised stats from the talk:</p><ul><li>Total headsets sold (excluding cardboard): 5 million</li><li>Games spending: $35 million</li><li>Less than $5 million spent on video (including ads)</li><li>2% of broadband subscriptions have a headset</li><li>&lt;1% of total games spending is on VR games</li><li>Headsets relative installed user-base sizes: GearVR &gt; PSVR &gt; Cardboard &gt; Rift &gt; Vive &gt; Daydream</li></ul><p>By far the most exciting talk for me on the second day was <a href="http://presence-thoughts.blogspot.co.uk/">Mel Slater</a>’s talk on virtual bodies and how they affect our perceptions and behaviours. Mel is an old hand when it comes to VR, having been involved in VR research since the 90’s. The premise of his talk was around the effects of substituting a person’s real body with a virtual one in first person perspective, that moves corresponding with their own movements — thus leading to a sense of ownership over the virtual body.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7iRBWo6NOmK96R7qodtteA.jpeg" /></figure><p>He presented a number of interesting findings from studies that suggest to me that VR is going to be a great productivity tool; but more importantly that VR will have a huge impact on the effectiveness of mental health therapy. He research showed that VR will play a big role in helping us to understand our own biases and how social situations work. One study used a VR representation of a participant’s body and had them describe an issue they were having to a ‘Freud’ character. The participant then switched body to act as ‘Freud’ and listened to themselves from the other perspective; it seems like fancy ‘<a href="https://en.wikipedia.org/wiki/Rubber_duck_debugging">rubber ducking</a>’, but the results were rather impressive. This technique was presented as a way of solving personal problems but I could see something similar being a very useful productivity tool when trying to work through difficult technical problems, or trying to spur creativity and judge your work or decisions from different perspectives.</p><p>As a big fan of ‘Ghost In The Shell’ (and having just seen the new film the day before), I was pretty excited to hear Sol Rogers talk about his experience developing the new GitS tie-in VR game, which was built in a very short window of time on a limited budget.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FkCFyE4NnJzM%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DkCFyE4NnJzM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FkCFyE4NnJzM%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c88531992dc20af8dc521d97a24b1463/href">https://medium.com/media/c88531992dc20af8dc521d97a24b1463/href</a></iframe><p>As I had just recently come off project ‘retne’, which had a similarly tight timeline — it was really interesting to see the trade-offs that his team made and where they differed from ours. Sol and his team went for a linear experience with only a minor level of interactivity which drastically reduced the development time and simplified many aspects. To make up for the lack of interactivity they made use of their resources in <a href="https://en.wikipedia.org/wiki/Motion_capture">mo-cap</a> and graphics to make sure the game looked great (and did an amazing job of mimicking the new movie’s aesthetic).</p><p>From a technical perspective, the highlight of the final day was the talk and panel on <a href="https://webvr.rocks/">WebVR</a> presented by Mr. Bozorgzadeh and a number of experts. They really pushed WebVR and made a great case for it spurring on the uptake of VR by lowering barriers. It makes sense; the faster you can get into a VR app the more likely you are to try it, the idea of the <a href="https://en.wikipedia.org/wiki/Metaverse">‘metaverse’</a> is alluring, and really — app stores are a pain in the ass. I think that there will always be use for native builds and as a PC gamer who loves to tinker with mods and squeeze maximum performance out of my machine I don’t think they’ll ever go away.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*VsxjDTER-CdUu7QHSAzz9g.gif" /><figcaption>You can check out some cool WebVR experiments at <a href="https://www.webvrexperiments.com/">https://www.webvrexperiments.com/</a></figcaption></figure><p>This is a different use case however and an elegant solution to making VR more convenient! From a technical perspective it looks like it’s come a long way in terms of performance, but it seems a little bit immature just yet. Support is making it’s way into the stable Chrome and Firefox builds but it’s not there right now, and it seems (from an outside perspective) like the API is rapidly changing. I’m excited, but I think it’ll take the full support of the browsers and major game engines like Unity and Unreal before WebVR really takes off. I think this will happen sooner or later (<a href="https://unity3d.com/unity/roadmap">it’s in the Unity roadmap as an in-progress development</a>) — watch this space!</p><p>Listening to Tom Nelson of the Royal Opera House describe their challenges in filming ballet and other performances for VR was great. Tom walked us through each approach they took and the difficulties they had in filming from an audio perspective as well as a video capture perspective. I was pleasantly surprised to find out how vigilant they are when it comes to new tech, not only with VR but AR as well; they showed off their prototype Hololens application, used for planning stage layouts and lighting. Tom described a number of use cases for the Hololens app including multi-user planning to help with choreography as well as life-size walkthroughs of planned stages in AR.</p><p>VR World Congress was a great experience; I’d highly recommend it if the event next year manages to attract such a great line-up of speakers and exhibitors. The general take away this year seemed to be; VR is still exciting and there’s lots to learn and lot going on — but I also felt like there was a little bit of trepidation in the air, VR is out in the world now; it’s not invincible and we need to work to make it work!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b109acc6e6b2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Project retne: What’s different for VR design?]]></title>
            <link>https://medium.com/@aaronmkainos/project-retne-whats-different-for-vr-design-b7c7c1e291df?source=rss-2a66cd6c63ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7c7c1e291df</guid>
            <category><![CDATA[vr]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[htc-vive]]></category>
            <category><![CDATA[virtual-reality]]></category>
            <dc:creator><![CDATA[Aaron Meehan]]></dc:creator>
            <pubDate>Thu, 20 Apr 2017 14:10:19 GMT</pubDate>
            <atom:updated>2017-04-20T14:10:19.359Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>This post is the second part of a series on project retne written by engineers <a href="https://twitter.com/KainosSoftware">@</a>K<a href="https://twitter.com/KainosSoftware">ainosSoftware</a>, you can find an earlier blog by <a href="https://medium.com/u/472054ef2bcf">Liam Ferris</a> <a href="https://medium.com/@liamkferris/prototyping-in-vr-4-things-ive-learned-f1d7e979d2ec">here</a> . At SXSW this year we launched “<a href="http://vrni.org.uk/">retne</a>”, a VR experience built for the HTC Vive. Retne is an immersive adventure produced by artist <a href="https://twitter.com/deepamann_kler">@deepamann_kler</a>.</blockquote><p>From roughly the middle of December 2016 to the middle of March 2017 the Applied Innovation team at Kainos worked on project retne which acted as a VR showcase for Northern Ireland at SxSW in Austin, Texas, in March. Although we’ve completed many small projects and prototypes ‘retne’ was the first big VR project undertaken by the team at Kainos. It’s also the most complete, and the project that’s had the most exposure to users and experts outside of Kainos — so it has been a great opportunity for us to expand our knowledge when it comes to VR design.</p><h3>Use your hands!</h3><p>So, what’s different for VR design? There are many elements to consider, one of the most immediate and the one I personally find most impactful is the level of tactility offered by VR that you can’t get with traditional interfaces. Doing stuff with your hands in VR feels very natural, and we observed with retne that once users realised that they could interact with things through touch they often immediately tried to touch everything in their vicinity!</p><p>It feels very disappointing then, and really takes away from the user’s experience if they’ve been set the expectation that they can do things with their hands, and yet when they try to touch and interact with other objects; nothing happens! This was doubly true for AI characters — it feels very strange to get no reaction when touching or poking a character after establishing a rapport in VR. When we saw the lack of interactivity in retne, we tried to somewhat remedy the issue by adding a sandbox table in the introductory scene with lots of fun touchable interactive objects — we then found that if people started playing with the table they often didn’t want to leave!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x84kYmqjtnVWAAcWk-YLdg.png" /><figcaption>The table in all its’ touchy glory</figcaption></figure><p>The table was a fun addition, and it was great to play with; realistically we didn’t have time for more coverage of the interactive elements considering our tight timeline. We didn’t have enough of this touch driven ‘juiciness’ in retne; if we were to be given more time to work on it, one of the highest priority tasks for me would be to go through every scene and make as many objects as possible react to your touch in some way, I feel that this would add an awful lot to the overall experience.</p><p>These interactions don’t have to be hugely complex, I think a good approach is to have little micro-interactions for anything you can touch; they don’t need to do a whole lot, just make it clear that you’ve affected them. This kind of approach would make the VR world feel much more tangible and alive, leading to improved immersion by making the player feel like a physical part of the world (see — Job Simulator).</p><p>As an alternative, for an approach that is probably a bit less work; you can make it very clear, through visual differentiation that objects with a certain ‘tell’ are interactive; done well this should remove some of that disappointment since the user won’t expect to be able to interact with other objects, (though I do feel that you lose a lot with this approach).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cATT2oW7dp0LVmIjCO4Geg.png" /><figcaption>The ‘correct’ letters glow</figcaption></figure><h3>Motion Sickness</h3><p>Motion sickness is an issue that many VR projects have to deal with at some point and retne was no exception. From what I’ve seen when working on multiple VR projects, I’m fairly sure that susceptibility to motion sickness is a bell curve. That is, I think there are relatively few people for whom motion sickness is triggered very easily, and a relative few that never seem to get motion sick in VR, with the majority of people being somewhere in the middle. I have no numbers to back this up — it just matches what I’ve seen in playtesting quite well.</p><p>Because of this variance, I think it’s important to decide early on whether you’re ok with excluding some people on this basis. I think there are lots of experiences that have great potential in VR, but would cause some people to get motion sick; in the end you need to have a set expectation of who your target audience is, build your game for that group and play-test regularly with them to ensure your project is going to work. This will determine how free or limited you can be with elements such as movement of the scenery and player. With retne we wanted an experience open to everyone and so we had to cut some features during development. At one point we had a ‘Mario Galaxy’-esque planet that the user could walk around, personally I very much liked the sense of space from this feature; but as some people reported motion sickness we had to replace it with a stationary planet surface — you must be prepared to work around issues like this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ajk9d-hpPIir_Jhlmr7vfw.png" /><figcaption>The asteroid in question</figcaption></figure><h3>Chaperone</h3><p>The next point is one that should really have been obvious but that we didn’t actually pick up on until close to the end of our development on retne; pay attention to how the chaperone relates to the actual physical room. In our case for example the player progresses through the game by means of a series of portal doors that the player can walk through. With most of the scenes in retne, in order to frame the portals well, we elected to position them on the outer portions of the chaperone; which looked really good and we could ensure that players would almost always be looking in the right direction when a portal appeared.</p><p>However, there’s an obvious issue with this; people generally aren’t keen on walking through a virtual portal and into a very real wall! Of course, we left plenty of room for the player to walk through — they were never in any real danger of walking into the wall; but because of their proximity to the outer edges of the chaperone, most (almost all first time players) were very hesitant when walking through the portals.</p><p>This is something that is going to have to be figured out for each individual project, in our case we felt that the edges were far enough away but obviously we were wrong; pay attention and if people are hesitant in play-testing ask why. Often it’s the common fear of walking around with the headset strapped to your face, very common in newer players with a lack of trust in the system — but it could also be that you’ve placed things too close to real walls. In the case that you can control the play area (for example when giving demos) simply making sure the edges of the chaperone are a good distance away from the actual walls can alleviate this; but it’s still a design issue and this is just a band-aid — I feel that when designing your project to work with a certain chaperone size it should feel good even if the chaperone is exactly along the walls of the room.</p><h3>Intensity</h3><p>The next few points follow a similar pattern to some of the others in that they’re really just a reflection of the fact that most experiences are more impactful in VR, and how to take that into account. A major point on the intensity scale is the issue of moving objects getting too close to your face. This is another one of those issues that is really going to be down to the kind of experience you’re going for; you can get a pretty powerful reaction by making things move towards a person’s face at speed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RDxZDQXyQ12nZZ6dre4EcQ.png" /><figcaption>Some of the evil butterflies — thankfully this screenshot was after their downsizing</figcaption></figure><p>We found this out at the cost of one spilled coffee during retne development; essentially the butterflies moved a little too close to you (through you at times) and their insectoid bodies were much larger earlier in development. Combine the creepy bodies with them accelerating straight through your head and you have the stuff of nightmares; definitely not what you want if you’re going for a relaxed experience!</p><p>Similarly, if you’ve ever played a VR game with a large character, you know how intimidating it can be. Early on in retne we had the issue that Lil’ Mo wasn’t quite little enough; some of the early feedback was that he was a bit scary. Mo still wasn’t particularly big back then, the difference between him feeling like a friendly companion and a somewhat imposing tour guide was a scale change of fairly small magnitude.</p><h3>Performance</h3><p>Before I conclude I feel that I should address another huge issue that isn’t necessarily a design point, but is closely related; performance. It’s well known that a good VR experience requires a constantly high frame rate. Without this crucial element motion sickness and general unpleasantness is rife. During the development of retne we additionally found that fps fluctuations are especially noticeable in VR; at one time we were averaging ~145 fps, which obviously felt great! At a particular sequence during play however fps dropped to ~125; this is still a very high frame rate to be hitting but even so; the 20 fps drop was very noticeable and felt terrible to players. I highly recommend finding the lowest frame rate your VR application reaches on recommended hardware and capping a little below that to avoid big drops like this.</p><p>So there we have it; don’t scare players with walls, let them use their hands a lot, try not to make them sick, and be careful with throwing things at their face (and other potentially intense experiences). We had a lot of fun working on retne and learned a lot; hopefully some of the realisations we had will help you out in your own VR development journey!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FnTIv5fM87hI%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DnTIv5fM87hI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FnTIv5fM87hI%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/1c7bdb4e88bdd6e6c7407b33280cb9ca/href">https://medium.com/media/1c7bdb4e88bdd6e6c7407b33280cb9ca/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7c7c1e291df" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>