Yulio Jump for Revit: AR Guidelines

This article will walk you through guidelines when preparing to render AR assets for VR using Yulio Jump for Revit. 

AR Object Scale:   

While you can create AR objects as small as a pin and as large as an entire building, generally AR is best suited for showcasing objects to be looked at (within the client’s real-world context), as opposed to being looked in.  

For example, if you wanted to show how a utility shed would look positioned in a client’s yard, AR would be ideal. If you wanted to show the interior details of the shed, VR would be the better option. 

Physically large AR objects can become difficult to position when using a phone or tablet, so we generally recommend keeping the AR footprint below about 100 square feet, or 35′ x 35′ x 35′ feet in volume.

AR Object Complexity:  

The complexity, and therefore realism, of your AR object is ultimately limited by the phone, tablet or headset on which it is to be viewed.  Rendering mixed reality in real time is very hardware intensive, so even high-end smartphones will struggle to display overly complex AR objects at a reasonable frame rate. 

The best approach when tagging Revit elements for AR treatment is to start with objects that are as simple as possible with respect to geometry / poly-count and textures, and to then add complexity after confirming desired viewing performance. Yulio will automatically convert Revit’s internal object representation into industry standard AR format (USDZ / glTF), so it is easy to quickly iterate to find the best trade-off between realism and performance.  The system limits the output AR objects to a maximum of 75MB, so if you receive a warning that your selection has exceeded this limit, try reducing the geometric complexity, removing unnecessary or hidden detail, and / or reducing the size and number of textures for best results.

Check out this sample project to try AR out for yourself: https://vr.yulio.com/rYKw6wcegp